Hey,
I got my nexus 1,5 months ago and it was pretty fast on 4.1.
Then I updated (OTA) to 4.2 and I got a lot of bugs like
screen doesnt turn on during call (not via turning and not via power button)
switching the phone on (to lockscreen) takes 3 press on power button
camera app takes hours to start
Then I unlocked the bootloader and installed a custom ROM (any 4.2 from xda, don't remember the name)
But it had the same problems.
Then I downgraded to aokp 4.1.
The call problem (phone crashing during call) didn persist but camera was still slow and after one day all the other apps too.
Facebook takes like 10-20 secs to open completely. Same for whatsapp. Even SMS takes 5-15 secs.
I reinstalled everything (after complete) wipe but still the same. I switched to cm 10.0, also the same but now also the phone takes 10 secs to open.
And it crashes sometimes when the screen off and I have to take the battery out.
Is my phone broken somehow?
flash the 4.1.2 google image and see if that helps
You may be suffering from this bug: http://forum.xda-developers.com/showthread.php?t=2029246
From what I've found out, you need to flash a factory image and afterwards flash your favourite ROM. The speed will be back to normal, at least for a short while.
Try to flash Purity 3.1 Rom. Is smoothness and battery saver.
Enviado desde mi Galaxy Nexus usando Tapatalk 2
Install and open this app: eMMC Brickbug Check
(Not to check if you got the eMMC brick bug, but to get your chip type and production date)
If it shows chip type V3U00M, you got this bug.
{
"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"
}
Solution without wipe
ph4zrd said:
Solution without wipe
Click to expand...
Click to collapse
The discard and dd/rm method did not work for me and others reported similar results.
The only thing that brought back the speed (at least temporarily) was to flash a factory image.
It's 'sort-of' non wipe as I took a nandroid backup, wrote the factory image and restored the nandroid image.
wkwkwk said:
The discard and dd/rm method did not work for me and others reported similar results.
The only thing that brought back the speed (at least temporarily) was to flash a factory image.
It's 'sort-of' non wipe as I took a nandroid backup, wrote the factory image and restored the nandroid image.
Click to expand...
Click to collapse
This is strange as most users reported positive results using this workaround...
Also, it is the only permanent fix for the bug currently available (if it works for your phone, of course).
Maybe some kernels have disabled the TRIM/ERASE capabilities of the eMMC driver or something similar, which blocks the discard option from working?!
Can you please post your exact eMMC chip type, production date & firmware rev?
Flash Factory image. I had the same problem but after flashing Factory i havent had any issues(2 months ago)
Sent from my Galaxy Nexus using xda premium
ph4zrd said:
This is strange as most users reported positive results using this workaround...
Also, it is the only permanent fix for the bug currently available (if it works for your phone, of course).
Maybe some kernels have disabled the TRIM/ERASE capabilities of the eMMC driver or something similar, which blocks the discard option from working?!
Can you please post your exact eMMC chip type, production date & firmware rev?
Click to expand...
Click to collapse
Interesting idea about the kernel having the trim disabled, I'm using CM10 (4.1.2) with franco kernel 300.
I have enabled the 'discard' option at mount but a few tests revealed that performance is not recovered (I tried even running sync a few times after rm).
I have:
model: V3U00M
date: 10/2012
fwrev: 0xd
hwrev: 0x0
Thanks.
wkwkwk said:
Interesting idea about the kernel having the trim disabled, I'm using CM10 (4.1.2) with franco kernel 300.
I have enabled the 'discard' option at mount but a few tests revealed that performance is not recovered (I tried even running sync a few times after rm).
[...]
Click to expand...
Click to collapse
Checked some kernel sources. Trim should work, at least in CM and franco kernel.
So it must be another problem on your phone...
Btw 'sync' only forces flushing of the filesystem buffers. This is also done at unmount/reboot and automatically as part of normal operation, so it should not be necessary.
Strange. I even rebooted a few times and the phone was still laggy and androbench was reporting between 0.5-1MB/s, sometimes even less.
After writing factory image it jumps to 10MB/s.
Are there any other things I can test?
Another thing, I tried enabling encryption immediately after writing the factory image and the performance dropped instantly, I'm assuming the encryption process writes zeroes (or random data) to fill the whole space.
Thanks.
Related
I have been having wifi issues since I moved up to CM10/JB. I'm able to boot up just fine, but when I attempt to turn on wifi one of two things happens. Either the slider returns to off immediately or the wifi attempts to connect to no avail. The wifi worked just fine for a week or so after jump to JB, then it dropped out while I was travelling. I've seen some older, similar posts, but haven't seen any concrete solutions.
I have tried a variety of things, but nothing has seemed to work.
• Updated TWRP, FFF using smirkit
• Total wipe/unroot, flash back to stock
• Re-rooted
• Flashed different ROMS, kernels
Sorry if I come off a little noobish. I'm a bit out of practice. I haven't touched my kindle in a while, but now have a 13 year-old who would like to use it.
Could it be a hardware failure? Any suggestions, solutions or commiseration is greatly appreciated. Thank you!
monteith said:
I have been having wifi issues since I moved up to CM10/JB. I'm able to boot up just fine, but when I attempt to turn on wifi one of two things happens. Either the slider returns to off immediately or the wifi attempts to connect to no avail. The wifi worked just fine for a week or so after jump to JB, then it dropped out while I was travelling. I've seen some older, similar posts, but haven't seen any concrete solutions.
I have tried a variety of things, but nothing has seemed to work.
• Updated TWRP, FFF using smirkit
• Total wipe/unroot, flash back to stock
• Re-rooted
• Flashed different ROMS, kernels
Sorry if I come off a little noobish. I'm a bit out of practice. I haven't touched my kindle in a while, but now have a 13 year-old who would like to use it.
Could it be a hardware failure? Any suggestions, solutions or commiseration is greatly appreciated. Thank you!
Click to expand...
Click to collapse
"the slider returns to off immediately" or say "Turning Wi-Fi On..." forever,
Actually, the WiFi switch is grayed out (but still can push on/off)
The problem was started after the second day that I have flashed "cm-10.1-20130223-0102-otter-sgt7.zip".
I was using my File to play online game, all network connection was drop suddendly. I turn off the Wifi and try to reconnect and then my Wifi goes death up to now.
I tried to flash other build of CM-10/10.1, stock rom, apkp, etc. Wipe even external storage. The wifi still not work.
I am unable to confirm that is hardware problem or rom problem at this point.
.....or say.....a Kindle File with dead wifi is worse than a bricked one
{
"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"
}
Resetting battery stats helped with Wi-Fi (SGS II)
wunit said:
"the slider returns to off immediately" or say "Turning Wi-Fi On..." forever,
Actually, the WiFi switch is grayed out (but still can push on/off)
The problem was started after the second day that I have flashed "cm-10.1-20130223-0102-otter-sgt7.zip".
I was using my File to play online game, all network connection was drop suddendly. I turn off the Wifi and try to reconnect and then my Wifi goes death up to now.
I tried to flash other build of CM-10/10.1, stock rom, apkp, etc. Wipe even external storage. The wifi still not work.
Click to expand...
Click to collapse
fatbuccha said:
I also experience this before, i tried to reset fuel gauge if you're on siyah or dorimanx, problem went away after doing that. Try if it will also work on you, im on wanam lite leaked version of jb and never encounter the problem again
Sent from my GT-N8000 using xda app-developers app
Click to expand...
Click to collapse
As found in another forum, I desperately tried one last thing: booted to recovery and cleared battery stats. My Wi-Fi can be turned on and works! What a magic...
Things had broken after first time flashing rooted kernel and ROM (currently Kernel_Siyah-Dorimanx-V9.0-[17-39]-[05-03]-JB-CM-AOKP-SGII-PWR-CORE and cm-10.1-20130304-NIGHTLY-i9100)
This is hella old thread, but it slightly helped me when converting a Kindle to cm11. Flashing none of the recent 2015 nightlies had wifi. Flashed the M12 from 2014 and wifi worked, then dirty flashed the newest and wifi still worked.
I have a backup for 2.3.0 LiquidSmooth that works fine and reboots and everything.
I change a few settings such as:
-Overclock to 1350
-Change voicemail number
-Change Ringtones
-Edit the Navring
-Change the Alpha of the status and nav bar to 100%
-Update a few Data Apps from the market.
-Turn off Drymatic tiles.
-Set an Alarm
-And a few other tweaks I cant remember.
Then All of a sudden I try to Reboot and Bootloop (Ive waited 10 minutes before pulling the battery) Then I restore my backup and try the changes again and it does the exact same thing but if I dont make those changes it works fine.
Can someone Please explain to me what is going on. Im not stupid I have flashed many roms before but never seen something this strange where I dont even change the /system folder and it bootloops
(
I have restored just the /data floder with CMR and it booted up fine so it has to be soemthing in the /data folder
The phone works 100% on other roms
I have been trouble shooting for a few hours with no luck please help.
I have 7GB left in storage and the /system folder has 374mb left.
)
About 2 days later after This happened I decided to Try a different 4.2.2 ASOP rom, Axiom by DroidTh3ory. And after I got done setting it up the same thing happened D: Please help me.
Might not be the answer your looking for but i think its the overclock thats bootlooping your phone, might be a rouge app :-S i can't really say i havn't experienced anything like this before
Full wipe?
irizwan said:
Might not be the answer your looking for but i think its the overclock thats bootlooping your phone, might be a rouge app :-S i can't really say i havn't experienced anything like this before
Click to expand...
Click to collapse
Okay I will try it again and do everything expect overclock and let you know if it happens again. My phone used to be able to handle 1350 mhz
Also does flashing a new kernel Reset the Clock Values in the system Data?
bananagranola said:
Full wipe?
Click to expand...
Click to collapse
I did a full wipe before Each one but I restored some data files for The live wallpaper,Homescreen, and Widgets when I flashed but It rebooted fine after that. It wasnt till I got to fine tuning my settings that I got a bootloop.
Hmm... you restored the backup and installed the kernel directly without rebooting? if your talking about trickstermod in data then i think yea it should reset someone knowing better than me can comment but as far as i know trickstermod can detect different kernels and it resets when you do flash a diff. kernel
Full wipes also an option when all else fails
irizwan said:
Hmm... you restored the backup and installed the kernel directly without rebooting? if your talking about trickstermod in data then i think yea it should reset someone knowing better than me can comment but as far as i know trickstermod can detect different kernels and it resets when you do flash a diff. kernel
Full wipes also an option when all else fails
Click to expand...
Click to collapse
Im talking about the Perforance controls built into roms settings now a days. All I do is bump it up to 1350 mHz I dont change kernels I just move the slider xD. For all these test Im on the kernels that come in the rom (Lean for Liquid not sure aobut Axiom though)
I just tested. I changed the Overclock value to 1350 mHz on my backup then rebooted so that isnt it.
Does anyone know of any Rouge apps that cause Bootloop problems after thier settings are changed or any settings in AOKP that cause bootloops
Nah, they should be the same i don't know it's a weird problem we have here LOL
irizwan said:
Nah, they should be the same i don't know it's a weird problem we have here LOL
Click to expand...
Click to collapse
I know right I have never had anything like this before I just restored my old rom but flashed a new kernel and it seems to be booting (Rebuilding davlik right now) but I dont know if that will fix it. I think having a phone that is almost 2 years old is really weighing down on the software.
Hope it works, sorry couldnt help that much.. you should try a flash install i know it's gonna be time consuming and a little work but it'll be worth it in the end
It seems to be working now here is a Screenshot of my homescreen to say thanks for helping. Just ask if you want a walk through on how to build it.
{
"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"
}
---------------------------------------------------------------------------------
CyanogenMod12 for the XT907
---------------------------------------------------------------------------------
SOURCES:
> https://github.com/dhacker29?tab=repositories
> https://github.com/CyanogenMod/
CHANGELOG: (MASTER)
> http://www.cmxlog.com/12/xt907/
---------------------------------------------------------------------------------
DOWNLOADS
---------------------------------------------------------------------------------
CM12 Thread:
> http://forum.xda-developers.com/droid-razr-m/development/rom-cyanogenmod-12-t2994972
---------------------------------------------------------------------------------
SCREENSHOT
---------------------------------------------------------------------------------
{
"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"
}
Wow
Thanks for sharing
Odesláno z mého XT907 pomocí Tapatalk
Can't wait to see the finished product!!!
Seriously...? And what bootloader is supported?
Dr. Mario said:
Seriously...? And what bootloader is supported?
Click to expand...
Click to collapse
The 3.4 kernel indicates KKBL, but I don't know if anyone is or will be working on a JBBL version.
Ouch... Still it's possible to get Linux v. 3.4 kernel to work with Jelly Beans bootloader, just takes a bit work in figuring out how to make it work. I didn't like Kit Kat bootloader, too much problems.
Dr. Mario said:
Ouch... Still it's possible to get Linux v. 3.4 kernel to work with Jelly Beans bootloader, just takes a bit work in figuring out how to make it work. I didn't like Kit Kat bootloader, too much problems.
Click to expand...
Click to collapse
You have to realize people are probably going to stop supporting JB at some point.
Sent from my HTC6525LVW using Tapatalk
Well, still. I was put off by the Kit Kat bugs, and I wouldn't want it to happen again, I had to replace the battery due to slow thermal damage (the phone obviously ran too hot - I noticed the damage was already done by the time I downgraded my RAZR M back to Jelly Beans in order to run cooler, I tried calibrating it, the runtime nosedove).
https://twitter.com/dhacker29/status/533142687873265664
Looks like at least a test version of CM12 is out
seasonone said:
https://twitter.com/dhacker29/status/533142687873265664
Looks like at least a test version of CM12 is out
Click to expand...
Click to collapse
Yeah its over here no idea if it boots if it will flash or what gapps to use... flash at your own risk
Edit... Maybe these Gapps
We cannot teach people anything; we can only help them discover it within themselves.
So I've downloaded it and flashed it, while flashing it returned an error with mounting something regarding msm8960 in /data but in the end it said that flashing is done. The ROM doesn't boot on my phone, it's possible that I did something wrong I was in school when I tried it.
Shefczenko said:
So I've downloaded it and flashed it, while flashing it returned an error with mounting something regarding msm8960 in /data but in the end it said that flashing is done. The ROM doesn't boot on my phone, it's possible that I did something wrong I was in school when I tried it.
Click to expand...
Click to collapse
How long did you wait for it to boot? I know when I flashed Lollipop on my Galaxy Nexus, it took forever..... to boot.
EDIT:
On CM12 Test build the sim card doesn't work. Nevermind got working. I wiped everything + formatted data, then I pulled my sim then re-inserted it.
ATTACK said:
How long did you wait for it to boot? I know when I flashed Lollipop on my Galaxy Nexus, it took forever..... to boot.
EDIT:
On CM12 Test build the sim card doesn't work. Nevermind got working. I wiped everything + formatted data, then I pulled my sim then re-inserted it.
Click to expand...
Click to collapse
Thanks Attack. Care to comment on what works and what does not?
ATTACK said:
How long did you wait for it to boot? I know when I flashed Lollipop on my Galaxy Nexus, it took forever..... to boot.
EDIT:
On CM12 Test build the sim card doesn't work. Nevermind got working. I wiped everything + formatted data, then I pulled my sim then re-inserted it.
Click to expand...
Click to collapse
About 15 minutes, guess that wasn't long enough. Gonna test it again later in the evening and I wíll report back on how it went.
jdb3654 said:
Thanks Attack. Care to comment on what works and what does not?
Click to expand...
Click to collapse
So far, everything seems to work. WiFi, Data, Sms (idk Mms) and GPS (after mfastbooting these commands)
Code:
mfastboot erase modemst1
mfastboot erase modemst2
Shefczenko said:
About 15 minutes, guess that wasn't long enough. Gonna test it again later in the evening and I wíll report back on how it went.
Click to expand...
Click to collapse
Yeah... 15 mins. is a bit to long, but you should see around 2 - 5 mins on first boot.
Agreeable. 15 minutes are a tad too long.... ART typically take a good while recompiling the apps on the first boot but I am surprised that it took so long.
Anyways, know of any good Kit Kat ROM that doesn't have overheating problems? I might flash the bootloader and jump to Lollipop at some point.
'Kay, so I've downloaded the files again, installed it and the system came up right away (~3 minutes) so I have no idea what I did wrong in the morning. Nevermind that the system is working perfectly, smooth, fast and fully working. I actually didn't though that first build will be daily driver quality, the only thing I noticed is bit buggy animation when closing apps but that is minor thing. I will test battery life tomorrow.
Only problems I've seen so far is the video on YouTube doesn't work and the compass icon won't go away at least for me but it looks like it could a dd.
I just installed lp, first impressions are good everything seem to work and is mostly smooth and snappy.
{
"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"
}
This is the discussion thread for the Official CM13 Nightlies for OnePlus 3.
Click to expand...
Click to collapse
Development Thread
[ROM] [6.0.1] Official CyanogenMod 13
Downloads
ROM
https://download.cyanogenmod.org/?device=oneplus3
GAPPS
1.Banks Dynamic Gapps
2.ARM64-OpenGapps
TWRP Downloads
https://twrp.me/devices/oneplusthree.html
SuperSU Downloads
UPDATE-SuperSU-v2.76.zip
Flashing Instructions
http://wiki.cyanogenmod.org/w/Install_CM_for_oneplus3
Sources:
https://github.com/CyanogenMod/android_device_oneplus_oneplus3
https://github.com/CyanogenMod/android_kernel_oneplus_msm8996
Changelog
https://www.cmxlog.com/13/oneplus3/
Bug Reports
https://jira.cyanogenmod.org/projects/NIGHTLIES
Important Notice:
1.Do not post irrelevant stuffs in the development thread.
2.You can ask questions or queries here, in this thread.
3.Do not ask for ETA's here,or in the development thread.
Frequently Asked Questions
Q1:Is VOLTE working?
Yes.
Q2:Is Pocket Mode included in this ROM?
NnePus did not release the sources for Pocket Mode.
Q3:Is DASH Charge supported?
Yes.
Q4:Where can I find the toggle for SRGB mode?
Display&Lights->LiveDisplay->Color Profile->Photography
Awesome, much helpful for the new comers with all the required download links in the place. :good:
Cant fins otg enable option on storage and usb, is this option missing?
I have tried otg in twrp and is working, now I am not at home till Sun, so I can't try in CM.
Anybody found a way to enable 720p 240fps slow motion video?
Sent from my ONEPLUS A3000 using Tapatalk
bschmidy10 said:
Anybody found a way to enable 720p 240fps slow motion video?
Click to expand...
Click to collapse
Not possible as the sensor used in the Oneplus 3 (Sony IMX 298) doesn't support it.
Hello
From the 0718 nightly until 0822 i found a wakelock bug. If I connect with this nightlys to my home Mikrotik AP (3 different types and on different firmware routers), the phone always in awake and it made a heavy battery drain. If i connect to any other AP on my home network or other places this problem didn't appear, the phone can sleep.
In the Battery menu the Android OS was who keep the phone awake. In the BetterBatteryStat it was the qcom_rx_wakelock. It runs near 100%.
Before 0705 this problem never happened on official CM13. Between 0705 and 0718 i didin't find any archive nightly to test it.
This problem present in every unofficial CM13 and every AOSP rom that use CM13 kernel that i tested.
It happened on SultanXDA rom too until 0823. But on 0825 he made some changes and this problem never appeared again. On this latest build the phone sleep as well on my AP, so i am happy with it but of course i would like if this change move to the main CM13 tree.
So the question is: Do i have to open a CM13 bug ticket with log, or CM13 devs can ask SultanXDA in the house what he did?
Thanks!
Hi Guys, i've an issue but probably it's easy to solve but i don't know how.
In CM using Trebuchet even configuring in buttons section some action to open search assistant i can't open Google Now Cards. Is there a solution or a configuration to solve this?
Edit: Problem Solved on Accessing Default Apps em switch to None and Back to Google App
Can you please tell the behavior of your device?
I have both set as lockscreen security the Pattern method and i also use the fingerprint sensor.
So, if the screen is off and you touch the fingerprint sensor, the device gets unlocked? Is the usage of the sensor bypassing the Pattern screen?
I'm asking because for almost 2 weeks the fingerprind sensor couldn't unlock the device if the screen was off, i should first double tap the screen, and after i saw the lockscreen i could use the sensor in order not to draw the pattern.
The last few days even if the screen is off i can unlock the device by using my finger.
Well seeing as this is the "Official" question location I'll ask. After I made a full nandroid backup earlier in Aug, then I manually applied OOS OTA 3.2.4, which caused me to loose my Baseband (was able to get it back after lots of tricks mentioned here in XDA that I had to use when my OPO lost it's Baseband awhile ago), once the Baseband issue was resolved I reflashed my nandroid backup (only Data partition, I did a full wipe of the device and did a full reinstall of the CM13 Nightly at the time). Once it all booted (even tried a completely clean install of CM13), I have been unable to find the option to do a Manual Network Search. Is this a known issue or a bug?
Since 7th of October I faced the issue that after flashing the nightly the using of fingerprint sensor reboot my OnePlus 3. When I flash back to nightly 10/06 all works as designed. Last test today with nightly 10/13. Anybody else faced this issue?
Recovered and updated OOS 3.24 to 3.27 there are no problems sensor works well.
Tested with 10/14 and 10/15 again... Same result
Edit: Flashed 10/20 and got again reboots. Removed alls screen security options and flashed it again. Configured password and fingerprints and now it works
I've been running LineageOS 14.1-20170612-NIGHTLY-bullhead on my phone since I updated it. I wanted to put a different ROM on my phone so I decided to cleanup/backup my phone. After doing my work, I formatted the phone through the regular settings. Upon resetting the phone, there seems to be a permanent vertical white line across the screen.
I proceeded to wipe dalvik/cache thru TWRP (The white vertical line appears in recovery mode) and nothing has changed.
Before I replace the ROM, which I think is the cause of the line, I wanted to see if it was hardware or software. I would like to guess it's software because the line seems to push a certain portion of the screen over. Before I keep continuing this post, maybe someone can help me diagnose the phone.
Phone is new, I bought it last year and opened it from it's sealed package 3 months ago. There's been no heavy usage, battery is charged with phone turned off, and I use this phone to simply test ROMs before I install them on my regularly used (other) Nexus 5x.
Will post pictures, but what media site should I upload to?
momostarz said:
because the line seems to push a certain portion of the screen over.
Click to expand...
Click to collapse
If it were me i'd start with a fresh flash of the latest factory image from google. BL, radio, vendor, etc. Then start over with the custom stuff(recovery, roms).
To my knowledge, I dl an image from google's site and just flash all, correct?
shhnedo said:
If it were me i'd start with a fresh flash of the latest factory image from google. BL, radio, vendor, etc. Then start over with the custom stuff(recovery, roms).
Click to expand...
Click to collapse
I used googles image for bullhead with the flash all method. No luck. Attempting second method (flashing seperately)
{
"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"
}
[/IMG]
Look closely and you'll see the push over.
I think it's hardware..
momostarz said:
http://i63.tinypic.com/2eoian5.png
Look closely and you'll see the push over.
Click to expand...
Click to collapse
Where? Cause... I don't see anything wrong on the screenshot itself. In this case, I'd say hardware too. The screenshot captures the output picture, not what the LCD itself is displaying.
And why is the screenshot in 900x1900 resolution? All my screenshots are 1080x1920...
shhnedo said:
Where? Cause... I don't see anything wrong on the screenshot itself. In this case, I'd say hardware too. The screenshot captures the output picture, not what the LCD itself is displaying.
And why is the screenshot in 900x1900 resolution? All my screenshots are 1080x1920...
Click to expand...
Click to collapse
How can I change the resolution?
[/IMG]
This is the best I can do.
http://i64.tinypic.com/ou8tc5.jpg
Phone is also put back to stock completely. I flashed via flash all and flashed again via all files separately. No changes.
momostarz said:
Phone is also put back to stock completely. I flashed via flash all and flashed again via all files separately. No changes.
Click to expand...
Click to collapse
Then it's a hardware issue. Haven't seen or encountered it, though...
shhnedo said:
Then it's a hardware issue. Haven't seen or encountered it, though...
Click to expand...
Click to collapse
I really want to doubt it's a hardware issue ):
I've only used the phone within 3 months, and with a wild guess for accumulative time usage, less than 48 hours. It was taken out of a sealed package, and was never carried in my pocket, never dropped, nor was it ever out of my office space. If it is a hardware issue, what are steps (any step is a procedure I will try) I can commit?
I would like a screen replacement to be the last option.