[Q] Problems since upgrade to 4.4.2 - HTC One Mini 2

Anyone else experiencing any issues since upgrading to 4.4.2? My phone is Vodafone branded, and ever since I upgraded the bluetooth seems to have severely suffered.
It struggles with disconnecting from one device and connecting to another, quite often it can't find the device at all and will require a reboot before it can see the device.
I'm also finding that the top button to turn on the display will intermittently not work. I don't think it's a hardware fault as it always works eventually.
Also the battery life seems to have taken a significant hit since this update, I'm at about 10% by each evening.

Upgrade? The mini 2 was born with 4.4.2... Are you sure you're talking about the mini 2?

There have been a few updates for the mini 2 but not too sure if there was any major version updates.

Related

[Q] overheating + battery drain problem, and sensor problem.

I have read lots of posts relating to call-drop, battery problems, and overheating at Android Forum in Korea. (GalaxyS is originally manufactured by a Korean Company, Samsung).
But I do not see many threads regards these matters. Does anyone experience this kind of problem yet?
1. Battery drain - if I charge it fully, it cannot go last one day so I need to re-charge it before coming home. I think this might be a problem of the current firmware and expect to be solved in froyo stage.
2. overheating - this one is the problem i am currenty experiencing.
regularly, my captivate is 25~30 degree' but when i use a small app, then firsly it turns to be a warm stage and sometimes it is over 105~110 f'. I did not have this problem before, but i think this is a problem of lag-fix. (because the official forum in Korea said that lag-fix occurs overheating problem in M110s so i think it might be the same thing to captivate)
3. call-drop
i think this is a problem of the sensor loacting left-top. since it is too sensitive or not too sensitive, sometimes the captivate assumes the call is already ended even i am still on the phone. OR it does not have an auto-lock feature, so I push the end button unexpectly.
Does anyone experience this?
OR
MY PHONE IS DEFECTIVE?????????
I am kinda so tired to find solutions of these problems every day. I used to use Iphone 3G, and 3GS but I did not feel so stressful like the situation.
If it is a problem from the lagfix, then How can I reset this thing to the factory default one??
(just one click JF6 thing? or change something entirely?)

[Q] A2DP and Mobile Data problem with official ICS ROM

Hey guys! This is my first post on XDA, though I've been using it for quite a while.
I'm not exactly looking for answers/solutions, but rather sharing my problem and see if someone else is having them too.
I have a Latin American version of the I91000 (TTT). I recently upgraded to ICS using the official firmware from Samfirmware (UHLPE). At first everything looked great. The performance improvement was noticeable from the first bootup. Not only was it faster, but the intro video was far smoother and looked nicer. The general UI changes are very nice, and I did notice an improvement in battery life.
However, I've been experiencing a couple of glaring issues that really mared the experience enough to make me want to go back to Gingerbread, which I will probably do.
These are the problems:
1. The mobile data connection is very unstable. Sometimes it just doesn't load anything, and sometimes I lose the signal altogether. The 3G/H/H+ icon disappears and all. I never had this problem in GB during the 6 months I've had this phone.
2. The Bluetooth audio connection also has problems. It's now more unstable and susceptible to interference, and the lag is also much more noticeable now. It was about .5 seconds before, but now it's more than a full second.
But that's not the worst issue. The media remote control functions just stopped working altogether, namely, the |<< , >>| , >/|| buttons on my headset. I have a Nokia BH505 Bluetooth headset, and I didn't have any of these problems before either.
So that's it. I would like to know if someone else is experiencing one or both of these issues. I'll also check the Samfirmware forums to look for replies on the matter. Thank you for your feedback.

[Q] HTC One is suddenly much slower after GPE conversion

Hello all, this is my first post on Android Central! I wanted to see if anyone had similar problems after converting their T-Mobile HTC One to GPE. I've been tinkering around with my phone for the last few weeks, first by rooting my One and trying out different roms, including a 4.3 GPE rom. When using this rom in particular, my phone would perform beautifully early in the day and in the evening (or sometimes after 50% battery) swiping between the home screen, scrolling, and opening apps would be noticeably slower and less buttery. Resetting the phone would normally correct the issue, at least until the next day.
Needless to say, this was the only downside of running stock Android so I decided to try out full GPE conversion to see that fixed the issue. I did a full wipe and ran the OEM RUU before rerooting, went S-OFF, and finally converted my phone to GPE. I installed the OTA update and everything was working fine until the slowness issues returned, essentially the same as before I converted?
Has anyone else had this problem? Is this being caused by a particular app or process? What kind of screenshots/logs would be helpful to find out what the issue is?
I have a TMO version and a few months ago i did the GPe conversion and mine is working very well. No sluggishness or or battery issues.
josetheman said:
Hello all, this is my first post on Android Central! I wanted to see if anyone had similar problems after converting their T-Mobile HTC One to GPE. I've been tinkering around with my phone for the last few weeks, first by rooting my One and trying out different roms, including a 4.3 GPE rom. When using this rom in particular, my phone would perform beautifully early in the day and in the evening (or sometimes after 50% battery) swiping between the home screen, scrolling, and opening apps would be noticeably slower and less buttery. Resetting the phone would normally correct the issue, at least until the next day.
Needless to say, this was the only downside of running stock Android so I decided to try out full GPE conversion to see that fixed the issue. I did a full wipe and ran the OEM RUU before rerooting, went S-OFF, and finally converted my phone to GPE. I installed the OTA update and everything was working fine until the slowness issues returned, essentially the same as before I converted?
Has anyone else had this problem? Is this being caused by a particular app or process? What kind of screenshots/logs would be helpful to find out what the issue is?
Click to expand...
Click to collapse
Had some issues because I triggered some developer options.. I don't know which it was.. but try to turn them off! ALL of them! Then look if you still experience such performance problems
Thanks for all of your comments. I spent last night deleting apps I didn't use to see if I could find a culprit. As it turns out, the CPU management option in Battery Doctor was turned on. I never thought of turning this off and, frankly, Battery Doctor did little for my battery life in general. I uninstalled the app completely, rebooted, and have actually seen a better battery life and NO sluggishness whatsoever all day today.
Hopefully this wasn't just a temporary solution to my problem!
Good follow up. Keep an eye on it and if its ok for a few days you "should" be out of the woods.

Galaxy Tab S 8.4 wifi lollipop upgrade is rubbish

After a lot of issues i just ended up downgrading back to kitkat on my galaxyTab S8.4 wifi, from lollipop.
Issues i was experiencing were:
-totally unreliable battery meter & performance. - Could read 100%, and 10 mins later would read 5% and turn off.
-screen flicker - lines would flicker across the screen randomly, usually before the device crashed.
-Rebooting - the device would randomly reboot, but usually happened 3-4 times per hour, making the device useless.
-screen freeze - the touchscreen would stop working randomly, usually before it rebooted itself.
Ive just gone back to kitkat (voided my warranty in the process) and its still to be seen if downgrading resolves the battery issue, but already the screen flicker seems to be gone. Il update after a day or two use.
Very annoyed with Samsung for releasing an unusable update that rendered the tablet useless & the solution was to load a rom myself, voiding the warranty.
Have experienced absolutely none of the issues you refer to on my SM-T805.
Runs just fine for me.
Downgrading to KITKAT doesn't void your warranty.
ashyx said:
Have experienced absolutely none of the issues you refer to on my SM-T805.
Runs just fine for me.
Downgrading to KITKAT doesn't void your warranty.
Click to expand...
Click to collapse
I agree with ashyx , my tab s runs fine n dandy , sounds like you have a faulty unit schmintan
I don't know if your tablet has Knox, you can see status if you go under status in about device, usually, and see if it is "official" or not.
Far as what you did, before you went and loaded a ROM, I would have done a factory reset. Quite often, settings/apps brought over from a previous version cause issue. I don't care if the upgrade tells you too or not, read through the forums and you'll see it littered with people stating how they noticed a massive improvement after their upgrade once they factory reset. Yes, it does suck, but these days Android makes it very easy to do.
schmintan said:
After a lot of issues i just ended up downgrading back to kitkat on my galaxyTab S8.4 wifi, from lollipop.
Issues i was experiencing were:
-totally unreliable battery meter & performance. - Could read 100%, and 10 mins later would read 5% and turn off.
-screen flicker - lines would flicker across the screen randomly, usually before the device crashed.
-Rebooting - the device would randomly reboot, but usually happened 3-4 times per hour, making the device useless.
-screen freeze - the touchscreen would stop working randomly, usually before it rebooted itself.
Ive just gone back to kitkat (voided my warranty in the process) and its still to be seen if downgrading resolves the battery issue, but already the screen flicker seems to be gone. Il update after a day or two use.
Very annoyed with Samsung for releasing an unusable update that rendered the tablet useless & the solution was to load a rom myself, voiding the warranty.
Click to expand...
Click to collapse
Hi, have you solved The issue downvrading? I have The same problems you described.
same issues
White lines then crashes, battery life under 4 hours,
Sounds like a case of broken hardware or one seriously misbehaving application. And in general, if nothing works, I'd recommend to do a full factory reset of the tablet after the lollipop upgrade (erasing all of your data and settings of course). The only issue that concerns me about lollipop is the increase in battery drain at idle. You need to hunt down for the apps that keep your tablet awake. But spend a full battery charge in minutes? No way. Impossible. Get the tablet replaced.
I've been having the same issues. When I did a clean install, the tablet worked fine. However, as I install various apps, the issue begins again. I haven't been able to identify a particular app.
Going to try Marshmallow and see if it's more stable
If you both post your apps list that might be interesting see if you both share an app?
bigaloz said:
I've been having the same issues. When I did a clean install, the tablet worked fine. However, as I install various apps, the issue begins again. I haven't been able to identify a particular app.
Going to try Marshmallow and see if it's more stable
Click to expand...
Click to collapse
nope. no stable mm roms yet.
Well, I've upgraded to Marshmallow and whilst it took a few goes to get it up and running properly (problems with installing gapps) it's working fine (mostly) now.
I've only had it running for a day but it is much smoother and quicker than kitkat and lollipop. So far there hasn't been any random shutdowns. It's too early to say whether battery life is better.
The only problems I've had is the camera isn't working (haven't bothered to look for a fix yet) and auto rotation doesn't work all the time.
I'll keep you up to date on how things go but so far I'm very pleased with the upgrade. I might now upgrade my 10.5
schmintan said:
After a lot of issues i just ended up downgrading back to kitkat on my galaxyTab S8.4 wifi, from lollipop.
Issues i was experiencing were:
-totally unreliable battery meter & performance. - Could read 100%, and 10 mins later would read 5% and turn off.
-screen flicker - lines would flicker across the screen randomly, usually before the device crashed.
-Rebooting - the device would randomly reboot, but usually happened 3-4 times per hour, making the device useless.
-screen freeze - the touchscreen would stop working randomly, usually before it rebooted itself.
Ive just gone back to kitkat (voided my warranty in the process) and its still to be seen if downgrading resolves the battery issue, but already the screen flicker seems to be gone. Il update after a day or two use.
Very annoyed with Samsung for releasing an unusable update that rendered the tablet useless & the solution was to load a rom myself, voiding the warranty.
Click to expand...
Click to collapse
Hola, which procedure did you follow to downgrade OS to kitkat? I m right now on official Lollipop without root.
I had a notion that even if we downgrade to kitkat screen flicker will remain.
Awaiting your reply- thanks in advance
schmintan said:
Very annoyed with Samsung for releasing an unusable update that rendered the tablet useless & the solution was to load a rom myself, voiding the warranty.
Click to expand...
Click to collapse
If your issues are caused by Lollipop wouldn't everyone one else with Lollipop experience the same issues? I have absolutely none of the problems you mentioned and I have had Lollipop installed since it was first made available for this tab. Seems to me you more then likely have a hardware problem. You said you were going to update in a day or two but you haven't so far. I'm curious if downgrading solved your issues.
Sent from my SM-T800 using XDA-Developers mobile app
schmintan said:
After a lot of issues i just ended up downgrading back to kitkat on my galaxyTab S8.4 wifi, from lollipop.
Issues i was experiencing were:
-totally unreliable battery meter & performance. - Could read 100%, and 10 mins later would read 5% and turn off.
-screen flicker - lines would flicker across the screen randomly, usually before the device crashed.
-Rebooting - the device would randomly reboot, but usually happened 3-4 times per hour, making the device useless.
-screen freeze - the touchscreen would stop working randomly, usually before it rebooted itself.
Ive just gone back to kitkat (voided my warranty in the process) and its still to be seen if downgrading resolves the battery issue, but already the screen flicker seems to be gone. Il update after a day or two use.
Very annoyed with Samsung for releasing an unusable update that rendered the tablet useless & the solution was to load a rom myself, voiding the warranty.
Click to expand...
Click to collapse
i have found a fix for the white lines. but you need root
share the fix
zalso said:
i have found a fix for the white lines. but you need root
Click to expand...
Click to collapse
what is the fix? please share! i have root, i have the problem, and it is super irritating!
Fix
brio09 said:
what is the fix? please share! i have root, i have the problem, and it is super irritating!
Click to expand...
Click to collapse
here buddy http://forum.xda-developers.com/gal...-flicker-screen-freezes-t3374336#post66951302
I have the 8.4 and 10.5, both are stock running lollipop and neither device has had the issues you are having!
Sent from my SM-T800 using XDA-Developers mobile app
screen freeze + screen flickers bright flash bars
random reboot, screen freeze and crazy screen flickers with bright flash bars), which occurred when it had low battery
(may be not relevant but have also just given up on firefox for chrome!)
this seems to sum up my experience in the last week or so, I thought I was heading for some hardware failure but parallels what others are reporting....
SM-T705Y running 5.0.2 (LRX22G)
looks like update from 20th May which would be around when this started

Question Device rebooting during calls [Exynos)

It has been a very long while since this is happening. I don't even remember if this was happening at the very beginning, in February when I bought it but it has been at least 4 months since I remember. I don't do much calls over the SIM network but I talk a lot over Messenger, Teams and Whatsapp. It is happening randomly but quite often. I can hear the other person's voice dropping like it simply dissappears suddenly. First I hear a few milisecond crack and then it dissappears for a second or two during Messenger. When I am doing Whatsapp calls it does the same and sometimes even drops the call and shows that I got Mic problems (Whatsapp shows that ). And when I am in a Teams call the phone might even reboot during talking. It is not hardware because when I was on Android 11 before the Update, it had similar problems but instead of rebooting the phone it simply freezes and makes a glitchy noise continuously until I reboot the phone. If I dont rboot it, The microphone simply won't work. When I am on a call via the Bluetooth Buds I don't have this issue. Both microphones work fine. The bottom one and the top ones.
It feels like it is the baseband....or whatever it is called... I don't want yet to put a cutom ROM as I lose the warranty. It is an Exynos version with 512 Gb space and I am looking for a solution first, and if I find out that a different ROM will fix this, I am OK but if I find out that it is hardware I would rather post it back to Samsung and get a replacement.
Many people like me here?
Found a small workaround. I installed an early version of the ROM via Odin and everything is working fine so far. So I assume it is Software/Hardware not just Hardware. I installed version G998XXU3AUE1 because you can't downgrade from Android 2 to an more earlier version than this. It has to do something with "3" after XXU which I think is the version of the baseband. We need Samsung to fix this so we can use the Phone with the latest ROMs... I did not test other versions asd this one works fine and the battery is even better than on newers ones. I actually missed the battery life from old verions to be hojnest, since the updates it could be noticible that it drains faster.
Another theory is that after installing Samsung weareble and starting using the buds that spoils the audio codecs ...I still didint connect it since flashed this ROM so after completing the testing with all calling apps I will put the Wearble again and see if it works.

Categories

Resources