Hi all. I just got a Captivate after using Mattc on my HD2 and I used an Aria for a couple weeks as well. I used Mattc on the HD2 for a couple months and really liked it. I understood it was running from the SD and lived with the other issues like slow wake up and occasional goofiness.
So when I got my Captivate I was thinking, wow, I'll have one of(if not the) fastest Android phone on it's native hardware. Everything should rock. I should be blown away... Not.
HELP!
The brightness settings. WTF! Why did they implement like 10 ways the brightness screws with your day. On my HD2 w/Mattc I set the brightness in settings to where I wanted and it stayed. Forever. Also when it hits 10% it kicks the brightness all the way down. 10%? Com on maybe 5%. But what is worse is when it does kick it down I kick it back up but it dims again at every percent it goes down. ANNOYING. Please let me control my phone... Oh and don't get me started on the Browser brightness. Huh? Even with the browser brightness set at max it's still dimmer than my regular brightness setting. Noticably. I only keep my brightness at like 75-80% too.
Also what the hell is with the lame Calendar notification settings? Are there any?
My question is this. Is there any ROM out there that will strip all that Samsung ideology and give me a stock Android experience. Especially without the brightness issues. Why do I need to slide my notification bar to change brightness? All it does for me is just cause my brightness to vary accidentally when I don't want it to.
Why must I add on programs for my Calendar alerts to function normally? Why?
So again. Is there a ROM out there that will strip all the Samsung goofiness? If I can't get this phone to work like I want I'm going to sell it and look for a Telus HTC Desire to use on ATT. HTC phones are the best man. IMHO
Thanks.
juiceppc said:
The brightness settings. WTF! Why did they implement like 10 ways the brightness screws with your day. On my HD2 w/Mattc I set the brightness in settings to where I wanted and it stayed. Forever. Also when it hits 10% it kicks the brightness all the way down. 10%? Com on maybe 5%. But what is worse is when it does kick it down I kick it back up but it dims again at every percent it goes down. ANNOYING. Please let me control my phone... Oh and don't get me started on the Browser brightness. Huh? Even with the browser brightness set at max it's still dimmer than my regular brightness setting. Noticably. I only keep my brightness at like 75-80% too.
Click to expand...
Click to collapse
Turn off auto brightness and pick a setting you like. Done.
Also what the hell is with the lame Calendar notification settings? Are there any?
Click to expand...
Click to collapse
I don't know what lame is, but I use my Google calendar and I can set notifications. I get notified. Is there a specific problem you have?
My question is this. Is there any ROM out there that will strip all that Samsung ideology and give me a stock Android experience. Especially without the brightness issues. Why do I need to slide my notification bar to change brightness? All it does for me is just cause my brightness to vary accidentally when I don't want it to.
Click to expand...
Click to collapse
There is no stock Android experience. Android is just the core - Samsung, HTC, etc, they all add specific things in order for their specific hardware to function. If you don't want what comes on your AT&T Captivate, then you can root and uninstall the apps you don't like, flash one of the many, many cooked ROMs available on this forum (just look around - they are everywhere, and all with great pictures and descriptions and huge threads full of information), tweak settings to your heart's content, or anything else you want to do.
Why must I add on programs for my Calendar alerts to function normally? Why?
Click to expand...
Click to collapse
I don't have any add-ons and I get my alerts. What exactly isn't working for you?
Auto brightness has been off. First thing I do-
I do not get audible alerts when a Calendar reminder goes off-(and there is no where in settings to change/check this)
I had to install "Calendar Snooze" to play an audible alert for a Calendar reminder-
Phone is at 10% now fully dimmed. Nice... Considering how bad the battery life is for this phone(for me) I'll be spending a lot of time with the screen fully dimmed.
juiceppc said:
Auto brightness has been off. First thing I do-
I do not get audible alerts when a Calendar reminder goes off-(and there is no where in settings to change/check this)
I had to install "Calendar Snooze" to play an audible alert for a Calendar reminder-
Phone is at 10% now fully dimmed. Nice... Considering how bad the battery life is for this phone(for me) I'll be spending a lot of time with the screen fully dimmed.
Click to expand...
Click to collapse
Try reading a little and you will see you can set the brightness at where you want it by un-checking the automatic brightness setting..Then you can swipe along the status bar to raise and lower the brightness..It will stay where you had it set IF the automatic brightness is unchecked..Where you have the slider at will be the brightest it will swipe to..
Set your alerts to something you can hear and turn up the volume..They work fine.
Battery life is not a issue provided you follow some advise..Bump charge it 1 time and then use it till it drains down to single digits before recharging...also make sure you back out of all programs and turn off wi-fi and gps and syncing when you don't need them. Loose any task killer program you have and run it stock..you will find your battery life is excellent..if not you may or may not have a bad battery..Lastly..if you are really dissatisfied with it..take it back..
Good Luck
Mac
In regards to the brightness, turn off auto brightness and the 'power saving option.', that should solve your issue.
As far as removing the AT&T bloatware goes, try Unleash the beast.
If you want to run Froyo try flashing a rom, I used the latest version of Cognition.
Run far away from this phone if you still have the chance.
MikeyMike01 said:
Run far away from this phone if you still have the chance.
Click to expand...
Click to collapse
Broad-brush damnations do nothing to help anyone.
Mac11700 said:
Try reading a little and you will see you can set the brightness at where you want it by un-checking the automatic brightness setting..Then you can swipe along the status bar to raise and lower the brightness..It will stay where you had it set IF the automatic brightness is unchecked..Where you have the slider at will be the brightest it will swipe to..
Set your alerts to something you can hear and turn up the volume..They work fine.
Battery life is not a issue provided you follow some advise..Bump charge it 1 time and then use it till it drains down to single digits before recharging...also make sure you back out of all programs and turn off wi-fi and gps and syncing when you don't need them. Loose any task killer program you have and run it stock..you will find your battery life is excellent..if not you may or may not have a bad battery..Lastly..if you are really dissatisfied with it..take it back..
Good Luck
Mac
Click to expand...
Click to collapse
Thanks for the advice. Although I have done all of those things. I'm kind of coming to one real main pain point that I can't seem to solve. The screen dimming at 10%. Does anyone know how to disable that? Even if I kick the brightness back up after it dims at 10% it will redim at 9% and so on...
Bitter. But hopeful.
Picsman said:
Broad-brush damnations do nothing to help anyone.
Click to expand...
Click to collapse
Unfortunately, running away from this phone does seem to be good advise. It doesn't mater how slick it is in theory. Uber display and kickass hardware are useless if the basic functionality suffers due to glitches most of the other options don't seem to exibit.
I decided to play the "mod and wait" game with this thing, and I'm regretting it. Broad-brush damnations would have helped me. At this point, enough issues have came up about this hardware that a "broad-brush" sticky may be warranted. The alert issues found by the OP, may be related to his speaker begining to fail. I had a similar issue. Calander and alarm notifications began failing in some apps, but not others. The phone would still ring. Some apps could still use the speaker. Within a week, nothing could use the speaker, and I had to do the "push-on-it" fix.
It's a forum. Posts are opinions. I've been impressed occasionally by the raw performance of this phone. Yet, I've also spent hours, hours, researching problems, applying fixes, flashing, pushing on the speaker, etc. And I've spent hours "waiting" for the thing to do something simple like send an email when it did fine the day before. With as much time and effort as I've put into researching and working on this phone, I feel like I (and others) have not gotten enough stability out of it.
I propose a broad brush damnation for this phone: "slick but intermittent".
fshalor said:
Unfortunately, running away from this phone does seem to be good advise. It doesn't mater how slick it is in theory. Uber display and kickass hardware are useless if the basic functionality suffers due to glitches most of the other options don't seem to exibit.
I decided to play the "mod and wait" game with this thing, and I'm regretting it. Broad-brush damnations would have helped me. At this point, enough issues have came up about this hardware that a "broad-brush" sticky may be warranted. The alert issues found by the OP, may be related to his speaker begining to fail. I had a similar issue. Calander and alarm notifications began failing in some apps, but not others. The phone would still ring. Some apps could still use the speaker. Within a week, nothing could use the speaker, and I had to do the "push-on-it" fix.
It's a forum. Posts are opinions. I've been impressed occasionally by the raw performance of this phone. Yet, I've also spent hours, hours, researching problems, applying fixes, flashing, pushing on the speaker, etc. And I've spent hours "waiting" for the thing to do something simple like send an email when it did fine the day before. With as much time and effort as I've put into researching and working on this phone, I feel like I (and others) have not gotten enough stability out of it.
I propose a broad brush damnation for this phone: "slick but intermittent".
Click to expand...
Click to collapse
haha. Thanks for the ,.. opinion. I'm starting to feel the same way about this phone. I had super high hopes. But I'm really going to stick with HTC. They just get it. IMHO.
I think most people regret buying this phone. Or they will, when FroYo never arrives, the lag gets worse and worse, the phone dies on them, and the GPS never come close to working, the market decides not to intall your app, this, that, or the other thing force closes, etc. etc. etc.
MikeyMike01 said:
I think most people regret buying this phone. Or they will, when FroYo never arrives, the lag gets worse and worse, the phone dies on them, and the GPS never come close to working, the market decides not to intall your app, this, that, or the other thing force closes, etc. etc. etc.
Click to expand...
Click to collapse
Umm froyo is already leaked and OTA is on its way.
Lag has never been an issue.
And GPS is a software fix... proven on these boards over and over.
SHEESH... I'd say go tell somewhere else.
Sent from my SAMSUNG-SGH-I897 using XDA App
yeah, 5 million people are completely dissatisfied because one guy managed to not know how to operate his phone.....
MikeyMike01 said:
I think most people regret buying this phone. Or they will, when FroYo never arrives, the lag gets worse and worse, the phone dies on them, and the GPS never come close to working, the market decides not to intall your app, this, that, or the other thing force closes, etc. etc. etc.
Click to expand...
Click to collapse
I think your wrong. I think quite a few people got defective phones and haven't bothered returning them,thinking that if they root it and flash a different rom that would magically fix a broken phone. This is XDA and folks here mostly do this..thus the reason for most of the complaints. Problem is..it won't change much of anything to reflash if the phone is defective..If it is broken to begin with..it will be broken no matter what you do to it.. If yours is defective..quite *****ing about it and get one that isn't..or a different phone entirely. The working ones are great..just like they are supposed to be.
I have 2 of them built in September..both work and neither is defective.This tells me many of those built prior have some issues..perhaps not all of them..but some of them certainly. This certainly doesn't make it right by anyones account..just saying if yours is defective..return it and get one that isn't.
I honestly don't understand people who have the option of doing this,not doing it.The folks at my AT&T store opened 7 different boxes and checked every one of them for any blue tint on the screen and having the 3 button recovery option..for my second one bought at the same time,so I do know there are many out there that ain't working properly..The OP of this thread..is unhappy with it..damn..loose it and be done with it if you are that unhappy..or take that one back and get them to open up the boxes and show you one that works properly...If it was bought mail order..then you should just return it as defective and get your money back..and buy where you can see it first..It's your choice...and your money.
Mac
Related
haptiClock vibrates you the time (haptic feedback) if you shake/bump/tap your phone. It works when your screen is off, doesn't use much battery. The pattern to decipher the time from the pulses is simple to learn.
Great for checking the time on the sly, or when you can't pull your phone out.
Free version for trial then limited, and then paid for full version. Send me feedback, I want to make this a useful app! QR code at ... well as a total newb here I can't post links even a barcode, but lookitup!
-Phil
Permission: Prevent phone from sleeping
Makes me very nervous about battery life.
Otherwise, very interesting idea, and I'll check it out.
EDIT: I'm getting constant force-closes just reading the tutorial. Galaxy S phone (Android 2.1)
"I'm getting constant force-closes just reading the tutorial. Galaxy S phone (Android 2.1) "
Wow thanks for the info, I'll look into it... been tested on Droid, Droid X, Nexus
edit:<strike>The battery use isn't as bad as I thought it would be</strike>!
apparently it is using more juice than I had seen during beta testing
Android is really challenging- lots of hardware (IMO this is a good thing) and versions make testing unreliable...
Version 1.1 just uploaded should fix problem Izkata had... THANKS FOR THE INFO!
Just a quick test this morning, and it does appear to be fixed.
I'll test it more thoroughly later today.
I just downloaded the free version of this and it looks really promising.
While the screen was on and the app still open it worked perfectly, but when I turned the screen off and activated it again, it did hours fine and the rounded min fine, but the 2nd activation didn't work.
OK, noted ADeadlySpoon... thanks.
There is a time window to second tap to get the exact minutes, it's 10 seconds, you can also just go into "one tap" mode and time to exact minute every time. Still, I'll try to re-create your issue.
Wont work if screen is off.. on my EVO
drummer2780 said:
Wont work if screen is off.. on my EVO
Click to expand...
Click to collapse
Same with Desire HD which makes it useless for me atm.
But it's a nice App, hope this will work soon.
Okay, so - I left it running with the screen off and phone unused for about an hour and a half, to check the battery usage.
(Phone: Samsung Captivate (Galaxy S on ATT))
Normally, on average, I lose just under 1% per hour when the phone is not in use. With haptiClock active, I lost right around 1% per 10 minutes, while the phone was not in use. So the drop isn't as bad as I was expecting (yay!), but it's not something I'd leave on all the time, either.
No force-closes, ether, so the fix earlier seems to have fixed it entirely.
I have a habit of discreet time-checking, so this'll be great. Best trigger for me seems to be about 13 or 14 - juuust enough that I don't have to whack my phone/make an obvious movement to trigger it.
I have to change the language on the help, because when it did appear in my battery use stats it was always about the same as Cell Standby, which didn't seem to make sense, I should have grabbed Izkata's app (and will now) to check battery usage. It is important to turn off when you don't anticipate needing it.
On the Desire HD & EVO, I have no idea why ATM, but will look into it over the next 24hrs. I did test it on an HTC myTouch 3G and it worked.
If either of you get a chance, could you post OS version / API level and any mods?
Thanks for checking it out.
-Phil
upperTriangle said:
I have to change the language on the help, because when it did appear in my battery use stats it was always about the same as Cell Standby, which didn't seem to make sense, I should have grabbed Izkata's app (and will now) to check battery usage. It is important to turn off when you don't anticipate needing it.
Click to expand...
Click to collapse
Yey, thanks
It's not the best thing for measuring usage like this, though. To get the numbers in my previous post, I just recorded the percent before and after, and manually divided. 'Tho you can see in the History graph when it drops faster, so that helps.
upperTriangle said:
If either of you get a chance, could you post OS version / API level and any mods?
Click to expand...
Click to collapse
Android 2.1-update1 / API 7, rooted, but with no mods.
When screen is on, it works alright. But when screen turned off, no response from the app. Great idea though. I'm using a wildfire btw..
To those of you for whom the app doesn't work when the screen is off, this is an Android bug affecting certain phones. I believe it is a problem (be it a feature whereby the manufacturer is trying improve battery usage profile, or a bug) with the firmware. The HTC phones with Sense UI seem to be among the more commonly afflicted devices.
I remember seeing this bug report I started working on the app:
http://code.google.com/p/android/issues/detail?id=3708
BUT by the time it was getting close to done, my impression was that this had basically been fixed, and I didn't mention it anywhere in the release, none of the phones I tested on had this problem.
Now, there is another newer Android bug report regarding this issue, please STAR it (upper left of page)
http://code.google.com/p/android/issues/detail?id=11028
and hopefully we will see more rapid resolution of this issue, I think the OS isn't the problem, but perhaps manufacturer firmware updates could help resolve it.
Please don't leave negative comments on the Market if the app doesn't work with the screen off. Because of users doing this (which I should have seen coming) my star rating is started to go down. I have included language on the Market entry which should prevent people from giving the app a low rating solely because of this issue.
Lastly, there is a workaround of sorts for this which will fix the problem on some phones. I will implement it, but am going to proceed very cautiously, because last thing I want to do is break the app for users for whom it is currently functioning appropriately.
As such, I would really appreciate it if people who are experiencing this issue would beta test a new release with the workaround prior to my releasing it on the market.
So drummer2780,Testuser_01,thunderskain, ADeadlySpoon(?) ... if any of you would be so kind as to receive an APK file from me for testing on your device, in return I'll try to somehow get you the full version gratis of course (how we'll do that I'm not sure as I don't want an APK with licensing disabled floating around out there!, perhaps you can buy it from the Market and I'll refund the payment)
Izkata, for your help I'd like to do the same (give you free version) so if you buy it I will refund. I don't *think* a refund will invalidate the licensing, but I'm not sure, it is unclear from the Google distribution agreement language.
Thanks for checking out my app, I'm hoping people are finding it useful!
Izkata said:
Best trigger for me seems to be about 13 or 14 - juuust enough that I don't have to whack my phone/make an obvious movement to trigger it.
Click to expand...
Click to collapse
Since you are using it at a pretty sensitive setting:
Go to settings->overall sensitivity and select "Make more sensitive" and you'll find you can be a little more in the middle of the range and will have better precision for where you'd like the trigger to be, of course set it back if you want to use it and you're being more active.
-Phil
upperTriangle said:
So drummer2780,Testuser_01,thunderskain, ADeadlySpoon(?) ... if any of you would be so kind as to receive an APK file from me for testing on your device, in return I'll try to somehow get you the full version gratis of course (how we'll do that I'm not sure as I don't want an APK with licensing disabled floating around out there!, perhaps you can buy it from the Market and I'll refund the payment)
Izkata, for your help I'd like to do the same (give you free version) so if you buy it I will refund. I don't *think* a refund will invalidate the licensing, but I'm not sure, it is unclear from the Google distribution agreement language.
Click to expand...
Click to collapse
Since we both have a paid version of an app out, we could just do a "trade" and buy each others' apps, assuming you haven't already. The difference in pricing is small enough that I wouldn't really worry about it. Or we could try out the refund idea, then have experience to advise others in the future (I haven't bought haptiClock yet, and might not for a while - various stuff going on IRL)
upperTriangle said:
Go to settings->overall sensitivity and select "Make more sensitive" and you'll find you can be a little more in the middle of the range and will have better precision for where you'd like the trigger to be, of course set it back if you want to use it and you're being more active.
Click to expand...
Click to collapse
I'll take another look at the setting(s) eventually, and try and remember to post my comparisons in this thread once I do. (However, I'm starting a new job this week and don't want to mess with stuff/might not have time to mess with stuff until next weekend)
Great app! I've been looking for an app that did this for a really long time.
I was thinking though. The vibrate system's a little confusing, and I don't really need to know the exact time. Usually I only need to know it to the closest 15 minutes. Perhaps you could set toggles for the 10/15 minute vibe, the 5 minute vibe, and the 1 minute vibe?
SamUserInterface said:
Uually I only need to know it to the closest 15 minutes. Perhaps you could set toggles for the 10/15 minute vibe, the 5 minute vibe, and the 1 minute vibe?
Click to expand...
Click to collapse
There is a setting which allows you to only receive the 10/15 vibe (at least it requires an add'l tap to get the exact minute)... but I do like your idea of being able to specifically set where to stop. It would be a fairly extensive task for me to implement, as I basically have it set up to do just to the minute, or require add'l tap. We'll see how it goes, I can't say I'm going to be spending a bunch more time on this thing unless it attracts more users.
Thanks for the feedback!
Doesn't work with the screen off on the dell streak running dj steves 1.6.0 froyo ROM. Would definetly be interested in buying when (if) it can.
Well, it looks like all workarounds I've tried for phones which don't respond to the sensor when the screen is off (in standby mode) have failed. This is likely a firmware issue which ought to be addressed by the manufacturer. The code should run the same on all devices, this is the point of Android!
Given that it works on most phones, it is a "bug" or "defect".
Please take a moment to star the issue at code.google:
Issue 11028
Also, contact your phones manufacturer rolleyes: HTC) regarding this issue.
I think there are lots of possibilities here and hopefully it will get fixed because there are similar apps I'm creating which rely on the accelerometer working in standby as I've implemented in haptiClock.
Thanks
Phil
Is it just me or does the auto-brightness seem to only stay at a certain brightness and never change? On my previous phone, usually when I had auto-brightness enabled, whenever I walked into a dark room, my brightness would lower right away but on this phone, no matter where I go, the brightness seems to always be the same with auto-brightness on. The brightness does not change, even when I walk out with the sun out..
Can anybody confirm this please, I'm thinking of exchanging this unit as it might be defective...
Sent from my LG-P999
Might be your phone. In my moderately-lit office, I can definitely see the screen brightness change when I focus a flashlight on the sensor and then take it away. It's not a huge difference, but definitely observable.
Do you use a case? Is the case blocking the light sensor?
I do not use a case. I have also tried blocking the sensor with my fingers and the brightness just seems to always stay the same... also when I use the power control widget to change brightness and set it to auto-brightness it immediately jumps to that same particular brightness level that I've been stating
Sent from my LG-P999
I was noticing this as well. It seems to just go to medium brightness and stay there all day. I never notice any changing.
abowmedia said:
I was noticing this as well. It seems to just go to medium brightness and stay there all day. I never notice any changing.
Click to expand...
Click to collapse
That's exactly what I'm experiencing, glad to know I'm not the only one..
Sent from my LG-P999
The change is definitely less noticeable on this phone than my Nexus One, but is there.
I just got the G2x and it does the same for me. It's range of brightness seems to be 20-30% and that's it. I had this problem with stock gingerbread, so I tried rooting and installing CM7, but same problem. So I got it set to manual 10/40/100 on my power control.
My friend said his original droid did this for quite a while until a software update came along a few months later. Maybe we just have to wait till there's a software update to fix it?
Yes, it's borked, always has been.
Mine is broken too. Same happens to me.
Sent from my LG-P999 using XDA Premium App
Same here. It has never worked, as far as I can remember. Depending on where the setting happens to be left at, my battery runs out in just a few hours, or I cannot use it in the car.
Aside: I switched to an original Droid from an iPhone 3G, then onto a G2X. My next phone is going to be an iPhone -- and I'm not coming back to Android until Google figures things out. Android is nice, but I hate being out of date after a couple of months, and having to install unsupported, hacky, half-broken user-built ROMs to stay current with the state-of-the-art functionality.
Allright, i've owned my Sensation for several weeks now. Today, i sent a text, and as soon as i went back to the home menu, the phone turned itself off, and rebooted. It was a pi**-off, for sure, and now im worried.
I've done some research, and apparently (correct me if im wrong) it's because of too much RAM usage. However, i set the phone to notify me when free RAM is less than 50MB, and it never did. It just pulled an auto-reboot on me.
Should i worry about this? Is it normal; basically 100% guaranteed that it is because of low RAM?
Which leads me to this: I ALWAYS questioned all the things i had running at the same time. That's probably the only thing i don't like about the phone. Things start automatically. I have an EQ program, Groove IP, and the Music Player running at the same time. I don't understand why the phone won't just close apps if they aren't in use... Or at least if there was a more streamlined way of closing apps. Not going into Settings,Apps,Manage Apps, Running... That's pretty stupid, if you ask me... If there are alternate/better methods, i'd like to know them.
Back to the point, though. Should i worry about this reboot? And, what exactly is the cause/is it RAM usage?
Do not worry unless it becomes a persistant problem.
And even then do not worry because it can probably be fixed as long as its a software issue and not a hardware problem.
And free ram isnt a big deal with android. If you use it, you will use up all your ram quickly. But android will kick things not in active use out of ram when apps in use need more ram. Having free ram is actually a waste.
Sent from a rebel ship by storing the message in an R2 unit. (Help me, XDA. You're my only hope)
Oh, ok...If it's a one-time thing, then i won't worry about it. However, i'd still like to know the cause of it.
Why does this happen?
Did your phone feel warm or hot when it switched off?
Okay, this thing about RAM is one of the biggest misconceptions I think a lot of people have regarding Android. Android doesn't use RAM like Windows. On Android, RAM usage is a good thing. It means that when you want to reload an application, it does it quickly. In other words, RAM unused is just RAM wasted on Android. And the other thing is, apps running in the background do not consume resources unless they also have background processes running as well. The other thing is that Android will automatically kill off certain processes when your RAM is low. So yea. You don't have to worry about RAM.
If you're worried about the crap that comes preinstalled with the phone, you might want to consider rooting and removing all those apps though.
Prenihility said:
Oh, ok...If it's a one-time thing, then i won't worry about it. However, i'd still like to know the cause of it.
Why does this happen?
Click to expand...
Click to collapse
Are you using an app killer to monitor your free ram?
That could easily be the cause. Sometimes those app killers will kill the wrong things and force a reboot.
You're better off dumping apps killers altogether. They work counter productively to the way Linux operates.
Yeah, i kill processes/apps in the settings menu, don't use any downloaded/third party apps for that purpose.
I guess i'll stop doing that...
HOWEVER, i still don't like how, for example, once i sign into Groove IP for the first time, it will stay signed in. Every consecutive time i go to use the phone again, it signs in automatically... After it wakes up from sleep mode, it will sign into Groove IP, and load things like the EQ program i use. I won't worry too much about the EQ, but other apps like Groove IP that are connected to some sort of signal, i don't want automatically running... Is it really not safe to just terminate a process in task manager?
Finally, on to the subject of reboots...Since owning the phone for...I don't know...A few weeks now? I've only actually turned it off/rebooted once...
Did that contribute to the random reboot? Was that not a good move, on my part, to pretty much always keep the phone on (although in sleep mode when not in use, of course...) ?
Prenihility said:
Finally, on to the subject of reboots...Since owning the phone for...I don't know...A few weeks now? I've only actually turned it off/rebooted once...
Did that contribute to the random reboot? Was that not a good move, on my part, to pretty much always keep the phone on (although in sleep mode when not in use, of course...) ?
Click to expand...
Click to collapse
Yeah it could have. Try reboot the day every week at the bare minimum. Ideally, I'd suggest rebooting every 4 days or so.
Prenihility said:
Yeah, i kill processes/apps in the settings menu, don't use any downloaded/third party apps for that purpose.
I guess i'll stop doing that...
HOWEVER, i still don't like how, for example, once i sign into Groove IP for the first time, it will stay signed in. Every consecutive time i go to use the phone again, it signs in automatically... After it wakes up from sleep mode, it will sign into Groove IP, and load things like the EQ program i use. I won't worry too much about the EQ, but other apps like Groove IP that are connected to some sort of signal, i don't want automatically running... Is it really not safe to just terminate a process in task manager?
Click to expand...
Click to collapse
If you are manually killing an app that's causing problems / pissing you off / or because you just don't like it's face, then no. That's okay. It's the automated app killers that kill everything as soon as you close them and then keep killing and killing like battle droids gone berserk that you want to avoid. It's that constant killing, which means an app restart and power usage, that will drain battery. And being unmonitored they can kill the wrong things that cause system instability.
But if you have 1 app that's bothering you you can kill it through the apps menu. That's normal.
The bigger problem is an app that constantly turns itself on like that. I hate those. There should be an option in the app settings to prevent that from happening. If there isn't, it's a bad app no matter how well it does what it's supposed to do.
You can use gemini app manager to change autorun settings for each app individually and autokiller memory optimizer to change the preset android memory limits so your phone automatically closes apps itself a little bit sooner.
Both are free apps but require root.
Gemini is really good. Certain apps start just because you received a text or plugged your usb in. Or your signal changed. I put a stop to that straight away!! Just don't change the settings for system apps.
sent from my Sensation XE
Happened again... Alright, im being irritated by this restarting problem... My phone was just idle, i haven't touched it for hours. It was next to me on my desk, and i heard/felt the vibration upon restart.
Should i call my service provider for a replacement? This is ridiculous... I didn't get this thing expecting it to restart on me.
Prenihility said:
Happened again... Alright, im being irritated by this restarting problem... My phone was just idle, i haven't touched it for hours. It was next to me on my desk, and i heard/felt the vibration upon restart.
Should i call my service provider for a replacement? This is ridiculous... I didn't get this thing expecting it to restart on me.
Click to expand...
Click to collapse
They are going to make you go through a lot of TS steps that you can do prior to calling them.
Have you downloaded any apps recently, say just before you had the problem the first time. It could be the fault of a buggy app, (Usually not likely, but is possible). Are you rooted or fully stock?
As for the Groove ID - look in settings, there may be a way to stop the auto sign in. Just an idea, I don't use it.
I'm not having anymore problems with Groove IP auto sign in. The "lite" version of the app doesn't have the option to disable it, anyway. I just don't run it, unless i need to use it.
This is the second or third time it's restarted. I believe it's the second time, since the 23rd of April, when i created this thread.
As far as rooted or not rooted, i'm not sure what that means. I think it's in regards to the SD card. No, i haven't messed around with it. It's stock. Other than adding some music to the phone. Nothing has been messed around with.
I'm really annoyed by the fact that this happened AGAIN during idle/sleep mode. I wasn't even using the phone. It was just sitting there. It's quite irritating.
Anyhow. What are all the possibilities of the reboots? I'm starting to think it's not lack of memory. Supposedly the RAM-related issue is Sense restarting because of lack of RAM.
The phone vibrates, and the HTC logo comes up, and finally comes to the Home screen.
The only good news, really, in the end, is that it's only happened a couple of times in such a long span of time... I seriously hope i get this figured out, and it never happens again. Or else i'm getting a replacement, for piece of mind, and as a solution.
Prenihility said:
I'm not having anymore problems with Groove IP auto sign in. The "lite" version of the app doesn't have the option to disable it, anyway. I just don't run it, unless i need to use it.
This is the second or third time it's restarted. I believe it's the second time, since the 23rd of April, when i created this thread.
As far as rooted or not rooted, i'm not sure what that means. I think it's in regards to the SD card. No, i haven't messed around with it. It's stock. Other than adding some music to the phone. Nothing has been messed around with.
I'm really annoyed by the fact that this happened AGAIN during idle/sleep mode. I wasn't even using the phone. It was just sitting there. It's quite irritating.
Anyhow. What are all the possibilities of the reboots? I'm starting to think it's not lack of memory. Supposedly the RAM-related issue is Sense restarting because of lack of RAM.
The phone vibrates, and the HTC logo comes up, and finally comes to the Home screen.
The only good news, really, in the end, is that it's only happened a couple of times in such a long span of time... I seriously hope i get this figured out, and it never happens again. Or else i'm getting a replacement, for piece of mind, and as a solution.
Click to expand...
Click to collapse
Referring back to my previous question, did you install any apps prior to the first reboot?
l2icky said:
Referring back to my previous question, did you install any apps prior to the first reboot?
Click to expand...
Click to collapse
Oops. Forgot, sorry... Uuuummmm... Either the Equalizer App, or Groove IP. The only ones i've downloaded. Although im leaning more towards Groove IP (doesn't start up anymore though; because i don't want it to. Never launched it).
Regardless, are you saying i should uninstall it?
Also, one thing i want to add, that i find a bit strange. If i restart the phone, the display brightness will be noticeably brighter than what i actually set it to. It's almost as if i have to remind the phone of the brightness level i set in display options. All i have to do is go to the brightness setting, and touch the slider.
Is this normal behaviour? For it to be brighter upon startup? (even when reaching the home screen/whilst the main UI, past HTC logo screen)
Prenihility said:
Oops. Forgot, sorry... Uuuummmm... Either the Equalizer App, or Groove IP. The only ones i've downloaded. Although im leaning more towards Groove IP (doesn't start up anymore though; because i don't want it to. Never launched it).
Regardless, are you saying i should uninstall it?
Also, one thing i want to add, that i find a bit strange. If i restart the phone, the display brightness will be noticeably brighter than what i actually set it to. It's almost as if i have to remind the phone of the brightness level i set in display options. All i have to do is go to the brightness setting, and touch the slider.
Is this normal behaviour? For it to be brighter upon startup? (even when reaching the home screen/whilst the main UI, past HTC logo screen)
Click to expand...
Click to collapse
It's a possibility that the app is causing the problem, though it is a small one. You might uninstall it and try it for a while, see if the device continues to reboot.
As far as your quirky brightness issue... It's technology. No two devices are the same, even if they have the "same" hardware/software. That almost seems like a fluke happenstance. Just a minor bug in your software.
You might want to read into S-Offing your phone and rooting it. Do some research into it. There are a lot of perks of rooting your device and going with custom ROMs. And if you ever have issues and have to get a replacement, as long as you can turn the device on and it's functional, you can always set it back to S-On with no root.
I've learned over the years, and this is just my personal opinion, stock ROMs are more likely and it seems as if they are meant to have more problems, however it's like anything else in the tech world, it's bound to deteriorate over time. It's how they keep you buying their product.
There are some really good guides that lead through the process step for step if you decide to S-off and root. And there are a lot of helpful people on XDA that will answer any of your questions.
l2icky said:
It's a possibility that the app is causing the problem, though it is a small one. You might uninstall it and try it for a while, see if the device continues to reboot.
As far as your quirky brightness issue... It's technology. No two devices are the same, even if they have the "same" hardware/software. That almost seems like a fluke happenstance. Just a minor bug in your software.
You might want to read into S-Offing your phone and rooting it. Do some research into it. There are a lot of perks of rooting your device and going with custom ROMs. And if you ever have issues and have to get a replacement, as long as you can turn the device on and it's functional, you can always set it back to S-On with no root.
I've learned over the years, and this is just my personal opinion, stock ROMs are more likely and it seems as if they are meant to have more problems, however it's like anything else in the tech world, it's bound to deteriorate over time. It's how they keep you buying their product.
There are some really good guides that lead through the process step for step if you decide to S-off and root. And there are a lot of helpful people on XDA that will answer any of your questions.
Click to expand...
Click to collapse
Allright. Went to grab my phone just now, and saw the error notification. The old "abnormal reset" notification.
I'm going to assume it reset on its own once again. So....
Any insight into this? Why's is reseting itself? Hasn't happened in a while... but... still.
It was just sitting there, idling.
There really should be a pinned thread for utter disappointed features and/or people.
I am not returning my new SW2. Its too cool to have the lamest, inept and funtion-killing GUI cause me to give up. ** But I bought a Pebble watch the same day because (the SW2n currently):
- can not function as a watch. It does but it goes to sleep VERY fast. WAY too fast. This is completely unacceptable. If I want to drain my f*ing watch and be able to read it all day, I should be able to!!! Put a warning on the settings area.. like: WILL DRAIN BATTERY VERY FAST or something...
- Can not finish reading my incoming sms. Maybe you dont know the girl I am dating but she WRITES A LOT... and this may not be normal amounts ... I really mean a lot. And SONY clearly has NO IDEA about this.
- AND continuing from the above point, it goes back to the f*ing CLOCK in sleep mode. SHOULD dim and remain on my screen until I SAY OTHERWISE. NOW I have to press the power button and NOT make it power off buy accident (another STUPID DESIGN) and make it activate, press the home button and then the stupid function messaging button. NO LOGIC FLOW HERE. I have to read 5 or 6 TXTs by now.
- CAN NOT read the messages in order without going BACK and opening the messaging app again. At least that seems to be what I had to do. I might have missed proper procedure here but if that is true, shame on SONY for lacking a more intuitive operation.
The Poweramp app is cool when it works. It should STAY active. I DONT CARE about anyone else or what slogan SONY wants to claim about battery life. I want FUNCTION my f*ing way. I use Poweramp all the time. But it is not able to stay on my watch, active? Total shame.
The ONLY app I kept on my watch is the custom watch faces. It allwos me to keep the display on until the dumbwatch, overthinking watch disconnects from my RazrMaxx/4.4 Dhacker29 ROM.
So in conclusion, This watch completely fails at being a watch. Fails at running apps because it times out WAY TOO FAST. Fails at every possible area other than fitting well.
Maybe your accelerometer is faulty. It should not timeout when on hand, actually it dims and always shows time.
Sent from my SM-N9005 using Tapatalk
jmaciak said:
Maybe your accelerometer is faulty. It should not timeout when on hand, actually it dims and always shows time.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I hate to be the guy to say it, but is the OP trolling us?
I have the smartwatch 2, just got it yesterday, and what the OP is saying makes no sense.
deitiphobia said:
I hate to be the guy to say it, but is the OP trolling us?
I have the smartwatch 2, just got it yesterday, and what the OP is saying makes no sense.
Click to expand...
Click to collapse
Well it can timeout and go totally blank ... try it, put them on the table and do not move the watch/table and it will dim and then go completely blank after a while, because the accelerometer sees it's not on the hand. So if OP's accelerometer is faulty, it might behave this way ...
jmaciak said:
Well it can timeout and go totally blank ... try it, put them on the table and do not move the watch/table and it will dim and then go completely blank after a while, because the accelerometer sees it's not on the hand. So if OP's accelerometer is faulty, it might behave this way ...
Click to expand...
Click to collapse
I am not a troll. At least I am not trying to be a troll. I do feel slightly underwhelmed buy my experience so far.
And maybe my accelerometer needs checking? If it is supposed to remain on (the screen) for more than 5 seconds when I am wearing it and trying to read something, then yes, something is wrong. Maybe the watch doesnt know when it is on a troll arm?
deitiphobia said:
I hate to be the guy to say it, but is the OP trolling us?
I have the smartwatch 2, just got it yesterday, and what the OP is saying makes no sense.
Click to expand...
Click to collapse
Hello,
What he is saying actually makes perfect sense, especially on this forum - we are not the average, marketing-targeted user and we like to use our devices any way we please, without being limited by design hickups. And we are more sensitive to design flaws and marketing bs than the average consumer.
Sony missed and even lied about basic features and is not allowing, at least so far, anyone to tweak with this product's FW.
In my experience the watch proved very useful ONLY IF YOU ARE NOT RELYING SOLELY ON IT for most of your work - i, for one, would not like to read my correspondence on such a tiny screen and prefer to use the phone instead - but it would sure be nice to know that I CAN use the watch if i wanted to.
Fortunately, while driving a motorcycle, for example, getting a hint of the message content usually suffices for me to determine if i need to pullover and get my phone out, provided i get to see the screen before it times-out, which is another awkwardly missing basic function.
I will, however, hold on to the SW2 for now in hopes that Sony will straighten things the way they should.
Sent from my LT25i using Tapatalk
i agree fully with the OP as well
if i didn't know better, i would suggest posting your opinions on talk sonymobile, but as i already did that and got NO reply from Sony, i guess it would be just a waiste of time
that's my biggest problem with Sony right now: no communication
(although i must admit most manufacturers suck at communicating with their customers, try finding out when the Butterfly s is getting 4.3/4.4, not a chance)
I actually agree with the OP, there are some features that could be included in the settings menu like timeout duration or stopping the watch default to the watch screen every time it goes into standbye especially useful if travelling and using features like poweramp - you need 3x button presses to bring the poweramp screen back on and if you have a messaging app open (reading messages) it should prevent the watch from sleeping
and how fecking hard is it to develop a few watch face designs with different colours etc
TBH I think Sony are in the process of designing a totally new Smartwatch for release in early 2014 and have completely dropped the ball with this one
well, there was an update today, so i guess they didn't drop it completely
update looked good at first, but disappointing anyway
-only 1 extra watch face that's usable, i still want the abilty to design/choose my own watch face
-the option to use the light sensor for brightness is nice, but i'm glad it's optional, don't like it
-music app update totally messed it up (used to work for me)
-camera app update didn't do anything for me, still does nothing
-still no selectable timeout, huge issue for me
---------- Post added at 06:47 PM ---------- Previous post was at 06:36 PM ----------
Find It for SmartWatch by AQ i purchased also doesn't work anymore
argh, their own Find Phone Smart Extension ALSO doesn't work anymore!
JarlSX said:
their own Find Phone Smart Extension ALSO doesn't work anymore!
Click to expand...
Click to collapse
AFAIK I suspect that problems might occur pairing the SW2 with a non-Sony smartphone.
But please let's keep the discussion in one place only, so we can better compare these findings:
http://forum.xda-developers.com/showthread.php?t=2554874
i think i know why the watch can't dim while still displaying an app
those apps don't really run on the watch, they're just displaying what's happening on the phone (that's where the app is installed)
so for a watch-app to work, the watch is constantly communicating with the phone
such a connection will probably drain the watch very quickly
only the watch part can run independently, so that's why it always goes back to that screen, to save power
this is of course just what i think
FWIW, the screen on time can be controlled by the app. I use and app called IPBike for cycling which runs on the phone. This app allows you to use the watch as a head unit on the bars. It has an option to keep the watch screen on for the entire ride.
jmaciak said:
Well it can timeout and go totally blank ... try it, put them on the table and do not move the watch/table and it will dim and then go completely blank after a while, because the accelerometer sees it's not on the hand. So if OP's accelerometer is faulty, it might behave this way ...
Click to expand...
Click to collapse
Should it really go totally blank/black? Mine is only dimmed out and showing clock face all the time, but really dimmy. And it is on the table...
Oh it does, took some time, longer than i expected...
Sent from my GT-N8000 using Tapatalk 4
I was very excited to see this:
http://forum.xda-developers.com/ver...w-to-update-to-g900voc4-5-0-keeproot-t3068546
So, I pushed ahead thinking that Lollipop has already been in the wild long enough, surely the initial kinks like WiFi drops and battery hogging have been resolved. No such luck, and after doing it, it looks like I'm going to have to do this:
http://forum.xda-developers.com/showthread.php?t=2784880
Lollipop is horrible. My phone no longer does one of the most basic things that's been around since the G1: Go (the F) to sleep! Seriously?!?!
Here are my other problems:
-Phone doesn't sleep on its own if timeout set for longer than 30 seconds (and even then, it's not reliable)
-WiFi doesn't reconnect after sleep (when sleep even happens, which is only when I push the button to force it). I have to toggle WiFi off/on to reconnect.
-Battery drain is pretty bad. My first month with the S5 had me barely even thinking about charging. Now, with Lollipop, I feel like I'm back on my old HTC MyTouch!
-The silly way they implemented the lockscreen. Here's my problem: I can ONLY use Settings > Sound and Notification > While locked with the option "Do not show notifications". Why? Any other setting blocks the Owner Information (Settings > Lock screen > Owner Information). If I don't, and if I'm unfortunate enough to have lost my phone, yet fortunate enough to have it found by a good samaritan, I better hope I haven't miss any calls or received any messages in the meantime. This one REALLY GRINDS MY GEARS because it's a horribly-implemented Feature ... at least the others are unintended bugs, but somebody had to give this one the green light.
-I can't adjust the icon sizes anymore. There used to be a choice of large or small icons.
-Oh, and for some bonehead reason, Samsung decided their stock ROM wouldn't have the Lollipop built-in flashlight icon.
-Another intentional feature that I can't disable: the phone keeps a history of recent activity that persists through reboots. YUCK! Why can I not disable this?!?! Again, another bonehead call that somebody had to green-light, without even considering the possibility that I might want to turn it off!
-All the UI "polishing" and improvements don't mean a thing to me, I want it to work.
I found all of the above in less than 24 hours on Lollipop! I might lose my s**t entirely if I keep it for much longer.
Here is my take on why:
Google and Apple are in a heated race to the top. They wrongly assume that what will set each apart from one another is almost entirely dependent on what a few bloggers say about some hot new feature. The paradigm appears to be something like: "Who cares if millions of loyal subscribers lose functionality when we want 100 people to have this one obscure and half-baked feature?"
Latest != Greatest
-----
EDIT:
I've had a change of heart on this. It's not too bad, I just needed to adjust a few settings and live with the other issues.
I too do not like the lolli. Bad battery life, and for some reason the Heart rate monitor led turns on whenever anything is within a half inch of it. I just can't figure that out, but it sucks the battery like a red led vampire!
Sent from my SM-G900V using XDA Premium HD app
Tldnr
Don't start a thread just to complain
Lmfao when I saw that link and clicked it, I actually had that same thread opened moments before opening this thread because I, too, am having to go back to KitKat. I laughed for a good 20 seconds. Lollipop is freaking terrible at the moment. Zero customization and Google + Samsung are forcing too much garbage on us without giving any bit of customization.
mygraine said:
I too do not like the lolli. Bad battery life, and for some reason the Heart rate monitor led turns on whenever anything is within a half inch of it. I just can't figure that out, but it sucks the battery like a red led vampire!
Sent from my SM-G900V using XDA Premium HD app
Click to expand...
Click to collapse
Heart rate monitor thing was fixed in OC4 I think, but if it still goes off a factory reset will fix it.
Agree
OP, I agree with you. It probably is the first version without the definitely improvement overall for users. It is risky to upgrade and troublesome if it didn't work out well on your devices. Wish Android 5.1 could be better than Kitkat overall.
I have absolutely no problems with the lollipop. I always had it stock from the start and just let the OTAs take over on their own. Have you tried even rebooting into recovery and wipe cache? Even though it's not a custom recovery you can still do that, also even when you dirty flash nightlies that's something that's good practice. My wife's phone had similar issues that I wasn't experiencing, until I did that to her phone and now she's having no problems. Now the general annoyances of how Samsung implemented ****, I understand, it's stupid with not having native flashlight, tethering is annoying having to use foxfi, and the lockscreen.. bleh. But other than that, everything is actually working like it is supposed to
Chiming in, Yes it's bad.
I have two lines with Verizon, both with S5 phones on them. Great device, its actually the first Android phone I've had that I did not do anything with beyond the out of the box experience. That changed when Lollipop was pushed via OTA, the most prominent issue I experienced on both of my S5s is general responsiveness issues, simple things like switching apps or launching apps sometimes would leave me with a white screen for between 5-10 seconds, an eternity especially when the device was lighting fast on 4.4.4 Kitkat. I followed every suggestion from wiping the device in Android, Wiping in recovery, wiping cache, all of these with only marginal improvements. It really is a shame that Google / Samsung did not do a bit better quality assurance on this build before it was pushed out to carriers and ultimately peoples devices. It says something that other carriers skipped 5.0 and that very rapidly 5.1 surfaced on Newer devices / Nexus devices.
As of last night both of my phones are Odin'd back to 4.4.4 and its like having a brand new phone. Sure, there might not be as much polish, but there are no features I will die without having. The only one that I can say I do miss is the feature where the device will disable the lock screen when your smart watch or home WiFi is connected.
Here's to hoping that Google eventually gets Android 5 right in the optimization department and that Samsung picks it up for the S5, and that Verizon gets it ready for OTA before I am ready to move on to a new device. Not interested in the S6 at all for its sealed nature for storage and battery, but that's for another thread on a different day.
-Nate
I Have to agree. I've given it several chances to perform to expectations but it just fails.... ( insert sad puppy face here ) no matter what I have tried it just under-performs and the biggest thing is the horrible battery life. Sooooo yeah like most of the other commentators in this thread, I'm moving back to 4.4.4......
Unfortunately/fortunately, I have found most of my battery issues were solved with a factory reset. I'm more frustrated that Samsung seems to having issues with Android Auto.
ldeveraux said:
Tldnr
Don't start a thread just to complain
Click to expand...
Click to collapse
Observations, not complaints. Getting these points out in the open is an essential stepping stone to getting them fixed. Maybe, just maybe, a Producteer or architect at Google has read this by now so they know what to improve next time. Problems cannot be solved until they are defined.
---
UPDATE:
The issue with the screen not sleeping was actually related to the "Show CPU Usage" setting in the app "OS Monitor". I've used that for years on previous Android version with no problems. In Lollipop, it must be disabled.
CaptainRewind said:
Observations, not complaints. Getting these points out in the open is an essential stepping stone to getting them fixed. Maybe, just maybe, a Producteer or architect at Google has read this by now so they know what to improve next time. Problems cannot be solved until they are defined.
---
UPDATE:
The issue with the screen not sleeping was actually related to the "Show CPU Usage" setting in the app "OS Monitor". I've used that for years on previous Android version with no problems. In Lollipop, it must be disabled.
Click to expand...
Click to collapse
Yeah, go start a petition, just like the bootloader guys, see how far it got them? No one from google reads your complaint threads and regrets their work...
ldeveraux said:
Yeah, go start a petition, just like the bootloader guys, see how far it got them? No one from google reads your complaint threads and regrets their work...
Click to expand...
Click to collapse
Yeah, I guess that was wishful thinking.
In any case, it seems this thread was a complete waste of time. It made me feel better at the time, but looking back on it and the purpose of this site, it doesn't add any value or help anyone modify their phone. Not only that, one of my primary reasons for the OP was the screen lock issues which turned out to be an app, not the Android version.
So, I stand corrected. Live and learn. Enough said.
My wife would never let me root her phone ever. After this update either I find a way to go back a few with root or it goes against the wall. Looks like I have to start reading and figure out how to do this.
Lol I love how you described it. Sometimes you have to vent. Lol
CaptainRewind said:
UPDATE:
The issue with the screen not sleeping was actually related to the "Show CPU Usage" setting in the app "OS Monitor". I've used that for years on previous Android version with no problems. In Lollipop, it must be disabled.
Click to expand...
Click to collapse
Care to share where this app is?
Sent from my SM-G900V using XDA Free mobile app
dk-v1 said:
Care to share where this app is?
Click to expand...
Click to collapse
This is the one:
https://play.google.com/store/apps/details?id=com.eolwral.osmonitor&hl=en
It's a great app, but something about it staying active in the Notification Bar keeps the screen awake. I still use the app, just can't keep the notification active in Lollipop.
And in case it isn't obvious, even though I still have my concerns about Lollipop, I never did go about the procedure of downgrading. It looks like a risky procedure, and I don't want to trip Knox, or worse, have a brick.
CaptainRewind said:
This is the one:
https://play.google.com/store/apps/details?id=com.eolwral.osmonitor&hl=en
It's a great app, but something about it staying active in the Notification Bar keeps the screen awake. I still use the app, just can't keep the notification active in Lollipop.
And in case it isn't obvious, even though I still have my concerns about Lollipop, I never did go about the procedure of downgrading. It looks like a risky procedure, and I don't want to trip Knox, or worse, have a brick.
Click to expand...
Click to collapse
Ok, so it's not a stock app. I am still having poor battery life and overheating issues.
Sent from my SM-G900V using XDA Free mobile app