Sensors not working after a while, needs reboot. - One (M8) Q&A, Help & Troubleshooting

Good day to everyone who stumbled upon my humble thread, would you mind helping me?
I got my M8 two weeks ago and the first thing to do with it was to flash a custom ROM. That's when the problems appeared. Features like auto-rotate, doubletap to wake, compass etc. stopped working after the device has been running for some time. After reboot everything got back to normal, but the problems reappeared quickly. I tried several different ROMs and kernels and I'm currently on CarbonROM. And I'm NOT planning to switch back to stock. I've searched a lot and found nothing, but feel free to give me even the most basic advice. Any advice besides reverting to stock is welcome. Thanks

Related

Touch pro 2 heating up

Hi everyone. First of all I would like to thank everyone for providing support and apps on this forum.
I have a question. I have the Sprint Stock ROM and the only thing I have changed for the past 2 days (other than install different apps) is install TypeNotes. As soon as I start the app, the unit starts heating up. Using "Battery Meter" the temprature goes upto 43C.
Even after I close the app, it dosent seem to change. Does anyone know if there is a problem with this app or if there is a way to figure if TypeNotes is interacting with any other process which is making the phone warm.
Thanks
I am in the same situation. I upgraded to 6.5 a week ago and have typenote installed. Whenever I use typenote, I have to perform a soft reset. At first I thought that it was GPS (AmazGPS). but it is pretty consistent with typenote.
Any suggestions.
BTW is typenote still being developed. I havent seen any newer updates.

[Q] Custom Roms Freezing

Hi everyone,
Sorry if this has been discussed in the past but I did several searches and didn't find anything.
I flashed my HTC Tilt 2 last week and installed the Energy Rom. I love everything about it but after about two days I began to notice that the touch screen and the phone itself will become unresponsive at least 3 times a day. I will touch the screen and nothing happens. My weather will freeze (no clouds moving etc) and none of my buttons will work.
There have been times when I was charging my phone and it would freeze and when I removed the charger, the charging light would remain on until I soft reset on the side with the stylus.
This is very frustrating and while I love the custom rom I am contemplating getting everything back to the stock rom.
Has anyone else experienced this? I tried several searches but found no answer or anyone else with a similar problem. If anyone can provide insight/advice I'd appreciate it!
You say that customs roms get you freezing...But you only mention energy. Did you try other roms? There are many other good roms that don't freeze. Believe me when I say that when you flash a decend rom, you won't go back to stock
Make sure you run a task29 before flashing an other rom.
I have a Tilt2 and have been running various (5 or more) versions of the Enregy ROM since May, and have never had any problems like the one you mentioned. I always run Task29 before every ROM flash.
Thanks for your replies!
I'll reflash energy and use task29 hopefully it fixes things!

[Q] Maps/Navigation force closing on custom ROM/Kernel - HELP Please!

Hi all,
Hopefully someone can shed some light on this and help a tortured soul. By no means am I an Android expert, but I definitely am not a noob. I had an S2 in the past and done plenty of flashing there, and now own a Bell SGH-I747M S3... my precious...
First off I tried a whole bunch of different ROMs, of all flavors (AOSP, AOKP, CM10, PARANOID, and some TW), and a lot of them are awesome. However, I found that after having done so much flashing and customizing using other people's work, it was now time for me and attempt to make my own ROM. I feel I now have the knowledge to do so. Don't get me wrong, I am far from a Dev, and I don't do much coding at all. I found this great suite called Android Kitchen, which pretty much guides you through the steps for making your own ROM, and it's great for learning.
In the end, I was able to come up with a final working version of my own ROM, built from scratch using the original official Bell JB 4.1.1 update file. and I have to say I am quite proud of it, as it has all the apps, features and theming that I want, and works quite well I might add. I get great results performance and battery wise (for my taste and needs) when using my ROM with KToonsez kernel.
BUT!!... as good as I think the ROM is, it is unfortunately not flawless. I do have an issue (the only one I could find so far after 2 weeks using it), and for me it is a BIG issue. Maps/Navigation does not seem to like the ROM/kernel combo on MY phone. I say MY phone because I have setup a friend with pretty much the same thing, and he is not experiencing the same issue.
Here is a description of the problem I get. Let's say I go to my contacts and select one with an address. I will touch the address, then Maps opens no problem, and finds the place, and I also get fast GPS lock, no issues there either. Then I will select Navigate to get a voice turn by turn description while driving. The Nav app starts OK as well and seems to work fine. Then after a few minutes (sometimes 2 sometimes 10), Navigation will shutdown, and I get a pop-up saying "Unfortunately Maps has stopped working...". When I OK that, after a few seconds, Navigation starts talking to me again, although not on screen. Also a Navigation icon will appear in the notification area, and if I hit that it resumes Nav, as if nothing had happened. Another few minutes like that, and then I get the same message again, but this time it crashes for good. ALWAYS!!
Troubleshooting:
- Flashed the ROM/Kernel 3 times now. Always wiping and formatting ALL!
- Cleared cache and data from Android Settings/Applications
- Cleared cache from Maps settings.
- Re-installed Maps
- Wiped phone cache, dalvik cache and fixed permissions from recovery.
- Changed kernel back to stock (that seems to work fine btw,, but I do not want stock kernel, plus the setup I want works well on my friend's S3, same as mine, which I setup myself for him (he's a total noob)).
- Changed kernel again from stock to KToonsez (that also works fine after that, however I get other things that start not working well... too many).
- I always wipe cache, dalvik cache and fix permissions after changing kernels.
I have been poking at this for about a week now, and I am tired! I was hoping someone would have a suggestion, maybe from past experience. The only thing I can think of that is different on his phone and mine is the apps that we restore after installing the ROM and kernel (Titanium Backup, user apps and data only, nothing related to system is touched). I am guessing one of my apps could cause a conflict, but pardon my laziness, but I really do not feel like testing / installing my apps one by one to hopefully without guarantee find a culprit... way too many apps for that So I am testing my luck here on XDA... there are a lot of smart people here
I appologize for the lenghty post, but this way, there is less chance I left anything out... PLEASE HELP!!!
Raz...
Sorry for the bump guys... I was really hoping someone can give some input here. Desperate for a solution here!!
Thanks

[Q] Hello all. Slight problem regarding the Xperia S speaker.

Hey everyone.
I am new to these forums and new to Android in general. I finally got an Xperia S a few weeks ago. After a lot of reading and trying things out, I was able to successfully flash some roms (and unlock the bootloader, root, etc).
I have learned a LOT in the last 3 weeks. I really like the Paranoid Android and now, Nova roms. However, something is troubling. The sound was not working on viber (maybe it never did... i just used it like 2 weeks ago, so maybe it's the Xperia S, roms, or a setting). I flashed a baseband, using flashtool and it solved it mainly. I still could not change volume (slider bar moved, no change audibly). Anyways, I flashed to Dark Passion PA a couple nights ago. It worked well for the most part.
No audio on Play previews prompted me to try youtube... resulting in the same error. All the while internet radio apps were not working. I finally got one to work ('Tuned in'), but Xiialive said "Failed to set volume". Anyways, eventually, no audio was being heard anywhere except via earphones, and in call. The speakers (internal and loud) are silent on any setting and in any media (ringing, youtube, net, radio, mp3's etc). I can hear calls though.
I tried plugging earphones in and out (as per search suggestions). This did not bring a positive result. I am considering flashing back to stock. My phone keeps leaving flash mode, on flashtool though. Emma is not working (Sony's newest tool). I hope I don't need to send it back to Sony or Amazon (where I bought it).
If it matters, I am on Nova RC2 and was most recently on Dark Passion PA. Both are quite cool. The sound problems (no sound at all sans earphones) started yesterday, as far as I can tell. Both clean installs.
I really appreciate the hard work and innovation of the developers, and the support of these forums. This is my first post, but tireless reading enabled me to learn how to flash and troubleshoot better, for that I am grateful. Any guidance in resolving the lack of sound, will be sincerely appreciated. Thank you.
Seems like even a flash to Official ICS does not solve the problem.
Strange behavior. Old rom's background was showing up after a few clean installs of NOVA rom. I am not blaming the rom, it may happen with any. Now, post-flashing the Official NL ICS firmware (which didn't work in many attempts) It seemingly worked, with sill NO SOUND. It died (battery) and now it won't boot. It doesn't even charge, all the time. Just an orange light sometime. I'll give it to Sony.
Welcome to the forum. Thread moved. Please make sure you post your threads in the relevant sections as all questions should be posted here in Q&A.
Thanks
AvRS

TM-320 Random Rebooting

Good morning all,
I wanted to get some thoughts on random rebooting and wi-fi dropouts I am having with my Samsung Galaxy Tab Pro 8.4. For some time now I have had issues with random rebooting of my tablet - often when first starting a game or other app. I mostly dealt with it, but finally got frustrated enough to really start trying some other options. My tablet has long been rooted and for a while I had some success with CyanogenMod. But then I started getting freq crashes with that. Tried rolling back to earlier and later versions (always with a complete wipe)...still got crashes. Then went back to complete stock, still crashes. Then reloaded TWRP and tried two other ROMS - Resurrection Remix and Slim (always with a complete wipe). Still getting random reboots.
At this point I wonder if it is hardware issue.
As pointed out in other threads I have the issue of the wi-fi frequently dropping. It usually reconnects after a bit, but very frustrating.
Any thoughts or insight is appreciated.
Thank you.
Raife1 said:
Good morning all,
I wanted to get some thoughts on random rebooting and wi-fi dropouts I am having with my Samsung Galaxy Tab Pro 8.4. For some time now I have had issues with random rebooting of my tablet - often when first starting a game or other app. I mostly dealt with it, but finally got frustrated enough to really start trying some other options. My tablet has long been rooted and for a while I had some success with CyanogenMod. But then I started getting freq crashes with that. Tried rolling back to earlier and later versions (always with a complete wipe)...still got crashes. Then went back to complete stock, still crashes. Then reloaded TWRP and tried two other ROMS - Resurrection Remix and Slim (always with a complete wipe). Still getting random reboots.
At this point I wonder if it is hardware issue.
As pointed out in other threads I have the issue of the wi-fi frequently dropping. It usually reconnects after a bit, but very frustrating.
Any thoughts or insight is appreciated.
Thank you.
Click to expand...
Click to collapse
I am sorry to see that we both have exactly the same problem, and that nobody seems to have an answer :crying:
I have wiped and installed numerous times several roms, but my tablet just won't boot again ...
misery loves company...
Fortunately mine boot and usually works...but the rebooting is very frustrating...
Good luck and I'll post if I find anything out.
Follow these simple steps to go back to stock ROM : https://forum.xda-developers.com/ga...ral/firmware-stock-firmware-tab-pros-t3087238
Tablet looks to work fine.
Still have to install twrp and flash RR or LOS and see what happens...
Edit: rereading your OP and realizing you already tried that : /
Hope second shot will be the good one...
Edit 2: RR 5.7.4 working perfectly
Mine just started to do something similar. Using ResurrectionRemix 5.8.2020170401 for months with no problem. In the last few weeks, tablet would not wake up after powering down. Had to do hard reset, then would work fine for hours until next failure.
I wiped the device and reinstalled RR and Gapps, same thing happens. Wondering if there is a hardware problem sneaking up on us?
pilotbob3 said:
Mine just started to do something similar. Using ResurrectionRemix 5.8.2020170401 for months with no problem. In the last few weeks, tablet would not wake up after powering down. Had to do hard reset, then would work fine for hours until next failure.
I wiped the device and reinstalled RR and Gapps, same thing happens. Wondering if there is a hardware problem sneaking up on us?
Click to expand...
Click to collapse
I will be able to answer precisely within a few days.
In the meantime, tablet working great after reverting to stock, then falshing MM version of RR for 2 days straight...
ROM has nothing to do with hardware problem, especially the flaw in Samsung battery connector's cables, loosely contact to pins of battery connector on mainboard.
Everyone has a good technical background will clearly see what is causing reboot or shutdown:
https://forums.androidcentral.com/s...350-goes-continual-boot-loop.html#post5928150
You will see this problem in any Samsung tablet which has that battery connector: Tab A, Tab Pro, Note Pro, Tab S.....etc...
This is another example of this problem regardless different ROMs are loaded.
https://forum.xda-developers.com/galaxy-note-pro-12/help/wifi-disconnecting-battery-charge-t3664128

Categories

Resources