Related
I installed the Android OS on my phone that was found on this post:
http://forum.xda-developers.com/showpost.php?p=5480057&postcount=7353
I updated it and everything to what he has but occasionally my hard buttons at the bottom will either stay lit or not respond at all. Or it will even go crazy as if I were sitting there spinning my finger around the middle hard button thus making it highlight everything on my menu. That also causes trouble because then it thinks that when I press the home key it decides to bring up the call log screen.
Is there anyway to disable the "iPod Scroll" on the center hard key?
Dude. You should update to the newest build. And update Rootfs and zImages.
everything is in the XDAndroid thread in this forum.
I updated to the one found here:
http://forum.ppcgeeks.com/showthread.php?t=104276
And my scroll wheel and hard buttons still mess up from time to time.
What device do you have? RAPH100?
Sorry I don't know the developer names but its the HTC Fuze for AT&T so it's either the RAPH100 or just the RAPH. The start up config I'm using for Droid is the RAPH config.
Its best not to touch the capacitive DPAD and scroller during boot up. (safe time is when you can see a n d r o i d or the bootscreen.) This and having the pad clean is very crucial if you don't want it going crazy.
Try cleaning it with a wet cloth/tissue and try again.
I also had a screen protector which was massively scratched which caused problems. Ever since removing it the DPAD has been working great.
dude i totally have the same problem.
i ve tried wipe it clean but no luck.
sometimes everything work great but all of a sudden the buttons go wild and start flashing. after that, nothing will bring it back to normal. maybe after a few minutes if will stop blinking, lefting one or two LEDs on, and the button is then less responsive, though still works if you place your finger on the button you want for a few seconds before pressing.
I've seen a few people complaining about this but other says its because of our own device...
However everything works normally in WM... so i guess it might be about the sensitivity or something like that.
no matter it get fixed or not, I do want a method to disable the scrolling too, and maybe the left and right buttons, because they never work even under WM...
Yeah, mine does that too. Its random, sometimes not happening for days, then all of the sudden it starts. And this is within the same boot. Very odd. BTW, I keep up on all builds, always update asap, and my pad is spotless. I can't really figure it out.
also getting the exact same problem a lot, with everything up to date, clean, and not touching on bootup. would it be difficult to implement a code where we could just disable the middle scroll wheel? thats the thing that causes the most problems, and its not really that useful anyway.
@reverendkjr
This may be off topic but, you say you leave your phone running Droid all the time? How do you not drain your battery in like 4 hours unless you leave it charging all day?
But I'm pretty sure I'm as up to date as I can be and I still get this issue.
twiggy159 said:
@reverendkjr
This may be off topic but, you say you leave your phone running Droid all the time? How do you not drain your battery in like 4 hours unless you leave it charging all day?
But I'm pretty sure I'm as up to date as I can be and I still get this issue.
Click to expand...
Click to collapse
Its not off topic at all. I have been using Xandroid as my one and only OS for about a month now. I do charge it quite often, and I leave it on my desk at work on a charger. I also charge it at night as I sleep. I start off the day with 100% and can go 6 or so hours without issue. I continuously get 3-4 days in a row without a reboot or a failure. I find that it has become a suitable alternative to Winmo. The difficulty that I have is that there are primary functions which I miss a bit (camera mostly). But I feel that in order for me to fully understand and appreciate this, and to be able to contribute as a quasi beta tester, I must be willing to spend as much time with it as possible. I keep up with these forums on a regular basis , checking them sometimes 2-3 times a day. It is difficult to distinguish helpful info sometimes, since there are several versions floating around, and not everyone has the same setup & environment. I search as much as I can to find my own solutions, and for the most part, I'm relatively proud of myself. I usually only chime in when something is really bugging me, or I see something valuable that I can add to a conversation.
This issue was one that I had seen a few people talk about, and it had always been chalked up to being a dirty sensor type of thing, or someone touching the pad while it was booting. Having tried all of these solutions with no success, I had come to the determination that it was not constant, it could be ignored or dealt with, and eventually someone would fix it. It is most definitely not a "hot" item, so I never made a stink about it. Now that others have brought it forward, I decided to add my experiences.
I have loads of respect for the developers, and realize that they are not doing this for me. They are doing it for themselves, and fortunately, they share it with us. I am envious of their ability to make this project possible, and have no expectation or demands. I just take what they give us, and try to make it work for me.
Just my two sense, I'll step away from the pulpit now.
+1 for Navigation Wheel or capacitive D-pad issue
reverendkjr said:
Yeah, mine does that too. Its random, sometimes not happening for days, then all of the sudden it starts. And this is within the same boot. Very odd. BTW, I keep up on all builds, always update asap, and my pad is spotless. I can't really figure it out.
Click to expand...
Click to collapse
May I appeal to the developers to move Raph110 Navigation wheel to "Not working" so further development can occur. I do not touch the wheel during boot, but it still randomly flips out. My screen is clean. I did the clean cloth thing. The Navigation wheel not only flips out going all over the place. It actually rarely works the way it should in any application.
All I really need is to turn it off or disable the Navigation wheel if at all possible. Is it necessary to load the Nav-wheel capacitive drivers or can we disable them? Would it disrupt the function of the D-pad if disabled because all I need is the D-pad.
Chime in RAPH110 guys. Would you care if the Nav-wheel was disabled, because I actually think this is what is causing the issue.
I just want to make sure that I communicate to any developers that this is not a major issue. To me, I feel as though this is the only issue that I have at all. With the build I use, I honestly have no other issue which means that the Raph110 Android end product is 99% complete. To be direct, Thank you! I feel as though you purchased me a new phone, so this is no way a complaint. It is only the last 1% quality assurance analysis. ;-)
Edit: I just re-read this thread and the common denominator is HTC Fuze or RAPH110 users are having this minor issue. RAPH100 posting are saying "Just read the thread" or "use updated packages" or "clean the screen" which I think may all work and be valid for you RAPH100 users. I can indeed say without a doubt that this does not work for RAPH110.
In order for me to stop the random D-pad/Nav-wheel random scrolling, I have to screen lock it, let it go to sleep, then it might stop. It does stop mind you, but it is quite random how I am able to stop it.
spideyngo said:
May I appeal to the developers to move Raph110 Navigation wheel to "Not working" so further development can occur. I do not touch the wheel during boot, but it still randomly flips out. My screen is clean. I did the clean cloth thing. The Navigation wheel not only flips out going all over the place. It actually rarely works the way it should in any application.
All I really need is to turn it off or disable the Navigation wheel if at all possible. Is it necessary to load the Nav-wheel capacitive drivers or can we disable them? Would it disrupt the function of the D-pad if disabled because all I need is the D-pad.
Chime in RAPH110 guys. Would you care if the Nav-wheel was disabled, because I actually think this is what is causing the issue.
I just want to make sure that I communicate to any developers that this is not a major issue. To me, I feel as though this is the only issue that I have at all. With the build I use, I honestly have no other issue which means that the Raph110 Android end product is 99% complete. To be direct, Thank you! I feel as though you purchased me a new phone, so this is no way a complaint. It is only the last 1% quality assurance analysis. ;-)
Edit: I just re-read this thread and the common denominator is HTC Fuze or RAPH110 users are having this minor issue. RAPH100 posting are saying "Just read the thread" or "use updated packages" or "clean the screen" which I think may all work and be valid for you RAPH100 users. I can indeed say without a doubt that this does not work for RAPH110.
In order for me to stop the random D-pad/Nav-wheel random scrolling, I have to screen lock it, let it go to sleep, then it might stop. It does stop mind you, but it is quite random how I am able to stop it.
Click to expand...
Click to collapse
I think mine is a RAPH100... i cant take out the battery and double check... but mine is a unbranded version fron 3 australia... which i remember is raph100. and i totally have the same issue so this is not only happening on raph110 i believe.
Hey guys,
I was having the same problem in wm6.5 using many different energyroms, i disabled the scrollwheel altogether within the registry, never used it anyway. I am now getting the same problem in Android. is there is a registry parallel in android?
btw using a RAPH100 (all above fixes did not work)
devs, is there no easy way to implement a disable scroll wheel setting?? i swear that wheel will drive me crazy at times
While this could be an issue with all Raph 110's (AT&T Fuze), I think it is just a subset due to hardware problems. For me, the problem only happens occasionally and it does not only occur in xdandroid, but also in WM. There is an HTC tool (for WM) named NavDbgTool.exe that will show you what is happening with the capacitive buttons/touch area on the Raph. For me, when I have issues it lights up all over and shows touches occurring that are not occurring. I know of at least one XDA member (Captain Throwback) who was able to get a replacement phone (a Tilt2) from the insurance carrier because of this issue.
Perhaps this is a problem that eventually happens with all Raph 110's due to a hardware flaw. If that is the case, maybe enough complaints to AT&T will cause them to replace all of the devices (similar to how Sprint is replacing all their Touch Pro's due to overheating issues). In the meantime, if you have insurance, you should be able to get a replacement phone, just use the NavDbgTool.exe to document the problem in WM.
Also, due to this issue, it would be nice to have the option to disable the capacitive touch area on the Raph 110 in xdandroid (while keeping the D-pad working). I don't use it for anything now that zooming doesn't work for recent versions of Opera in WM.
I'm starting to think that this is Winmo ROM related. I noticed that since I've used the ROM that I have installed right now, the amount of times this issue has affected me has been slim to none. I am currently running the an NRG rom from june 12 with sense 2.5.
link: http://hotfile.com/dl/47992175/ccd8b44/Energy.RAPHAEL.21905.Sense2.5.Jun.12.7z.html
I'm not guaranteeing anything, but its working for me.
Maybe it has something to do with a package that is built into certain roms. I have noticed a few times where the winmo ROM i have loaded will affect Android's performance as well. The ROM that I am currently running was also what provided me with the ability to get GPS working in Android.
I hope this helps some of you.
I don't think it has anything to do with WM. For me, it only happens in Android.
firstly i have a raph100 that has this issue too, so its not just raph110
secondly, for me, this happens in wm too but a lot less frequently and seems to repair itself. It happens in android 70% of time when i boot, the 30% else happens later...
newly released zimages seem to shutdown the capacitive panel when sleeping, and this solved my problem a little bit since every time it goes crazy I can put the device in sleep then resume it...
But when it goes asleep the two buttons on the right act as back, the two on the left act as home. I think there is only one physical button on both sides, the touch figures if you are pressing back or end.
Sent from my AOSP on XDANDROID MSM using XDA App
i've tried searching this forum with no luck for results, so maybe someone can point me in the right direction...
just wondering if there is a fix for this issue, that apparently is a bug:
when receiving an incoming call, and while the phone ringer is turned on, it will ring for a split second then it will stop ringing. the call will still be coming through and i can answer it and talk just fine, it's just the ringer that is the problem. this happens randomly, and i've found numerous posts on other forums by searching google, but haven't been able to find anything here.
can't post a url so here's some quotes:
My Dinc sometimes stops ringing after half a second with incoming calls. I'd hear a very short ring and then it just stops ringing or vibrating. I just noticed this today after missing several calls with my phone today.
This problems comes on randomly and goes away in a similar fashion. This seems to happen only when the phone is lying screen down on a flat surface. I called HTC and they said it might be due to the sensor in the front and advised me to not put phone face down and always carry it in a pouch. This is not an acceptable solution. I carry my phone in my pocket and it can very well be face down in there.
Has anyone noticed this problem? If not, I invite you to reproduce this problem. Put your phone screen down on a perfectly flat surface and try to call your cell. I'm wondering whether my phone is defective or it's a much wider issue.
Thanks.
Update: Apparently there is a feature on HTC devices when if you're holding the phone and if it rings, it will mute if you put it on a surface face down. While this is fine, the problem with my device is that if I leave it on a flat surface, it will do that for all subsequent calls too (ring for half a second and then mute). Maybe my phone has a bug in implementation of this 'feature'?
Click to expand...
Click to collapse
It's a well known issue that HTC has not fixed and will most likely never fix. I've been through 3 Dincs because of this problem and they all do the same thing. Quite irritating! Nice phone except for this BIG bug.
Click to expand...
Click to collapse
is there any fix for this bug? and does anyone know if this bug is software or hardware related. currently, i'm running stock 2.2 rooted with city id deleted. thinking about flashing CM7 or another custom rom, and just curious if it will do this with those roms as well.
thanks for any help
Must be an issue with the stock rom. I've never had a problem. But I've also never ran the stock 2.2 rom. I ran stock 2.1 until root was achieved. Custom Rom's from there on out.
Sent from my ADR6300
Also on my HTC Wildfire
This happens also on my htc wildfire android v2.2.1 (latest official rom), i think it is caused by the mute-on-pickup feature that is bugged in some way, even if i have turned it off.
I know the proximity sensor is not functional with the Rhodium400. My wife and I are both running the newest version FRX 7.1 on the .27 kernel.
She had issues with Windows Mobile getting a data connection, and it would carry over to Android. So I dd a hard reset on Windows Mobile and started her Android from scratch (as it was having other slowness and issues also). Ever since then she tells me (and I have heard this in call) that every time she puts her cheek or face to the phone it will sound as if the call dropped but it doesn't drop really. She can't hear me and I can't hear her, but as soon as she takes her head away she and I can both hear again. This doesn't happen all the time, and is likely only happening when XDAndroid has not been rebooted in a few days.
I have not been able to confirm it by sitting right beside her and calling and confirming the problem, but I plan to do so tonight. At first I thought she was just muting me because she was ticked at me...don't ask , but she isn't smart enough to come up with something like this, because technically it sounds like the proximity sensor is mucking up the phone call which I thought was not possible from everything I have read. I even had her turn the power button off at the top to turn the screen off, to make sure she wasn't bumping any buttons. The way it looks, it almost sounds as if the phone is inadvertently trying to place another phone call and putting the first phone call on hold.
Has anyone else had this issue? Doe anyone think this is likely a proximity sensor issue, or have any advice for when I get home tonight and start playing with the phone?
Supposedly also this issue was going on with her in the car and the phone plugged into a car charger. She called me back with it not on the charger and it is not messing up anymore. I don't know if it is coincidence or not, since it wasn't always doing it to begin with.
Never heard of this, almost sounds like a hardware failure.
Run WinMo for a few days, see if you can recreate the problem there. If so, there's something going haywire with the physical hardware.
I get a situation kind of like this in Android, but not WinMo. Basically if I recieve a call it's about a 50/50 chance that this happens. I can't hear them and they can't hear me. There is no sound at all, like the speaker and mic don't even turn on. However, mine doesn't seem to have anything to do with the proximity sensor as it does it as soon as I hit the answer button and moving the phone away doesn't fix it. Also, it's only when recieving calls, outgoing calls work all the time.
I've had similar problems, but quite a bit in the past, making me think mine was software or settings. So don't discouraged!
My thinking is, since auto-mute to rear speaker/mic system is a 'feature', that maybe that system gets triggered. Check those settings, and that level/bubble calibration stuff.
So I am hoping someone with some real hardware/software knowledge can provide some input...
I recently received my warranty replacement unit because of unresponsive touch and phantom touches. My new unit seems to work perfectly, except now every 10 to 20 touches, the touch will register, but the touch sound "click" doesn't play (if I put my ear close to the speaker, I can hear the speaker activating though). Repeated touches (like repeatedly pressing back) won't reproduce the problem, but more random timing and touches (like in regular use or typing) will. I'm wondering if anyone thinks this is a hardware issue, or some component of the stock software that wouldn't have been overwritten between the update to JSS15Q, and then to JSS15R (it happens in all three versions).
Think I should go for another replacement? Or do you think I should root and unlock, and see if a full installation of a ROM fixes it. It's definitely a sign that something is wrong and it's annoying, I just can't figure out if it's software or hardware related. I'm definitely not going to just ignore it.
(SIDE STORY: When I called nexus help for my first unit, the guy was so helpful and took my word that I had already tried factory resets, and set me up for an RMA. My call on this unit, the woman told me to reboot and toggle touch sounds, and kind of rudely insisted that I was on 4.3 and that Build Version (e.g. JSS15R) had nothing to do with software!! :what: She then told me she'd send me an email with more troubleshooting steps, which never came. I had figured I'd wait for the email, so that I had her name for my next call. Totally unacceptable.)
You come off as just looking for a reason to complain at this point, there doesn't seem to be any real problem with your device other than you being overly picky
Sent from my HTC One using Tapatalk 4
You're completely right. I was so delighted when I managed to find something wrong with my new tablet...
Seriously? You come off as just a worthless ass of a poster at this point. The problem is there, and can be consistently reproduced. I press home and it clicks, and five seconds later I press home and it doesn't click. Your opinion on whether this is a "real problem" or me being overly "picky" is completely irrelevant. It is most certainly real and not normal, and indicates either some software or driver bug on my device, or a strange hardware malfunction. My previous unit (which had very real problems) did not have this problem.
I hope I speak for others here, when I tell you to **** off unless you have something worthwhile to contribute. Just because you don't think something is important, annoying, significant, etc. doesn't make it any less so for someone else.
Do you have this issue with SwiftKey?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Yeah. It's actually everywhere throughout the OS. System settings, stock launcher, Nova launcher, Swiftkey, AOSP keyboard, etc.
I have the opposite problem as you. When muted, every 20 or 30 taps I will get a 'pop' from the speakers, similar to the sound of plugging a guitar into an amp when it's on. Pretty bloody annoying, but I don't want to risk returning it for receiving a unit with worse problems.
GoneTomorrow said:
I have the opposite problem as you. When muted, every 20 or 30 taps I will get a 'pop' from the speakers, similar to the sound of plugging a guitar into an amp when it's on. Pretty bloody annoying, but I don't want to risk returning it for receiving a unit with worse problems.
Click to expand...
Click to collapse
Exactly my thoughts on going through another RMA. But I do feel that it's reasonable to expect a properly functioning tablet on our parts. What you're experiencing is strange. I can tell you that on my Optimus G, when muted, I can hear a faint speaker "activation". Sounds like maybe yours is a hardware issue. Are you stock, or have you tried flashing other ROMs?
Well, I installed CM10.2 last night, and the problem went away. Maybe you might want to try CM, or even just unlocking and reflashing stock JSS15R. You might get lucky with your popping noises.
FYI: I've seen this on multiple tablets (TF101, GTab, Nooks, 2012N7, 2013N7) with different customed ROMs.
So, I wouldn't blame it specially on the Tab. In fact, I see this issue less often on the 2013N7. It usually happens
after I just freshly loaded a new ROM.
spackmanbr said:
Well, I installed CM10.2 last night, and the problem went away. Maybe you might want to try CM, or even just unlocking and reflashing stock JSS15R. You might get lucky with your popping noises.
Click to expand...
Click to collapse
So a couple of nights ago, I decided to try disabling touch sounds in settings. Since doing that I haven't heard a single pop from the speakers. Looks like it was either the touch sounds 'leaking' or the speakers popping from being activated, which they do even when muted (the mute being software)
I'm quite happy with this fix, since the tablet is muted 99.5% of the time, and I don't care for the touch sounds anyway.
Hi Folk's,
Sorry to drag up an old post, but I've noticed my N7 shows this behaviour on KitKat as well.
It misses the touch sound if you pause for about 5 secs during input. Does it every time and it's very annoying. I've tried a couple of different KK roms and it does the same on all of them.
Just tried going back to CM10.2 (JB 4.3) and it works fine!
Does anyone know the cure for this, apart from going back to JB, please? Would really like to be running KK, but this bug is bugging me!
Thanks for any info.
Cheers
I have bought one nexus 7 2013 32gb recently and im experiente this strange beahvior ...im on lolipop 5.1.1! What i have to do to solucionate?
Petermira said:
I have bought one nexus 7 2013 32gb recently and im experiente this strange beahvior ...im on lolipop 5.1.1! What i have to do to solucionate?
Click to expand...
Click to collapse
@Petermira @Xi2or @spackmanbr
I have this same behavior on a stock 4.4.2 S3.
After 5 seconds, if I click anything UI (keyboard, Soft buttons, shortcuts, toggles) there is no sound. If I quickly click again and keep clicking, the sounds work as normal. It's definitely ROM related but is there a fix???
UPDATE: Issue does not happen with headphones plugged in. STRANGE!!!
UPDATE: Issue does not happen if I keep a song playing in Power Amp or similar.
Affected UI items include:
- keyboard
- shortcuts
- toggles
- capacitive buttons
- dialer pad
- etc.
I don't try Beta releases, but I tried the P anyway, mostly because of the new UI design and stuffs, but I couldn't stay on it for like 30 mins even.
Firstly, and I don't know whether it will be brought back or not, you now have to swipe down from notification bar area twice to access Settings menu! I mean WTF!
Secondly and the most annoying and inconvenient thing, now you can't increase or decrease the Ringer with the volume buttons. No matter what you do Volume buttons now will only control the Media volume! I mean WTAF! I use the Ringtone volume at least 10 times than the damned Media volume! To increase or decrease the Ringtone you now have to click on that tiny Settings icon and then increase the ringer or decrease, and while you do that, your ringtone will be played for a brief period of time, unlike the older method, where you could just slide left or right to decrease or increase from any screen and it will never play the ringtones in the process!
Really? No one goes to any business meetings or something? Now you gotta alert them hey look I am controlling my phone's ringer! What the actual **** Google?
I used it for like 15 mins before coming back to Oreo, but if these changes are made fundamentally then its a big pile of ****.
Oh, and that swipe up from home button, I mean please Google, really? Worst implementation of gesture based navigation one could ever think of! Either gestures should be done from full screen or go back to old nav bar or just GTFO!
Every Android update now seems to think how to make users spend more time in trying to do the simple things, it's baffling how inconvenient the experience is becoming. Remember in Nougat we actually had double tap to lock screen and then swipe to unlock? Never had to press the power button, ever. Now with Oreo they got rid of that, quad tap was introduced and now with P these even more stupid things are here.
Is it time? I mean to go back to dumb-phones or something?
ithehappy said:
I don't try Beta releases, but I tried the P anyway, mostly because of the new UI design and stuffs, but I couldn't stay on it for like 30 mins even.
Firstly, and I don't know whether it will be brought back or not, you now have to swipe down from notification bar area twice to access Settings menu! I mean WTF!
Secondly and the most annoying and inconvenient thing, now you can't increase or decrease the Ringer with the volume buttons. No matter what you do Volume buttons now will only control the Media volume! I mean WTAF! I use the Ringtone volume at least 10 times than the damned Media volume! To increase or decrease the Ringtone you now have to click on that tiny Settings icon and then increase the ringer or decrease, and while you do that, your ringtone will be played for a brief period of time, unlike the older method, where you could just slide left or right to decrease or increase from any screen and it will never play the ringtones in the process!
Really? No one goes to any business meetings or something? Now you gotta alert them hey look I am controlling my phone's ringer! What the actual **** Google?
I used it for like 15 mins before coming back to Oreo, but if these changes are made fundamentally then its a big pile of ****.
Oh, and that swipe up from home button, I mean please Google, really? Worst implementation of gesture based navigation one could ever think of! Either gestures should be done from full screen or go back to old nav bar or just GTFO!
Every Android update now seems to think how to make users spend more time in trying to do the simple things, it's baffling how inconvenient the experience is becoming. Remember in Nougat we actually had double tap to lock screen and then swipe to unlock? Never had to press the power button, ever. Now with Oreo they got rid of that, quad tap was introduced and now with P these even more stupid things are here.
Is it time? I mean to go back to dumb-phones or something?
Click to expand...
Click to collapse
Definitely all you.
1. You've got me with the settings, but I don't usually get to settings through there, so for me, I could care less.
2. Umm, how about you, ya know, put your phone on silent BEFORE you go into the meeting? 90% of the time I touch the volume buttons, it's for media. My ringer is either on, off, or vibrate. I very rarely set it to a lower volume. When I'm in a business meeting, I'm there for business. I don't need my phone to go off, even low.
3. I like the gesture nav, so you've lost me on that one as well.
If you don't like it, I'm sure you'll have other manufacturers who still include the regular nav bar. Doubt Android will completely take it away, at least for the foreseeable future. Maybe on Pixel devices, but they won't enforce that globally. Android is changing. It's been changing. You either change to keep up with times, or you try to trailblaze. I've had Android since the g1 .. trust me, you learn to take the good with the bad. At least in the preview the gestures are an option. The double tap does annoy me a bit, but at the end of the day ... It's a phone. It will take me less than a second to tap two more times, and go about my life. There is no reason to be raging this hard. Nobody is forcing you to update
ithehappy said:
I use the Ringtone volume at least 10 times than the damned Media volume!
Click to expand...
Click to collapse
You are one of a very small number of people. Most people have been asking for Google to make this change for years, because almost nobody changes their ringer volume. If you need to silence your phone, why not use the "Do Not Disturb" quick tile, instead of changing your ringer volume?
This is actually the one change I am most excited for with Android P, because it was one of the reasons I used to use Lineage.
Omg! This stupidly accepting mentality is the reason why Google will not be bothering to consider bringing back the practical, convenient options any more!
I mean jeez! Time is obviously of no importance to the people who can adapt with time wasting method rather than time saving ones! Like double tapping to quad tapping. Like going into sound option and then get the option for changing ringer volume, rather than just hitting volume buttons! Also it's so aesthetically displeasing. Every time you wanna change the ringer you'll hear the ringtone, RoFL.
ithehappy said:
Omg! This stupidly accepting mentality is the reason why Google will not be bothering to consider bringing back the practical, convenient options any more!
I mean jeez! Time is obviously of no importance to the people who can adapt with time wasting method rather than time saving ones! Like double tapping to quad tapping. Like going into sound option and then get the option for changing ringer volume, rather than just hitting volume buttons! Also it's so aesthetically displeasing. Every time you wanna change the ringer you'll hear the ringtone, RoFL.
Click to expand...
Click to collapse
Are you a child? Honestly, you sound stupid. Times change. Go back to another manufacturer, as I'm sure there are those who will do things differently. If you think quad tapping is going to take years off your life, you must be expecting to live for a mighty long time. It's not that huge a deal. You're making a mountain of an anthill. You only want what YOU want, and don't care what anyone else wants. YOU think it's dumb, so you think everyone must agree. Grow up. To change my ringer, I simply press the volume button, then click the icon for silent, audible, or vibrate. I don't change my ringer volume 10+ times a day. Most of the people who have been asking for YEARS don't. We get it, you want to go back to nougat forever. Then do so, and shut up. Honestly. Every single time Google changes something people complain. They aren't forcing you to use Android. If you don't like it, there are alternatives, or you can learn to program yourself and make your own. Year after year you people belly ache over a FREE operating system. My time is very valuable, which is why I don't spend so much time on it to need to change volume 10+ times a day, or worry about having to quad tap the few times I actually need the phone. When I pull it out of my pocket, it lights up. Double tap. I'm not glued to my device. Also, I don't think it's aesthetically displeasing. I enjoy it. I also prefer German cars over Japanese. I think the Audi rs4 looks better than the Mitsubishi Eclipse. I like vanilla instead of chocolate. The world is full of different flavors than just what YOU want, and you'll get further in life the less you complain because things aren't going your way, and start enjoying what you have. Officially done with this stupid thread.
dictionary said:
Are you a child? Honestly, you sound stupid. Times change. Go back to another manufacturer, as I'm sure there are those who will do things differently. If you think quad tapping is going to take years off your life, you must be expecting to live for a mighty long time. It's not that huge a deal. You're making a mountain of an anthill. You only want what YOU want, and don't care what anyone else wants. YOU think it's dumb, so you think everyone must agree. Grow up. To change my ringer, I simply press the volume button, then click the icon for silent, audible, or vibrate. I don't change my ringer volume 10+ times a day. Most of the people who have been asking for YEARS don't. We get it, you want to go back to nougat forever. Then do so, and shut up. Honestly. Every single time Google changes something people complain. They aren't forcing you to use Android. If you don't like it, there are alternatives, or you can learn to program yourself and make your own. Year after year you people belly ache over a FREE operating system. My time is very valuable, which is why I don't spend so much time on it to need to change volume 10+ times a day, or worry about having to quad tap the few times I actually need the phone. When I pull it out of my pocket, it lights up. Double tap. I'm not glued to my device. Also, I don't think it's aesthetically displeasing. I enjoy it. I also prefer German cars over Japanese. I think the Audi rs4 looks better than the Mitsubishi Eclipse. I like vanilla instead of chocolate. The world is full of different flavors than just what YOU want, and you'll get further in life the less you complain because things aren't going your way, and start enjoying what you have. Officially done with this stupid thread.
Click to expand...
Click to collapse
Calm the **** down. My complaint is against Google, not you. Though I have seen Google shills before, so nothing new.
If your time is as valuable as you claim it is, then you would not have preferred more time consuming thing, period, simply confirms you're just another Google shill, or just someone needing medical care.
I didn't ask you to say anything here, you came yourself, because you were pissed off simply because I pointed out facts of Google's idiosyncratic choices. Simply bugger off if you think topic is stupid, I for one not giving the slightest damn about it anyway.
ithehappy said:
Secondly and the most annoying and inconvenient thing, now you can't increase or decrease the Ringer with the volume buttons. No matter what you do Volume buttons now will only control the Media volume! I mean WTAF! I use the Ringtone volume at least 10 times than the damned Media volume! To increase or decrease the Ringtone you now have to click on that tiny Settings icon and then increase the ringer or decrease, and while you do that, your ringtone will be played for a brief period of time, unlike the older method, where you could just slide left or right to decrease or increase from any screen and it will never play the ringtones in the process!
Really? No one goes to any business meetings or something? Now you gotta alert them hey look I am controlling my phone's ringer! What the actual **** Google?
I used it for like 15 mins before coming back to Oreo, but if these changes are made fundamentally then its a big pile of ****.
Click to expand...
Click to collapse
Ringer on/off is power button + volume down.
really dude?
It's pretty quick to turn off the ringer... Hit the volume control then touch the bell on top of the volume slider.
ithehappy said:
Calm the **** down. My complaint is against Google, not you. Though I have seen Google shills before, so nothing new.
If your time is as valuable as you claim it is, then you would not have preferred more time consuming thing, period, simply confirms you're just another Google shill, or just someone needing medical care.
I didn't ask you to say anything here, you came yourself, because you were pissed off simply because I pointed out facts of Google's idiosyncratic choices. Simply bugger off if you think topic is stupid, I for one not giving the slightest damn about it anyway.
Click to expand...
Click to collapse
I'm gonna suggest you are the one needing to calm down here.
I'm on P.
Now I'm getting used to how it's working, I'm liking it.
Still needs some tweaks, and you can turn off gestures if it's really causing you sleepless nights
y2grae said:
I'm gonna suggest you are the one needing to calm down here.
I'm on P.
Now I'm getting used to how it's working, I'm liking it.
Still needs some tweaks, and you can turn off gestures if it's really causing you sleepless nights
Click to expand...
Click to collapse
No, i was calm. Just because i made one forum post seemed to look like i was raging, it has no relation with my personal life.
Like i said, I'm not the accepting lot, I'll never support this stupid ass decision of Google. And I'll die before becoming a shill. If you like it, good for you, the shills, not saying you are, mostly like whatever Google brings about without even giving it a personal thought, good for them, well not really but whatever.
You understand that the P Beta is not the final release and that Google actually throws stuff out there that they aren't 100% sure about just to get public feedback on it, right? P isn't perfect.. It crashes apps fairly often... But... you know... it's in Beta... If you don't want to deal with some things that aren't quite polished yet, don't participate in the Beta testing.
ithehappy said:
No, i was calm. Just because i made one forum post seemed to look like i was raging, it has no relation with my personal life.
Like i said, I'm not the accepting lot, I'll never support this stupid ass decision of Google. And I'll die before becoming a shill. If you like it, good for you, the shills, not saying you are, mostly like whatever Google brings about without even giving it a personal thought, good for them, well not really but whatever.
Click to expand...
Click to collapse
If this is your "calm", I suggest there are deeper issues you might want to look into. "I'll never support this stupid ass decision of google. And I'll die before becoming a shill"
ISSUES!!!
Also, for the record, that ISN'T calm. That's wound up over something
As stated above, this is Beta, and this is a testing environment. Maybe this environment isn't best for someone who doesn't like change?
For me, P has been great. Especially battery life.
I love how everything you hate is everything I love on P and why I'm never going back. I was just thinking who adjusts their ringer volume a few weeks back, guess I found the 1 person.
y2grae said:
If this is your "calm", I suggest there are deeper issues you might want to look into. "I'll never support this stupid ass decision of google. And I'll die before becoming a shill"
ISSUES!!!
Also, for the record, that ISN'T calm. That's wound up over something
As stated above, this is Beta, and this is a testing environment. Maybe this environment isn't best for someone who doesn't like change?
Click to expand...
Click to collapse
Yeah ROFL, ISSUES, I mean yeah, with you lots. Someone who found issues with me preferring death than a Google shill definitely is the one with the issue.
Something should be be tried to fixed if it's not broken, old saying, but **** that yeah, those who don't understand who need to change their ringtone volume often obviously never went to office or meetings, otherwise this would not have been even needed to think as to the reasoning, FFS, damned 16 year old kids, what would they know about phone calls at first place, sorry my fault.
I sincerely hope Google will revert to old method, because it's simply changing how mobile phones should work, the very fundamental thing, and even for a beta they shouldn't have done that and apologise for the same.
ithehappy said:
Yeah ROFL, ISSUES, I mean yeah, with you lots. Someone who found issues with me preferring death than a Google shill definitely is the one with the issue.
Something should be be tried to fixed if it's not broken, old saying, but **** that yeah, those who don't understand who need to change their ringtone volume often obviously never went to office or meetings, otherwise this would not have been even needed to think as to the reasoning, FFS, damned 16 year old kids, what would they know about phone calls at first place, sorry my fault.
I sincerely hope Google will revert to old method, because it's simply changing how mobile phones should work, the very fundamental thing, and even for a beta they shouldn't have done that and apologise for the same.
Click to expand...
Click to collapse
They won't revert to the old method. They made it clear that this is their plan and its the number one request they had from users. You can revert back and just avoid updates or try lineageos if you prefer that method and make changes on your own. Most of us in an office environment walk in and turn on vibrate mode. I can tell you none of the people on my floor operate by turning down the volume. We all go into meetings and if the sound went off in the customer meeting even at low volumes we would be kicked out of the meetings. I travel 2-3 times a month and I've never been in a customer meeting where they left their phone on at low volumes. Again, its up to you to live your life how you want, but I recommend not assuming we aren't going through the same things. Anyhow, why don't you try switching methods? try the silent mode vs the low ringer. Is there a particular reason you don't like it on vibrate mode? Some of these things can be changed via apps as well. For instance, Tasker can automate your volume adjustment based on events and location if you want.
haibane said:
They won't revert to the old method. They made it clear that this is their plan and its the number one request they had from users. You can revert back and just avoid updates or try lineageos if you prefer that method and make changes on your own. Most of us in an office environment walk in and turn on vibrate mode. I can tell you none of the people on my floor operate by turning down the volume. We all go into meetings and if the sound went off in the customer meeting even at low volumes we would be kicked out of the meetings. I travel 2-3 times a month and I've never been in a customer meeting where they left their phone on at low volumes. Again, its up to you to live your life how you want, but I recommend not assuming we aren't going through the same things. Anyhow, why don't you try switching methods? try the silent mode vs the low ringer. Is there a particular reason you don't like it on vibrate mode? Some of these things can be changed via apps as well. For instance, Tasker can automate your volume adjustment based on events and location if you want.
Click to expand...
Click to collapse
Oh dear lord, I hate any type of ringing at all, back in the days when mobile phones were still thick as brick I never used anything other than vibrate mode, but nowadays these slim phones can't be felt vibrating inside pockets, so you must have the ringtone enabled. Anyway, that's not the point. A low sounded ringtone is still a ringtone, which you can hear, however faint but enough to reach your ears and at the same time not disturbing others, and for you to not miss a call, but vibration can missed if you are a bit distanced from your desk.
If ringtones were meant to stay at a static level, then there would not have been different volume levels at all! And how funny could something be when you can't control your mobile phone's ringtone with your volume rocker. I don't know which sort of users requested this, and I don't know to depth of daftness got into Google to approve a dreadful request like that. I am still more than confident that this will be reverted though. Stupidity lasts not longer.
ithehappy said:
Oh dear lord, I hate any type of ringing at all, back in the days when mobile phones were still thick as brick I never used anything other than vibrate mode, but nowadays these slim phones can't be felt vibrating inside pockets, so you must have the ringtone enabled. Anyway, that's not the point. A low sounded ringtone is still a ringtone, which you can hear, however faint but enough to reach your ears and at the same time not disturbing others, and for you to not miss a call, but vibration can missed if you are a bit distanced from your desk.
If ringtones were meant to stay at a static level, then there would not have been different volume levels at all! And how funny could something be when you can't control your mobile phone's ringtone with your volume rocker. I don't know which sort of users requested this, and I don't know to depth of daftness got into Google to approve a dreadful request like that. I am still more than confident that this will be reverted though. Stupidity lasts not longer.
Click to expand...
Click to collapse
you might look at getting push bullet if you can't hear the phone vibrating like a jackhammer on your desk. Just a thought.
ithehappy said:
Yeah ROFL, ISSUES, I mean yeah, with you lots. Someone who found issues with me preferring death than a Google shill definitely is the one with the issue.
Something should be be tried to fixed if it's not broken, old saying, but **** that yeah, those who don't understand who need to change their ringtone volume often obviously never went to office or meetings, otherwise this would not have been even needed to think as to the reasoning, FFS, damned 16 year old kids, what would they know about phone calls at first place, sorry my fault.
I sincerely hope Google will revert to old method, because it's simply changing how mobile phones should work, the very fundamental thing, and even for a beta they shouldn't have done that and apologise for the same.
Click to expand...
Click to collapse
Yeah
Google needs to revert back because of 1 person.
gonna happen.
when you say you'd rather die than be a shill (who uses "shill" this millenia?!) - then you need to put the tech down. walk away, look at some tranquil scenery