Hi!
I have a huge and strange problem with androids since two months.
Can someone tell me what's this for?
Code:
[<number>] msmfb_start_dma <number> ms after vsync request
I have a lot of lines with it while booting.
It slowdowns booting and when this line shows up, i cannot use Android(because android is freezed).
When this line didn't showed up, Android worked great. But unfortunately the line shows up every boot now.
Can someone help me :/?
@edit
Tried everything, look here please:
http://www.neopeek.com/viewtopic.php?f=30&t=6225
Related
Hello guys!
I'm having some trouble with my HTC Touch Diamond. I am running the latest ROM, and the phone has worked perfectly since I've got it!
But one day it suddenly powered itself of during a phonecall and I was not able to power it on again. I removed the battery, put it in again, didn't work. Took out the battery and waited for almost 30 minutes, tried again and now it worked!
Since then the phone locks up in no systematical pattern (when I wake up in the morning it mybe locked itself, sometimes when I listen to the radio or typing an SMS..). Do you have any idea what the problem might be? Can't type in the serial number as I just have managed to turn it on.
What should be mentioned is the behavior when trying to start it. Either the phone gives no respons, or it "buzzez" and the display shows "touch diamond", but the rom version is not appearing down to the right. When it starts, it starts just as it should and no error messages is displayed.
I have not tried doing a hard reset yet, which I must say is considered the last option.
Have anyone experienced something like this? Or does anyone have a suggestion about what might be causing this?
Thanks on beforehand
Edit: have performed a hard reset now (did not format the 4gb). But the problem is not gone.. The phone just died while surfing. Now it locks at the green windows mobile-screen just before the homescreen loads (if it even boots at all...)
Please help anyone!
Has anyone ever ran into a situation where the UI locks up after a boot? I keep searching through threads and can't find anything. I'm not sure if it's something I have installed or if there is actually something wrong with the device. I had a nook previously and never encountered this problem but on the new one I just got (ebay refurb) the problem just keeps coming back.
Basically, it boots just fine and starts to show the Launcher but then the screen goes black and leaves the soft buttons at the bottom. The only way to recover is to shut it down and start it back up.
The funny thing is it doesn't do it all the time... sometimes it boots just fine and never locks up while in the OS... it's only on boot it does this.
I've tried multiple different versions of cm7 and am getting the same thing on all versions. I've tried different kernels and stock speeds and it still happens.
Any help or advice would be appreciated!
Hmmm... well after hours of troubleshooting I think I pinpointed it to beautiful widgets
Hello,
This is my first time posting here, and I would like to request anyone on here to please assist me with the problem I am currently facing. I bought an unlocked, rooted HTC One with stock Android 4.3 installed as it's sole, primary OS this past summer. The person I bought it from is the one who actually rooted the phone, as my knowledge of such processes is fairly limited. I understand there are plenty of complications that I may run into dealing with this problem on my own and technical references may be lost on me, but I'm fairly competent enough to follow instructions from someone who may be able to help.
Here's the problem: I received an Android 4.4 OS update yesterday, which downloaded automatically and asked me if I wanted to install it. I thought the process would be fairly simple and I would not encounter any problems. However, when I asked the update to register and install, first it went into boot (I'm not certain which software was used for root), then the process started and everything seemed to be going fine until 'Patching files onto the whatever' came up and then it appeared that I encountered an error and the phone automatically went into what I can only assume is the bootloader menu? There were big Stock Android looking buttons on it which said things like Install, Root, Settings and a few others I don't recall. I tried to hit Install to see what happened and it brought me back to the part where 4.4 was supposed to be installed and I could read the error message at the end of it which said something like 'Error in patching files to zip folder or something', and I went back to the supposed bootloader menu. Confused and afraid, I think I pressed a button which I felt would allow me to reboot my phone and bring me back to my original 4.3 OS and that I would still be able to use my phone. First it said something like 'You no longer have root permissions', and there was an option where I could slide to apparently 'fix this', but I selected the 'don't fix' option as I obviously had no idea what I was doing. After this, the phone attempted to reboot, and a turquoise blue screen with strange markings came up on it and my phone hung. I killed the phone with the master power button and held it to switch off the phone.
BUT now, even since that has happened, my phone appears to be dead. It isn't starting up. When I put it on charge, the red LED doesn't show up. I have tried to used several ways to turn on my phone but it just wouldn't work.
I would like some light to be shed on this particular problem, and if anyone has experienced something similar to this, PLEASE, help me in fixing this. I am an eager learner and despite my limited, close to non-existent knowledge about dealing with a phone's OS, I know I can learn fast and follow instructions cleanly.
Please help me. Thank you.
Hey guys how are you?
Well everybody knows about the Stuck in motorola logo right? Well, I always use the RSD Lite and re-install the Rom (9.8.2I-50_SML-29_Retail_BR_SIGNED_SLATAMUnlk_USASMI01RETBRLA022.0R_S1FF_CFC_fb.xml) and ALWAYS get the problem back in a few weeks like 4 or 6 weeks.
So, here in forum I only found replies like "fastboot", "rsd lite"...and I already am doing that every time but doesn't fix the problem (just for a little time).
Someone knows how to fix like "forever"? (or at least more than 1 month haha)
dudubets said:
Hey guys how are you?
Well everybody knows about the Stuck in motorola logo right? Well, I always use the RSD Lite and re-install the Rom (9.8.2I-50_SML-29_Retail_BR_SIGNED_SLATAMUnlk_USASMI01RETBRLA022.0R_S1FF_CFC_fb.xml) and ALWAYS get the problem back in a few weeks like 4 or 6 weeks.
So, here in forum I only found replies like "fastboot", "rsd lite"...and I already am doing that every time but doesn't fix the problem (just for a little time).
Someone knows how to fix like "forever"? (or at least more than 1 month haha)
Click to expand...
Click to collapse
I have the same problem here =/
hardware or software error?
Same problem here.
It starts with apps closing without error message, random reboots and slowdowns. The first time I also could not call anyone although I had a good connection.
Sometimes the booting process also lasts several minutes. Then, finally after some days one of those reboots or forced reboots ends at the Motorola logo.
Used RSD Lite to flash "CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU", everything works fine and after 1-2 month the history repeats itself.
People seem to have this problem a lot since mid 2014.
Do you think this is a hardware error (memory fail e.g.)?
Or a software problem induced by some newer apps?
Hi there,
I've got OnePlus 10 Pro phone and it came with strange random reboots right after starting to use it. I tried flashing different roms, factory resetting it with no luck. The last thing I've done is checking logs with logcat . The closest one I've got is reboot right after disconnecting cable with active logcat. After reboot I've saved log (attached).
Looks like it is system process but I don't know what to do next. The main message looks like this:
01-19 18:37:24.045 25684 26842 F libc : Fatal signal 4 (SIGILL), code 1 (ILL_ILLOPC), fault addr 0x7f0bd91500 in tid 26842 (binder:25684_9), pid 25684 (system_server)
Hope someone could help because OP support is not responding =\
Thanks in advance!
Same thing was happening to my on a daily basis, at least once per day of not two or three times. I noticed it was somehow related to the wifi/data connection, but I couldn't exactly figure out the reason.
I updated to Android 13 ( NE2213_11.C.22 ) on december and that issue went away until today, that I had another random reset. (I say that issue because the Android 13 update comes with some other less annoying bugs, like the notifications bar getting stuck every once in a while)
I've tried every firmware found with no luck.
I've tested hardware with app and it says everything is fine.
I've tried to fill storage fully and it worked with no reboots.
Memory app filled RAM fully and phone still doesn't reboot.
I have no idea what to do next
And the saddest thing is total ignorance from 1+ support.