Related
Ok so heres my experience over the first week of having googles flagship phone...
1) When i first got the device home and turned it on It auto downloaded like 50 apps that i had installed on my sgs which i didnt want it to do...
2) when ever i scrolled through the app drawer the first 2 pages was fine but when i scrolled to the 3rd page the launcher would force close every time. A battery pull didnt fix the problem either... Luckily i got an update to 4.0.2 about 30 minutes after the device was on which got rid of that problem...
3) Now that im on 4.0.2 sometimes when im leaving the app drawer to go back to the homescreen the launcher will freeze for a few seconds between the zoom out transition so i see half of thr app drawer and half of the homescreen. This happens completely random and i cant reproduce it.
4) I have just been looking on the market and my screen just shut itself off... I couldnt turn the phone back on through the power button and i had to long press the power button to turn the phone back on. Basically the phone just died for no reason.
I love this phone and ICS but i just wish it would work how its supposed to.
Each of these little things is adding up and starting to ruin the experience.
What makes it worse is that i have seen other people with these same problems.
This is googles latest and greatest phone to the world to show what they can do and it just doesnt work.
I understand that ICS is brand new and that its the biggest rewrite to the OS since its birth but they shouldnt be releasing phones in this state.
If this continues i will be returning my device. I hope the next update brings some majour fixes.
And BTW im 100% stock.
Stock 4.0.2 GSM version have not experienced a single issue you have.
The one thing I can say is this is a developer phone and its just gonna have bugs. Its probably not what you want to hear but that's kinda how it is : /
martonikaj said:
Stock 4.0.2 GSM version have not experienced a single issue you have.
The one thing I can say is this is a developer phone and its just gonna have bugs. Its probably not what you want to hear but that's kinda how it is : /
Click to expand...
Click to collapse
Yeah i understand that.
When i first read about other people with random reboots and stuff i was like damn that sucks im glad that hasnt happened to me... But alas it has happened along with the other issues mentioned.
I might have to return it but even then they will probably just sen it away for 2 weeks and reflash it.
I just want it to work to its full potential.
As i said i know its the first versions of ICS and i expect a bit of problems until they iron out the creases but the list is just getting longer. Ive only had the phone like a week.
first off... put down ur phone...
.......
.........
..............
.........
.....Breathe.....
look... no android device is perfect... you knew this buying the phone...
android is a work in progress... it is still one of the newest OS's out there.
of course ics has faults... its not near perfect yet... no worries... slowly it is going to get better and better...
look... unlock that bootloader of yours... and install a custom rom
most people and my self are using AOKP, install a custom kernal... Lean kernal and franco kernal are great choices...
custom roms usually preform better than stock...
relax... try it out...
im 100 percent sure this will fix your problems or any doubts u might have.
It sounds to me like the OP should just get rid of the Gnex and buy and iPhone. ICS is new! It will be buggy at first. Each update will bring a more stable and better all around experience. Like Radsolutionz said, unlock the bootloader, install Clockworkmod Recovery, and get to flashing a custom Rom. Most custom Roms are 4.0.3 which works better than 4.0.2. Just be patient my friend. It will get better as Google releases updates to ICS.
Yeah i know i know.
I just hope it gets better soon lolz.
Im trying to keep this one stock as long as possible.
Dont get me wrong im no stranger to flashing roms. I flashed hundreds on my sgs but i just want to keep this one stock for the first few months.
fingers crossed that the next update isnt too far away and this will fix these problems.
housry23 said:
It sounds to me like the OP should just get rid of the Gnex and buy and iPhone. ICS is new! It will be buggy at first. Each update will bring a more stable and better all around experience. Like Radsolutionz said, unlock the bootloader, install Clockworkmod Recovery, and get to flashing a custom Rom. Most custom Roms are 4.0.3 which works better than 4.0.2. Just be patient my friend. It will get better as Google releases updates to ICS.
Click to expand...
Click to collapse
I would rather go back to a nokia 3210 then get an iphone!
As i said in the post above im no stranger to flashing roms and kernels and playing with the build props etc but im trying to avoid that for the time being.
I would just like to point out that #1 is not a problem at all, it is a feature all android phones have, when activating a new phone it automaticly syncs everything from the last phone to the new one, if u didn't want that to happen then u shouldn't have checked the box to restore all Google information or whatever the message is when u first setup the phone, should probably delete it...
Sent from my Galaxy Nexus using XDA App
#1 is your fault, when you sign into your Google account, it specifically asks you if you want to backup your data (app data, wifi passwords, and other settings) and/or Automatic restore apps and user data.
Don't give him such a hard time he loves his phone. I was disappointed to I also had random stuff happen but now its all settled down and battery life is great. Give the phone time to adjust and delete as many apps as you don't really need. It could be a bad app that's causing the problem.
If you still don't like it sell it and get something else .
Sent from my Galaxy Nexus using xda premium
andy2na said:
#1 is your fault, when you sign into your Google account, it specifically asks you if you want to backup your data (app data, wifi passwords, and other settings) and/or Automatic restore apps and user data.
Click to expand...
Click to collapse
This.
10chars
i dont know but i just had to reply.
1) When i first got the device home and turned it on It auto downloaded like 50 apps that i had installed on my sgs which i didnt want it to do...
as said by other member, do that. OR go quickly to market > my apps, and press the 'X' to stop all progress. yeah it stops all.
2) when ever i scrolled through the app drawer the first 2 pages was fine but when i scrolled to the 3rd page the launcher would force close every time. A battery pull didnt fix the problem either... Luckily i got an update to 4.0.2 about 30 minutes after the device was on which got rid of that problem...
i'm sure you have this rare problem as others did not but glad it worked out.
3) Now that im on 4.0.2 sometimes when im leaving the app drawer to go back to the homescreen the launcher will freeze for a few seconds between the zoom out transition so i see half of thr app drawer and half of the homescreen. This happens completely random and i cant reproduce it.
same as number 2. if you got a slight lag opening the app drawer, its normal.
4) I have just been looking on the market and my screen just shut itself off... I couldnt turn the phone back on through the power button and i had to long press the power button to turn the phone back on. Basically the phone just died for no reason.
This is very normal in many smartphones. Even iphones have this. Had to do hard reboot for my gf's iphone 4 a few times since she buy it a year ago. so with ICS/Android or whatever still a new OS, its understandable. i dont know what OS you use on your PC/laptop, but if you use Windows, you know this is normal. hehe.
anyway, to my experience, I had this while on SGS2, and Desire while on Beta builds. Never had any trouble with stable builds with Nexus S, Gnex, SGS2, TF, Desire unless I played around with UV/OC. oh and while on AOKP Gnex, i had it once(just remembered now).
I think OP needs to update to 4.0.4. That solved allot of software issues for me. The whole thing with apps installing happens on any android phone if you select the option when setting up.
No no i mean im 99.9% sure i unchecked the box because i didnt want it to download all of my old apps, It downloaded superuser and titanium backup and adfree and all the rest that i didnt want it to lol.
maybe i didnt but im pretty sure i did.
As i said i LOVE this phone and im still happy with it despite these things and have no trouble keeping it for 2 years. Its just a bit dissapointing at the minute with the bugs.
I was just thinking maybe i got one of the "dodgy" devices and would be better of taking it back for a new one.
I will wait for the next update first and see if that fixes the problems.
I dont want to mess flashing custom kernels etc just to mess undoing it all.
by the sounds of it 4.0.3 and 4.0.4 are a big improvement over 4.0.2 so i look forward to get that little you have an update window on my phone
thanks for replies guys. Made me feel a little better
Don't worry, I unchecked the box too and it downloaded everything I had on my Xoom instead of my R2D2 D2. My gnex rebooted randomly and is nowhere near as stable as my Droid 1. And for all of you apologists exclaiming that this is a developer phone, well guess what? 6 weeks in, Googlerola decided "not anymore because CDMA is too hard."
Screw them. I'm going back to a phone that isn't so smart that making calls is beneath it when my contract is up and getting a decent laptop. It's a nice phone when it works but I didn't pay the development community to fix the gross design flaws and production oversights that the people I did give my money to caused to such a device with so much potential. I don't want have to rely on some kid in a basement somewhere to make my $600 phone work. Google/Samsung/Motorola should actually cut these modders a check for cleaning up their messes.
Sent from my Xoom using xda premium
As for 2 and 3, have you ever considered that your phone could be a lemon? I am running stock 4.0.1 and the worst I have experienced was random reboot once a week.
Hey.
I totally get where the OPs coming from. I've got multiple posts on issues I've had. Just some really annoying **** that has really made this a flaky experience. I love this phone just like you man and I'm trying sooo hard not to return it. I've had 3 replacements now and its been like a month. I'm probably just real picky but he's got some points there, why release this if its clearly not ready. I had a 3gs once and I really don't want to go back. The iPhone 4s combined with the latest ios is, and I even can't believe I (me) is saying this but, not toooo bad. I mean, you can actually change your SMS tone now!!! Nice work apple, although other phones have had that option standard for like a billion years! Haha. Anyway, going off track here... yeah dude, I'm not sure if the problems I'm having are just gremlins (which by forums they are) or I have a 4th faulty unit. My other 3 were for the most part probably fine, that's the problem, YOU DONT KNOW!
But by the sounds of it, and I'm sort if happy to hear it is that it is gremlins. I do also want a phone that just f'king works and does what its told. It this phone did that, it would probably be the best phone I've ever owned.
Sent from my Galaxy Nexus using XDA App
zolah said:
1) When i first got the device home and turned it on It auto downloaded like 50 apps that i had installed on my sgs which i didnt want it to do...
2) when ever i scrolled through the app drawer the first 2 pages was fine but when i scrolled to the 3rd page the launcher would force close every time. A battery pull didnt fix the problem either... Luckily i got an update to 4.0.2 about 30 minutes after the device was on which got rid of that problem...
3) Now that im on 4.0.2 sometimes when im leaving the app drawer to go back to the homescreen the launcher will freeze for a few seconds between the zoom out transition so i see half of thr app drawer and half of the homescreen. This happens completely random and i cant reproduce it.
4) I have just been looking on the market and my screen just shut itself off... I couldnt turn the phone back on through the power button and i had to long press the power button to turn the phone back on. Basically the phone just died for no reason.
Click to expand...
Click to collapse
1.) YOU CHOSE to "backup/restore apps to/from Google's servers". It was a check box when setting up the phone.
2.) That is strange, never had this problem. And I didn't make it out the Verizon store w/o the 4.0.2 update so I really was never on anything before that.
3.) I also experience a little lag here and there with 4.0.2. Now that I'm on 4.0.4 I NEVER have a problem with it. Also, install spare parts, set screen transitions and other things like that to "fast" for a little added speed boost.
$.) Nobody likes the sleep of death, fortunately I haven't had this problem. Again, most of my time with this phone I have been on 4.0.4. I highly recommend you upgrade if possible.
martonikaj said:
Stock 4.0.2 GSM version have not experienced a single issue you have.
The one thing I can say is this is a developer phone and its just gonna have bugs. Its probably not what you want to hear but that's kinda how it is : /
Click to expand...
Click to collapse
So not true. I love my GNex, but the reboot issues are very annoying. And it's not because it's a 'developer phone'. If that's the case they need to stop plastering advertisements in major media outlets and TV commercials saying how great the phone is and instead putting disclaimers that it has annoying problems and 'we'll fix them when we get around to it'.
I love nexus phones and Android and I've stuck by them since the launch of the G1, but they still have problems and making excuses for them using these silly arguments is not how they should be addressed. I seriously hope they did not release this phone to the public knowing about these reboot issues. But it seems that way. Either that or the QA process is badly broken.
Sent from my GSM Galaxy Nexus on TMoUS using Tapatalk
I don't understand all the "it's a developer phone" posts.
It is marketed as consumer device and for me, it's a very good consumer phone.
I may be totally lucky, but I never had a single issue with this phone so far.
My Desire HD used to have issues like freezes, gps problems etc. The GNEX does not. At least for me...
I agree that an Iphone is even a little more polished. But that doesn't mean you need to be an android developer or cook custom roms every day to like the GNEX.
Sent from my Galaxy Nexus using xda premium
So I've been having a bit of trouble with my t989 lately, when I try unlocking the phone I will either get a black screen (the lock screen will appear for a split second before going blank if I hit the lock button again) or it won't track my finger movements on the screen. If I manage to unlock the device I end up seeing numerous graphic glitches ranging from the bar at the top w/ the clock/battery meter just gone and the keyboard not working.
I'm runing CM9.0.0 because I had issues with 10.2 (battery wouldn't charge) and 10.1.3 (similar to my lock screen issues but not as severe, still agitating) and also 9.1 which had the same exact issues as I'm having now. I've tried installing with different gapps but the same thing happens. The phone will work for a day or two, then the glitches come. After resetting, everything is normal for a day or so, then it's normal a few hours, etc. The time is getting narrower between reboots and it's a bit frustrating.
Does anyone know what I could be doing wrong, if anything? I flash via twrp and wipe, then install the rom, then install gapps, then reboot, wait 20min, reboot, and go about my business w/ the setup and such. I would be fine going back to 10.1.3 but jellybean roms and snapchat don't really like to work together on this phone for some reason. It's really the only app I use because it seems like the only way my friends want to communicate nowadays, so I'd prefer to stay on ics if possible...
If anyone can give any insight I'd really appreciate it
greenghoul said:
If anyone can give any insight I'd really appreciate it
Click to expand...
Click to collapse
Have you tried using Odin to flash back to stock? That is usually the recommended step if you are having problems with custom ROMs.
And the newest stock is 4.1.2, so at least you wouldn't have to be on ICS.
meekrawb said:
Have you tried using Odin to flash back to stock? That is usually the recommended step if you are having problems with custom ROMs.
And the newest stock is 4.1.2, so at least you wouldn't have to be on ICS.
Click to expand...
Click to collapse
I'll give that a try. Odin is just the program used to root originally, correct? Also, I want to stay on ICS if possible. So after doing that I'm going to try CM9 again and see how that works.
Anyway, the past few days I've been using AOKP mr2 milestone 1 and it's been okay. For some reason the battery life is bad even with juice defender and a task killer taking care of things. In a matter of minutes after clearing tasks I'm down from ~350mb of ram free to 60. Is that normal with that rom?
I'm not sure what to do at this point. I'm not the best with technology but i figured i was smart enough to figure this out...
bump.
I still haven't tried flashing w/ odin yet. Does anyone know where I can find a gingerbread stock rom? I've been looking for a while and can only find the jellybean one. Since I want to stay on ICS what I want to do is go from gingerbread and up to that rather than downgrading from the jellybean stock rom if that makes sense.
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
gt-kingz said:
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
Click to expand...
Click to collapse
You most likely got a bad part. OEM like One plus and xioami are known for using something called product binning. Which means their parts have a higher failure rate then other oems. They also dont make extra parts really so what you got was most likely just a generic screen like you can buy at any shop in China.
Nothing you can really do about it except try a different screen but to be honest I would get a different device and this time dont skip on the price. You get what you pay for and when a good device is cheap there is always a reason. (why do you think most of the owners and mods of XDA run Iphones as their daily drivers and leave android for a hobby)
gt-kingz said:
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
Click to expand...
Click to collapse
As an experiment, try stock OOS and see whether the issue goes away.
i too have this problem cant find any solution anywhere been trying for about a week now arrggghh
ireaper4592 said:
i too have this problem cant find any solution anywhere been trying for about a week now arrggghh
Click to expand...
Click to collapse
tnsmani said:
As an experiment, try stock OOS and see whether the issue goes away.
Click to expand...
Click to collapse
Hey there again. I know my answer is kinda late but I wanted to share my experience. So I tried like 10 different custom ROMs with different Android version. The problem got even worse sometimes.
Anyway a few days ago I installed stock OOS and the problem is fixed now. I could not believe at first, but after excessive testing I am 100% sure now.
Anyone can tell why? Is the stock display driver proprietary?
TBH I always used to use custom ROMs (mostly CyanogenMod and now Lineage. Now on stock rom O feel like everything is better than ever before. Battery life, performance. Some features even offer more customization than custom ROMs.
I always thought the opposite is the case since custom roms advertise things like this. I will definitely stick with stock rom for now!
gt-kingz said:
Hey there again. I know my answer is kinda late but I wanted to share my experience. So I tried like 10 different custom ROMs with different Android version. The problem got even worse sometimes.
Anyway a few days ago I installed stock OOS and the problem is fixed now. I could not believe at first, but after excessive testing I am 100% sure now.
Anyone can tell why? Is the stock display driver proprietary?
TBH I always used to use custom ROMs (mostly CyanogenMod and now Lineage. Now on stock rom O feel like everything is better than ever before. Battery life, performance. Some features even offer more customization than custom ROMs.
I always thought the opposite is the case since custom roms advertise things like this. I will definitely stick with stock rom for now!
Click to expand...
Click to collapse
Thanks for the confirmation. The cheaper screens seem to have an issue which is not faced by the costlier ones. I have found while roaming the threads that sometimes flashing OOS helps. May be a driver issue.
My understanding from what I've read, third party displays needed kernel support.
I paid OP to replace mine - no problems.
Hi!
I'm having a similar issue with my Oneplus 5. Had my screen replaced (new one: OEM) and now it doesn't wake up most of the time either using power button or double tap or fingerprint scanner. I tried everything that I read on forums but nothing worked. Now I seem to have found a solution that I haven't read anywhere yet: I turned off night mode and now it's working as it should. Actually, whenever I want to use any screen adjustment feature like night mode, reading mode etc the screen doesn't wake up. But if I keep the default settings, there is no problem. The issue is definitely the new screen because before that I used night mode all the time (I mean after dark). Now I'm still thinking if I should return the phone to the repair shop and ask for another screen (they offer one year warranty after the repair) or just deal with it... I mean these OEM screen are cheap for a reason (as someone had written here before) and there is no guarantee that the next one will be good, and I don't feel like waiting weeks again for an uncertain outcome, also I can live without said features (gonna miss night mode tho'). Any suggestion? Should I give it a try? Maybe the repair shop made a mistake during assembly? Anyway, I hope this comment will be helpful for those lurking for a solution for a similar problem.
csabatoro said:
Hi!
I'm having a similar issue with my Oneplus 5. Had my screen replaced (new one: OEM) and now it doesn't wake up most of the time either using power button or double tap or fingerprint scanner. I tried everything that I read on forums but nothing worked. Now I seem to have found a solution that I haven't read anywhere yet: I turned off night mode and now it's working as it should. Actually, whenever I want to use any screen adjustment feature like night mode, reading mode etc the screen doesn't wake up. But if I keep the default settings, there is no problem. The issue is definitely the new screen because before that I used night mode all the time (I mean after dark). Now I'm still thinking if I should return the phone to the repair shop and ask for another screen (they offer one year warranty after the repair) or just deal with it... I mean these OEM screen are cheap for a reason (as someone had written here before) and there is no guarantee that the next one will be good, and I don't feel like waiting weeks again for an uncertain outcome, also I can live without said features (gonna miss night mode tho'). Any suggestion? Should I give it a try? Maybe the repair shop made a mistake during assembly? Anyway, I hope this comment will be helpful for those lurking for a solution for a similar problem.
Click to expand...
Click to collapse
Did you try OOS?
OEM screen is not cheap (atleast compared to what is offerred online).
May be you are better off with what you have since you have found a work around. Who knows what you will get next time?
Yea I have same problem it works totally fine on oos but on custom roms it is ****ed up
skymera said:
My understanding from what I've read, third party displays needed kernel support.
I paid OP to replace mine - no problems.
Click to expand...
Click to collapse
How much plz?
Shreeram02 said:
Yea I have same problem it works totally fine on oos but on custom roms it is ****ed up
Click to expand...
Click to collapse
Thank you also for confirming that on OOS there is no issue. Looks like the cheaper of the online replacements have this issue while the costlier ones don't.
Funniest thing is I have a slim ROM backup on 7.1. and that works fine so like what the f--- any ideas people?
gt-kingz said:
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
Click to expand...
Click to collapse
Yes, I have the same issue and I wanted to revert back to Stock OOS, but I just tried Caesium latest kernel, and the display wakeup issue seems to have gone. I'm using Havoc OS 2.3 based on Android Pie.
Guys the latest mad kernal reborn it wakes up all the time
At least for my screen
It used to be worse on all the other kernals
Finally found a solution
I had same problem on custom roms after replacement of display of my oneplus3...i was on oos 5.0.8 i had no issues in that but am a custom rom user and now the solution is flash any rom clean flash not dirty flash and flash gapps then flash any module if you want like magisk and then reboot setup the device and after first boot flash mcd custom kernel and yippeee enjoy... Present am on havoc os with no issues... Try and let me know...
Mohammed Raihan said:
I had same problem on custom roms after replacement of display of my oneplus3...i was on oos 5.0.8 i had no issues in that but am a custom rom user and now the solution is flash any rom clean flash not dirty flash and flash gapps then flash any module if you want like magisk and then reboot setup the device and after first boot flash mcd custom kernel and yippeee enjoy... Present am on havoc os with no issues... Try and let me know...
Click to expand...
Click to collapse
post link to one u have plz
Mail me i have that file..
[email protected]
There is issue while sending here
Mohammed Raihan said:
[email protected]
There is issue while sending here
Click to expand...
Click to collapse
got anyway working fine cheers dude
Even i have the same problem as mentioned above..even i changed my oneplus 3 display
I always prefer custom roms..but screen wakeup issue had made my phone worse...then i tried oos 5.0.8 and it works like a charm...yeah i know its very old android version but no other option though...
Others who have same problem and have no issues going back to oos oreo then go for it...your problem is solved..
---------- Post added at 01:47 PM ---------- Previous post was at 01:43 PM ----------
ireaper4592 said:
got anyway working fine cheers dude
Click to expand...
Click to collapse
Is this kernel working for you!??
Hi. I'm kinda new to xda forums.
When I stream music via youtube, soudcloud, drive, spotify (you got it), the sound is completely ok.
When I play an mp3 however, the sound is distorted.
My AOSP rom is based of lineageos, so I tried my best deleting audiofx via debloat (magisk module) and deleting audio_effects.conf and soundeffects in /system/vendor/lib, yet the problem persists. I'm completely lost.
If anybody knows about this issue or how to fix it, help is appreciated. Thank you!
If you need a logcat, gtfo or anything, I'll be available.
is this your 1st experience with kind of aosp rom?
that's normal.. and that's why i back to stock
nothing can fix this problem. even with viper4android. but neither for stock rom.
leo31 said:
is this your 1st experience with kind of aosp rom?
that's normal.. and that's why i back to stock
nothing can fix this problem. even with viper4android. but neither for stock rom.
Click to expand...
Click to collapse
But is has to be. I used AOSP on a s3 mini and htc one. Both didn't had this issue. Only this one had.
Try disabling google now or whatever that was, you should check the official LoS thread, also i dont reccomed using aosp roms on this phone since HWC is broken so the battery is very poor
CoinKiller said:
Try disabling google now or whatever that was, you should check the official LoS thread, also i dont reccomed using aosp roms on this phone since HWC is broken so the battery is very poor
Click to expand...
Click to collapse
1. About the battery, that is certainly not true. Battery life is greater than expected. If you think about an older phone, then I would agree, but here, even fast charging works (even though it constantly says slow charging, I think that's just a minor bug). In short, no need to complain.
2. What do you mean google now? I think that's dead since 2017. Are you bringing me back to 2015? Nowadays, it's just called my feed, and there is no way disabling it, heck, what is even doing with audio? If you are referring to google assistant, I used it on my previous AOSP phone and nothing happens.
3. Unfortunately there is no talk regarding about the audio in the custom rom forums.
Sorry for being rough and negative, I just want to clarify :victory:. Please don't be mad at me.
The known bugs on my experience are:
Casting
Missing libgdx.so
Sometimes advanced restart does not work
Audio crackling
Keeps telling slow charging
No internet at OTA update (when I actually have)
Some are minor, others are frustrating. Thanks for your reply.
Check google app settings and disable ok google now
Also battery life was trash when i installed the rom for myself
TechGuyOnTechIT said:
1. About the battery, that is certainly not true. Battery life is greater than expected. If you think about an older phone, then I would agree, but here, even fast charging works (even though it constantly says slow charging, I think that's just a minor bug). In short, no need to complain.
2. What do you mean google now? I think that's dead since 2017. Are you bringing me back to 2015? Nowadays, it's just called my feed, and there is no way disabling it, heck, what is even doing with audio? If you are referring to google assistant, I used it on my previous AOSP phone and nothing happens.
3. Unfortunately there is no talk regarding about the audio in the custom rom forums.
Sorry for being rough and negative, I just want to clarify :victory:. Please don't be mad at me.
The known bugs on my experience are:
Casting
Missing libgdx.so
Sometimes advanced restart does not work
Audio crackling
Keeps telling slow charging
No internet at OTA update (when I actually have)
Some are minor, others are frustrating. Thanks for your reply.
Click to expand...
Click to collapse
We've gone quiet on the audio front because we just have to accept it's not good. Changes of this nature happen on ALL devices. E.g. I had Xperia SP years ago. Amazing camera on stock... completely crap in LOS (CM at the time). Galaxy S3 mini... battery. Moto X Play...camera (absolutely important s it has a 21mp camera). They take time to get sorted. Some are done well...others not so well.
It's the high-end mid-range phones that suffer (A5 2017 and the above mentioned) the most. Cheap phones are perfect (LG Spirit 4G and the Alcatel Pixi 3 both work better with LOS based ROMs than they did on stock).
moozer said:
We've gone quiet on the audio front because we just have to accept it's not good. Changes of this nature happen on ALL devices. E.g. I had Xperia SP years ago. Amazing camera on stock... completely crap in LOS (CM at the time). Galaxy S3 mini... battery. Moto X Play...camera (absolutely important s it has a 21mp camera). They take time to get sorted. Some are done well...others not so well.
It's the high-end mid-range phones that suffer (A5 2017 and the above mentioned) the most. Cheap phones are perfect (LG Spirit 4G and the Alcatel Pixi 3 both work better with LOS based ROMs than they did on stock).
Click to expand...
Click to collapse
I understand that this rom is unnoficial and comes with bugs, but the problem is software-wise, which means it can be fixed, even though we need to dig deeper to the root files. Maybe we can recreate or port the samsung drivers used for audio, deleting all traces of audiofx and other minor fixes just to acomplish this. This may sound unrealistic, impossible and bluffing, but the limits are not only from the rom. Maybe we need custom kernel, or who knows.
Heck, there is little to no talk regarding this issue, so I presume some don't have this issue which could mean only a handful of devices have, because of revisions, idk.
So to sum it up, it could be fixed, but I guess no one has the time and motivation to do it.
I have such a strange problem, I have never encountered anything similar before - well, in the summer I bought a used Redmi Note 5 4/64, buying it I only knew about it that it is blocked by a Mi account, after removing the lock (thanks to Xiaomi Support <3) I quickly understood why the phone had the bootloader unlocked from the beginning - the phone comes from China, it had Miui 9 global, after blocking BL and uploading miui 10 global you can guess what happened a moment later, that's when I found out where the phone came from xD
It may not be that important, but I am writing so that you know more or less how much this phone has gone through, and now to the point - in its current state it is practically unusable, no matter if I am installing the official Miui, a custom Pixel Expierience type, Havoc etc., even changing the kernel does not change anything, the phone lags mercilessly, every now and again it hangs even when navigating the interface itself, and when I turn on some app of the Play store type, sir, I will prepare the tea before it all moves, and it happened almost all the time - even the first system startup after a fresh installation looks like this, and I wrote "cannon" because for unknown reasons (and this is the strangest part) after turning it off for a few days and after these few days of trying again to install Miui everything started walking as lively as it should, zero lags, cuts, everything is beautiful, but by the time. It's been about two weeks and all these problems have returned, even TWRP thinks for a long time before anything happens, someone can meet something like that?
To be honest, I have no ideas for this phone, it doesn't heat up, you can't see anything wrong with it, but 90% of the time it goes worse than Moto G3, I never believed in such things, but is it possible for it to happen to some physical damage to some components, and that's where all this comes from? Or maybe these Chinese versions work badly with systems other than Chinese? Because beyond general efficiency, everything else works as it should, camera, speaker, screen, etc.
And one more thing - every custom rom based on Android Pie installs in TWRP for half an hour, it goes very slowly, I don't know if it should be like that.
Rayekk said:
I have such a strange problem, I have never encountered anything similar before - well, in the summer I bought a used Redmi Note 5 4/64, buying it I only knew about it that it is blocked by a Mi account, after removing the lock (thanks to Xiaomi Support <3) I quickly understood why the phone had the bootloader unlocked from the beginning - the phone comes from China, it had Miui 9 global, after blocking BL and uploading miui 10 global you can guess what happened a moment later, that's when I found out where the phone came from xD
It may not be that important, but I am writing so that you know more or less how much this phone has gone through, and now to the point - in its current state it is practically unusable, no matter if I am installing the official Miui, a custom Pixel Expierience type, Havoc etc., even changing the kernel does not change anything, the phone lags mercilessly, every now and again it hangs even when navigating the interface itself, and when I turn on some app of the Play store type, sir, I will prepare the tea before it all moves, and it happened almost all the time - even the first system startup after a fresh installation looks like this, and I wrote "cannon" because for unknown reasons (and this is the strangest part) after turning it off for a few days and after these few days of trying again to install Miui everything started walking as lively as it should, zero lags, cuts, everything is beautiful, but by the time. It's been about two weeks and all these problems have returned, even TWRP thinks for a long time before anything happens, someone can meet something like that?
To be honest, I have no ideas for this phone, it doesn't heat up, you can't see anything wrong with it, but 90% of the time it goes worse than Moto G3, I never believed in such things, but is it possible for it to happen to some physical damage to some components, and that's where all this comes from? Or maybe these Chinese versions work badly with systems other than Chinese? Because beyond general efficiency, everything else works as it should, camera, speaker, screen, etc.
And one more thing - every custom rom based on Android Pie installs in TWRP for half an hour, it goes very slowly, I don't know if it should be like that.
Click to expand...
Click to collapse
Have You try format data?
Shadow337 said:
Have You try format data?
Click to expand...
Click to collapse
I tried everything, I changed the system many times, I tried MIUI 9, 10, 11, each of them works just as badly, today I installed Havoc 2.9 and the phone works relatively well, still not quite as it should, but it is simply possible to use. I still care about working MIUI the most, but every version hangs on the Setup Wizard, I tried the global and CN versions, I still have no idea why it does not work correctly.
Pixel Experience also works, but only for the first few minutes, then problems with google play etc. start, Havoc is the first system that can be used on this phone, but again, I just want to use MIUI
Rayekk said:
I tried everything, I changed the system many times, I tried MIUI 9, 10, 11, each of them works just as badly, today I installed Havoc 2.9 and the phone works relatively well, still not quite as it should, but it is simply possible to use. I still care about working MIUI the most, but every version hangs on the Setup Wizard, I tried the global and CN versions, I still have no idea why it does not work correctly.
Pixel Experience also works, but only for the first few minutes, then problems with google play etc. start, Havoc is the first system that can be used on this phone, but again, I just want to use MIUI
Click to expand...
Click to collapse
Have You done exactly FORMAT data? Not just wipe and install other system
Because if yes, u can have hardware problems and u should go to spec.
I can say more, that my old redmi 3s half year ago was fast response, now without any changes, only ring!( Because i gave it for my dad ) is lagging as hell, even adding some mods like FDE.AI don't help much
Can you please run some kind of internal memory read/write test using Andro Bech and post the results ?
Sent from my whyred using XDA Labs
Havoc OS 2.8 Fan Edition + Kangaro kernel OC version
@Rayekk
Can You please do the tests ?
Sent from my whyred using XDA Labs
MikiGry said:
@Rayekk
Can You please do the tests ?
Sent from my whyred using XDA Labs
Click to expand...
Click to collapse
What tests? What do you mean?
@Shadow337
Wow
My scores with old Superior OS build and Illusion 4.4 kernel and phone full of dowloaded .pdf"s, tons of photos gets about 1/2 of your score in pretty much every section
I guess its time for a clean flash
Sent from my whyred using XDA Labs
---------- Post added at 12:20 AM ---------- Previous post was at 12:19 AM ----------
Rayekk said:
What tests? What do you mean?
Click to expand...
Click to collapse
Install and run Andro Bench
Sent from my whyred using XDA Labs
I leave here my tought, get the battery checked and or replaced
MikiGry said:
@Rayekk
Can You please do the tests ?
Sent from my whyred using XDA Labs
Click to expand...
Click to collapse
I did the tests, these are the results, what now?
@Shadow337 @SIRKRA It's not the fault of the battery or data formatting, it's memory, but I don't know what to do now
Rayekk said:
@[email protected] It's not the fault of the battery or data formatting, it's memory, but I don't know what to do now
Click to expand...
Click to collapse
If u dont have guarantee, try get out blackplate and unconnect, then connect wires
If doesnt work, try ask local "gold hand" in mobile phones mind.
Rayekk said:
I did the tests, these are the results, what now?
Click to expand...
Click to collapse
That is a absolutely TERRIBLE score. That"s no suprise that your phone is barely working. There is something wrong with hardware.
As suggesed. Try replugging internals of your phone
If no go, then the only way is to replace the motherboard (as i haven"t seen a guide go completely erase the partition table and rebuild it)
Sent from my whyred using XDA Labs
MikiGry said:
That is a absolutely TERRIBLE score. That"s no suprise that your phone is barely working. There is something wrong with hardware.
As suggesed. Try replugging internals of your phone
If no go, then the only way is to replace the motherboard (as i haven"t seen a guide go completely erase the partition table and rebuild it)
Sent from my whyred using XDA Labs
Click to expand...
Click to collapse
I already tried to replug all cables