Hello,
I've started experiencing a weird problem with my Desire. Generally everything looks fine, but when I try calling somebody
instead of hearing "waiting tone" it goes back to dialer app.
And AFAIK I'm not available as well - I didn't check it thoroughly.
The thing is rebooting the phone (by rebooting device, switching airplaine mode on and off) fix the problem - for the moment - so I'm able to make a call - but my problem is that all the time I'm afraid that in a moment I won't be accessible by other people.
Other solution I've been using, is switching it to GSM only - and I think it solves the problem permanently - but since I'm using a lot of Internet I want to use 3G.
I'm not sure If it really is a 3g (maybe switching 3g/gsm) or other thing - I don't want to reset it default to just check if it will solve my problem.
I'm using original Froyo (from Polish Era) - I didn't do anything to my ROM, and I was thinking of trying maybe some custom (clear) rom - but since this was working fine - I didn't want to mess anything up.
If you have any suggestions how to fix it - please help. I've searched google and xda, but I didn't find a similar problem.
Generally I'm more than happy with my Desire, and I find it to be almost perfect, but this thing is affecting basic functionality, and I really need to do something with it.
P.S. I'm wondering if had something to do with Market, because it started the same day I was upgrading several apps at the same time - and probably because of the connections problem I restarted my device to finish everything. But I'm not really convinced that it was the cause of my bug.
Strange problem - haven't heard of that before.
I would suggest ensuring you have the latest Radio installed and/or also installing a clean rom but try the radio first.
Ever since I use the Llama app (Location Aware Mobile Application)on my i9195 (Carbon ROM 4.4.2) I have the problem that Llama doesn't receive cell tower information when the screen is turned off. This is a major feature of the app, which doesn't work. I activated the active cell polling, wake up during sleep etc, but the only thing working is to activate the screen during every poll, which is not favorable of course.
The thing is, that with my previous Huawei Y300, with stock ROM 4.1.2 it worked flawlessly without having to enable all the extra (battery consuming) settings. Unfortunately I don't know if the stock Samsung ROM didn't have this bad behavior since I booted the original ROM only once to enable root, in order to instal CWM recovery
Would this be a ROM issue or device issue? Too bad this is my first post here and therefore I can't post in the dev. section of Carbon ROM on this website :crying:
Has nobody issues with Llama on this device/ROM? The location awareness is really adding something to the use of the phone. Really too bad that I have to turn the screen on, before Llama realizes that I am at another location.
I love Llama, it's a great app which allows me to set it and forget it. I love not having to remember to turn radios on/off, muting phone at college or work.
I had to uninstall it because I switched carriers, and with the new one I keep getting "1-1-1-1 No signal" on the Recent towers tab. It's intermittent (once every detected tower) and it had my profiles going nuts.
I also was experiencing issues where my phone would freeze until it forced a reboot almost every time I got back home.
Sounds like your current ROM might be to blame. I suggest you try Llama with the stock rom. I for one prefer stock with Action Launcher. You might lose the added features of the custom ROM, but at least Samsung's camera interface is way better than AOSP, at least to my taste and needs.
JoeCastellon said:
I love Llama, it's a great app which allows me to set it and forget it. I love not having to remember to turn radios on/off, muting phone at college or work.
I had to uninstall it because I switched carriers, and with the new one I keep getting "1-1-1-1 No signal" on the Recent towers tab. It's intermittent (once every detected tower) and it had my profiles going nuts.
I also was experiencing issues where my phone would freeze until it forced a reboot almost every time I got back home.
Sounds like your current ROM might be to blame. I suggest you try Llama with the stock rom. I for one prefer stock with Action Launcher. You might lose the added features of the custom ROM, but at least Samsung's camera interface is way better than AOSP, at least to my taste and needs.
Click to expand...
Click to collapse
Thanks, luckily I don't have any of your issues so far, only the cell tower updates being delayed until the screen turns on. A few posts away from now I can ask the question in the specific ROM forum and see if they can fix it.I love the ROM and don't like the Samsung layer of the original stock ROM.
In the meantime the cell tower option has been added to the Carbon rom!
TF-101 & S4-mini i9195
Just curious to see what people use this tablet for these days. I'm trying to find a good use for mine and am coming to the conclusion that if you want what has features its going to come with issues. But Lineage is quite fast just no features.
Curious on others opinions!
Having installed a12 I was disappointed with its work (compared to stock a6). The rom works fine (except for quick settings, the curtain always lags) until additional programs are installed
Then disappointed in the A12, I decided to switch to the A11, namely the OFFICIAL latest CRDROID. It also started to work worse when a bunch of programs I needed appeared, but not so, it could be in use. However, when I tried to listen to music all night because of him, he was unloading Spotify (he seems to have serious problems with working with RAM. Of course, another reason is 2 GB of RAM)
I also had a strange bug that the tablet completely hung, and after restarting the ROM broke. The blind did not want to open completely, there were problems with the software.
As a result, I returned to a12, put fewer programs, tried to configure the kernel, the system to be more or less comfortable to use it. Of course, this is not the level of a6 or a9, but if you want Something new, cool design, why not.
In my opinion, it is better to use the 9-11 android, as well as install the kernel with overclocking, it is very necessary here.
I'm still new to using this device, so I haven't used much ROM, but it's probably in the future
From here ... > ... The best
No need to look at a high Android!
erdar said:
Having installed a12 I was disappointed with its work (compared to stock a6). The rom works fine (except for quick settings, the curtain always lags) until additional programs are installed
Then disappointed in the A12, I decided to switch to the A11, namely the OFFICIAL latest CRDROID. It also started to work worse when a bunch of programs I needed appeared, but not so, it could be in use. However, when I tried to listen to music all night because of him, he was unloading Spotify (he seems to have serious problems with working with RAM. Of course, another reason is 2 GB of RAM)
I also had a strange bug that the tablet completely hung, and after restarting the ROM broke. The blind did not want to open completely, there were problems with the software.
As a result, I returned to a12, put fewer programs, tried to configure the kernel, the system to be more or less comfortable to use it. Of course, this is not the level of a6 or a9, but if you want Something new, cool design, why not.
In my opinion, it is better to use the 9-11 android, as well as install the kernel with overclocking, it is very necessary here.
I'm still new to using this device, so I haven't used much ROM, but it's probably in the future
Click to expand...
Click to collapse
CrDroid isn't broken but it does have an odd systemUi bug likely to the system partition and other things being so outdated. Whenever restarting the tablet it will continue to respring until it decides to boot the best way to handle this is just to leave it be I've found that more often then not it will eventually start up, other times it refuses to start at all and I will have to reboot again most times I try to refrain from turning it off. Unfortunately this seems like the only way to get good features for this tablet. Wishing someone would take interest like forkLineage or EvoX perhaps
Mr.Conkel said:
"CrDroid isn't broken but it does have an odd systemUi bug ....."
Click to expand...
Click to collapse
I agree, although I prefer pixel experience (and the like).
As for the CRDROID ... My problem was that the curtain does not open, and many programs were not launched, and there was an arrow in the bar, which is displayed only when the navigation bar is two Buttons, and I had gestures enabled) Very strange, actually. It's funny that it all started after the ROM crashed .. I still wanted to try at least lineage 18.1, but after reinstalling a12 I'm too lazy
Running unofficial LineageOS 17.1. I don't really use the tablet or anything really. My touch screen doesn't really work, along with the tilt sensor. It's really slow which is to be expected. I use my Fire 7 since it's faster and less frustrating to use.
I pulled my old nexus out from the cupboard a few weeks ago and was amazed that the battery still had decent life after yrs not being used. I managed to unlock bootloader and install twrp before the micro USB charging port stopped working. I now have DotOS android 9 installed and am using the nexus as my eReader, charging via Qi wireless
Ok all, I'm getting quite frustrated with my P6P. Was on A12 and sideloaded the OTA for 13 Beta 4.1. I didn't want to lose any data but also didn't want to enroll in the beta program which would have pushed the OTA anyway.
Beta was working but definitely noticed a hit to battery life at first and some weird things like running warmer, phone being warm just sitting on the pixel stand fully charged, just generally not feeling right. The good news was, it seemed to have gotten a little better over the next few days of use but still not great so when I saw stable A13 released last week, instead of going back to 12, I committed to using the Android flash tool and fully flashing A13.
After flash, I chose to restore my Google One / Drive backup and omg the battery life was completely abysmal and running hot. We are talking losing 20% per hour of light usage, standby was losing 10%+ per hour and wasn't going into deep sleep at all. I thought at first it was my Galaxy Watch4 and the Samsung health app causing the majority of the issues but when I disabled "activity tracking" on the app, it didn't fully resolve the issues.
Other issues include: taking phone out of my pocket, screen sometimes doesn't wake up (I remember this was an issue with A12 but G eventually acknowledged and fixed but I guess it's back), connected via Bluetooth to my car (no Android auto) the ring tone is no longer playing when I get a call, generally feeling not as smooth, weird system usages showing up in accubattery and the Android battery manager as using good chunks of battery, etc.
At this point I got another idea: reflash A13 but don't restore from backup (which I hate doing because then I have to go through every single setting to find stuff I changed and set it again both in the system and on apps). It seems like that helped a little with stand by battery drain but still seems to be draining at a higher level while in use. The issue of screen not waking up sometimes is still present and now, I just saw this morning that I tap on the Google Play System Updates within the security menu and it does nothing. I was able to get into it yesterday morning and it found an update (still says July 1 though) but I didn't reboot to complete it until this morning. Now I can't get into it anymore at all. I also found some weird folders in my DCIM folder and another one that referenced icloud and iphone transfers but I've never been an iphone user.
I'm so frustrated with this phone lately and it seems like no matter what I do, I cannot get it to work right with multiple little things as well as battery drain.
Am I the only one? And if not, anyone have any ideas on how to fix my issues? Is it time to contact Google for an RMA? I was one of the launch day orders so I don't know if my specific hardware is the issue. I am now locked in to 13 bc of the bootloader thing, I didn't manually flash the BL to both slots, only used official flash tool which you'd think of this was a critical thing, Google would do that with the flash tool but I guess they can't get their left hand to recognize what the right hand is doing.
Just typing this post on Chrome browser for 10 mins, burned through 4% battery.
You're not the only one...
https://www.reddit.com/r/GooglePixel/comments/wddk1s
nomisunrider said:
You're not the only one...
Click to expand...
Click to collapse
Thanks for that reddit article but that's not exactly answering my questions. Yes I know I'm not the only one who's had battery issues and I've gone through all those steps up to and including reflashing cleanly and wiping.
What about the other stuff I'm having issues with? Anybody else experience any of those issues? Is there anyone on 13 stable NOT having some issues with battery or other oddities?
Essentially I'm debating on wiping again and/or reloading the OS again but if others are having the same or similar issues then it may just be Google being Google and releasing a buggy build (yet again).
Side note, I also just got a notification that Google One backup is currently running and to tap for more info but yet, I don't have it plugged it nor is the phone idle. It is on wifi though but I tapped the notification and nothing was happening. It said the last backup was at 3:37am. Also, I am now down another 10% of battery since posting this with barely any usage.
Hi, I've been on Android 13 Stable for the past 7+ days, and haven't had any problems.
The only suggestion I have is a start completely fresh type, but there's no guarantee it'll fix anything. Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own).
^ It's fixed things for many users, including myself, that nothing else including the factory image would fix, but for me, that was six months ago so obviously on Android 12, and it was a different issue than any that you're describing.
jrg67 said:
Is there anyone on 13 stable NOT having some issues with battery or other oddities?
Click to expand...
Click to collapse
I've had no issues with 13 but didn't have any on 12 either. Day one phone too.
roirraW edor ehT said:
Hi, I've been on Android 13 Stable for the past 7+ days, and haven't had any problems.
The only suggestion I have is a start completely fresh type, but there's no guarantee it'll fix anything. Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own).
^ It's fixed things for many users, including myself, that nothing else including the factory image would fix, but for me, that was six months ago so obviously on Android 12, and it was a different issue than any that you're describing.
Click to expand...
Click to collapse
I did what I thought was starting fresh the last time around (Sunday). Used the official flash tool and didn't restore anything from backup. All I did was add my Gmail accounts and then manually downloaded every app I use and then tried to set all the settings again in both system and apps to how I like them. Is there something I'm missing? Is there a difference between the pixel repair tool and the Android flash tool? What about the settings that are flash tool? I have them set to wipe, lock, and force flash everything. Not sure if that exists on pixel repair tool. I've also noticed a fairly large reduction in size of the backup that occured last night with the apps section showing only 44 apps at about 11.7MB in size when my previous backup was 60 apps at about 48.2MB. I'm thinking of just wiping/reflashing again for the 3rd time but restoring from backup this time since it really didn't make much difference.
How about the Google play system up bug thing? Can someone tap on it and see if it comes up checking for an update or if it does nothing like me. And when I say nothing, just the menu option to tap on just lights up but doesn't open anything. How about the issue with the screen not waking up if taken out of your pocket?
For what it's worth, I haven't started from scratch since I accidentally did last December (after originally setting my phone up in late October or in November). I used the Android 13 factory image over top of my existing install without wiping.
I'm under the impression that yes, there is a difference between the Pixel Repair Tool and the Android Flash Tool, but I've never actually used the Pixel Repair Tool. I know the first several months, at least, the Pixel Repair Tool hadn't yet been updated to work with the Pixel 6 Pro. It may have been updated since then, I just don't know for sure.
When I have wiped/factory reset in the past six years (starting with my Pixel 1), I always restore all or almost all data from Google's backup. I do have Swift Backup do automatic nightly backups as well, but I only restore data (through Swift Backup) for the apps that I really need to - definitely not very many.
Your settings for the Android Flash Tool sound fine.
Is the "Google Play System Up(date) bug where clicking on it doesn't do anything? If so, it doesn't do anything for me, either. Mine doesn't even light up, but I have dark mode on, plus using Pitch Black theme from AOSP mods.
I rarely have my phone in my pocket, so it probably just doesn't come up often enough for me to have noticed, so I can't confirm one way or the other.
Well, I found an answer to the Play System Updates "bug". We are not the only ones, road warrior! https://www.google.com/amp/s/9to5google.com/2022/08/20/check-google-play-system-updates-pixel/amp/
jrg67 said:
Well, I found an answer to the Play System Updates "bug". We are not the only ones, road warrior! https://www.google.com/amp/s/9to5google.com/2022/08/20/check-google-play-system-updates-pixel/amp/
Click to expand...
Click to collapse
Cool, thanks for sharing the news! I hadn't bothered checking manually in very many months, possibly since late last year or very early this year.
Now, on to the other stuff like no more ring sound over Bluetooth in my car, the screen not waking sometimes, terrible battery life, etc etc. Boy do I love this time of year when new the OS launches, screws up many phones and makes people trade them in for the next version. P7P here I come!
roirraW edor ehT said:
Cool, thanks for sharing the news! I hadn't bothered checking manually in very many months, possibly since late last year or very early this year.
Click to expand...
Click to collapse
jrg67 said:
Well, I found an answer to the Play System Updates "bug". We are not the only ones, road warrior! https://www.google.com/amp/s/9to5google.com/2022/08/20/check-google-play-system-updates-pixel/amp/
Click to expand...
Click to collapse
Google Play Store v31.9.20-21 is rolling out and will fix that Play System Updates "bug".
jrg67 said:
Now, on to the other stuff like no more ring sound over Bluetooth in my car, the screen not waking sometimes, terrible battery life, etc etc. Boy do I love this time of year when new the OS launches, screws up many phones and makes people trade them in for the next version. P7P here I come!
Click to expand...
Click to collapse
Here's another weird one.. apparently now I can't keep my phone on vibrate while in the car. For a test, I turned my ringer on and then tested it again.. low and behold, it rang through the speakers in my car. This is trash. I know Android enabled in-band Bluetooth audio years ago and I recall this same thing happening way back with my nexus 6p and each pixel I've had but this one. There was a setting in developer settings to turn that off which fixed it and allowed it to work correctly but with this phone, it worked out of the box so I never thought twice about it. I just checked the dev settings and it's nowhere to be found. I have no idea what A13 could have done to screw that up nor do I know if the dev setting even existed on this phone prior to A13. I just don't get it. I guess I could see if there's any updates to my car's multimedia system but I have an Audi and any software updates come from the dealer for a price. How dumb. I guess I'll be scouring the Audi forums for a fix on that.
Meh, the Google Play Store updates are irrelevant to me. So no worries there on my part, haha. But this phone's battery life has been rather questionable. I have, however, noticed that after being on the full A13 build for around a week or so and disabling 5G from the get-go that my battery now lasts MUCH longer. My phone does not seem to generate as much heat either - which is always a plus. But I also seem to have more phone/messaging reliability than I have had in the past with this device.
I am beginning to think that the modem and 5G has had the most to do with this phone's imperfections.
Also - for OP - but I have noticed that my phone often doesn't wake up with a single tap either - but only when the gyroscope stays mostly stationary for a longer period of time. When I pull the phone out of my pocket, it usually comes on with one tap. But if it has been sitting on a table or other mostly flat surface for a while, it takes two taps to wake the display.
Ultimately, I won't be getting the Pixel 7 Pro. I will, however, be getting the Pixel Fold which should launch at around the same time =).
I can't say too much about the google provided and infiltrated system images, since I only booted it on that image ONCE -- just long enough to flip the "allow OEM unlock" switch so I could flip it to AOSP and then GrapheneOS. But I will say that on GrapheneOS, the update from 12->13 has been pretty seamless. One fairly minor glitch with activating wifi hotspot that was fixed with yesterday's SECOND update, but aside from that, not a single one of the bugs mentioned in this thread.
96carboard said:
I can't say too much about the google provided and infiltrated system images, since I only booted it on that image ONCE -- just long enough to flip the "allow OEM unlock" switch so I could flip it to AOSP and then GrapheneOS. But I will say that on GrapheneOS, the update from 12->13 has been pretty seamless. One fairly minor glitch with activating wifi hotspot that was fixed with yesterday's SECOND update, but aside from that, not a single one of the bugs mentioned in this thread.
Click to expand...
Click to collapse
This kills me. Why is it that a third party dev can release a stable build with little to no bugs but if bugs are found, a patch is pushed out right away to fix yet Google cannot seem to get it right. Furthermore, if they do fix bugs, they refuse to push them out-of-band. This isn't 2008 anymore, we shouldn't need custom ROMs to get the best performance out of our phones.
jrg67 said:
This kills me. Why is it that a third party dev can release a stable build with little to no bugs but if bugs are found, a patch is pushed out right away to fix yet Google cannot seem to get it right. Furthermore, if they do fix bugs, they refuse to push them out-of-band. This isn't 2008 anymore, we shouldn't need custom ROMs to get the best performance out of our phones.
Click to expand...
Click to collapse
Well, aside from the bugs issue, as time goes on, more and more you need something besides what it ships with in order to actually have security and privacy. Google has fallen a very long way from the openness and respect that they once promised. The final straw for me was when they started working with governments to include and share covid contact tracing functionality.
Update:
Apparently the 4th complete wipe and OS flash was apparently the trick to fix the majority of my phone's issues. I did restore from my backup this time because the last time that I started from scratch, it made no difference. I figured if it's still going to be buggy, I may as well have all my info and settings correct. It's now been about 24 hours. See below for status of my issues.
1. Massive battery drain - fixed for the most part. Still have to restrict Samsung Health app but for the most part, it seems to be back to normal.
2. Screen not waking up when pulled from pocket or elsewhere that the proximity sensor activated and screen was off. - Fixed so far
3. Play system update button broken - already found this wasn't an A13 bug. I still haven't gotten the fixed update of playstore but before this latest wipe and OS flash, I sideloaded the latest version and it fixed it.
4. Connected to Bluetooth in car no longer plays ringers out loud. - Weird one as I think this is part A13 because Google baked in a new BT stack that's been in development since A11 called gabeldorsche https://www.androidpolice.com/android-gabeldorsche-bluetooth-stack/ and partly my infotainment system in my car. I am not on the current version of the car's infotainment but since my car is a '14 Audi, it doesn't have OTA updates.
5. Heating up during normal use - seems to be fixed
6. Warm while on the pixel stand and fully charged - haven't been able to observe this one bc last night, I put the phone on the stand and by morning it was at 72% and not charging. No clue if that's a new bug or if it was just not sitting on there just right. Didn't really look into it but we'll see what happens tonight.
So that seems to be the majority. Overall the phone doesn't feel "weird" anymore and most things I was having trouble with appear to be resolved. Sort of ridiculous that I had to wipe and reload the OS 4 times though.
jrg67 said:
2. Screen not waking up when pulled from pocket or elsewhere that the proximity sensor activated and screen was off. - Fixed so far
Click to expand...
Click to collapse
I actually had a similar issue with A12 -- when on a phone call, pull the phone away and it took forever to turn the screen back on. Seems to have been corrected with A13.
96carboard said:
I actually had a similar issue with A12 -- when on a phone call, pull the phone away and it took forever to turn the screen back on. Seems to have been corrected with A13.
Click to expand...
Click to collapse
This one still may be around for me but perhaps not as severe as it was during the first 2 times I loaded 13. I just experienced it about an hour ago. Took phone out of my pocket to place on my desk at work and screen was black but the AOD did eventually come on by itself after about 10 long seconds. We'll see what happens.