Hello,
Sorry to post this here. I've been following a few threads about x10 mini pro custom roms for weeks now but after signing up I am not allowed to ask my question to that specific rom there. It said I should post it here first.
I am using the [ROM]MiniCM7 Pro - V7x - GingerBread (2.3.5) by paul-xxx for more than 2 weeks now and it works great, I even have a battery life of about 14 hours now instead of 6 after I stopped using launcher pro and used the standard adw.
But I have 2 serious problems.
The first is that I cannot always unlock my phone. I know I have seen this question a lot but in my case the screen just stays black. There is no slider that does not want to slide. Just a black screen. If I slide open the keyboard I see the lights go on some times. When I connect via usb I can open a shell (via putty) and every thing seems up and running. Just the display is now showing anything.
When pushing buttons and sliding the keyboard several times I sometimes get the screenback. Some times just have to wait 5 minutes or so.
Does anyone have any clue what to do about this?
I tried killing the launcher process but that did not help, it just restarts and even if it did help I do not always have the phone connected to usb.
The other question is about missing calls. I had several missed call alerts while i was sure I was next to the phone all day.
Today I saw it happening for the first time. (because I got a missed call sms and right after that a call on the land line which was the same person who called my cell)
So I called my phone (after letting it go to sleep), used top to see whats going on. I saw the process android.phone.com starting to use more cpu (but not 100%) and I even saw the screen get activated (after 10 seconds or so) but no sound and then it went to voicemail and the phone went dark again but the sms with the missed call came in right away.
Is there a solution to this or are there more people have problems with this?
Any suggestions would be appreciated.
Related
Hi everyone, I hope someone can help me.
I just upgrade to the offical Verizon ROM to WM 6.5 and I'm having some issues.
The main problem: I take my phone off of sleep mode or stop it from entering just prior to and my TF3D home screen shows but the banner reads "messaging" instead of "start" like I'm in my messages and the virtual keyboard will pop up. This also happens 85% of the time when I recieve a new txt/mms not with emails however. This is a new development I;ve had the ROM since launch.
Before I call VZW and get stuck on hold for 50 years I figured i would see if anyone else has this issue or knows of a .cab that might fix the issue. I have had luck with .cabs in the past for other issues.
Side note, has anyone successfully stopped the clock from flipping an hour and two minutes? I have checked the fourms downloaded all the .cabs and nothing seems to actually stop it.
I am in the exact same boat as you my friend. I am also having diffuculty locating a background for all tabs .cab and a working rotator for all screens that functions in the VZ TP2 6.5update
PaulKiefer1821 said:
The main problem: I take my phone off of sleep mode or stop it from entering just prior to and my TF3D home screen shows but the banner reads "messaging" instead of "start" like I'm in my messages and the virtual keyboard will pop up. This also happens 85% of the time when I recieve a new txt/mms not with emails however. This is a new development I;ve had the ROM since launch.
Click to expand...
Click to collapse
I have a very similar problem to you my friend. When I check my messages (txt or emails) and close out of them the Messaging will pop up like yours, although my keyboard doesn't show up. Sometimes it takes 5 seconds sometimes 30 seconds.
My main issue is it will turn my screen back on when this happens. So if I read a txt and close it and I don't wait for it to pop up, my screen will stay on. It's killing my battery life and some funky things happen when its in my pocket turned on..
Any idea if anyone has come across a solution to this?
Hi,
I've only had my Nexus S for a couple of days and loving it so far, but this morning I had a problem. Here's how it happened:
When my alarm clock went off I hit the snooze button and turned the screen off, went back to sleep. 10 minutes later the alarm went off again later as expected and so I hit snooze again and turned the screen off like before. 5 minutes later I decided to get up as otherwise I would have been late for work, so I go to my phone to disable the alarm as otherwise it would be buzzing when I'm in the shower and the missus would get annoyed. The problem however was that I couldn't unlock the screen! I was jabbing at the power button repeatedly to get it to come on but no response at all. I ending up removing the battery. I should also add that my phone was plugged in a the time as I'd left it charging over night.
Has this ever happened to anyone else? I will try and replicate the problem. Here's how my phone is at the moment:
All my homescreens are bare apart from the main one where I have a 4 shortcuts, google search bar and the analogue clock widget. Apps I currently have installed are: Ebay official, facebook official, Twitter official, 3G watchdog, Fruit Ninja, Angy Birds, Live Holdem, Google maps, Gmail Unread Count, Movies, TV Guide.
I'm hoping that this problem was just a one-off.
Thanks
sort of same here. i bought it last thursday and today i can't use the lower part of the screen, right where the phone, menu and browser icons are. Space bar won't work when writing text, etc.
If anyone knows how to fix, pls share
The device is stock 2.3.3, i9023XXKB1, didn't root.
D G said:
Hi,
I've only had my Nexus S for a couple of days and loving it so far, but this morning I had a problem. Here's how it happened:
...
Thanks
Click to expand...
Click to collapse
I have been using Nexus S for 4 months now, and I do have random reboots once in a while. Did the phone well work after the reboot?
sort of same here. i bought it last thursday and today i can't use the lower part of the screen, right where the phone, menu and browser icons are. Space bar won't work when writing text, etc.
If anyone knows how to fix, pls share
The device is stock 2.3.3, i9023XXKB1, didn't root.
Click to expand...
Click to collapse
I never had responsive problem on my phone other than the phone just freezing... Maybe theres something wrong, go ask Samsung.
unfortunately i also have such a problem now! since this morning my screen does not respond on touch correctly...it is very hard to unlock the screen (have to do it very slowly, bar is jumping like crazy) and after that it seems like the screen is reacting even on any reflection, suddenly the status bar is coming down, if i am in a menu, it always scrolls down and up...damned, that sux!
any ideas what i could do? or is this a case for samsung support?
ps: i did not flash anything in the last days, i even restored my nandbackup, that i made after 2.3.4-update (no custom kernel, no nothing), but that did not change anything...
Hi,
I have quite a weird problem...
I have to pop out the battery to restart the phone nearly every day.
The screen just blacks totally out and the phone will not respond to anything.
The phone is not dead, I know this because I can hear messages and incoming calls but I cannot do anything about it since the screen is all black (turned off).
Experience? Workaround? Advice?
Update: The screen actually wakes up to show me the phone call or the message, but I cannot do anything about it. So it seems rather that some services on the phone is stuck and, as said, only way to get the phone working again is to reboot by taking the battery.
I came across the same problem and I wasn't able to fix it till now.
I did a full-wipe two times and restored only the basic apps.
I have no idea anymore.
"adb reboot" is an alternative solution.
Hi There,
I got an really annoying problem and can't find anything on the web or this forum. Probably due to the common keywords....
My problem, since 1,5 months (can't remember if this is after an update) notifications stay on screen for 45 seconds! App notification but also android system notifications (the grey ones beneath the screen). For instance, picking up my phone from the wireless charger the phone says "Draadloos laden onderbroken" this is the dutch message for saying the phone has stopped charging wireless. Then opening let's say whatsapp, this notifications hovers 45 seconds above the text input position.
I can't find any setting that let's me adjust the screen time duration of notifications. Rebooted the device and also had a new update few days ago, but the problem stays. I'm running Android 10, One UI 2.0 with kernel 4.14.113-17806689.
I feel really stupid not figuring this seemly simple thing out by myself.
Gr,
Erwin
MrReaL said:
Hi There,
I got an really annoying problem and can't find anything on the web or this forum. Probably due to the common keywords....
My problem, since 1,5 months (can't remember if this is after an update) notifications stay on screen for 45 seconds! App notification but also android system notifications (the grey ones beneath the screen). For instance, picking up my phone from the wireless charger the phone says "Draadloos laden onderbroken" this is the dutch message for saying the phone has stopped charging wireless. Then opening let's say whatsapp, this notifications hovers 45 seconds above the text input position.
I can't find any setting that let's me adjust the screen time duration of notifications. Rebooted the device and also had a new update few days ago, but the problem stays. I'm running Android 10, One UI 2.0 with kernel 4.14.113-17806689.
I feel really stupid not figuring this seemly simple thing out by myself.
Gr,
Erwin
Click to expand...
Click to collapse
Have you found this setting?Settings\Accessibility\Advanced settings\Time to take action
Instellingen\Toegankelijkheid\Geavanceerde instellingen\Tijd om actie te ondernemen
Not sure if it will solve the problem, but it seems related. This setting is hard to find and you might not remember having changed it. No 45 sec option though.
OMG, this did the trick. #Nunspeet #hero
NoCo33 said:
Have you found this setting?Settings\Accessibility\Advanced settings\Time to take action
Instellingen\Toegankelijkheid\Geavanceerde instellingen\Tijd om actie te ondernemen
Not sure if it will solve the problem, but it seems related. This setting is hard to find and you might not remember having changed it. No 45 sec option though.
Click to expand...
Click to collapse
That worked for me for some reason mine was set to 2 minutes. I don't remember changing this setting. Ooo well it's resolved now.
Thanks
Notifications are a disaster on this phone. It kills apps in the background too aggressively, also (excluding apps from that seems a little hit-and-miss). I love customization, but Android 10 and OneUI have made a real mess of this.
My current problem is when I get a call, the popup flashes only for a second. Everything was so much simpler on my old rooted phone!
When I get a flood of notifications, my phone freezes up. Either it's Notistar's fault or there is a huge issue with the notification system.
Hi,
I experienced for the second time some strange incident on my OP Nord (eu). When I looked on my phone it had this OP Bootupscreen with the one red and two white moving Dots but it didnt start up. The dots where moving for about 15 minutes. I had to press Vol up + on/off button to shut down the Phone and then Start it again to get it up and running again.
The first Time I was in the Car listening to some music. The Phone was via BT to the Car Radio connected and played Music with the app Musicolet. After a short stop at a store it didnt connect again with the radio. I had a look on the Nord and saw this issue the first time.
The second time, I used it with some messaging apps, placed it on my desk, wanted to use it around 10 minutes later again and had this Bootup Failure a second time.
Had anybody of you some simlar Problem? Or maybe an Idea what could be wrong?
The Nord is not rooted or manipulated in any other way. Just standard Phone with the Latest OP Updates installed.
Kind Regards
Yes I had the same problem. I had to use Vol up + on/off button aswell, but it worked again after that. I just had it in my pocket and didnt do anything and when I put it out of my pocket I had the bootlogo as well. Strangely I had this also the second time as you said.
Random reboot force restart
Same to me 12gb version about 5th time now this has happened.. As other members say. You only notice it if your looking for at the screen. Had to do same it booted up into safe mode 1st. Have have seen on the Oneplus forums that some phone auto goto factory reset lucky that hasn't done that for me. However it does make you choose your default Internet search engine each time and my Google one account resets again... Anyone any idea of the cause any Dev / programmer's on here know the cause yet. As you all say its random done it to me while in pocket car and work desk.. Bloody annoying
Yes! Same problem here.
Strange auto reboot and gets stuck after connecting bluetooth sometimes, or while just simply decreasing volume . Screen goes unresponsive many times while using Google chrome and handling media on whatsapp. Mobile data and wifi would take 10-20 secs to turn on sometimes, don't know why!
DAMN! THIS PHONE HAS A TON OF BUGS THAT INTERFERE WITH DAY-TO-DAY TASKS!
Happened to me once too
Happened to me too a couple of times on EU firmware.
On the forum it's been madness with this , they issued a statement that they are full on it . But there were some users suggesting that it was caused by the forgot password option , and if pattern was used there was no problem. This though , was not confirmed. I have the phone about a week , i've been using pattern since my first android . Nothing has happened to me . Did anyone of you use pattern ? Or everyone had a password/ PIN ? If so , try using pattern lock to see if it happens again...maybe it could be a chance to pinpoint the root of it and save other users...
It happened 2 times when I used face unlock. I stopped using a locking method and no random reboots since, but there was also updates recently so dunno...
Happened twice