Related
Mostly I am trying to see if this is an isolated issue with mine that might be fixed by rolling the dice again and re-flashing 2.1, but I'm sure people have interesting anecdotes to share as well.
For me, the ROM gave me severe overheating issues. Like, I would be in a heavily air conditioned room playing a video file, and after 20 minutes even though the outside doesn't feel exceptionally warm, running the internal temp monitor would show 98-100 degrees! This heated area was highly localized in the lower left corner, where according to ifixit the processor rests. Without air conditioning, even simply browsing the internet would cause it to eventually overheat.
To add to that, comparing 1.6 to 2.1 charging speed and general battery life seems to be much better after going back to 1.6. Whereas in 2.1 watching a 20-minute video could cut down my battery by 30 percent even in airplane mode, in 1.6 I lose maybe 5 percent in the same situation.
Of course even in 1.6 I am still having troubles with heat when I am in a hot environment, though I don't know if this is just the nature of running a modern smartphone in 29 degree C (84 F) weather. As an aside, has anybody had overheating issues in hot environments?
Several reasons include:
1 - Utterly crap, slow, useless & innaccurate keyboard
2 - Less icons fit on screen
3 - Only 5 home screen in which you cannot remove/add
4 - Wallpaper does not work properly, instead of filling one screen
it distorts and stretches onto all the other screens...
That's all I can think of now...
100*F after 20 minutes of video playback? That's absolutely normal. In fact it's kinda cool.
I'm back on 1.6 because:
No WMA support in stock or aftermarket players (RockPlayer did work, but that's no good for music)
I prefer the 1.6 keyboard
I like Dell's FB, Twitter and RSS widgets
I want my restricted market apps to be available
I do miss (from 2.1)
The eye-candy
Being able to charge in aeroplane mode (what is UP with that anyway?)
The dialer/contact app is great
Did I mention the eye-candy?
2.1 was very pretty and I am very much looking forward to it in an official ROM. IMHO though, it doesn't provide the functionality I need.
MSigler said:
100*F after 20 minutes of video playback? That's absolutely normal. In fact it's kinda cool.
Click to expand...
Click to collapse
Seriously? I mean, what's the point in having a media tablet if it can't even finish a TV episode without an emergency shutdown? Is this normal for android smartphones in general, or is the streak just badly designed?
gilrad said:
Seriously? I mean, what's the point in having a media tablet if it can't even finish a TV episode without an emergency shutdown? Is this normal for android smartphones in general, or is the streak just badly designed?
Click to expand...
Click to collapse
my guess is that the cpu throttling isnt fully implemented or that it doesnt support hardware decoding.
either way, i feel the 2.1 is pretty buggy, the facebook sync goes funny, the dell rss widget crashes every few hours, and a few more that i cant recall off the top of my head.
waiting eagerly for 2.2 to release.
I have to agree with the other posters...
- New icon spacing is terrible (what a waste of a big screen)
- Old keyboard was better
- Old recent programs menu was better
- Old camera UI was better
- Old desktop (with seperate rooms/wallpapers) was better
If the final OTA update is this bad I'm going to be sticking with 1.6 - and I'll be happy with it.
Updates are supposed to make things better, not worse.
kanej2006 said:
Several reasons include:
1 - Utterly crap, slow, useless & innaccurate keyboard
2 - Less icons fit on screen
3 - Only 5 home screen in which you cannot remove/add
4 - Wallpaper does not work properly, instead of filling one screen
it distorts and stretches onto all the other screens...
That's all I can think of now...
Click to expand...
Click to collapse
Ok all of that is fixed by third party solutions. ADWlauncher rocks
Did anybody ever have trouble with videos in 2.1? I fixed my overheating issue, got it so that I could watch videos as much as I wanted in 1.6. So I went back to 2.1 thinking my biggest gripe was solved, but now, even at 30 degrees C (86 F), the thing restarts maybe ten minutes into a video.
Not sure whats behind this overheating, but i am running 2.1 since it was leaked without any issues, to be fair I have only watched about 30 mins of District 9 but ran fine.
I was really glad to see the back of 1.6, so many awesome apps were unavailable. As the other post mentioned most of the failures of the current 2.1 can be remedied with other istalls. ADW lets you set the ammount of columns and rows of icons, and up to 7 home pages, plus loads of other tweaks, themes and portrait mode.
I was super dissapointed with the new keyboard too, but the HTC multitouch keyboard is awesome and super fast with really good correction too, only thing that doesnt work yet is auto capitolisation as far as I know, and theres various skins to chose from.
For me there was also a noticable speed increase, this with proper multitouch meets my gaming needs with psx4droid. The dialer and contacts is a huge improvement, as is the stock gallery. Only thing with that is the proximity hangs sometimes and takes a while for the sceen to light up but thats pretty rare and I think that could be some app interfering...
I for one cant wait for the official 2.1 hopefully sligly ironed out release, this will nicely hold me over till froyo, which better be soon Dell!! Though I understand some people cant be bothered to tweak and play with it, just want it working out of the box. I guess coming from WM im used to that LOL..
So I've had this update for almost more or less than 2 months now, and the speed has improved just a little bit. As we all know, typical samsung software, has some glitches and stutter and all that still occurs, for some reason that I and every users don't know why this still exist. Sometimes I'm watching on Youtube, and the damn video just freezes but you can still hear the audio. But I thought maybe it's just the app so i reset the app by force stopping and clearing the data but the thing still occurs. Camera overtime, has slowed down. I don't know why but this specially occurs on lowlight situations that whenever but not always, i launched my camera, it just lags and stops and gos and it's so annoyingly slow. But most of the time, it is snappy. On the other good side of this story, i like the minimalistic Camera app. It's really just their software. Overall it is indeed snappy, but the consistency is their problem. My storage isn't even full yet, for all we know storages slow down as you're taking it all up. I've scheduled automatic restarts, i think it helped. The fingerprint, ugh i don't even wanna talk about it. I don't know how a oneplus 3 has better fingerprint than samsung's flagship. I mean it's just unreliable, i don't know maybe it's just mine??? I literally had 3 fingers assigned on my one and only right thumb just so that the phone won't have excuses lol. But no, im disappointed. It always has to be two damn tries, thats the least. Bluelight filter is now baked in, which is a very nice feature, atleast for me. Battery, i personally didn't notice any change, but thumbs up to that cos im more than satisfied with it. And as we all know, snapchat camera still sucks not only on this phone but with every android phone. The modes, man are they helpful for those times we really need to save battery. You can customize the resolution of you're desire., well not really but three choices is a lot. 720p,1080p,1440p. Now on the update, I don''t know if you noticed, my resolution is set to 1080p because the mode that is chosen after the update will automatically choose the "optimized" mode which adjusts the resolution and cpu speeds and all that according to the activity you're currenty doing. Which is another good thing. Also, google assistant arrived as well, which great! Interface has some major color and look and design changes. The status bar along with the pull down menu in my opinion has become cleaner and better looking than the previous version. The settings has been better, way way better organized than before. Samsung Pay hasn't yet to come in Canada for some goddamn reason (i know it's not suppose to be here but maybe just maybe someone from samsung reads this ****). I'll leave it here, overall, again, it's faster and snappier, app switches are better almost perfect. But you know, stutters and lags will be there. This is my review for the nougat update on my Sprint Samsung Galaxy S7. Thanks for reading!
I purchased a refurbished Nexus 9 a year and a half ago. I've used ROMs to get it to 7.x and get all the regular updates OTA, currently on the May 5th security update. I've been playing CSR Racing 2 on it for about 9 months. The game has many known issues on Android of all versions and all devices, including crashing to "desktop". This problem is more unique. At almost any given moment in-game I can get a whited out or nearly opaque white, blocky screen overlaying the game image. At the same time, usually, an ear-piercing squeal kicks off. I have the volume at zero at all times, btw.
I've done everything except wipe the thing and re-install. Interestingly, I've had the problem outside the game once, although I can't recall what I was doing at the time. I'm inclined to believe it's the hardware. I actually ordered a Shield, and should be receiving it tomorrow, believing that it's the hardware. Once that is received and the game is up and running - unless I have the same problem on the Shield (meaning the problem's in the game or my profile itself) - I will be wiping the Nexus 9 and finding out once and for all if the thing's toast. In that vein, I have two questions.
One, is there some type of diagnostic I could run to check the limits of this tablet? CSR2 is very taxing on hardware, especially Android, and pushes it very hard. I'm wondering if there's a diagnostic that is a stress tester of sorts that I could use to see if there is any specific problem with the hardware.
Secondly, is there a ROM folks think may have better hardware interfacing for the memory, CPU/GPU, than stock Android? Obviously, I'd like the diagnostic to test the hardware while the new tablet will test whether it's the game/profile. What I won't have tested is the Android OS itself. Any recommendations?
Thanks for your time and any help that you may be able to offer!
Kazz5 said:
I purchased a refurbished Nexus 9 a year and a half ago. I've used ROMs to get it to 7.x and get all the regular updates OTA, currently on the May 5th security update. I've been playing CSR Racing 2 on it for about 9 months. The game has many known issues on Android of all versions and all devices, including crashing to "desktop". This problem is more unique. At almost any given moment in-game I can get a whited out or nearly opaque white, blocky screen overlaying the game image. At the same time, usually, an ear-piercing squeal kicks off. I have the volume at zero at all times, btw.
I've done everything except wipe the thing and re-install. Interestingly, I've had the problem outside the game once, although I can't recall what I was doing at the time. I'm inclined to believe it's the hardware. I actually ordered a Shield, and should be receiving it tomorrow, believing that it's the hardware. Once that is received and the game is up and running - unless I have the same problem on the Shield (meaning the problem's in the game or my profile itself) - I will be wiping the Nexus 9 and finding out once and for all if the thing's toast. In that vein, I have two questions.
One, is there some type of diagnostic I could run to check the limits of this tablet? CSR2 is very taxing on hardware, especially Android, and pushes it very hard. I'm wondering if there's a diagnostic that is a stress tester of sorts that I could use to see if there is any specific problem with the hardware.
Secondly, is there a ROM folks think may have better hardware interfacing for the memory, CPU/GPU, than stock Android? Obviously, I'd like the diagnostic to test the hardware while the new tablet will test whether it's the game/profile. What I won't have tested is the Android OS itself. Any recommendations?
Thanks for your time and any help that you may be able to offer!
Click to expand...
Click to collapse
Hi, Kazz5...
I can't comment on CSR Racing 2, having never played it myself, however the crash symptoms you describe - a largely white, blocky, garbled pixelated screen accompanied with a loud, high pitched banshee like squealing or shrieking noise (it scared the crap out of me the first time it happened ) is certainly something I've experienced myself several times on my Nexus 9.
I've had this spectacular and very noisy crash happen whilst playing Minecraft and whilst playing old (1990s) pinball games via video game emulator apps. But it's also happened when doing something no more taxing on the hardware than checking my emails with Inbox or browsing the web using Chrome.
There doesn't seem to be any logically consistent reason why it happens or under what circumstances are required in order for it to happen. It just happens, suddenly and unexpectedly, and then I find myself hurriedly scrambling around for the power button and long pressing it in order to make the ear piercing howl go away!
I've noticed when it happens my battery is on the low side, usually less than 25%, although I'm uncertain whether this is the actual cause.
----------------------------------
A Possible Solution...
Recently I flashed the Fire-Ice kernel , primarily for the purpose of improving the thin, weedy audio that Andoid Nougat 7.1.1 suffers from on the Nexus 9. (See my post here.)
Now it could just be a complete coincidence or maybe the unique circumstances required to trigger this crash haven't yet arisen on my Nexus 9 since I flashed it - in other words, perhaps I haven't been running it long enough yet, but since flashing Fire-Ice eight days ago, I've had no recurrence of this hard and spectacular crash as you and I have described.
Flashing this kernal though, will cause complications (but not insurmountable ones) when the June OTA security patch is due from Google in around three weeks or so.
----------------------------------
Sorry I couldn't provide a more definitive solution to this problem... or suggest any diagnostics of the type you allude to or suggest solutions regarding CSR Racing 2. If this game is as cutting edge as you suggest, it may be asking more than the now two and half year old Nexus 9 can deliver.
Minecraft, old pinball games and Solitaire card games are about as high octane as it gets for me these days .
Good luck with your Shield and I hope you have a better experience playing CSR Racing 2 on it than on the Nexus 9, and which I suspect you probably will. The Nexus 9 has been riven with a variety of problems ever since it was released back in November 2014, and this seemingly random, complete crashing of the device is unfortunately one of 'em .
Rgrds,
Ged.
I read this reply via email before taking the time to come here and I just want to say thanks for such a thorough sharing of your experience and perspective! You made it clear to me that ordering a Shield was the right thing to do in my case. Interestingly, my Nexus 9 did the squeal/crash in another app soon after I posted this.
My Shield came in, upgraded painlessly, OTA, to 7.0.0 and seems to run much smoother than the Nexus 9 in every way. Yes, the screen is a bit smaller. But, frankly, I'm seeing less pixelation - I have to assume - due to the smaller screen size. The Shield runs cooler (I used to blow on the hot end of the Nexus 9 when holding it in my hands, in it's case, for longer periods of time) and the battery definitely lasts longer.
I will finish moving everything over to the Shield in the coming few days and make up my mind what I want to do with the Nexus 9. With it's large size and 4:3 aspect ratio, I may relegate it to electronic magazine reading - of which I have a few. I saw a reference to running some flavor of *nix on it. That could be interesting. A touch panel for security cameras is a thought, if do-able, as well. I'm sure more thoughts will come up, including getting a more stable Android installed on it.
Please keep me/us posted on your experiences with the Fire-Ice kernel! And thank you again!
GedBlake said:
Hi, Kazz5...
I can't comment on CSR Racing 2, having never played it myself, however the crash symptoms you describe - a largely white, blocky, garbled pixelated screen accompanied with a loud, high pitched banshee like squealing or shrieking noise (it scared the crap out of me the first time it happened ) is certainly something I've experienced myself several times on my Nexus 9.
I've had this spectacular and very noisy crash happen whilst playing Minecraft and whilst playing old (1990s) pinball games via video game emulator apps. But it's also happened when doing something no more taxing on the hardware than checking my emails with Inbox or browsing the web using Chrome.
There doesn't seem to be any logically consistent reason why it happens or under what circumstances are required in order for it to happen. It just happens, suddenly and unexpectedly, and then I find myself hurriedly scrambling around for the power button and long pressing it in order to make the ear piercing howl go away!
I've noticed when it happens my battery is on the low side, usually less than 25%, although I'm uncertain whether this is the actual cause.
----------------------------------
A Possible Solution...
Recently I flashed the Fire-Ice kernel , primarily for the purpose of improving the thin, weedy audio that Andoid Nougat 7.1.1 suffers from on the Nexus 9. (See my post here.)
Now it could just be a complete coincidence or maybe the unique circumstances required to trigger this crash haven't yet arisen on my Nexus 9 since I flashed it - in other words, perhaps I haven't been running it long enough yet, but since flashing Fire-Ice eight days ago, I've had no recurrence of this hard and spectacular crash as you and I have described.
Flashing this kernal though, will cause complications (but not insurmountable ones) when the June OTA security patch is due from Google in around three weeks or so.
----------------------------------
Sorry I couldn't provide a more definitive solution to this problem... or suggest any diagnostics of the type you allude to or suggest solutions regarding CSR Racing 2. If this game is as cutting edge as you suggest, it may be asking more than the now two and half year old Nexus 9 can deliver.
Minecraft, old pinball games and Solitaire card games are about as high octane as it gets for me these days .
Good luck with your Shield and I hope you have a better experience playing CSR Racing 2 on it than on the Nexus 9, and which I suspect you probably will. The Nexus 9 has been riven with a variety of problems ever since it was released back in November 2014, and this seemingly random, complete crashing of the device is unfortunately one of 'em .
Rgrds,
Ged.
Click to expand...
Click to collapse
I wanted to follow-up with you on an experience. I moved to the Shield K1 and have been using it since May. Something's happened with it's charging (I suspect the mini-USB port's connection as it seems to be a weak spot for many). In a pinch, to keep playing my game of choice, I picked up my Nexus 9 and gave it a full charge. I was thrilled since it was working so well. But once it hit 58% charge the weird screen and shrill shrieking returned. Now cornered, I did my best google-fu and uncovered a couple of threads that claimed I could fix my Nexus 9!
It seems many people were having success with removing the back panel (easy), gently prying a small, metal cover off of the battery's connection at the circuit board, unplugging the cable, cleaning connections with isopropyl alcohol, and re-assembling. I found a Youtube link (ifixit, I think?) there that showed how to disassemble the Nexus 9 and I was off! It seems some folks have had this clear up the problem for months and some have had it recur, fixing it again with the same procedure.
I've been using it for days in all states of charge with no return of the problem so far. It's given me plenty of time to get my warranty-replacement Shield enroute. The Shield is still much quicker. But I'm thrilled that there's not some odd gremlin with the Nexus 9. I knew I needed to track this post and your reply down in order to let you know. I hope it helps you and/or someone else!
And thanks again!
Just wanted to bump this thread as I am having the same problem with my N9 and it is steadily getting worse. When this problem first started, it would happen once every 2-3 weeks, usually when I was in Instagram. Now it is happening daily, or multiple times in a day, and sometimes it occurs right after reboot.
I have gotten frustrated enough that I am going to do a clean (reflash) of Pure Nexus, ElemX, etc and see if that has any effect.
Did you read my reply? Cleaning the connector to the battery has fixed my issues - which were constant - for weeks now!
I just got one of these Nexus 9 32GB giving to me by a family member as they upgraded to something else due to the issues with the Nexus 9 . It had the whole deal going on with the white pixelated screen freezing followed by a loud ear busting screeching noise at roughly 50% and 20% battery. I factory reset the tablet and cleaned the cache in recovery then popped back off the tablet and disconnected battery for a min or two, hooked it back up and it runs like butter so far for the last week through the whole cycle of the battery without freezing or screeching. Strange indeed but that fix works for whatever reason.
I have made this thread since a lot of problems which are currently plaguing the POCO F1 are not being discussed properly on XDA. I intend that people will relate to the issues i am posting here which are still unfixed.
1. SLOW CHARGING
The charging speed on the poco has reduced due to thermal throttling. As soon as the battery temperature hits 37, the speed drastically reduces. I can confirm this and i have extensively tested it. I put my poco in front of an air conditioner which reduced battery temperature and the charging bumped upto 2700-2800mah.
Now thermal throttling is good(Especially since its summer season in India) but they should increase a thresholds a bit. My brother used a Asus Zenfone5z and my dad uses a Galaxy S10. On both these sets the charging throttling is not so harsh.
The narrow tolerance range of temperature while charging has lead to extremely bad charging times. This needs to be fixed.
2. Audio Issues ( Especially PUBG)
Try wearing earphones while playing PUBG in a poco and in a different phone. You will instantly notice how muffled/low the sound is in poco. You can barely make out the direction from which the footsteps are coming or the gunshots are being fired. I never realized this untill i played PUBG while wearing earphones in other cellphones. The sound in poco earphones is extremely low. I am not talking about songs in which case the sound loudness seems to be fine. This is mostly the case while playing games.
3. Speakerphone Loudness
I swear the speakerphone loudness had decreased over time. The poco was plenty loud at the start. Now the main speaker loudness just sucks. Whether its watching youtube, netflix or anything else. They have definitely decreased audio volume. Speaker generates considerable amount of heat. Try watching a movie which is already downloaded on your cell and after sometime you will notice that the hottest area to touch of the whole phone is around the main speaker(and not the cpu or gpu).
This makes me wonder whether the main speaker quality was bad right from the start and Xiaomi actually lowered volume to help avoid any issues. In any case, watching youtube is not as fun as before due to low sounding speaker now.
4.Touch Screen Issues
Well what to say about this. I mean there are tons of thread about this already. Xiaomi just release new touch drivers in Miui beta 9.5.6. This means they are still trying to fix touch issues even after almost 9 months of launch. Whether it is multi touch, ghost touch or missed touches. Poco has it all.
The reason is simple. Poor quality touch sensor. Its a hardware issue. Poco had to cut corners somewhere and the touchscreen was the component which took a big hit. The display quality of poco is general is also not good. But i am not complaining due to what all the poco gives at the price point it sit in.
But the touch sensor should not have been compromised with. This is something unacceptable. The general usage experience of the poco due to touch issues is really bad. It frustrates me daily. I have tried tons of custom firmwares too. But then the issue has to be fixed(if at all it can be ever fixed) through vendor firmware. Custom roms or kernels will never fix it. The most major issue of Poco f1-----------still unfixed----its terrible touchscreen.
5. Auto Rotation
I am not sure if many people have noticed this but the auto rotation while using youtube is extremely bad. This is something i won't be able to explain properly but can say this that i am sure many of you find the auto rotation in youtube not to be a seamless experience. This is not the case in other phones.
The accelerometer in general works fine. So i am mostly sure that this must be a software optimization issue.
6. No 4g+ Vodafone
I don't know whats the deal here but poco will never catch 4g+ in Vodafone. At the same spot other phones from nokia, samsung etc does but poco does not. My poco catches 4g+ in Jio but not Vodafone. No matter the spot, the finding remains the same. How can two different manufacturers produce two different results at the same spot even when both the sets in question have lte advanced capability.
I can only assume that there must be some internal issue between xiaomi and Vodafone due to which poco does not support 4g+ in Vodafone. If any1 reading this post has latched onto Vodafone 4g+ successfuly while using a poco please let us know.
P.S.
Using POCO F1 64GB/6GB Indian variant running Miui Global Beta 9.5.17. These issues have persisted through both stable and beta builds and i have tried all.
I have the Global version of the F1 running Stock MIUI 10.3.4.0 locked bootloader and have not encountered any of the issues you are having.
I had touch problems playing PUBG on poco where the screen just froze and i couldn't do anything, locking and unlocking the phone worked sometimes but it still is a problem
Also had thermal throttling playing pubg for more than 20 minutes, fps dropped down and phone got hot
I don't play any games on my phone anymore so these aren't problems for me anymore but there is one big problem and that being the "call echo" , almost everyone who i had a call with complains about hearing their own voice and it's very annoying, so I'd say this is a very important issue and needs a fix immediately
You must be on stable build then. The echo is fixed in beta builds. Can anyone confirm this??? I am not entirely sure but no one is complaining about echo now to me. Was complaining earlier though.
I can confirm for the speaker loudness issue with listening to songs through headphones or earphones the sound is good.
But the speaker is not that loud and i constantly need to keep changing volumes when watching YouTube video through speaker.
In pubg i need to keep the sound at full through earphones then only its usable.Before this Poco i was using Zenfone Max Pro M1 and its sound quality was lot better as compared to poco at least with speakers and in pubg,i never used to keep my sounds more than 60-65 %.
Nice topic!
Anyways I'm completely agree with your point 1,2 & 3.
For Point No. 4 I didn't face any touch issue yet. I bought this device 21 sept. 2018. But I heard that many people have touch related issue. So maybe I'm lucky one.
For Point No. 5, I didn't face any auto rotation issue till date.
For Point NO. 6, I don't have vodafone But I saw a screenshot of poco f1 somewhere, It shown 4g+ at status bar with vodafone network.
I'm on miui global beta 9.5.9
Stransky said:
I have the Global version of the F1 running Stock MIUI 10.3.4.0 locked bootloader and have not encountered any of the issues you are having.
Click to expand...
Click to collapse
You are quite lucky then. Can you share Vodafone 4g+ screenshot?
Ezio553 said:
I can confirm for the speaker loudness issue with listening to songs through headphones or earphones the sound is good.
But the speaker is not that loud and i constantly need to keep changing volumes when watching YouTube video through speaker.
In pubg i need to keep the sound at full through earphones then only its usable.Before this Poco i was using Zenfone Max Pro M1 and its sound quality was lot better as compared to poco at least with speakers and in pubg,i never used to keep my sounds more than 60-65 %.
Click to expand...
Click to collapse
They have definitely reduced speaker volume. Though its not that bad but its lower than before and as you said, while watching youtube etc, slight background nooses ruins the whole experience. It was louder before for sure.
However, the audio in pubg while using earphones...the difference feom other phones is MASSIVE. People need to check other phones to realise what i am talking about.
yogeshsharmagamerz said:
Nice topic!
Anyways I'm completely agree with your point 1,2 & 3.
For Point No. 4 I didn't face any touch issue yet. I bought this device 21 sept. 2018. But I heard that many people have touch related issue. So maybe I'm lucky one.
For Point No. 5, I didn't face any auto rotation issue till date.
For Point NO. 6, I don't have vodafone But I saw a screenshot of poco f1 somewhere, It shown 4g+ at status bar with vodafone network.
I'm on miui global beta 9.5.9
Click to expand...
Click to collapse
Auto rotation is a minor issue in only youtube... Not that major i agree... Lucky you got a touch issue free device.
Touch issues are there thats why they recently released new touch drivers in 9.5.6.
Can you share that screenshot bro??
The only major issue I have for now is audio loudness, I used to listen songs on YouTube at around 80% volume but after recent updates even full volume feels insufficient. Also I feel BT volume has gone down though I am not sure about it.
Touch issues are there for me too but I dont play any game so its a minor thing for me
raman.hwr said:
The only major issue I have for now is audio loudness, I used to listen songs on YouTube at around 80% volume but after recent updates even full volume feels insufficient. Also I feel BT volume has gone down though I am not sure about it.
Touch issues are there for me too but I dont play any game so its a minor thing for me
Click to expand...
Click to collapse
I think they reduced volume so as to generate less heat. Speaker generates good amount of heat. Maybe high volume would have lead to high heat and damage to speaker..
Ghost touch on notch
Ghost touch issue on pocophone especially on the notch area is making me sick. Is it a hardware or a software issue? Ive tried all the suggested troubleshooting methods like disabling the 3fingers slide screenshot but the problem is still evident.
Screen, audio issues
I have read a similar problem of mine on some forums. When using the phone while holding it, the screen works okay (except for some touch delay sometimes on the lower part of the screen). But what agitates me the most is that whenever I lay my phone flat on a soft surface (Bed is the worst), the phone does not respond at all to my touches (except when I heavily, and i mean heavily tap it)
Some say this is a hardware issue, but I was like what? If the screen works fine when held, how come it's a hardware issue? I think the problem is that Xiaomi tied the screen response/touch with the gyro/accelerometer in the software (MIUI 10.2.3.0).
As for the audio, why bother creating a stereo setup if the other one is just a small earpiece? Also the audio channels are also separate, meaning, whenever you play a stereo audio file (with separate instruments per channel), you can only hear one side clearly. Fortunately, there is a fix, its by turning on the mono audio on accessibility settings, but UNFORTUNATELY, this also affects the output on headphones
I hope Xiaomi fixes this soon!
I have not read about this issue with anyone but since the last update I have this strange problem, when ever i go from First space to Second space, the phone freezes and reboots after a few seconds, sometimes it works but sometimes it freezes completely. Secondly FB and other FB related logins dont work.
GamerArc said:
I have made this thread since a lot of problems which are currently plaguing the POCO F1 are not being discussed properly on XDA. I intend that people will relate to the issues i am posting here which are still unfixed.
1. SLOW CHARGING
The charging speed on the poco has reduced due to thermal throttling. As soon as the battery temperature hits 37, the speed drastically reduces. I can confirm this and i have extensively tested it. I put my poco in front of an air conditioner which reduced battery temperature and the charging bumped upto 2700-2800mah.
Now thermal throttling is good(Especially since its summer season in India) but they should increase a thresholds a bit. My brother used a Asus Zenfone5z and my dad uses a Galaxy S10. On both these sets the charging throttling is not so harsh.
The narrow tolerance range of temperature while charging has lead to extremely bad charging times. This needs to be fixed.
2. Audio Issues ( Especially PUBG)
Try wearing earphones while playing PUBG in a poco and in a different phone. You will instantly notice how muffled/low the sound is in poco. You can barely make out the direction from which the footsteps are coming or the gunshots are being fired. I never realized this untill i played PUBG while wearing earphones in other cellphones. The sound in poco earphones is extremely low. I am not talking about songs in which case the sound loudness seems to be fine. This is mostly the case while playing games.
3. Speakerphone Loudness
I swear the speakerphone loudness had decreased over time. The poco was plenty loud at the start. Now the main speaker loudness just sucks. Whether its watching youtube, netflix or anything else. They have definitely decreased audio volume. Speaker generates considerable amount of heat. Try watching a movie which is already downloaded on your cell and after sometime you will notice that the hottest area to touch of the whole phone is around the main speaker(and not the cpu or gpu).
This makes me wonder whether the main speaker quality was bad right from the start and Xiaomi actually lowered volume to help avoid any issues. In any case, watching youtube is not as fun as before due to low sounding speaker now.
4.Touch Screen Issues
Well what to say about this. I mean there are tons of thread about this already. Xiaomi just release new touch drivers in Miui beta 9.5.6. This means they are still trying to fix touch issues even after almost 9 months of launch. Whether it is multi touch, ghost touch or missed touches. Poco has it all.
The reason is simple. Poor quality touch sensor. Its a hardware issue. Poco had to cut corners somewhere and the touchscreen was the component which took a big hit. The display quality of poco is general is also not good. But i am not complaining due to what all the poco gives at the price point it sit in.
But the touch sensor should not have been compromised with. This is something unacceptable. The general usage experience of the poco due to touch issues is really bad. It frustrates me daily. I have tried tons of custom firmwares too. But then the issue has to be fixed(if at all it can be ever fixed) through vendor firmware. Custom roms or kernels will never fix it. The most major issue of Poco f1-----------still unfixed----its terrible touchscreen.
5. Auto Rotation
I am not sure if many people have noticed this but the auto rotation while using youtube is extremely bad. This is something i won't be able to explain properly but can say this that i am sure many of you find the auto rotation in youtube not to be a seamless experience. This is not the case in other phones.
The accelerometer in general works fine. So i am mostly sure that this must be a software optimization issue.
6. No 4g+ Vodafone
I don't know whats the deal here but poco will never catch 4g+ in Vodafone. At the same spot other phones from nokia, samsung etc does but poco does not. My poco catches 4g+ in Jio but not Vodafone. No matter the spot, the finding remains the same. How can two different manufacturers produce two different results at the same spot even when both the sets in question have lte advanced capability.
I can only assume that there must be some internal issue between xiaomi and Vodafone due to which poco does not support 4g+ in Vodafone. If any1 reading this post has latched onto Vodafone 4g+ successfuly while using a poco please let us know.
P.S.
Using POCO F1 64GB/6GB Indian variant running Miui Global Beta 9.5.17. These issues have persisted through both stable and beta builds and i have tried all.
Click to expand...
Click to collapse
Just change ur handset.
or visit nearby mi service center.
Charging issue is happening since june updatea, so I suggeat all of you to go back to may vendor so you can charge your phone as usual
Bought this phone 20 days ago
Bought this phone 20 days ago due to the processor. But now it seems like a mistake.?
Facing ghost touch but it's manageable (I know it's not but the processor...)
I use earphones mostly so no problem with phone speaker. While playing pubg I have to keep sound level at 90% to hear clearly.
Charging... It's charging Faster than my previous phone. I had Lyf Earth 1. Yea I know...
Miui 10.3.6 stable
6/64gb
GamerArc said:
I have made this thread since a lot of problems which are currently plaguing the POCO F1 are not being discussed properly on XDA. I intend that people will relate to the issues i am posting here which are still unfixed.
1. SLOW CHARGING
The charging speed on the poco has reduced due to thermal throttling. As soon as the battery temperature hits 37, the speed drastically reduces. I can confirm this and i have extensively tested it. I put my poco in front of an air conditioner which reduced battery temperature and the charging bumped upto 2700-2800mah.
Now thermal throttling is good(Especially since its summer season in India) but they should increase a thresholds a bit. My brother used a Asus Zenfone5z and my dad uses a Galaxy S10. On both these sets the charging throttling is not so harsh.
The narrow tolerance range of temperature while charging has lead to extremely bad charging times. This needs to be fixed.
2. Audio Issues ( Especially PUBG)
Try wearing earphones while playing PUBG in a poco and in a different phone. You will instantly notice how muffled/low the sound is in poco. You can barely make out the direction from which the footsteps are coming or the gunshots are being fired. I never realized this untill i played PUBG while wearing earphones in other cellphones. The sound in poco earphones is extremely low. I am not talking about songs in which case the sound loudness seems to be fine. This is mostly the case while playing games.
3. Speakerphone Loudness
I swear the speakerphone loudness had decreased over time. The poco was plenty loud at the start. Now the main speaker loudness just sucks. Whether its watching youtube, netflix or anything else. They have definitely decreased audio volume. Speaker generates considerable amount of heat. Try watching a movie which is already downloaded on your cell and after sometime you will notice that the hottest area to touch of the whole phone is around the main speaker(and not the cpu or gpu).
This makes me wonder whether the main speaker quality was bad right from the start and Xiaomi actually lowered volume to help avoid any issues. In any case, watching youtube is not as fun as before due to low sounding speaker now.
4.Touch Screen Issues
Well what to say about this. I mean there are tons of thread about this already. Xiaomi just release new touch drivers in Miui beta 9.5.6. This means they are still trying to fix touch issues even after almost 9 months of launch. Whether it is multi touch, ghost touch or missed touches. Poco has it all.
The reason is simple. Poor quality touch sensor. Its a hardware issue. Poco had to cut corners somewhere and the touchscreen was the component which took a big hit. The display quality of poco is general is also not good. But i am not complaining due to what all the poco gives at the price point it sit in.
But the touch sensor should not have been compromised with. This is something unacceptable. The general usage experience of the poco due to touch issues is really bad. It frustrates me daily. I have tried tons of custom firmwares too. But then the issue has to be fixed(if at all it can be ever fixed) through vendor firmware. Custom roms or kernels will never fix it. The most major issue of Poco f1-----------still unfixed----its terrible touchscreen.
5. Auto Rotation
I am not sure if many people have noticed this but the auto rotation while using youtube is extremely bad. This is something i won't be able to explain properly but can say this that i am sure many of you find the auto rotation in youtube not to be a seamless experience. This is not the case in other phones.
The accelerometer in general works fine. So i am mostly sure that this must be a software optimization issue.
6. No 4g+ Vodafone
I don't know whats the deal here but poco will never catch 4g+ in Vodafone. At the same spot other phones from nokia, samsung etc does but poco does not. My poco catches 4g+ in Jio but not Vodafone. No matter the spot, the finding remains the same. How can two different manufacturers produce two different results at the same spot even when both the sets in question have lte advanced capability.
I can only assume that there must be some internal issue between xiaomi and Vodafone due to which poco does not support 4g+ in Vodafone. If any1 reading this post has latched onto Vodafone 4g+ successfuly while using a poco please let us know.
P.S.
Using POCO F1 64GB/6GB Indian variant running Miui Global Beta 9.5.17. These issues have persisted through both stable and beta builds and i have tried all.
Click to expand...
Click to collapse
Bought this phone around 10 months ago, never had any issues except number 6.
I NEVER had 4G+ on my Pocophone in my region (thailand, Truemove carrier), i think this is due to the Pocophone only supporting CA(4G+) on bands 3+40 or 40+40/3+3 (i think), my carrier uses B1+B3+B8 or any of that in 2CA so yeah, pocophone's CA(4G+) capablity is extremely limited due to it only being able to do CA in very limited bands (it will do CA fine with indian carriers i heard)
About number 1, I charge my phone overnight anyways so I am not in a hurry and when i wake up it will always be at 100% anyways. I also sometimes charge it outside of my home with my QC3.0 powerbank, and yes since I am in thailand the heat does affect me and it slows charging down to around 12-16 watts instead of full 18 watts, but really charging is a non issue
No touch issues on my unit aswell, had a great experience from the start of using this phone in terms of touch, guess i got lucky or the earlier pocophone models (9/2018,10/2018) had higher quality digitizers, I also heard problems about screen bleeding which I think you didn't mention specifcally , my screen has a VERY minor bleed around the bottom left corner of the screen
One display issue which I think not alot of users face but I do, is image retention. I experienced this myself when looking at something static for a long time with this brightness (70%-85%), it's noticeable in the "dark grey" kind of screens which is the default dark mode setting in Pixel Experience (the rom that I've been using for 7 months now, don't really like how menus are placed in MIUI, or does that just have to do with me using pixel experience for so long), the image retention is not like some extreme burn-in you see on amoled displays, just a very hard to see but "it's there" kind of thing. The image retention will usually solve itself if you leave your phone's screen off for a decent amount of time (image retention =/= burn-in) and this can happen with any brightness setting i found out, i once left the phone's screen on for like 24+ hours mirroring the screen to my pc with the minimum brightness (i see the screen on my pc anyways so no point in leaving the screen on anything but minimum brightness) and yes it did have image retention once i was done using it after 24+ hours, i turned the brightness up and instantly saw retention in the screen of static menu elements.
Of course that's a bit extreme of a use case, not many people are gonna leave a phone screen on for 24+ hours, but yes it can happen lol
Headphone/audio issues: never experienced bad audio in my pocophone F1 when listening to music (I use PowerAmp and it's high-res setting of 24bit/96KHz) it sounds amazing from this phone, but when playing games the audio is definitely sub-par compared to phones I had before.
Another problem I have is random freezes with MIUI, I solved this by using pixel experience and i really love this rom so this is a non-issue for me since I don't see myself returning to MIUI until MIUI 11 comes out or something like that.
1. SLOW CHARGING
true and frustrating
2. Audio Issues
didn't face it
3. Speakerphone Loudness
it's just a software thing, using any aosp based rom or custom kernel solves it
4.Touch Screen Issues
didn't face it
5. Auto Rotation
what?
Vodafone 4g+ /VoLTE Solution
I had mine fixed . Try calling the customer care of Vodafone..Tell them your problem of VoLTE not Showing..They will fix that for u..in 30 mins !! Hope this helps ??
Hi there! I just got a Tab S7 (the "basic" LCD model. not the plus). I update to Android 11, factory resetted it, debloated like crazy with ADB. I'm coming from a Tab S4 that had the exact same debloat and optimizations steps.
I use this tablet ONLY to play some games. I mostly play Rules Of Survival.
Well, I'm really disappointed. The game still lags with the same graphical settings I was using on the tab S4. I was expecting to get a decent amount of free ram after debloating it but it's not that better if compared with the S4. Don't get me wrong, the game runs smoother than on the S4, but from a Snapdragon 865+ I was expecting a lot more. The super crowded scenes now are pretty playable, but it still hangs a bit quite often. I have tested it with different internet connections, same results. Lowering the graphis did not help on the S4 and it does not help on the S7.
A weird issue is related to the touch screen sensitivity. It's usually pretty good but sometimes when I have to aim precisesly with my right thumb, the whole movement of the crosshair feels super slow and inaccurate.
You know what's strage? I have tested the same game on my OnePlus Nord and I had no issues at all. A friend of mine on the latest and crappiest iPad has a bettere gaming experience than mine, for half the price.
Any hint before returning it?
I'm having some strange issues with my Galaxy Tab S7+ as well, mostly touch-related. But in overall, the tablet's performance is really disappointing. I was expecting much more from this SD865-based tablet compared to my previous one, Pixel C.
Taps are not being registered accurately. Sometimes it gets registered prematurely (before my finger actually landed), and in other cases late or not registered at all.
From time to time, the tablet would suddenly lose responsiveness, dropping or delaying a good amount of touches, that even holds and drags may break into several separate taps. In rare cases, the tablet would stop responding to touches and generates a few taps on its own at the edge of the screen (the taps are generated at one particular spot and the spot is random, but it tends to be near the navbar if brought up).
As I mostly play rhythm games in which every touch matters, such issues can be devastating. The issue is becoming more frequent since Android 11 update, with average frame rate being much worse compared to Android 10. It seems these touch-related issues become more apparent when the games start to stutter (lower frame rate).
I suspect the issue might have something to do with System UI. On Android 10, when the touch issue happens, it affects everything as I can also reproduce the ongoing issue inside Multi-Touch Test app. On Android 11, things become a bit different, as when the touch issue starts to happen in a game, it seems to affect only that game and the System UI (that it takes about 2-3 swipes just to bring out the navbar), and the impact to other apps, including Multi-Touch Test, is less than before.
I don't know what might be contributing to the touch-related issues. But the tablet's stock firmware is often seen spamming logcat at an incredible rate implying a huge amount of processing is going on behind the scenes, and from the looks of it, a good amount of the logs were audio effect related so it's possible that certain audio enhancements might be very demanding.
EDIT: I also suspected Game Optimization Service might be involved in this. However, that service is part of the core system components, with related code inside system_server, that it's not possible to disable it completely. Although I've taken out the apks systemlessly through Magisk modules (root), it only made sure the service would never be able to launch again, yet its usual routines (scanning apps and detect whether the app is a game) continues in the background, which is done by system_server on behalf of GOS.
PS: It appears Samsung is indeed not happy with people disabling these services, that they're going great lengths to deter people from doing so.
LSS4181 said:
I'm having some strange issues with my Galaxy Tab S7+ as well, mostly touch-related. But in overall, the tablet's performance is really disappointing. I was expecting much more from this SD865-based tablet compared to my previous one, Pixel C.
Taps are not being registered accurately. Sometimes it gets registered prematurely (before my finger actually landed), and in other cases late or not registered at all.
From time to time, the tablet would suddenly lose responsiveness, dropping or delaying a good amount of touches, that even holds and drags may break into several separate taps. In rare cases, the tablet would stop responding to touches and generates a few taps on its own at the edge of the screen (the taps are generated at one particular spot and the spot is random, but it tends to be near the navbar if brought up).
As I mostly play rhythm games in which every touch matters, such issues can be devastating. The issue is becoming more frequent since Android 11 update, with average frame rate being much worse compared to Android 10. It seems these touch-related issues become more apparent when the games start to stutter (lower frame rate).
I suspect the issue might have something to do with System UI. On Android 10, when the touch issue happens, it affects everything as I can also reproduce the ongoing issue inside Multi-Touch Test app. On Android 11, things become a bit different, as when the touch issue starts to happen in a game, it seems to affect only that game and the System UI (that it takes about 2-3 swipes just to bring out the navbar), and the impact to other apps, including Multi-Touch Test, is less than before.
I don't know what might be contributing to the touch-related issues. But the tablet's stock firmware is often seen spamming logcat at an incredible rate implying a huge amount of processing is going on behind the scenes, and from the looks of it, a good amount of the logs were audio effect related so it's possible that certain audio enhancements might be very demanding.
EDIT: I also suspected Game Optimization Service might be involved in this. However, that service is part of the core system components, with related code inside system_server, that it's not possible to disable it completely. Although I've taken out the apks systemlessly through Magisk modules (root), it only made sure the service would never be able to launch again, yet its usual routines (scanning apps and detect whether the app is a game) continues in the background, which is done by system_server on behalf of GOS.
PS: It appears Samsung is indeed not happy with people disabling these services, that they're going great lengths to deter people from doing so.
Click to expand...
Click to collapse
I have deeply read thru your thread this morning. This is ways beyond disappointing. I have ordered and iPad air 4. But guess what? I cannot transfer my rules of survival account from Android to iOS. I will have to return that as well.
The only tablet with at least 6gb of ram available is the Lenovo something pro blabla but it spots a lower Snapdragon with a higher price tag than the galaxy S7.
I will have to stick my galaxy Tab S4 still for a while. I have debloated it like crazy (I just did not remove the game crap system). It will be still kind of bearable for some more time.
Any hint on some alternative android tablets?
exnokiafan said:
I have deeply read thru your thread this morning. This is ways beyond disappointing. I have ordered and iPad air 4. But guess what? I cannot transfer my rules of survival account from Android to iOS. I will have to return that as well.
The only tablet with at least 6gb of ram available is the Lenovo something pro blabla but it spots a lower Snapdragon with a higher price tag than the galaxy S7.
I will have to stick my galaxy Tab S4 still for a while. I have debloated it like crazy (I just did not remove the game crap system). It will be still kind of bearable for some more time.
Any hint on some alternative android tablets?
Click to expand...
Click to collapse
If it's not about 120Hz display I think some other tablets, including older generation ones, might be good choices.
It's just that I don't think I'll ever pick another Samsung product anymore thanks to the GOS fiasco (app/service apks that would be automatically re-enabled by watchdogs placed deep inside system core processes by Samsung themselves).
As for going for an iPad... sadly, thanks to g00g13 & 4pp1€ intentionally placing barriers on doing cross-platform account transitions (at least losing access to paid/non-paid in-game currencies), it certainly won't be easy to switch.
(PS, nowadays it's not even easy to migrate on the same platform. Restoring a backup, such as those done using Titanium Backup or Migrate from an old device to a new one would not work and I still need to go through the usual transfer procedures from the old device, which varies among games).
Honestly, I don't think gamers are the main audience of Samsung devices, considering how much efforts they put on security stuffs such as Knox (actually, Knox was what led to Google introducing the Safety Net, and all the problems that stemmed from it). The tablet itself appears to be more focused on office/productivity works, as features like S-Pen, air gestures, DeX are more useful for those tasks than gaming.
EDIT: As for touch issues, if you're rooted this thread (from Essential Phone forum) might be interesting. CPU and GPU governors, as well as affinities, might play a role in the issues we're having. Turned out the stock kernel has a good amount of options to tweak via SmartPack Kernel Manager.
Here I don't have any problem. When you update it, you already enter on recovery mode, wipe data, cache and fix apps ? I get little issue with my battery after update, but I perform recovery mode and do wipes and fix apps, finally all problems I get is solved.