sorry to start a thread about this but Im not finding a solution. When I first got my phone it worked fine. But eventually I had gotten just about every other problem there is with this damn phone so I did a hard reset. Now my gmail is setup right and everything, it says it connects and downloads folders/headers but I get nothing! someone please help
Ok I got it to work finally. I had to use active synch from the settings menu. yet the active synch app did nothing?! stupid phone. cant wait for a stable android rom.
now it doesnt receive mails automatically, I have to do it manually
ok lol, I got tired of waiting for another solution that wont work so I did another restore why not, and it works right now. thanks guys lol
Does anyone else experience this with the new leaked 2.3.4 HKTW build? Or is it just my Atrix?
Yeah I exp. It as well but I notice my screen becomes in responsive and so do the touch keys. Only the power button and volume rocker work.
I've only experienced this while on a phone call though to be honest. Like when I'm on hold and I'm.checking Facebook or I'm looking something up on the web while on a call. But I definitely think it's a bug in hktw build 2.3.4 cause I beverage had a problem before with it.
I tried looking through the forums and haven't seen any other complaints untilled this one so maybe its just a few of us. Can any one else confirm this or is there a fix some where?
Sent from my unlocked//rooted ATRIX
mine works fine...
Happens to mine all the time. Fixes itself after turning the screen off.
d3athsd00r said:
Happens to mine all the time. Fixes itself after turning the screen off.
Click to expand...
Click to collapse
when mine freezes even locking phone with the power button and waiting a few seconds to turn it back on doesn't help it still stays un-responsive at the lock screen. I'm actually noticing it happening more and more frequent. or I'm just multi tasking more and more frequent lol idk cant wait for a USA build as apposed to this HKTW build but hey i got to say its definitely pulling me through this month of waiting for it ;P
Mine happened a few times a few days ago...then once the day after, and not since. Been like 4 days now.
i've a cyanogen 7 in my wildfire, and start happens and i dont know why, i've this rom from 3 months and never heard such a thing, hope some one can help fix this.
I've have done a hard reset and nothing
Mine did that already in 2.2 , back then the fix was to lock and unlock the screen. That would always fix the issue, at least until next time. Now in 2.3.4, it still happens, but if I wait 15-20 seconds it usually fixes itself. Looks like Motorola applied some fixes but didn't fix the issue completely.
Bell ATRIX Gobstopper 2.3.4
well guys, i solve the problem for now....
solution:
1º make sure that you have a backup prior to the problem (original stock or other thing), if not you might have to install the room from set one.
2º retrieve you sd card, make a backup of some things that you dont want to lose (like pictures, ring tones, mp3 etc) and leave a folder with a backup that you have, next format sd card in fat32 and put the things that you save (note, dont do all the backup of sd card, like the folders with .com... and android folders etc)
3º go to clockworkmod recovery, by restarting to recovery, wipe all data, like the firs time you install the custom rom, now go to backup and restore and do restore to your backup.
4º Restart and voila, that works for me...i figure that was some app that might cause the problem,(thinking on ndrive 11) im going to test now, but it works.
cheers and post something that might help some one
Gingerbread Problem
I am the same problem everything was fine with Froyo once I updated to Gingerbread I had these issues. Also the droid and nexus folks are reporting those just google up gingerbread phone freeze. I have not found a fix yet. Thanks
Last night I reinstalled the stock rom onto the phone then updated through LG Mobile support tool but ever since iv done that every almost every app including settings, home and system ui crashes and I can only pull the battery out! Safe mode helps a little bit but cant reset the phone no matter how many times I press it and hard resetting dosnt work as it just boots up without resetting.
If anyone can help me fix this it would be amazing! I dont care if I have to format ect.. just want it working again
Update: Its locked to Tesco network and I tried D213n10c_00_0622.kdz which didnt work
bump
bump?
Anyone?
bump one last time before i throw the phone away
Hi,
I have looked on internet regarding the issues on motorola razr ( 2019 ) with peek display but i couldn't find anything helpfull. The thing is that the peek display when the phone is closed is working sometimes and I can see that the screen is on when I closed the phone and try to turn on external display. I have tried to clear the cache of the display app but it didn't helped much to be honest. The phone is brand new from official website so there is not option to have a faulty phone as like I said the screen (display app ) sometimes works sometimes doesn't. I have even tried to uninstall the app update and reinstall it but still doesn't work as it should. I do not want to factory reset the phone becasue my e-sim will be removed from phone and I will have to call my carrier to send me the code again.
Whoever has a phone could you please let me know if you experienced the issue as me ? If yes and you have fixed that please tell me how as this is let's say annoying for foldable phone when extra display just not working and I fell like to stick with my old phone
I have latest Android 10 update on the phone as well.
Thanks
Snip3r
My peek display is working fine. There don't seem to be many ppl with this phone so not a very active forum.
pjcons said:
My peek display is working fine. There don't seem to be many ppl with this phone so not a very active forum.
Click to expand...
Click to collapse
You lucky cuz for me it's working sometimes and it's annoying to check notification or whatever I have to open the phone and unlock it.. Like i said i tried reinstall app install update ect but it didn't helped much. I could restart it but I will loose by esim from phone and it will take time again to get the new one.
BE2026
The stock oxygen OS has a text message bug that apparently isnt fixed yet, so i thought id try a different rom.
I unlocked the bootloader, worked great.
Then i flashed TWRP and it worked great.
I then proceeded to try and flash DerpFest and when the ADB sideload (ACCORDING TO THE DIRECTIONS) was done, it is suppose to reboot into the new os. but I get nothing.
So Ive tried, a bunch of stuff. I tried using orangefox and it doesnt support SD cards and the sideload option just crashes. So then i try TWRP recovery instead of billies recovery and when i select the image to install in TWRP, and then 'swipe to flash' TWRP instantly resets. and nothing happens.
So then i tried the MSMdownloader tool and it will not recognize the phone at all. all adv and fastboot commands work great.
Can someone help me?
I tried switch A or B, and flashing both,
I tried to go back to stock and i cant even get that to work.
Help meh please, i just bought this phone and now i cant even use it
I also cannot get the MSMdownloader to work. it shows my phone on the list in EDL mode. but com port is empty. device id is empty. all the fields are empty and it just says waiting on device. nothing happens.
For MSM, did you get the driver properly installed?
[OPN105G][OOS 86AA/89BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
arda99 said:
For MSM, did you get the driver properly installed?
[OPN105G][OOS 86AA/89BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Click to expand...
Click to collapse
everyone comes up as it should in the device manager. sad face....
Just to be sure, what do you actually SEE? IIRC it was tricky the first times I used it, until I figured everything out.
There is a separate driver from the MSM tool itself; that makes your phone show up as a Qualcomm something or other... but only for about 3 seconds! In that time, you have to start the upload. Thus, I'd have the tool RUNNING, mouse over the start button, THEN plug in phone.... when it shows up, click, and wait till it says something akin to "beginning firehose download"... then you can let go of buttons on phone, sit back, and watch the magic.
Given a proper setup, it's really odd that this fails, for anything other than a completely bricked phone (e.g. dropped it in the ocean)... if you can get into FB or recovery, you should be able to have MSM recover to stock 100%.
Hope that helps.
SomeRandomGuy said:
Just to be sure, what do you actually SEE? IIRC it was tricky the first times I used it, until I figured everything out.
There is a separate driver from the MSM tool itself; that makes your phone show up as a Qualcomm something or other... but only for about 3 seconds! In that time, you have to start the upload. Thus, I'd have the tool RUNNING, mouse over the start button, THEN plug in phone.... when it shows up, click, and wait till it says something akin to "beginning firehose download"... then you can let go of buttons on phone, sit back, and watch the magic.
Given a proper setup, it's really odd that this fails, for anything other than a completely bricked phone (e.g. dropped it in the ocean)... if you can get into FB or recovery, you should be able to have MSM recover to stock 100%.
Hope that helps.
Click to expand...
Click to collapse
OH wow it did. Thank you, the documentation for that side of MSMd is vague. So after trying like 3 different "qualcomm" drivers I finally got it to work! As in the stock android 10 is loaded and the phone is no longer bricked. However, when I try the same methods again to actually put a custom rom on this phone the same thing is still happening.
No matter what OS i try to flash, no matter what mode or slot, or what recovery 'program' i use like twrp or orange FOX, nothing seems to actually boot into an OS. it just loops into Fastbook.
Can anyone help me? I dont want to use oxygenOS
I had a somewhat similar experience in loading custom ROMs, and simply took to de-bloating the stock image (emphasis on de-google-services, de-OnePlusSpyware, and de-auto-OTA). Still not really happy, compiling AOSP source now to try to swap out some of the system APKs that annoy me for customized ones. If there are only a few things that sour you to OOS, maybe I (or others) can help cure those? Debloat and replace...
I wish I had more silver bullets for you on custom ROMs, but you aren't alone. At least know that you can now go back to stock no matter how bad a ROM is... a lot of other phones, not so much.
So the main reason for me not wanting to use Oxygen OS is because when initally setting up the phone, everything works great. for about 2 or 3 days. then for what ever reason i cannot receive text messages. If I factory reset the phone, or put my simcard into another telephone all of them come rushing in.
In the event of me factory reseting my phone, ill get text messages from 3 or 4 days ago.
and it always works. as soon as my friend is texting me and i dont recieve it, i just factory reset then boom its there.
I tried everything, different SMS apps, update this, android 11 that. it always did it to me, like clockwork. like the phone installs an update and breaks text messages. I tried contacting oneplus customer support but that shhit is a joke. they told me they are aware of multiple isolated incidents about this and that the only thing to do left is to send it in. I JUST BOUGHT THIS THINg, im not about to send my device away, right after paying for it. I paid you guys $400 just to NOT have a telephone for 8-16 weeks?
SomeRandomGuy said:
I wish I had more silver bullets for you on custom ROMs, but you aren't alone. At least know that you can now go back to stock no matter how bad a ROM is... a lot of other phones, not so much.
Click to expand...
Click to collapse
See thats the thing, Ive never gotten another room, to boot. at all. no splash screen, no bootlogo nothing. it always just goes back to fastboot. it never tries to boot an OS. i follow these billie instructions and nothing happens. its the same result. I have tried all the different versions in this forum. from pixel experience to derpfest. all work great, untill the very last step where they say side load rom/flash and then reboot. your new os should be booting! and it doesnt.
Wow, that's a new one for me. I wish I knew more about the internals (slowly learning) to help troubleshoot. I would GUESS that if you can change phones (e.g. you said you can put the sim in a new phone, and get a backup of messages delivered), that it isn't so much that the phone is dropping them as it is not getting them in the first place.
With no guarantees- this is a SWAG- have you checked your APN settings? Most definitely, these come through as part of a new registration (duh), and consequently can get messed up for $diety knows why later... but at least you may be able to get a known-good set of settings (post reset, post registration) to compare to after terrorists strike and you are no longer getting messages. It should be easy to add a new APN with the "right" settings and manually select it.
If it is something like that, odds are an alternative ROM would just do the same thing; I assume there's some kind of handshake standard for initialization of the carrier network. I'm on TMo and happy to share my settings, if it helps....?
Looks like RCS issue as 1+ switched to google phone/msg in OOS11.
Read here.
Turn Off RCS "Chat" When You Switch Phones or Else...
Now that Verizon has committed to RCS with Google, the three major US carriers are all onboard. RCS is here (unlike 5G) and will be a big part of your messaging experience going forward, assuming you have an Android phone. And while RCS is great and a big improvement on traditional text...
www.droid-life.com
How to turn off RCS chats
messages.google.com
arda99 said:
Looks like RCS issue as 1+ switched to google phone/msg in OOS11.
Read here.
Turn Off RCS "Chat" When You Switch Phones or Else...
Now that Verizon has committed to RCS with Google, the three major US carriers are all onboard. RCS is here (unlike 5G) and will be a big part of your messaging experience going forward, assuming you have an Android phone. And while RCS is great and a big improvement on traditional text...
www.droid-life.com
How to turn off RCS chats
messages.google.com
Click to expand...
Click to collapse
sadly this has nothing to do with my problem.
After much testing and another go round of fractory resets and then magicly i recieve texts again. There is nothing that can stop the factory oxygen OS from updating or downloading and installing some update that completely brtiks message functionality. Can someone help me maybe mod or edit the factory ROM image to prevent this?
I found out in the "google assisnt" of setting up your phone for the first time, if i set it to remind me tomorrow then im all good and i can keep using the phone. as soon as i go back to that "setup" and hit continue, the next screen says "installing updates" and then I can no longer receive texts. Does anyone know how to bypass/get rid of this auto matic update thats in the "first time run wizard for adroid" or whatever the FUCFKA its called.
Please, I really think this phone might just be a lost cause
agentruley said:
sadly this has nothing to do with my problem.
After much testing and another go round of fractory resets and then magicly i recieve texts again. There is nothing that can stop the factory oxygen OS from updating or downloading and installing some update that completely brtiks message functionality. Can someone help me maybe mod or edit the factory ROM image to prevent this?
I found out in the "google assisnt" of setting up your phone for the first time, if i set it to remind me tomorrow then im all good and i can keep using the phone. as soon as i go back to that "setup" and hit continue, the next screen says "installing updates" and then I can no longer receive texts. Does anyone know how to bypass/get rid of this auto matic update thats in the "first time run wizard for adroid" or whatever the FUCFKA its called.
Please, I really think this phone might just be a lost cause
Click to expand...
Click to collapse
"carrier services"? that's the only one I can think of. Try to uninstall the update, or if you don't have it in your phone, install it.
I had to go through the setup process again. First time the DF just didn't catch. I read ADB sideload can be broken as **** sometimes.
arda99 said:
"carrier services"? that's the only one I can think of. Try to uninstall the update, or if you don't have it in your phone, install it.
Click to expand...
Click to collapse
Sadly this has nothing to do with my problem. Installing newer/ using older versions do not change the behavior.
The phone breaks as soon as I go back to the "Google Assisnt" -Setting up your phone for the first time- wizard and instead of selecting "Remind me tomorrow" i select next, and then the following screen says "Installing updates" and then the telephone will no longer recieve text messages. Does anyone have any help?
Oneplus customer service is terrible and they told me to buy another device.
This is the last phone i will ever purchase from them