Hello everyone, a few days ago i posted a question regarding the proximity sensor staying on all the time, even with every gesture option turned off. After trying several stock ROMs and a couple of different S4, all of them have the same issue. I have to note tho that with every ROM previous to MG5, the sensor stays on all the time, and when using the MG5 India ROM the sensor is off, except while using the stock browser, when it turns on after a few minutes, or after making a phonecall the sensor stays on and it only turns off restarting the phone.
This is seriously very weird. I have had many phones, and i've never seen anything like this. Just in case, i want to remark that every single gesture option, auto screen brightness and eye scroll and all those functions were disabled. Every single one. I even thought it could be i had a faulty phone, but i tried two more and they do exactly the same. Has anyone noticed this using a custom ROM? It's easier to see using another's phone camera.
hernanmcarg said:
Hello everyone, a few days ago i posted a question regarding the proximity sensor staying on all the time, even with every gesture option turned off. After trying several stock ROMs and a couple of different S4, all of them have the same issue. I have to note tho that with every ROM previous to MG5, the sensor stays on all the time, and when using the MG5 India ROM the sensor is off, except while using the stock browser, when it turns on after a few minutes, or after making a phonecall the sensor stays on and it only turns off restarting the phone.
This is seriously very weird. I have had many phones, and i've never seen anything like this. Just in case, i want to remark that every single gesture option, auto screen brightness and eye scroll and all those functions were disabled. Every single one. I even thought it could be i had a faulty phone, but i tried two more and they do exactly the same. Has anyone noticed this using a custom ROM? It's easier to see using another's phone camera.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2402121
Sent from my LG-E980 using xda premium
samomamo said:
http://forum.xda-developers.com/showthread.php?t=2402121
Sent from my LG-E980 using xda premium
Click to expand...
Click to collapse
Samomamo thanks a lot for your reply, but if you read what i said and what says in that post, we're talking about completely different things. In that post the guy had a problem with the sensor not working. I never said it didn't work, it works perfectly, it just stays on (aka, you can see a dim red light coming from it) but it works without any problems. Besides, he ended up having a defective phone, and like I said above, i tried 3 phones, from different companies, one of them brand new, and all of them had the same behaviour so I think i can safely discard a hardware problem (unless all three phones were defective, which is unlikely to happen).
Still, thanks for your reply!!:good:
hernanmcarg said:
Hello everyone, a few days ago i posted a question regarding the proximity sensor staying on all the time, even with every gesture option turned off. After trying several stock ROMs and a couple of different S4, all of them have the same issue. I have to note tho that with every ROM previous to ......
Click to expand...
Click to collapse
This is very strange, I also have stock browser as my primary browser running mg5 but I don't see the proximity sensor light going up (even in darkness). I do web browsing and reading for hours. Is this how you see your proximity sensor light showing slight red? I am still figuring out what you said and will confirm my own findings later today. Will update.
Sent from my GT-I9500 using xda premium
---------- Post added at 12:06 PM ---------- Previous post was at 11:45 AM ----------
_______________________________
Alright. Here are my own findings.
Stock MG5 i9500.
First of all, you are right. The proximity sensor does light up when everything is turned off. Literally Smart feature and even smart pause is turned off. So the proximity sensor shouldn't be turned on in the first place. Now that this is clear, Here is what I've found so far.
Bug present in stock browser, not in chrome. The way it turns on the proximity sensor is that as soon as you type any URL in the address bar and press enter, the sensor gets turned on and stays like that unless and until:
-You pull down the notification bar
OR
-Press home button and run the browser again (notice that the browser is still in RAM so we aren't restarting the app).
Then (assuming you have the website already open). You can browse all you want within the website pressing links and what not. But as soon as you use the address bar again, the sensor wakes up again. This is seriously strange and definitely a bug from the software end and not the hardware end.
LAMESUNG is prolly too busy releasing note3 and Galaxy Godzilla 20". So we don't know when will we see the fix for this. Let's hope on the 4.3 update after a couple months.
@ Everyone trying custom Roms and kernals.
Please confirm this if you experience this same issue.
Sent from my GT-I9500 using xda premium
Plasmastate thank you for testing it. My phone does exactly the same thing you described. One more thing. Look at the sensor through a digital camera or another's phone camera and you'll see it's always on although you can't see it with your bare eyes. The most weird thing is my brother has an iphone 5 and it has the same issue after recent software updates. This is well catalogued in apple forums. Strange huh?
plasmastate said:
This is very strange, I also have stock browser as my primary browser running mg5 but I don't see the proximity sensor light going up (even in darkness). I do web browsing and reading for hours. Is this how you see your proximity sensor light showing slight red? I am still figuring out what you said and will confirm my own findings later today. Will update.
Sent from my GT-I9500 using xda premium
---------- Post added at 12:06 PM ---------- Previous post was at 11:45 AM ----------
_______________________________
Alright. Here are my own findings.
Stock MG5 i9500.
First of all, you are right. The proximity sensor does light up when everything is turned off. Literally Smart feature and even smart pause is turned off. So the proximity sensor shouldn't be turned on in the first place. Now that this is clear, Here is what I've found so far.
Bug present in stock browser, not in chrome. The way it turns on the proximity sensor is that as soon as you type any URL in the address bar and press enter, the sensor gets turned on and stays like that unless and until:
-You pull down the notification bar
OR
-Press home button and run the browser again (notice that the browser is still in RAM so we aren't restarting the app).
Then (assuming you have the website already open). You can browse all you want within the website pressing links and what not. But as soon as you use the address bar again, the sensor wakes up again. This is seriously strange and definitely a bug from the software end and not the hardware end.
LAMESUNG is prolly too busy releasing note3 and Galaxy Godzilla 20". So we don't know when will we see the fix for this. Let's hope on the 4.3 update after a couple months.
@ Everyone trying custom Roms and kernals.
Please confirm this if you experience this same issue.
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
i have none of those issues you guys mentioned.
+1 as above. Don`t have those issues either.
im4eversmart said:
i have none of those issues you guys mentioned.
Click to expand...
Click to collapse
Do you own a i9500 or the i9505 variant?
Sent from my GT-I9500 using xda premium
plasmastate said:
Do you own a i9500 or the i9505 variant?
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
I9500
Has anyone tried looking at the sensor using a digital camera like i said?
I just noticed you guys have custom kernels/roms, so obviously this is a stock rom bug. I should also add that the phone works flawlessly. There's no excessive battery consumption or lag or anything and the sensor works fine.
Don't have any issues with my device.
Sent from my GT-I9500 using xda premium
kof200440 said:
Don't have any issues with my device.
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
What ROM/Kernel do you have?
hernanmcarg said:
What ROM/Kernel do you have?
Click to expand...
Click to collapse
Stock Rom / Kernal ..
Sent from my GT-I9500 using XDA Premium 4 mobile app
Are the sensors working when you have a third-party launcher? I use Apex launcher and none of the sensors is working. Even when using the stock TW, some of the sensors are not working also.
Using the factory test mode, all sensors are working.
All sensor work fine. I tested another S4, it has the sensor on all the time aswell. This is seriously very weird
The problem seems to be dirt. I used one of those "webcam microscopes" to take some pictures of the sensors and frant facing camnera. It appears that some units have a sealing problem on these components and they may get pretty dirty.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The front facing camera can get pretty disgusting.
I didnt have time to open it up and clean yet, but I will post the results as soon as I do.
I confirm that the problem comes from dust. Some people has said that it can be solved using a can of compressed air in the earphone in order to blow dust away.
I have done the solution of the can of compressed air two months ago and I have solve it. I haven't that problem since that time.
Enviado desde mi GT-I9505 mediante Tapatalk
I am on 4.3, Russian Update. Today, after installing Cm 11 the proximity bug was no more there. So I don't think compressed can air will do any good. Have tried all means possible to reports this to Samsung but it seems Samsung bluntly does not want to hear any of it customers complaints as they are busy with Galaxy s5. below is a screen of the proximity bug before I flashed cm11
Related
This thread is for any talk related to the Google Play Edition HTC One. If you have any questions on how to convert use the forum linked below.
How to convert: http://forum.xda-developers.com/showthread.php?t=2358781
The Google Play edition phones automatically receive updates of the latest Android software. Optimized for the latest apps, more storage for your content and a fast, clean user experience all come standard.
Click to expand...
Click to collapse
Related:
Android 4.4 update delivered to Google: http://gigaom.com/2013/11/18/htc-one-kitkat-update-ready-delivered-to-google/
Mines fine
What app could we download to see if the readings are correct? Mine is fine.
Sent from my HTC One using xda app-developers app
define "mine is fine"
because is common that the thing that uses more battery is the screen, but in android 4.3 is android system, but I think the battery is not bad at all...
In the other hand:
- super smoth
- ir enable
- better bluetooth
- sixasis support
the only fault that I see in 4.3 GPE (beside the battery report) is the camera app, it is just not good =/
SLver said:
define "mine is fine"
because is common that the thing that uses more battery is the screen, but in android 4.3 is android system, but I think the battery is not bad at all...
In the other hand:
- super smoth
- ir enable
- better bluetooth
- sixasis support
the only fault that I see in 4.3 GPE (beside the battery report) is the camera app, it is just not good =/
Click to expand...
Click to collapse
My definition just means i can use it all day without the bigbdrain sense 5 was giving me. (4.1.2). I guess I'll look more into it since I just flashed yesterday. Also for camera, at least for me, it works fine. Of all the phones I've owned I've never messed with the settings (filters, iso, etc) just because I've never needed to. Plus I have a DSLR camera to do that . but that's me.
Sent from my HTC One using xda app-developers app
I am thrilled with the 4.3 update. I have had zero issues and battery life is very solid. My wife finally took the plunge from her iPhone 4 and I picked her up a ONE yesterday. While settings hers up, I realized how much better Stock Android is just due to the smoothness and simplicity of it. In my opinion, Sense 5 is still the best manufacturer experience to date but it's still too cumbersome compared to plain ole Stock Android
My battery life seems to be decent. I don't notice much difference than when I was on sense. I do notice the high android usage but as gunny said, I think it's being misread as it doesn't seem to be having a negative impact.
Also I know some have mentioned low signal. Again its just the way its reported because last night I had two bars and I was pulling speeds in the 20,30,40mbps range. Which I think they must have upgraded some towers because here in NYC with all the network congestion I usually pull 9-15mbps on average(depending on location)
Sent from my HTC One using Tapatalk 4
My only issue on 4.3 is a lower LTE signal. I am only getting 1 bar now, and I used to get 3-4. The battery is good, even with that weird bug.
Does GPE 4.3 still has the 3 dot menu button?
proximity sensor bug is back,
pulling phone away from my face doesn't turn the screen back on.
gunnyman said:
proximity sensor bug is back,
pulling phone away from my face doesn't turn the screen back on.
Click to expand...
Click to collapse
How often does this happen? I was on a call yesterday and I was testing the sensor and it was super sensitive I thought. I barely put my hand over it about 2 inches and it shut off the screen .
Sent from my HTC One using xda app-developers app
GrimStranger said:
Does GPE 4.3 still has the 3 dot menu button?
Click to expand...
Click to collapse
with stock kernal yes
How do you receive the new 4.3 update.
I have been trying "System Update" under "About" for days now, and there are no update from Google.
gunnyman said:
proximity sensor bug is back,
pulling phone away from my face doesn't turn the screen back on.
Click to expand...
Click to collapse
True, I still have this bug.
Sent from my HTC One using xda premium
monkeypaws said:
How often does this happen? I was on a call yesterday and I was testing the sensor and it was super sensitive I thought. I barely put my hand over it about 2 inches and it shut off the screen .
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
It seems random
Yeah, 4.3 is all sacked. LTE ping is slow as a turtle. 4.2.2 everything was snappy. ADB doesn't work, screen off proximity sensor, when phone is off the charge animation doesn't work when rooted. Its not the root process. My nexus 4 & 7 have stock ROM and supersu installed.. No problems. What has HTC done!? Back to 4.2.2 I go. This 4.3 blows.
Look at this junk! Wow.. Horrible Horrible update. 4.2.2 was at 20-30% system this is at 80%+!?!? Horrific.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my HTC One using Tapatalk 4
Don't hold back tell us how you really feel
gunnyman said:
It seems random
Click to expand...
Click to collapse
Regarding the proximity sensor bug, I briefly flirted with the complete Google Play edition conversion then decided to return to completely stock sense. I started blindly messing about with mids, cids , firmwares etc. I eventually managed to run RUU 1.28.401.7 successfully. :laugh:
I factory reset my device for good measure then proceeded to install every subsequent update and I am now on 2.24.401.1 and I factory reset my device after every update. Everything appeared good and I have set my device up again with what I would consider to be a very clean install of the stock sense rom.
......Then ring ring and there it is...the dreaded proximity sensor bug
How can this be??
bobsie41 said:
Regarding the proximity sensor bug, I briefly flirted with the complete Google Play edition conversion then decided to return to completely stock sense. I started blindly messing about with mids, cids , firmwares etc. I eventually managed to run RUU 1.28.401.7 successfully. :laugh:
I factory reset my device for good measure then proceeded to install every subsequent update and I am now on 2.24.401.1 and I factory reset my device after every update. Everything appeared good and I have set my device up again with what I would consider to be a very clean install of the stock sense rom.
......Then ring ring and there it is...the dreaded proximity sensor bug
How can this be??
Click to expand...
Click to collapse
My good buddy has the HTC One for AT&T. I rooted it for her and all was well. Next thing she finds out her proximity sensor borked. She called att and they went thru a process to see what the sensor was on.. The sensor should be at 50 and the reports came back that her sensor was at 0. Hearing more and more of this sensor bug, makes me think its more of a hardware fault. Its only a matter of time till the sensor completely flakes out and dies.
Sent from my HTC One using Tapatalk 2
luckylui said:
My good buddy has the HTC One for AT&T. I rooted it for her and all was well. Next thing she finds out her proximity sensor borked. She called att and they went thru a process to see what the sensor was on.. The sensor should be at 50 and the reports came back that her sensor was at 0. Hearing more and more of this sensor bug, makes me think its more of a hardware fault. Its only a matter of time till the sensor completely flakes out and dies.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Any idea how they found out what the sensor was at?
Hello.
How many of you have serious problems with n4? I mean random reboots/shutdowns or freezes etc. I heard about this kind of troubles but I want to know if it occurs to many people or is this single cases.
Greetings.
Wysłane z mojego GT-I9000 za pomocą Tapatalk 4
no problems here. im very happy with my nexus 4
Anything you've read about reboots etc is just false conjecture. History has shown through various outlets like XDA, Google+ etc that the Nexus 4 is rock solid and stable. So much so the Nexus 5, whatever it may be has to be SIGNIFICANTLY better in design and features before I even consider upgrading. Which I doubt I will because the N4 is just perfect for me.
simms22 said:
no problems here, on my n4. im very happy with my nexus 4
Click to expand...
Click to collapse
Same here.
Sent from my Nexus 7 using xda app-developers app
Nope perfect.
Sent from my Nexus 4 using xda app-developers app
Works fine as ever
Sent from my HTC One using XDA Premium 4 mobile app
Even with browsing, the temperature is usually above 50 C. Its was never like this on 4.2.2. Rest all is fine i guess
All stock.
Sent from my Nexus 4 using xda premium
I'm getting freezes, random reboots,overheating...
oblikas said:
I'm getting freezes, random reboots,overheating...
Click to expand...
Click to collapse
overheating.. and what is your cpu temp? or are you just saying overheating because it "feels" hot to you? overheating can be real, but its mostly imagined by the user.
---------- Post added at 06:49 PM ---------- Previous post was at 06:48 PM ----------
filthykid said:
Even with browsing, the temperature is usually above 50 C. Its was never like this on 4.2.2. Rest all is fine i guess
All stock.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
50C is normal.
simms22 said:
overheating.. and what is your cpu temp? or are you just saying overheating because it "feels" hot to you? overheating can be real, but its mostly imagined by the user.
---------- Post added at 06:49 PM ---------- Previous post was at 06:48 PM ----------
50C is normal.
Click to expand...
Click to collapse
55-60° on browsing + music..
Sent from my Nexus 4 using xda app-developers app
oblikas said:
55-60° on browsing + music..
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
thats normal. considering that its summer there where you are, and the air temperature is warm, thats very normal. the phone temperature while being used will average lower when its cooler there. the phones safety shutdown is at 100C cpu temp, so you are still quite a bit in the safe range.
No problems or over heating after about 10 months of heavy usage!
I can't understand why some people have so many problems with the Nexus 4, mine does no random reboot/lock now (last time I rebooted to install 4.3)...
I had a problem with over-night lockups (i was not the only one), so I disabled a lot of apps/widgets, and got many days without lockups. So I started turning everything back again, one by one. I had a suspect always in my mind: dashclock, I never turned it up again (it has so many plugins, including some made by me with Tasker). I can't tell for sure dashclock was the culprit it's an excellent app, and I ended giving up other apps too (I really didn't used them frequently ).
But I learned that apps can create random reboots... (the system should still handle this, but appears it does not).
So, I don't think anything is wrong with the hardware, since software can take a system down to.
The Nexus 4 is a great phone.
My only dislike is: now on 4.3, I have to use "hangouts" (no status?!) instead of talk (i may root to get talk back).
PS: I've disabled Hangouts, it is of no use to me.
muldy said:
I can't understand why some people have so many problems with the Nexus 4, mine does no random reboot/lock now (last time I rebooted to install 4.3)...
I had a problem with over-night lockups (i was not the only one), so I disabled a lot of apps/widgets, and got many days without lockups. So I started turning everything back again, one by one. I had a suspect always in my mind: dashclock, I never turned it up again (it has so many plugins, including some made by me with Tasker). I can't tell for sure dashclock was the culprit it's an excellent app, and I ended giving up other apps too (I really didn't used them frequently ).
But I learned that apps can create random reboots... (the system should still handle this, but appears it does not).
So, I don't think anything is wrong with the hardware, since software can take a system down to.
The Nexus 4 is a great phone.
My only dislike is: now on 4.3, I have to use "hangouts" (no status?!) instead of talk (i may root to get talk back).
PS: I've disabled Hangouts, it is of no use to me.
Click to expand...
Click to collapse
as you said, most of the "issues" are user set up. the heat issue is blown out of proportion by too many, when the issue is a non issue. they "feel" the heat more because of the glass back.
anyways, the great thing about root.. im using talk on 4.3
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
filthykid said:
Even with browsing, the temperature is usually above 50 C. Its was never like this on 4.2.2. Rest all is fine i guess
All stock.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
well flash a custom Kernel which will undervolt the phone and then use an app to underclock the GPU not the CPU. I get 30-35 max, 5-6 hours of battery (4.2.2 ) I tried the 4.3 and did not like how it works.
Loud pops and crackles on the first 4-5 seconds of video taken with the camera.
Poor 3G signal/reception performance from update to update. 4.1 bad, 4.2 good, 4.3 bad again.
styckx said:
Anything you've read about reboots etc is just false conjecture. History has shown through various outlets like XDA, Google+ etc that the Nexus 4 is rock solid and stable. So much so the Nexus 5, whatever it may be has to be SIGNIFICANTLY better in design and features before I even consider upgrading. Which I doubt I will because the N4 is just perfect for me.
Click to expand...
Click to collapse
conjecture?
Since the 4.3 upgrade my Nexus 4 is essentially a paper weight. First it just refused to go beyond the X screen. After a downgrade of the radio back to 4.2.2 version, I could start up. After that, the problems weren't over. My N4 locks the SIM at random, shuts down a couple of times every hour and refuses to restart without being plugged in. Even when fully charged.
Worse: reflashing an older factory img (I tried 4.2 and 4.2.2) does not resolve these issues. Nor does flashing AOKP. Which is just bizarre, because my N4 worked perfectly before the upgrade. How can an upgrade lead to hardware problems?
I'm not alone.(but I can't post outside links, apparently.) There's a support thread on the google groups forum 6 pages long.
Joenr76 said:
conjecture?
Since the 4.3 upgrade my Nexus 4 is essentially a paper weight. First it just refused to go beyond the X screen. After a downgrade of the radio back to 4.2.2 version, I could start up. After that, the problems weren't over. My N4 locks the SIM at random, shuts down a couple of times every hour and refuses to restart without being plugged in. Even when fully charged.
Worse: reflashing an older factory img (I tried 4.2 and 4.2.2) does not resolve these issues. Nor does flashing AOKP. Which is just bizarre, because my N4 worked perfectly before the upgrade. How can an upgrade lead to hardware problems?
I'm not alone.(but I can't post outside links, apparently.) There's a support thread on the google groups forum 6 pages long.
Click to expand...
Click to collapse
Are you wiping your partitions in fastboot before flashing the images? Sounds like an error somewhere is causing serious issues for you. It probably stemmed from a bad download and has yet to be corrected. I would wipe EVERYTHING and start with a clean slate. Re-download the images and verify the md5.
KSLevel11 said:
Hello.
How many of you have serious problems with n4? I mean random reboots/shutdowns or freezes etc. I heard about this kind of troubles but I want to know if it occurs to many people or is this single cases.
Click to expand...
Click to collapse
I've had random re-boots, shut downs and freezes up to and exceeding 10 times a day, during phone calls.... youtube, web browser. you name it. there is no disparity.
it's random. . . it doesn't care when it wants to re-boot. - i've had this problem since the day i received my nexus 4 on January 2nd 2013
It doesn't matter if it's running stock android. rooted or not rooted locked or unlocked.... freshly installed, new rom, different build or new offical stock build.. ~ maybe some builds it has been a little bit more stable.... but there was a short period where i just left the phone as is...
no updates.... no new software.... nothing..... it was working fine for a couple of weeks then the random reboots started all over again.
so i have no idea... honestly.... i've heard every reason imaginable.... it's this software, it's that widget. . . it ain't true.
the problems persist.... on a fresh install....no widgets running... no software downloaded.....
ive tried cyanogen mod for the last few months.... it's been better.
but it's starting the problems all over again... so today i wiped the entire phone.... in a last ditch effort to get it stable....
i'm stuck now without an OS and i can't get fastboot recognized in the command prompt..... i don't know what to do now... ive been reading threads for hours without success.... installing driver, sdk.... you name it....
it ain't bricked..... but i sure can't get android back on there without an OTG cable and that doesn't work on nexus 4. well.... mine anyway.
i just want stock android 4.3 or 4.2 ... "ANYTHING" running... with minimal apps and something stable.... that's all i care about. i can't afford another phone at this time.... so i'm completely stumped.
so . . . there are others like you... that ARE having major hiccups with their NEXUS 4's......
my friends at collage all have the same phone without ANY problems at all..... BUT there are some of us....
who have just had bad luck all the way....
Did you try to RMA?
As of the Official Update of Jelly Bean 4.3 has been started to Rolling out, the users who have installed started using it. So if you find any bug pls report here so Others can be saved.
As far am using it more than 24 hrs,
- Touchwiz is still bit laggy
- Few app including XDA app is getting FC
- Ram usage is high
- Battery is same
- Opening and closing of app is taking bit more time
- Still Finding
Is it worth the update or should I wait?
Stock browser with quick controls and full screen enabled doesn't hide the nav bar properly... A bug since first leak.
4.3 Consumes 1.3gb to 1.7gb ram never lower than 1gb. Same in s4. I prefer 4.1.2 its faster
Sent from my GT-N7100 using xda app-developers app
torbjorne said:
Is it worth the update or should I wait?
Click to expand...
Click to collapse
Its better u can wait or Flash DN3 Rom.. but i can say this update is stable than S3 update.. less bugs..
The autobrightness is really bad
Even if I am setting it at +5 its really dim indoors as compared to 4.1.2
Really any idea how to fix it
Am I alone facing this issue
The "HealthService" starts, but I dont have the S Health app, and dont know why this service starts after reboot of the phone.
any one else with this?
akashsgpgi said:
The autobrightness is really bad
Even if I am setting it at +5 its really dim indoors as compared to 4.1.2
Really any idea how to fix it
Am I alone facing this issue
Click to expand...
Click to collapse
Am using in -2 , for me its gud in indoor and in sunlight also..
With about 90 apps installed, of which BBM, WhatsApp, Vonage, LBE Security Master, Greenify, CSipSimple, Google+ and KeepScreenOn run all the time in addition to the usual stuff like TW, Messaging, GMS that runs with Android, My RAM usage with MK4 is 784MB. I don't find any lag in TW or in any of the games I play (except Ingress, of course - but that is an app issue).
I of course have rooted, disabled a bunch of stuff from loading automatically at boot, and frozen Sammy crap that I don't want or use. And no Knox.
XDA App is working perfectly fine, deep sleep seems to pretty good - lost 1% overnight after 2 recharge cycles. Auto Brightness is cranky at times - sometime stuck at lowest or brightest - but returns back to sanity after a display off-on.
Overall there is nothing new or extraordinary in the MK4 version from what we have seen in the leaks - except of course the knox status in the bootloader (I didnt care about it as am out of warranty anyways).
Haven't tried the stock browser with quick controls+full screen though, I rely on Chrome...
Xposed Framework with Wanam's module, per app dpi setting, message notification to toast, and then some more - all works great.
ph03n!x said:
My RAM usage with MK4 is 784MB.... [and then some more] - all works great.
Click to expand...
Click to collapse
Can I ask, I just need some clarification: are you running a stock version or a custom ROM?
If it is the stock, which Open version are you using?
Static-Noise said:
Can I ask, I just need some clarification: are you running a stock version or a custom ROM?
If it is the stock, which Open version are you using?
Click to expand...
Click to collapse
This is a stock ROM, the only changes being removing the Knox related apk and rooting. I'm not sure what you mean by open, can you explain on it?
Any of you having issues with official rom should join me in using DN3 custom rom for note 2 with a bunch of note 3 features and very few bugs.
Sent from my Note 2 using DN3 V2.
grk007 said:
As far am using it more than 24 hrs,
- Touchwiz is still bit laggy
- Few app including XDA app is getting FC
- Ram usage is high
- Battery is same
- Opening and closing of app is taking bit more time
- Still Finding
Click to expand...
Click to collapse
- for me its a bit smoother than 4.1
- i haven't got any FC even on the leaked MI6
-not really
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
with many apps running
-yeah battery about the same as 4.1
-i think its about the same as 4.1
Many sincere thanks for taking the time to reply.
ph03n!x said:
This is a stock ROM, the only changes being removing the Knox related apk and rooting.
Click to expand...
Click to collapse
And, as much as this may seem like a stupid question, could you please show me which one you were using? I assume that you have upgraded and forfeited the "warranty void" issue for the new ROM?
ph03n!x said:
I'm not sure what you mean by open, can you explain on it?
Click to expand...
Click to collapse
I meant, for example, 'Open Asia', 'Open India', 'Open Europe', etc.
Henchman007 said:
...[You]... should join me in using [DN3 custom rom]... [with] very few bugs.
Click to expand...
Click to collapse
I am running that ROM at the moment, and to be honest, as much as I love it, there is still the issue with the screen off when the phone is in use, And the leg you get upon finishing the call itself.
Apart from that, is a fantastic update.
Major update but with few bugs.
When installing an app from play store, the downloading process is smooth but just when the installation is about to complete there are frame drops for a second or two and it really annoys me as a heavy play store user.
Frame drops and touchwiz!!! Brother's for life!!!
Sent from my GT-N7100 using xda app-developers app
I'm getting the odd FC, but it's very rare. I had to force a reboot twice since upgrading, but I've also been using my device like crazy and installing a lot of apps as i test this new firmware.
My only real gripe is that bringing up the multitasking list (long press home key)takes longer than before.
Sent from my GT-N7100 using Tapatalk
Static-Noise said:
Many sincere thanks for taking the time to reply.
And, as much as this may seem like a stupid question, could you please show me which one you were using? I assume that you have upgraded and forfeited the "warranty void" issue for the new ROM?
I meant, for example, 'Open Asia', 'Open India', 'Open Europe', etc.
Click to expand...
Click to collapse
I upgraded to the INU ROM that got released - http://www.sammobile.com/firmwares/3/?download=21880 - that is open India I guess (and there is no other 4.3 official ROM released yet? At least that's what Sammobile says...)
Code:
Model: GT-N7100
Country: India
Version: Android 4.3
Changelist: 2099172
Build date: Sun, 10 Nov 2013 06:00:26 +0000
Product Code: INU
PDA: N7100XXUEMK4
CSC: N7100ODDEMK1
MODEM: N7100DDEMJ9
And yes, I voided my Knox bootloader warranty - because I bought the phone from Singapore and didnt have India warranty anyway. And the phone is more than a year old too...
I see a delay in the caller number or name getting displayed when someone calls me (ringtone sounds, but screen is blank), but then that's nothing that can't be fixed with a build.prop edit.
I dont have a lag anywhere, at least nothing I can find - I have made a few tweaks to the PegasusQ parameters though (reduced freq_step from the default 37% to 5% so that all the frequencies of the CPU are used, Set the cpu_up_rate to 12 and cpu_down_rate to 16, set the hot plug frequencies to 600-400, 800-600, 1000-800 and hot plug run queues to 175-175, 275-275 and 375-375, down_differential to 10, sampling_down_factor to 1 nd sampling_rate to 30000) based on my experience with earlier stock and non-stock kernel performance.
I'm overall happy about the update, though we could have been shown some more love from the S4 / Note3 devices
Clipboard options have been removed and multiwindow isn't working.
Sent from my GT-N7100
are you refering to the n7105 Nordic 4.3 that release 2 days ago? can u put that in title or OP. n7100 users might get confused. (crazy cousins) think its about them......
finally LTE gets its rom date.
I had at beginning multi window issue where it was inactive but after full wipe it was fixes. Today I have an issue with keyboard as I can't switch to other languages rather than English anybody has this problem?
Sent from my GT-N7100 using xda app-developers app
Anyone have an issue with their accelerometer/gyro on their 6P? I'm thinking mines faulty, the first sign was Google Fit, telling me I've done 45,000 steps in a day (when Moto Body said I've done 5,000! which is realistic)...
Next I noticed that my Live Wallpaper Minima wasnt very smooth in its motions and kept on freaking out even when held as still as I could. It had always worked perfectly on the old Nexus 6.
The phone works fine in general & rotates fine etc. It just seems extremely jumpy. Anyone else having this same issue?
I spoke to Google and they're sending a replacement.
Heres a video of the issue:
I'll post a reply to confirm the replacement device has fixed the issue.
Hey Dyna. I'm Josh, the developer of Minima. I'm currently looking into what might be causing this issue, as I've received maybe ten complaints from various 6P and 5X users over the past couple weeks about the jumpy tilt effect. The fact that it's spread across both devices makes me think it has more to do with how the system handles sensor updates on Marshmellow, rather than a particular device flaw.
Either way, I should have an update out soon to deal with the issue. I hope it will be as simple as smoothing out the incoming raw sensor data. If you'd like to discuss further you can reach me at [email protected].
Hi Josh
I have a new 6P arriving tomorrow, but possibly not required if other people are having the same issue, unless its a more common hardware fault as not everyone will use similar wallpaper or Google Fit so may go unnoticed. I had a Nexus 6 prior to the 6P and it worked perfectly with Marshmellow and Minima.
I love Minima btw!
I had this problem as well, as Josh said it may be an app issue if we're all having the same problem.
Same problem as you but:
Having the same problem and noticed it the same way (Minima). I tried a random compass app and it was really finicky. At first I thought my gyroscope/accelerometer was defective but just now I tried Doodle Jump, which works fine. Now I'm just confused.
OkayDev said:
Having the same problem and noticed it the same way (Minima). I tried a random compass app and it was really finicky. At first I thought my gyroscope/accelerometer was defective but just now I tried Doodle Jump, which works fine. Now I'm just confused.
Click to expand...
Click to collapse
I can think of several reasons why some apps would work and others wouldn't. For one, the app can choose certain types of sensors for this info (gravity vs accelerometer) and certain delays (UI vs Game vs Fastest). It could also have to do with how the sensor registration process starts per app. I've tried different combos with no luck.
I really hope it's in my code, because then I can fix it and all's well. If it's a sensor problem though...:crying:
I published a fix for this last night, let me know if any of you are having a better experience now, and if so which device is working better or not.
JokoInteractive said:
I published a fix for this last night, let me know if any of you are having a better experience now, and if so which device is working better or not.
Click to expand...
Click to collapse
Yeah I got it this morning, it's working much better. I still get the odd jolt, not a full glitch where it would freak out but a small jolt where it will stop for a fraction then catch up again. To be honest it may had done it on the Nexus 6, but I just never paid that much attention to it.
This is on both my 6P's, the original one that made me start this thread & my new RMA. It works perfectly on both, so maybe it was a software issue all along. I havent it long enough to see how Google Fit behaves, I wouldnt had thought your app would have had any impact on Google Fit?
DynaMight said:
Yeah I got it this morning, it's working much better. I still get the odd jolt, not a full glitch where it would freak out but a small jolt where it will stop for a fraction then catch up again. To be honest it may had done it on the Nexus 6, but I just never paid that much attention to it.
This is on both my 6P's, the original one that made me start this thread & my new RMA. It works perfectly on both, so maybe it was a software issue all along. I havent it long enough to see how Google Fit behaves, I wouldnt had thought your app would have had any impact on Google Fit?
Click to expand...
Click to collapse
It wasn't really a problem with Minima. Minima has been using the Gravity Sensor since last year, which is a combination of accelerometer and gravity data on the device. It's more accurate than just accel usually, which is why I used it. It looks like the gravity data can get buggy on the 6p and 5x, so I reverted to just using the accelerometer and things seem to have smoothed out.
So apps using gravity may get whacked out, while apps using only accel (like Doodle Jump) might be just fine. I can't say for sure, all I know is the switch seems to have worked well enough. I'm still continuing research in hopes that I'll find something more concrete.
JokoInteractive said:
I published a fix for this last night, let me know if any of you are having a better experience now, and if so which device is working better or not.
Click to expand...
Click to collapse
What kind of fix? For what? For a app?
Send with the App Tapatalk
I think I have also worked out why my Google Fit registers a stupid amount of steps. I dont fully understand why as none of my previous phones have done this...
I use Daydream mode as a bedside clock, which I've done for years, but for some reason on the 6P, if I do this it'll clock up as much as 40,000 steps overnight!
Heres this morning so far... I've been up about 2hrs and not even left the house:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Heres when the steps were made... when I was asleep!
I have the same issue with my 6P, you can clearly see that accelerometer is weird by using apps like star chart, or try viewing photospheres in a VR mode, you'll see that it just randomly like crazy
aygul12345 said:
What kind of fix? For what? For a app?
Click to expand...
Click to collapse
Minima Live Wallpaper. I'm using a different sensor configuration on Android 6.0 to work around the faulty gravity sensor data the 5x and 6p are generating.
---------- Post added at 09:32 AM ---------- Previous post was at 09:31 AM ----------
DynaMight said:
I think I have also worked out why my Google Fit registers a stupid amount of steps. I dont fully understand why as none of my previous phones have done this...
I use Daydream mode as a bedside clock, which I've done for years, but for some reason on the 6P, if I do this it'll clock up as much as 40,000 steps overnight!
Heres this morning so far... I've been up about 2hrs and not even left the house:
Heres when the steps were made... when I was asleep!
Click to expand...
Click to collapse
Yeah, just sitting idle the 5x shows a lot of jumpiness. I can see how it's logging that as steps.
So I was having the same issues with my Nexus 6P, spoke with Google Support and ended up getting my device replaced. I just received my new replacement device today and this one is still having the same exact issues.
On further testing using the Street View app, I've noticed that when I switch to Cardboard View it tracks perfectly, it's only the photo-sphere view that will not track my movements; it either won't spin at all or spins wildly by itself. Anyone have technical data on what the Cardboard viewer uses to track movement versus standard photo-sphere?
My phone started messing up also after I updated to MDB08L on Nov 11. I got my phone November 9th and the step counts were normal until then. My UP app has me walking over 200,000 steps yesterday and 75000 today when I normally average 12000. This is using the phone sensors. My android wear watch has normal counts. I also use the daydream app at night but the trends graph in the UP app have me doing 30 - 70000 steps in a 5 to 10 minute span while my phone is not Daydreaming. I'll be waiting to see if your RMA'd phone has the same problem.
OP: Which build are you on?
---------- Post added at 10:11 PM ---------- Previous post was at 10:05 PM ----------
Also the Google Sky app is very jittery as compared to my 2013 Moto X. But photosphere is relatively smooth.
I just installed and so experiencing issues... any fix yet?
HartgE46 said:
So I was having the same issues with my Nexus 6P, spoke with Google Support and ended up getting my device replaced. I just received my new replacement device today and this one is still having the same exact issues.
On further testing using the Street View app, I've noticed that when I switch to Cardboard View it tracks perfectly, it's only the photo-sphere view that will not track my movements; it either won't spin at all or spins wildly by itself. Anyone have technical data on what the Cardboard viewer uses to track movement versus standard photo-sphere?
Click to expand...
Click to collapse
I just tried photosphere on streetmaps and although it doesn't spin on its own or anything and tracks my angular shifts as I do them, it does seem to consistently show 'micro jitter' like it has parkinsons. I'm just gonna check my Z3 and see if it has the same jitteriness there and update this post. And as a side note, if this pans out to be true, then at risk of sounding retarded, I wonder if this same issue has been why electronic stabilisation is not at optimum on the 6P.
I got a replacement and it also has the same issues... I wonder if it's a software problem
too bad I updated android as soon as I turned it on, so I can't verify if it was working before MDB08L... any easy way to rollback to verify it?
waldo447 said:
My phone started messing up also after I updated to MDB08L on Nov 11. I got my phone November 9th and the step counts were normal until then. My UP app has me walking over 200,000 steps yesterday and 75000 today when I normally average 12000. This is using the phone sensors. My android wear watch has normal counts. I also use the daydream app at night but the trends graph in the UP app have me doing 30 - 70000 steps in a 5 to 10 minute span while my phone is not Daydreaming. I'll be waiting to see if your RMA'd phone has the same problem.
OP: Which build are you on?.
Click to expand...
Click to collapse
I got mine just over 2 weeks ago now, I accepted an OTA straight away. I think it was from MDA89D to MDB08K & I noticed the issue straight away. I'm now on MDB08M and its still got the same issue.
I have raised the issue with Google support and the guy I spoke to said he'd raise it for me. Hopefully its just a software issue that'll be fixed in the next OTA update.
If anyone wants to roll back to the original image, you can flash the factory images here: https://developers.google.com/android/nexus/images?hl=en as standard it'll wipe everything inc your pics etc, you can get around this by not flashing userdata.img.
Hello LG G5 users , feel free to talk here about anything related to the LG G5 :good:
Thread Rules
1. Respect the others
2. This is an LG G5 thread , do not talk about any other LG phone here.
3. Use appropriate langage.
4. And of course , respect xda rules.
So what do you think about this LG phone ?
Hi guys , thread opened thanks to @KennyG123 , now that the G5 is out and available for sale feel free to share your experience in this discussion thread.
I will update it later with infos , reviews , battery tests..etc.
Enjoy
This is my first impression of the G5 and I'm sure once the stock and custom roms start rolling out I will have a much better experience with my phone. I picked up my new LG G5 a hour ago from my local Sprint retailer and I have already run into a few problems that kind of bother me about the phone. I switched from my Nexus 6 to this phone and I would have to say I do enjoy the feel of the phone and the fact of it being smaller and easier to hold. This is the only good thing I have really noticed about the phone so far though. The volume rocker on the left side of the phone seems very strange and would be much more ergonomic with it remaining on the back or on the right side to be easily accessible with the thumb. The G5 does not have an app drawer with the current software even though there were leaks saying that they were actually going to end up adding the app drawer for this phone. The software seems as if it went for a more Apple style design with a more vivid color scheme. I ended up looking through some of the apps and there are advertisements in the voicemail app which just seems wrong. I have already ran into a bug which should be expected with any new release of a phone of course and this bug happens when I double tap on a notification on the lock screen it locks the screen instead of opening the application which I really hope wasn't the intended purpose. So far the phone isn't as great as I expected it to be.
@CorruptProfile Thank you very much sir for this first well detailed feedback.
How about other things like the camera , performance ( if you tried any intensive game ) ? Is it buttery smooth or LG 5.0 UX suffer from lags ?
CorruptProfile said:
This is my first impression of the G5 and I'm sure once the stock and custom roms start rolling out I will have a much better experience with my phone. I picked up my new LG G5 a hour ago from my local Sprint retailer and I have already run into a few problems that kind of bother me about the phone. I switched from my Nexus 6 to this phone and I would have to say I do enjoy the feel of the phone and the fact of it being smaller and easier to hold. This is the only good thing I have really noticed about the phone so far though. The volume rocker on the left side of the phone seems very strange and would be much more ergonomic with it remaining on the back or on the right side to be easily accessible with the thumb. The G5 does not have an app drawer with the current software even though there were leaks saying that they were actually going to end up adding the app drawer for this phone. The software seems as if it went for a more Apple style design with a more vivid color scheme. I ended up looking through some of the apps and there are advertisements in the voicemail app which just seems wrong. I have already ran into a bug which should be expected with any new release of a phone of course and this bug happens when I double tap on a notification on the lock screen it locks the screen instead of opening the application which I really hope wasn't the intended purpose. So far the phone isn't as great as I expected it to be.
Click to expand...
Click to collapse
Have you checked right? T-Mobile users said that the app drawer is there, like seen in the GUI Official Video (not a leek)
Killua96 said:
Have you checked right? T-Mobile users said that the app drawer is there, like seen in the GUI Official Video (not a leek)
Click to expand...
Click to collapse
It is there if you use easy mode on your launcher as far as i know.
Sent from my GT-P5100 using XDA-Developers mobile app
Soufiansky said:
It is there if you use easy mode on your launcher as far as i know.
Sent from my GT-P5100 using XDA-Developers mobile app
Click to expand...
Click to collapse
Nope, there is a third option shown in the UX 5.0 video and confirmed by T-Mobile users
https://www.youtube.com/watch?v=lk8Zs3Mlbcs
Look at 2:19
I only really play Clash of Clans as far as game intensive on my phone and it ran very smoothly for the little bit that I was on it. The camera is far superior to any phone I have had in the past and the quality is great. The option for the regular launcher with an app drawer does not exist on my device which is no problem since I do not like the launcher in general and the Google Now Launcher is far superior to LG's. The biggest problem I have started to see with the device now is the fact the battery is weak as can be. I'm not sure if there isn't enough data collected yet to give an accurate estimate on how long the battery will last. I took the first screenshot of the battery usage before I used any high usage applications and it already was showing that my phone would last an hour and 47 minutes when it was at 41%. I would add screenshots to this but, I don't have over 10 posts yet so that isn't possible so I sent them to @Soufiansky so he can post them instead.
CorruptProfile said:
I only really play Clash of Clans as far as game intensive on my phone and it ran very smoothly for the little bit that I was on it. The camera is far superior to any phone I have had in the past and the quality is great. The option for the regular launcher with an app drawer does not exist on my device which is no problem since I do not like the launcher in general and the Google Now Launcher is far superior to LG's. The biggest problem I have started to see with the device now is the fact the battery is weak as can be. I'm not sure if there isn't enough data collected yet to give an accurate estimate on how long the battery will last. I took the first screenshot of the battery usage before I used any high usage applications and it already was showing that my phone would last an hour and 47 minutes when it was at 41%. I would add screenshots to this but, I don't have over 10 posts yet so that isn't possible so I sent them to @Soufiansky so he can post them instead.
Click to expand...
Click to collapse
Thank you again for the feedback , when i come back home i will post the links you send me in pm
Thanks to @CorruptProfile
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How's the phone size?
I'd be coming from the Nexus 6 which is like a phablet, so I want to know how it feels in the hand?
Mew351 said:
How's the phone size?
I'd be coming from the Nexus 6 which is like a phablet, so I want to know how it feels in the hand?
Click to expand...
Click to collapse
It is 5.3" , way smaller than the huge Nexus 6.
Soufiansky said:
It is 5.3" , way smaller than the huge Nexus 6.
Click to expand...
Click to collapse
I was going to get the S7 Edge but it's not rootable, so it is a huge deterrent for me
Mew351 said:
I was going to get the S7 Edge but it's not rootable, so it is a huge deterrent for me
Click to expand...
Click to collapse
You can wait for the M10 , and for root it will come one day , patience
Sent from my GT-P5100 using XDA-Developers mobile app
Soufiansky said:
You can wait for the M10 , and for root it will come one day , patience
Sent from my GT-P5100 using XDA-Developers mobile app
Click to expand...
Click to collapse
The M10 is waayyyyy too small for me ;/
Mew351 said:
How's the phone size?
I'd be coming from the Nexus 6 which is like a phablet, so I want to know how it feels in the hand?
Click to expand...
Click to collapse
I came from the Nexus 6 as well and honestly I like the size of the G5 it is smaller but not too small in the hand where it feels like you are holding nothing.
Mew351 said:
The M10 is waayyyyy too small for me ;/
Click to expand...
Click to collapse
Note 5 ? Nexus 6P ? We're going in an off topic here...
Sent from my GT-P5100 using XDA-Developers mobile app
CorruptProfile said:
I came from the Nexus 6 as well and honestly I like the size of the G5 it is smaller but not too small in the hand where it feels like you are holding nothing.
Click to expand...
Click to collapse
What about the module thing ? I saw a lot of issues about it these days
Sent from my GT-P5100 using XDA-Developers mobile app
I don't own a module and I don't really see the purpose of owning one to be completely honest. It's basically just buying add-ons if you prefer having them or not. I enjoy having the naked look of a sleek looking phone without having a bunch of stuff all over it. It really comes down to the person if they want the parts or not and personally I don't the parts won't make the phone any worse and if the modules really just fail then it won't have any overall effect on the performance of the phone itself.
CorruptProfile said:
I don't own a module and I don't really see the purpose of owning one to be completely honest. It's basically just buying add-ons if you prefer having them or not. I enjoy having the naked look of a sleek looking phone without having a bunch of stuff all over it. It really comes down to the person if they want the parts or not and personally I don't the parts won't make the phone any worse and if the modules really just fail then it won't have any overall effect on the performance of the phone itself.
Click to expand...
Click to collapse
No i was talking about the stock battery module , you haven't faced any issue ? Because some people were reporting bad screen colors reproduction next to the module , others said it started taking off....etc.
Sent from my GT-P5100 using XDA-Developers mobile app