Hi everyone!
I installed CM on my mothers phone some while back (+gapps). Seemingly she used the automatic update function yesterday and since then the mobile will not start up properly (start-screen stays even after a night). She tried taking out the battery and starting it afterwards. I'm about 2000km away for the next two weeks. Any suggestions what she could try, or what I could try once I'm back?
Thanks!
Related
I've been using my HD2 for months trouble free.
The last few weeks i've been running android and windows, mostly windows but playing about with android in the evenings about a week ago i downloaded the HD2 Froyo V2.1 and installed all went ok, thats been fine all week but yesterday i decided to have a go at running android most of the day which is working really well.
But here's the issue went back into windows last night and its just not running it will boot up and seem fine for a few min then it just freezes, i'm using elegancia rom so did a hard reset set everything back up seemed ok for about 10min then tried to log into twitter and the phone froze, reinstalled everything again and same thing happened.
So this morning i decided to install an Nrgy rom to see if that made any difference.
I put the 1914 sense rom on so its close to stock as possible and that seems to be ok but when i log onto twitter it restarts sense and i've had a few issue's with it randomly switching sense off but it doesn't freeze now it just restarts sense.
Any ideas i've not used android with the Nrgy rom as yet is there anyway that something android has put onto the SD card may be effecting the stability of windows ?
Any ideas much appreciated...
Just to add i've just read that there appears to be a twitter issue.
But i'm still getting random sense resets without using twitter ?
Hi
Since about a week ago my SGS2 answer an incoming calls with the speakerphone turned on by default, and there's no way I can change it.
I use lightning rom 1.5 for a few months and everything was perfect until now.
Please help!
TNX
Backup data>> factory reset .
jje
Oh I had this same issue just last week, out of nowhere. Here's what I did: plug the USB cord in & out the phone a few times, it should get okay. Just google it too, there's a bunch of HTC users who have reported the same issue but the plug in/out solution works for S2 as well.
Do you all use Go SMS Pro?....if so then its a software issue...
Update the application to the latest one and your issue will be resolved.
I used to have Go SMS pro, but I removed it long ago.
I heard about the problem it makes - similar to mine, so I tried to install and uninstall it again, but it didn't help.
I tried the USB connect/unconnect advice - didn't help.
I tried to install several auto-speakerphone apps to bypass the problem
Most didn't succeed, except from "save your brain" that worked OK for a while and than stopped. It also had annoying notification icon, and many Chinese notes, so I uninstalled it too.
Can't find the solution yet
I'd love more suggestions.
Thanks.
Lior
liorreem said:
Hi
Since about a week ago my SGS2 answer an incoming calls with the speakerphone turned on by default, and there's no way I can change it...
Click to expand...
Click to collapse
i had the same issue for about the same period, it started kinda a week ago, but in the past days i noticed that it just returned to normal
i updated gosms on 29aug to the last version, i guess this was all the fix i needed, stock 2.3.3 atm
Hi
I Managed to solved the problem using Elixir widget.
One of the possible widgets is Speaker widget.
Once I turned it off - the problem stopped.
Hurray.
Some time ago the blue button stopped working on my pro keyboard(the one that lets to write numbers etc.) Instead activating secondary buttons now it writes qrtc/ I thought it was cm getting bugged(I had some cm9 few months old version). So I decided that it was time to update, today finally found some time to do it, updated to latest cm10 build, but the problem is still present. Any ideas how to fix it?
Hi all,
I'm really hoping someone will be able to help me. My Nexus 10 has been working fine up til now. I just tried to take some photos, the first two were fine, the flash worked and they came out ok.. then I tried to take another but the flash didn't work. I figured it might just be a bug so I restarted the nexus, it still wouldn't work. then after a few mins the flash just came on and stayed on. so I went back to the camera app, the flash turned off and the app told me "cannot connect to camera". Another reboot and the camera is fine again but still no flash. Any suggestions? or is it RMA time... which I'm reluctant to do as other than this the tablet is perfect.
Thanks
The flash by-default is automatic, depending on lighting. May want to try going to the camera app, and making sure flash is actually on, and not automatic, and then giving it a shot.
Tried setting the flash from auto, no luck. Was in a fairly dark room anyway so auto should have caused the flash to go anyway. Thanks for the suggestion though
EDIT
------------
UPDATE - I tried flashing the factory image to check if it was some kind of corruption or software bug. Didn't work, still no flash. So I started reinstalling all my apps and setting everything back up and, while installing some humble bundle games, I accidentally started the camera app... and guess what, the flash came on and then went off again after it had focused. Took a few photos and the flash was working. Tried again 2 mins later (without changing anything on the device) and the flash has stopped working again...>.<
After switching to LineageOS 14.1, my Samsung S3 i9300 randomly turns off. Not a proper shutdown, screen just goes black.
Happened 7 times in 2 days so far, first time while I was tinkering with the settings, second time while I was swiping to another page in Nova Launcher, third time while I was asleep last night, woke up and discovered my phone was off. The other shutdowns happened while the phone was locked.
The device does not shut down completely. I can see the Samsung Led flashing for the message notifications. Just the display turns off. I have to go into recovery mode and reboot the system from there to get the display working again.
I came from the stock ROM. It started immediately after flashing Lineage.
If this happens on a stock rom, it is probably a hardware issue.
audit13 said:
If this happens on a stock rom, it is probably a hardware issue.
Click to expand...
Click to collapse
Thank you for your reply, but this does not happen on the stock rom.
It's definitely good that this doesn't happen in stock.
Sounds like a incompatibility between the phone and rom. Have you tried earlier or later versions of lineage?
All custom roms are considered beta. You will encounter issues. The issues should be in a list on the website/dev forum for the developers.
Beamed in by telepathy
I can also confirm this on the latest lineageos nightly update to date. It's as if phone is on standby/sleep and no way to wake it up without rebooting the phone by holding down the power button until phone restarts. I don't need to go into recovery like OP. Anyone else?
Are we the only ones experiencing this issue? Any help would be appreciated.
Gizmotech said:
Are we the only ones experiencing this issue? Any help would be appreciated.
Click to expand...
Click to collapse
You got a reply in the other thread where you posted about it:
minealex2244 said:
I'm feeling bad for you guys. Everyone should get the same beautiful LOS experience.
Thank you @Gizmotech for the last_kmsg. I think that you removed the battery to be able to reboot your phone. If you received a notification (sometimes you will receive it but it will freeze before letting you know that you got a notification) then the kernel will freeze. If the kernel is freezing it's because of root or a failed attempt to remove root (even if it said that it was a successful removal). It's very simple: you get a notification and it freezes. Maybe it will give a sound and the LED light maybe not. What's sure is that the kernel will freeze. Lastest SuperSU has this issue fixed. If you want it working then dirty flash latest build again. Tell me if the issue was fixed and avoid root until that time. After you'll tell me the results you can flash latest SuperSU and tell me again what happened. Do not remove root. This is always a dangerous thing.
Click to expand...
Click to collapse
kgndrn said:
After switching to LineageOS 14.1, my Samsung S3 i9300 randomly turns off. Not a proper shutdown, screen just goes black.
Happened 7 times in 2 days so far, first time while I was tinkering with the settings, second time while I was swiping to another page in Nova Launcher, third time while I was asleep last night, woke up and discovered my phone was off. The other shutdowns happened while the phone was locked.
The device does not shut down completely. I can see the Samsung Led flashing for the message notifications. Just the display turns off. I have to go into recovery mode and reboot the system from there to get the display working again.
I came from the stock ROM. It started immediately after flashing Lineage.
Click to expand...
Click to collapse
Providing the last_kmsg will help Simon to find a solution. If you only complain about this issue then it won't be solved. Next time make sure to include last_kmsg.
---------- Post added at 19:49 ---------- Previous post was at 19:45 ----------
shivadow said:
All custom roms are considered beta. You will encounter issues. The issues should be in a list on the website/dev forum for the developers.
Beamed in by telepathy
Click to expand...
Click to collapse
Really? Do you know what beta means? I'm sure that you don't. Beta means that it is not really stable (80% or less of the things are working) while stable means that 95% of the things are working. This explains why LOS 14.1 for S6 was considered stable: because everything was working. Also that issues are already listed in the forums.
kgndrn said:
After switching to LineageOS 14.1, my Samsung S3 i9300 randomly turns off. Not a proper shutdown, screen just goes black.
Happened 7 times in 2 days so far, first time while I was tinkering with the settings, second time while I was swiping to another page in Nova Launcher, third time while I was asleep last night, woke up and discovered my phone was off. The other shutdowns happened while the phone was locked.
The device does not shut down completely. I can see the Samsung Led flashing for the message notifications. st the display turns off. I have to go into recovery mode and reboot the system from there to get the display working again.
I came from the stock ROM. It started immediately after flashing Lineage.
Click to expand...
Click to collapse
Same problem with last lineage version. Are you found solution ?
Any news on this? g9305 boots just fine but reboots after a few seconds / minutes.
cRaZy-bisCuiT said:
Any news on this? g9305 boots just fine but reboots after a few seconds / minutes.
Click to expand...
Click to collapse
The problem is the rom or kernel. It happens to all custom roms and kernels on the s3. No-one has found the source of the problem.
Everything custom is beta even if it is considered stable. Beta means "not final". Unless you see a rom with "final" on it then you'll encounter issues at some point.
The only truly final product if you want root is stock rom rooted. If you flash a kernel you'll get the same problem.