Related
I am starting this thread to be a place for Terrain owners to come for the latest info on how to root and flash their phones. The Terrain is one of the best "rugged" phones on the market, but it has been abandoned by it's manufacturer, leaving owners to find their own solutions to problems and upgrades. This is actually a good thing price wise as you can now buy a brand new Terrain for less then $85. The Terrain has about as of hardware specs as any other ruggedized smartphone on the market currently, but at one third or a 1/4 of the cost. This makes this phone a huge attraction to anyone who is looking for a rugged waterproof phone on a budget and is why this guide is essential for users.
The NEC Terrain still has plenty of life left and this is why we need to come together and find solutions for it. Please feel free to post you success stories in rooting and flashing your terrain to this thread for the benefit of all. Hopefully, will be able to form a complete guide from all the information that get's posted here.
Thanks.
Hi!
I myself just today recieved this phone, and it would be great at least to debloat it.
Previous threads on XDA, just for reference:
NEC Terrain: ADB/CDC Serial Driver, 3e Recovery Password, and Root
[Q] Rooting NEC Terrain
[Q] Unlocking of NEC Terrain SIM/Root
gamerka said:
Hi!
I myself just today recieved this phone, and it would be great at least to debloat it.
Previous threads on XDA, just for reference:
NEC Terrain: ADB/CDC Serial Driver, 3e Recovery Password, and Root
[Q] Rooting NEC Terrain
[Q] Unlocking of NEC Terrain SIM/Root
Click to expand...
Click to collapse
Thanks for the post and the links. It appreas that much of the information on these links are still a work in progress. Hopefully this work will continue and we can create a How To guide from this.
For those that may be interested. You can buy the NEC Terrain Unlock on Amazon for $79.99. Here is the link.
http://www.amazon.com/NEC-Terrain-UNLOCKED-WaterProof-DustProof/dp/B00KZPI04S/ref=sr_1_1?s=wireless&ie=UTF8&qid=1405614968&sr=1-1&keywords=nec+terrain
For full specs on this great phone you can go here.
http://www.gsmarena.com/nec_terrain-5553.php
Well, I almost bricked it few days ago. :good:
I read a thread about a patch to unlock GSM in CDMA phones and saw there a code to enter some hidden menu. I entered that menu and messed a little with band settings (wanted to get LTE to work with my operator). Next thing I know Terrain stopped receiving any GSM signal and for next hour I tried to fix it. Factory reset got me 2G signal and that's all.
It turned out that the only way to fully fix it is to re-flash firmware or radio module and as we know that can't be done.
Well, this is not about unlocking or flashing, but it is a solution to another problem I and many other have been having with the predictive text bar blocking critical function keys from being accessed. The predictive txt bar is a function of the Adaptxt keyboard app and disabling it does remove that bar, but the keyboard also loses all special character function, upper case letters and numbers. After trying more then a dozen keyboard apps to replace adaptxt, I found one that works and brings back all keyboard functions without the stupid predictive text bar. It is called TouchPal.
https://play.google.com/store/apps/details?id=com.cootek.smartinputv5&hl=en
Forgive me for this slight OT-posting, but it's not that easy to find people with this device - let alone an unlocked one. I'm located in Germany and the device runs just fine - except for the fact that Tethering does not work - neither USB nor WIFI. The PC can connect to the phone, however the connection in Windows 7 always is shown as being limited (no internet access), while internet on the phone works fine.
GMail - as well as some other functions of google also rarely sync and basically just do so on request, while they sync just fine when being connected to Wifi. And no, background data are not restricted in the settings.
Has anyone experienced something similar?
laserdrome said:
device runs just fine - except for the fact that Tethering does not work - neither USB nor WIFI.
Click to expand...
Click to collapse
I have the same problem! After few minutes of "thinking" phone reports "There is a temporary nework problem... bla, bla, bla"
Is there any suggestions how to fix it?
iDomino said:
I have the same problem! After few minutes of "thinking" phone reports "There is a temporary nework problem... bla, bla, bla"
Is there any suggestions how to fix it?
Click to expand...
Click to collapse
Well actually I know that message as well. For me changing the APN helped. You could also try to restart the phone. I just remember I also had this problem sometimes. But like I said - even without that particular message I would not get tethering to work.
iDomino: Do you also experience the problem with syncing that I had?
That's funny, actually I haven't noticed syncing problems untill I read your posts. I myself have all the same problems that you mention.
Even more of that, Terrain has some silly feature that TURNS OFF WI-FI if it thinks that that hotspot has no internet connection. It is massively annoying and can drain all your data traffic. The only solution that I found is to install the app "Smart Wi-Fi Toggler", it constantly turns wi-fi on if terrain turns it off, but only in places where I turned wi-fi on myself (like home and work).
It's a pity the phone has so many flaws and due to its tight security and the locked down NEC mobile devision no one can do anything about it. I wonder if this just affects the users who use an unlocked phone outside the US or if people in the US have similar problems. I have tried contacting NEC about this - actually about providing us with some kind of unlock mechanism - but all I got was this:
"Dear Sir,
Thank you for inquiry.
We, however, regret to inform you that our phone is not available about your request.
If you have any issue, would you try to contact the company or shop where you have purchased this model, who might be of help to you.
Thanks and Best Regards,
Fujii /NEC"
By the way, I discovered a new bug: When Roaming the actually used Network-Provider is not shown and I also didn't find a way to choose one...
Do you also experience the problem with syncing that I had?
Click to expand...
Click to collapse
I had some sync problems and I don't know working methods to fix it.
First time I solved it this way:
turning off apps sync -> open Gmail app -> it will show notification offering to enable synchronization -> use it -> sync works.
But this solution worked just once. (
Other time sync turns on by itself after one day disabled.
P.S. My Nec reboots while connecting via USB to ubuntu laptop.
Battery life
Can someone tell me how your Terrains battery hold up charge? Because mine discharges completely in about 10 hours (without using phone at all). I think it's wakelock problem.
iDomino said:
P.S. My Nec reboots while connecting via USB to ubuntu laptop.
Click to expand...
Click to collapse
Does it crashes once or infinite loop begins? I had infinite loop problem while connecting NEC Terrain to Ubuntu, Linux Mint, Debian or CentOS. Removing "ModemManager" package solved it.
FFDA said:
Can someone tell me how your Terrains battery hold up charge? Because mine discharges completely in about 10 hours (without using phone at all). I think it's wakelock problem.
Does it crashes once or infinite loop begins? I had infinite loop problem while connecting NEC Terrain to Ubuntu, Linux Mint, Debian or CentOS. Removing "ModemManager" package solved it.
Click to expand...
Click to collapse
My phone works about 25-30 hours (30 min. calls, 5-10 sms, 30 min. messaging, 2 hours e-mail, internet & other applications. No video/gaming/music at all).
Infinite loop. Removing "modemmanager" helps! Thank you! :laugh:
Also got spontaneous rebooting after installing FTP Client made by Zifero. :silly: Removing app solved the problem.
Dreaming about root and working wi-fi tethering.
Who have usb driver of nec terrain? I need it, thanks
zolahn said:
Who have usb driver of nec terrain? I need it, thanks
Click to expand...
Click to collapse
Maybe this topic will help.
Cpu-z shows only 665MB RAM on device... Where are another 335MB???
Lets continue discussion in one thread!
http://forum.xda-developers.com/showthread.php?p=59514154#post59514154
I created a GitHub repo to collect information, also on how to disable apps (since thats as good as it gets for now).
Another Terrain user here!
Hi guys!
i am Kharl
i am another Nec Terrain user here!
due my lifestyle, i needed a phone which could gives me reliability and power under ANY circunstance, that could be done by any rugged phone, BUT i needed querty keyboard, fm radio, gps, gyroscope, accelerometer, loud speakers, that could work worldwide and touchscreen... the only one with those features was the Terrain... and with the extra, that it is amazingly cool, i dont know opther but i find this phone really cute, very sober and elegant design.
well, i live outside USA so, for me, to work it couldnt be locked to ATT, so i was able to get one unlocked.
my phone has almost all the problems you mentioned, althught i am still happy with it and i am not going to change it because its problems does nto interfere a lot with me, BUT of course id like to get those problems sovled.
trying to solve the problem i bough three of thes phones and all the three had the same problems
the first one was by mistake, locked to att, but it had the same problems, random restart and locked hotspot, i sold it, i got a second one, works with any sim, everything fines, but with the same problem, random restart and no hotspot, i bought a third one to see if the problem was with my particular phone... and n luck the same problems.
it has some other minors problems, like no stereo audio recording despite it has two mics and IT STATES IT CAN record in stereo, but thats not a problem, i can deal with that, and sometimes the people at the other side (while in a call) says my voice sounds like from within a box (lack of trebble or too much bass) and when i press the check too much to the phone boddy there is also clarity sound problem.... but thats ok....
regarding the two main problems
random reboot and hotspot
many of us suspect what the cause is
for the random reboot many could think it is a installe app which is causing it... NO, because it does it at factory state, to solve that i dotn think root is needed, there is a certain factory process that is causin to reboot, the reboot is VERY random, could doit threee times in a day or could happen only three times in a week, what i have notice is that it happe lessoften in cold weather.
the hotspot problem IT IS cause because att locked that function, even when the phone is ulocked, that part remain locked because ATT.
what about you guys?
u can try hard reset for begging
I have posted a similar post in the CRV Owners forum, but I thought this forum would make more sense since it's filled with a bunch of hardware-hacking programmers!
The interface between my car and my phone (LG G2 Lollipop stock) is abysmal. I have seen a number of posts on the web about this issue with modern cars, but no real solutions. The following is a list of what I would like the interface to be between the phone and car. Then at the end of the email I'll flame a little about the "why"s.
GIve me a button to allow me to talk to my phone directly without the HondaLink getting in the way. There was a similar issue with a Volkswagon and a solution using Tasker to intercept the call. That solution doesn't work with my Honda and is a kludge.
Always have the phone interrupt the radio (whether it's a call or audio, e.g. Google maps navigation). For me, the information coming from the phone will always be more important than the music or talk show on the radio.
Mirror the phone screen onto the car screen when I'm driving (so I can see my map when I need to)
When I receive a call, let the phone do the talking (the phone can speak the caller's name to me and can send the caller's name over the bluetooth connection) and let me hit a button to answer it.
Has anyone successfully hacked into the firmware/software in the CV-R to fix these issues? Is it possible? At this point, based on my research, I see no other option. If there is another option that doesn't involve replacing the system or "just dealing with it," I'd love to hear it.
The "why"s:
My phone is custimizable, has all of my contacts, recognizes my voice, has GPS, accurate and up-to-date maps, and does everything that I need a phone and navigation system to do. The Honda solution tries to duplicate all of that functionality and does it very poorly. As one user wrote last year, my $50 bluetooth headset can listen to my phone and pipe in navigation directions and let me know when I get a call. It is a joke that an expensive car can't even get that part right. The fact that I can't put my phone screen on the car screen while I'm driving is idiotic. Now I've got to find some way to hold my phone up for navigation. I don't want this post to degenerate into a series of posts and counter-posts on whether drivers can handle the increased cognitive demand. I've been driving long enough to see that the majority of drivers are not paying any attention at all to the road anyway and no one seems to care.
The hardware in the CR-V seems to be capable of doing the things that I have listed above. So, if the Honda programmers can't get it the way I want it, the only solution is to take the programming away from them and do it ourselves. Has anyone done this yet?
Thank you in advance for your help.
Here, check this out.
Me:
When two BT devices capable of telephony functions are connected, the second one connects as "Connected (no phone)", and its telephony function cannot be used.
Example (picture attached). If Huawei Watch is already connected, when Jabra Talk attempts to connect, it will connect as described above, and one cannot make or receive phone calls on Jabra Talk (but still can on the watch.)
Oneplus support:
Thank you for taking the time to send us this email as well as the screenshot that you provided. I understand that you want to use both of the Bluetooth devices for easy access and getting in touch with loved ones for helping us keep on track with our daily activities.
I would like to inform you that the OnePlus 6 can actually connect to two Bluetooth devices. However, by default, you can only choose one for making and receiving calls. Just choose which you preferred to use by toggling the "Phone calls" under each setting of the Bluetooth devices.
This bug was not present in 5.1.5. They introduced it in 5.1.6/7.
This bug is present in all Pixel phones because it's a buggy Google code that Google simply does not care to fix.
Samsung fixed this in their phones.
So, I am guessing OP had this fixed in 5.1.5, but then they just lazily copied and pasted that Google garbage code.
And they don't know how to fix it now. So now it's a freaking feature.
UNBELIEVABLE!
I have the same problem with my Huawei Watch and my cars hands free system
I tried to disconnect the watch with Tasker as soon as my hands free system connects, but it never worked reliable (because the watch connects again immediately and takes over the call functionality)
I guess we need to wait until we get Android Pie because as far as I know this problem is solved with Android Pie
MJFox78 said:
I have the same problem with my Huawei Watch and my cars hands free system
I tried to disconnect the watch with Tasker as soon as my hands free system connects, but it never worked reliable (because the watch connects again immediately and takes over the call functionality)
I guess we need to wait until we get Android Pie because as far as I know this problem is solved with Android Pie
Click to expand...
Click to collapse
I hope so. But I'm not that hopeful - I think it's a Google bug, and they simply don't care to fix it.
Meanwhile, I have to disable the phone functionality on the Watch so I can use my hands free car kit.
It's so disappointing, especially since this stuff always worked with Samsung phones, OOS 5.1.5 (the bug was introduced in 5.1.6/7) and even the early Pixel, pre Android 7.0.2.
nabbed said:
Here, check this out.
Me:
When two BT devices capable of telephony functions are connected, the second one connects as "Connected (no phone)", and its telephony function cannot be used.
Example (picture attached). If Huawei Watch is already connected, when Jabra Talk attempts to connect, it will connect as described above, and one cannot make or receive phone calls on Jabra Talk (but still can on the watch.)
Oneplus support:
Thank you for taking the time to send us this email as well as the screenshot that you provided. I understand that you want to use both of the Bluetooth devices for easy access and getting in touch with loved ones for helping us keep on track with our daily activities.
I would like to inform you that the OnePlus 6 can actually connect to two Bluetooth devices. However, by default, you can only choose one for making and receiving calls. Just choose which you preferred to use by toggling the "Phone calls" under each setting of the Bluetooth devices.
This bug was not present in 5.1.5. They introduced it in 5.1.6/7.
This bug is present in all Pixel phones because it's a buggy Google code that Google simply does not care to fix.
Samsung fixed this in their phones.
So, I am guessing OP had this fixed in 5.1.5, but then they just lazily copied and pasted that Google garbage code.
And they don't know how to fix it now. So now it's a freaking feature.
UNBELIEVABLE!
Click to expand...
Click to collapse
if Google's code is garbage, I suggest you stop using android and start making your own good code!
nabbed said:
I hope so. But I'm not that hopeful - I think it's a Google bug, and they simply don't care to fix it.
Meanwhile, I have to disable the phone functionality on the Watch so I can use my hands free car kit.
It's so disappointing, especially since this stuff always worked with Samsung phones, OOS 5.1.5 (the bug was introduced in 5.1.6/7) and even the early Pixel, pre Android 7.0.2.
Click to expand...
Click to collapse
I disabled the phone functionality too
I had a Samsung phone before as well (Note 8) and with that I had no problems with my hands free kit but instead the smartwatch lost the phone functionality after a few hours so I always had to reconnect it (basically the same problem but the other way round)... it's very frustrating that such a pretty basic thing doesn't work properly
I also tried this app: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
but it didn't seem to make any difference, it didn't seem to make anything at all
I read that Android Pie is able to connect to more than one Bluetooth headset at a time so this should fix the issue after all
kewlest22 said:
if Google's code is garbage, I suggest you stop using android and start making your own good code!
Click to expand...
Click to collapse
I had a Pixel XL for over a year. Only kept it for Project FI. Bug ridden POS.
Sold it for half going price just so I could feel clean again.
Even if Samsung *used* to have sluggish Touchwiz in the past, at least it didn't have deal breaking bugs.
Don't even have to make my own code - some XDA roms had fixed this bug, as opposed to Google.
MJFox78 said:
I disabled the phone functionality too
I had a Samsung phone before as well (Note 8) and with that I had no problems with my hands free kit but instead the smartwatch lost the phone functionality after a few hours so I always had to reconnect it (basically the same problem but the other way round)... it's very frustrating that such a pretty basic thing doesn't work properly
I also tried this app: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
but it didn't seem to make any difference, it didn't seem to make anything at all
I read that Android Pie is able to connect to more than one Bluetooth headset at a time so this should fix the issue after all
Click to expand...
Click to collapse
I am almost positive that if you had a somewhat similar problem on a Note 8, it's probably Google's fault.
I don't really use the 2 BT phone functionality for more than 30 min on average, but I've never had any problems on Note 7, GS6 or GS9, or even on a Pixel pre 7.0.2 android, when this bug was first introduced.
After 7.0.2, bluetooth stuff just broke everywhere. This bug, constant disconnects and reconnects, for some people music skips, for some doesn't even work, BT UI in Settings just crashing etc.
It's like Google replaced their BT programmer with a monkey at that point, or even a monkey's nephew.
So just because you cannot use 2 Bluetooth devices simultaneously to make phone calls, it's a deal breaker??? Lmao please please please go back to Samsung so we don't have to hear the whining anymore. Good luck with those bootloaders
The very first Android phone I purchased was in 2010, and it was an HTC Desire. I have been a huge fan of Android ever since, owning literally hundreds of phones and tablets from various manufacturers such as Samsung, Huawei, Motorola, Xiaomi, LG, Sony....the list goes on and on. I've tried iOS a few times, but I simply just didn't like iOS. In recent years my loyalty to Android was severely tested because of an issue that many may think is inconsequential and even petty, but to me it was ultimately a deal-breaker - delayed push notifications (predominantly when the screen is locked and off)
So picture this - I'm sat at home with three other members of my family who also own Android phones, and we have a group chat (FB Messenger) going with other members of the family. Every time someone posts a comment *PING*...but wait, four android phones, and only two went *PING*...then a few seconds later another goes *PING*, then a few seconds later the fourth goes *PING*.
I'm not exactly sure when this issue first arose, but I only really started to notice around the time Oreo was mainstream, and I've been obsessed with trying to figure out a cure ever since. Of course I've tried literally everything that's been suggested, hard resets, turning off battery optimisations, locking the affected app in the recents, disabling Doze with ADB, clearing the cache, custom roms, different routers, different networks, heartbeat fixing apps for GCM/FCM, bla bla bla...none of it works. Now I have finally accepted there is a flaw in the way the Android OS handles push notifications, a flaw that affects every single Android device, at least since Oreo, and maybe even before. It's a strange one because the issue doesn't seem to occur when the screen is awake, only when it is locked and off. At one stage I was hopeful features like AOD on AMOLED devices might be a solution, but alas, even with AOD active, the problem persists.
Now before you say "I've never had a problem with push notifications on my Android device", are you sure. Have you ever really been in a situation where you would notice? Try it for yourself, perform a test using a similar scenario to the one I mentioned in the second paragraph. Create a group chat in any messaging app you like, and have several of the group members with Android devices sit in the same room with their screens locked and off, then have one person send a message in the group chat, then watch as some get the messages immediately, some with a slight delay, and some not at all until they wake the screen. Do it a few times and you will soon notice there is no pattern at all, sometimes you will get the notifications immediately while others are delayed, then sometimes others will get the notifications immediately and yours will be delayed.
My most recent (and very last) Android purchase was the Samsung Galaxy S21 Ultra 5G (outright, not on contract, so you know roughly how much I paid). When I'm paying that amount of money for a mobile phone, I expect timely push notifications as a given, but no, the same issue occurs even with one of the very latest and greatest. I contacted Samsung Tech Support and the guy admitted it's the most common complaint he deals with every single day. I was previously given a similar story by Motorola and Huawei support too, and a little digging around online shows that thousands of Android users are complaining about the very same issue. Needless to say they now have that phone back.
I know I know, something this trivial shouldn't really bother me this much, but it does, it's just who I am. I can accept there is no such thing as a perfect mobile phone, I can live with an average camera, a budget processor, a dull screen, lifeless aesthetics etc. but there are some compromises I just won't make. Apart from the obvious (the ability to make and receive calls and texts), my requirements are quite simple - I require a phone with stable WiFi, Bluetooth and NFC, a decent battery life and of course timely push notifications. With no Android device currently able to fulfil my very simple requirements, it really did only leave me with one option - joining the dark side....so I bought an iPhone.
I have owned an iPhone for just over a month (that's two weeks longer than my last three Android devices), and thus far my delayed push notification woes have vanished. Now when someone in the family posts in our group, *PING* immediately every single time. The battery life is acceptable for someone like me who isn't the most demanding user, WiFi, Bluetooth and NFC have presented no issues, and it makes and receives calls and texts without a problem. I can honestly say the only thing I miss so far is my Android App Drawer. I know iOS introduced their App Library in iOS 14, and it's a start, but it's just not the same. There is probably an app in Cydia that would give me an app drawer, but I'm not quite ready to get into the world of jailbreaking just yet (I'm not that brave).
So after my big rant, here's a summary - Android push notifications are broken, they've been broken for some time and Google don't seem interested in fixing the problem. If someone told me tomorrow that Google had finally fixed push notifications, I would drop iOS like a hot potato and rekindle my love for Android. Please Google, help bring me back from the dark side, it's really cold out here!
Des
energy6uk said:
The very first Android phone I purchased was in 2010, and it was an HTC Desire. I have been a huge fan of Android ever since, owning literally hundreds of phones and tablets from various manufacturers such as Samsung, Huawei, Motorola, Xiaomi, LG, Sony....the list goes on and on. I've tried iOS a few times, but I simply just didn't like iOS. In recent years my loyalty to Android was severely tested because of an issue that many may think is inconsequential and even petty, but to me it was ultimately a deal-breaker - delayed push notifications (predominantly when the screen is locked and off)
So picture this - I'm sat at home with three other members of my family who also own Android phones, and we have a group chat (FB Messenger) going with other members of the family. Every time someone posts a comment *PING*...but wait, four android phones, and only two went *PING*...then a few seconds later another goes *PING*, then a few seconds later the fourth goes *PING*.
I'm not exactly sure when this issue first arose, but I only really started to notice around the time Oreo was mainstream, and I've been obsessed with trying to figure out a cure ever since. Of course I've tried literally everything that's been suggested, hard resets, turning off battery optimisations, locking the affected app in the recents, disabling Doze with ADB, clearing the cache, custom roms, different routers, different networks, heartbeat fixing apps for GCM/FCM, bla bla bla...none of it works. Now I have finally accepted there is a flaw in the way the Android OS handles push notifications, a flaw that affects every single Android device, at least since Oreo, and maybe even before. It's a strange one because the issue doesn't seem to occur when the screen is awake, only when it is locked and off. At one stage I was hopeful features like AOD on AMOLED devices might be a solution, but alas, even with AOD active, the problem persists.
Now before you say "I've never had a problem with push notifications on my Android device", are you sure. Have you ever really been in a situation where you would notice? Try it for yourself, perform a test using a similar scenario to the one I mentioned in the second paragraph. Create a group chat in any messaging app you like, and have several of the group members with Android devices sit in the same room with their screens locked and off, then have one person send a message in the group chat, then watch as some get the messages immediately, some with a slight delay, and some not at all until they wake the screen. Do it a few times and you will soon notice there is no pattern at all, sometimes you will get the notifications immediately while others are delayed, then sometimes others will get the notifications immediately and yours will be delayed.
My most recent (and very last) Android purchase was the Samsung Galaxy S21 Ultra 5G (outright, not on contract, so you know roughly how much I paid). When I'm paying that amount of money for a mobile phone, I expect timely push notifications as a given, but no, the same issue occurs even with one of the very latest and greatest. I contacted Samsung Tech Support and the guy admitted it's the most common complaint he deals with every single day. I was previously given a similar story by Motorola and Huawei support too, and a little digging around online shows that thousands of Android users are complaining about the very same issue. Needless to say they now have that phone back.
I know I know, something this trivial shouldn't really bother me this much, but it does, it's just who I am. I can accept there is no such thing as a perfect mobile phone, I can live with an average camera, a budget processor, a dull screen, lifeless aesthetics etc. but there are some compromises I just won't make. Apart from the obvious (the ability to make and receive calls and texts), my requirements are quite simple - I require a phone with stable WiFi, Bluetooth and NFC, a decent battery life and of course timely push notifications. With no Android device currently able to fulfil my very simple requirements, it really did only leave me with one option - joining the dark side....so I bought an iPhone.
I have owned an iPhone for just over a month (that's two weeks longer than my last three Android devices), and thus far my delayed push notification woes have vanished. Now when someone in the family posts in our group, *PING* immediately every single time. The battery life is acceptable for someone like me who isn't the most demanding user, WiFi, Bluetooth and NFC have presented no issues, and it makes and receives calls and texts without a problem. I can honestly say the only thing I miss so far is my Android App Drawer. I know iOS introduced their App Library in iOS 14, and it's a start, but it's just not the same. There is probably an app in Cydia that would give me an app drawer, but I'm not quite ready to get into the world of jailbreaking just yet (I'm not that brave).
So after my big rant, here's a summary - Android push notifications are broken, they've been broken for some time and Google don't seem interested in fixing the problem. If someone told me tomorrow that Google had finally fixed push notifications, I would drop iOS like a hot potato and rekindle my love for Android. Please Google, help bring me back from the dark side, it's really cold out here!
Des
Click to expand...
Click to collapse
Now that's what I call a structured rant!
But what type of phone did you owned ?
I know this problem from samsung phones, and other phones I've tested. usually it's because of the OEM's aggressive take on battery management. They freeze apps in the background, and run them periodically to check notifications.
I know that's frustrating, but with your story I could feel the social isolation you've felt. And even with all the perks in the world, I wouldn't want a phone that makes me the third wheel.
But I'm much more radical than you, I don't want to change my phone, so I changed my friends. Way better now you should try it, those Apple "cool kids" pigeons weren't good friends anyway.
Obviously I'm just kidding, but I think the issue can be solved by using a ROM to espace your OEM's restrictions, or try another brand. If you ever want to come back to the light (which I'm sure you will because I couldn't bare iPhones after using an android all this time, seriously wtf if that file manager of them, and wtf is the "Other" memory partitions that increases without me having any control over it!), ask in various xda sections if users experience notifications latency, and if they don't know suggest them your little experiment you described in this post.
Hope you'll come back from your journey in the shadow,
Have a great day
Interesting rant.
Were all the phones that your friends had on the same networks? It could easily be a network latency issue
affecting how fast each message was distributed. Given that the passage of a message, say a Whatsapp message is at least: :
from phone screen
to
Whatapp encryption software
to
wi-fi-switch
to
domestic router
to
domestic ISP
to
internet backbone
to
commercial ISP
to
Whatsapp run cloud server
to
Whatsapp redirection processes
to
commercial ISP
to
internet backbone
to
domestic ISP
to
domestic router
to
wifi-switch software
to
friend phone
to
Whatsapp decryption software
to
phone notification sub-routine
to
phone screen
I'd say a small discrepancy in arrival times would be expected.....
I only mention this because it seems that you've tested massive of phones - but did you take into account different networks?
I recently upgraded from my trusty Note 8 and am finding the new Android version to be completely underwhelming (a common theme, I'm finding). I can't really think of any actual improvements to my daily user experience and two things have gotten worse enough that I have been researching solutions to them to no avail. The first is the main topic of this thread. My older Bluetooth car stereo (not Android auto, but apparently that is equally as broken) sends an "autoplay on connect" request. No individual app autoplay setting seems to matter, it is a system problem. On the Note 8 this was also the case, however it would only actually play if the app was open (present in the task switch windows). This was occasionally annoying but now it is much much worse. What happens now on the S22U is that apps I have long since closed will just appear to open zombielike and autoplay. Even when I am in the middle of opening a music app, e.g. a podcast that I was listening to yesterday will just start playing because it was the last used app.
I can't believe that it's 2022 and Android doesn't just have this fixed yet it has been underdeveloped for YEARS now. Why can't it just be a system wide setting? And why on earth does it insist on playing audio even if it was PAUSED before Bluetooth is disconnected? I have a feeling there is nothing I can do about this, but I wanted to vent.
I mentioned there was a second most annoying issue with the new version of Android. This is that the "double tap to switch" to previous app window is inexplicably slower than it used to be, to the point you might as well not use it. I used to do that constantly and it was very effective. Why on earth they removed this feature is beyond me.
If anyone has a current solution to either of these problems please lmk.
I've also have this issue... Both with the Pixel 6 Pro and same thing when I switched to the S22 Ultra. I'm inclined to think it's an issue specific with Android 12. On my Pixel 5 (using Android 11), autoplay when connecting to bluetooth worked every time. Even with having setup a Bixby routine to autoplay upon connecting to a specific bluetooth device, it does not always work... It's frustrating.