Database Develop

[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.

[Q] TW stopping working, unfortunately

Hello!
TW stops working several times a day, I've haven't managed to narrow down the apps that might crash it (unless everything I use on the phone crashes it). It sometimes crashes in the home screen, in Chrome, in YouTube. The two apps I use the most are WhatsApp and Facebook, and it has crashed when I'm using them, too.
I have the habit of pressing the home button to leave an app, and the phone always takes a little bit to reload all the icons. I know TW lags and stutters for many, this is not a complaint but an observation. I used phase beam as the wallpaper before, so I changed it to a solid black picture. That hasn't helped.
My phone is not rooted, though processes unused are stopped in App Manager.
Any assistance and suggestion would be much appreciated. Thank you.

Reset phone
BAD ASS NOTE 4

Hey guys,
I am facing the same issue, where TW crashes and I receive the message that TW has stopped working, however in my case it happens each time I reboot the phone. Once I OK the error message, TW reloads, and remains stable until I next reboot my baby, which I tend to do once a day, for good measure. This is not the end of the world, something I can live with, yet I do find it irritating that I cannot figure out what is causing this.
Anyone with a suggestion would be greatly appreciated. FYI, I am running stock at the moment.
Regards,
Raziel

I'd be tempted to odin to stock or flash firekat.

Raziel, I cleared TW cache and then wiped the cache partition earlier this afternoon. It seems TW hasn't crashed as often as it usually does, but it has crashed. It might remedy your problem, though, if you haven't tried this already. I'm avoiding resetting my phone.

If you rooted and tw goes crazy on you something went wrong. Delete everything you got. Turn of antivirus software. Download everything. Start by going back to stock then update then root then your good to go. If you start with a bad hicupp it will just keep getting worse.
BAD ASS NOTE 4

ChinWonder dude! Thanks a bunch for this suggestion... I cleared TW cache in Application Manager, then booted into Recovery and proceeded with wiping the cache partition. Honestly I feel like a bit of a noob right now LOL, I should have thought about this myself!! But hey thanks nevertheless, much obliged .
BACARDILIMON, as stated above by the OP, ChinWonder, as well as myself, in both cases the devices are not rooted. Thanks for the effort though . I'd like to add however that all of my previous and current Androids (S2, S3 and Nexus 7 2013) have been rooted, and in the last 2 cases, on day 1... hell I even made my own custom ROM for the S3 based on stock Bell 4.1.1 and stayed on it despite several available upgrades, I was getting such good performance and battery out of it, and FULL compatibility since I used a firmware base from my carrier, which is not the case for most custom ROMs found here, since none of them (or close to) are using Bell, but AT&T in most cases. From my experiences, I was always getting issues receiving voicemail notifications when using those. Long story short, I have been on the flashing bandwagon for a few years now, and tweaking the hell out of all my devices up to now, but this time, I feel this is the perfect (ok nothing is perfect) smartphone for me, as is, stock, and it performs like no other device I've had until now, and battery is just incredible!! getting regularly well over a day of charge, mostly average 36 hours, with 6 to 8 hours screen on time!!! WOW!!! seriously for the time being, I don't feel I want to root and flash and all that jazz, but instead I just want to enjoy this beast, the way Samsung thought of it, for a little while.
Again ChinWonder, thanks!
Raz

Please help - root issues

I consider myself an moderately experienced root and rom person. I've done the note 2 the note 3 and now the note 4. Both times that I rooted this phone within an hour or two I get the same issues. Apps in the AppStore hang at 89 percent. Current apps needing updating hang at 31%. A considerable lagginess with typing and opening and closing apps. So both times within a few hours I have odin back to stock and left my phone non rooted. I just don't understand why it keeps happening. Is it because I'm not doing a complete factory reset after a root and recovery? Maybe there are some data within my apps that is causing this? I really want to root this phone to make it better but this issue that keeps happening is really annoying. Does anyone have any insight? Please and thanks.

Hmmm well what rom are you flashing after root? Apps getting stuck could be network issue or play services trying to to update it self.
BAD ASS NOTE 4

No ROM. Stock. Two different WiFi and LTE same issues. I even did a davlic and cache clear Nada. Makes no sense

Ok then time to odin back to stock. What are you running. Which stock.
BAD ASS NOTE 4

I am back on stock. Nk4.

It's the reason you should flash something after you root.
I use firekat as my base.

That'll work. But maybe what the op needs is one of those stock deodexed/odexed roms.
I use this one for people that are scared to flash:
http://forum.xda-developers.com/showthread.php?t=2966770
There are others.

Random notifications or not notifications all since lolipop update in phone

Hi all!
Since I updated my phone, a Samsung galaxy S4 plus (GT-I9506),my LG watch G R does not show any notification or very few of them. Things started to get worse when I updated the watch to 5.0.1,at the time my phone was in 4.4.2, but since the official update of my S4 to lollipop the watch just does not work. I have reseted the phone, the watch, clean data and cache but with no success... I took the watch to the shop but they are doing anything they can not to give me a refund or exchange it change for another product. I do not know what else to do...
Any ideas? Is anybody else having the same issues?
Thanks in advance!

It could be lollipop firmware on your phone
I updated my note 3 to a leaked version of lollipop just before Xmas and my G watch R was unusable.
Constant disconnections etc
I flashed my phone back to Kit kat and it has been perfect ever since
The official lollipop for note 3 has just been released today but I am very reluctant to go through all that again until I know it works perfect
You could try going back to kit kat on your phone and see if it works again

Thanks for your reply! The lollipop firmware in my phone it's official. I thought android wear had support for Android 4.3 onwards... I am regretting so much having sold my pebble...

I took the plunge and updated my note 3 to lollipop official release and it's much better than the leak was
I'm still getting random disconnects now and again But it reconnects again straight away so not a massive deal

I had to go back to official 4.4.2. The watch was loosing connection constantly... Hopefully they will solve this in a future update

Upgrade or Downgrade Baseband 8

Hello experts,
Since Oreo was pushed to my S7 Edge through OTA, it has been nothing but trouble. My phone is extremely sluggish and unresponsive, to the point that when I get a call, the phone rings but doesn't come on so I cant answer the phone. I have wiped out cache multiple times and even factory reset it couple of times and the phone is still very slow. I have been reading here trying to find a solution, but have not been very successful.
The Baseband Version on my phone is "G935AUCS8CRK1". From reading all the threads here, it looks like I am on BB8 and stuck and wont be able to upgrade or downgrade. But still I thought I post the question here and one of you experts can confirm and/or suggest a solution for the problem I am experiencing.
If it is not possible to flash any rom once on BB8, is there anything I can do to improve the performance of my S7 edge after Oreo upgrade? As mentioned above, I have wiped and cache and done a factory reset multiple times with no luck. Am I the only one experiencing the lag/sluggishness?
Thanks in advance for your suggestions and support!

I have had occasional slowdowns on Oreo, but nothing like what you are describing. There is a bit of lag when an incoming call comes in that wasn't there before, and I often see a purple screen for a second before it pulls up the contact info, but it is ringing as this happens. I have never had an issue answering a call, etc. I am CRK2, though, not CRK1. Overall, the lack of keyboard lag, which made me despise Nougat on this phone, makes up for the occasional lag elsewhere.
Unfortunately, you can't downgrade the bootloader/baseband, so you can only run software builds that are based on that version - all of which, I believe, are Oreo builds now.

Mine is running very well, very improved. The only problem that I have is the battery drain, I can hardly reach 4 hours of screen on time on battery, but the normal average is 3, 3.5 hours of screen on time. So sad that actually is not a way to downgrade to B8