I seem to be having a weird behaviour with my phone lately. Once in a while, it just slows down to a crawl, and intermittently vibrates (not the quick haptic vibrations, but maybe 1 to 1.5 second long vibrations). although the phone still responds, it's really slow, and i had to do a battery pull in order to get it property working again. I didn't actually have that problem, so i can't be sure, but the symptoms may match those of a bad temp root. (phone slows down, etc). I never waited long enough to see if the phone reverts to normal after a while, and i've always just pulled the battery.
it seems to be correlated to blutooth connections. it happened once when i was turning on an app (torque) ...and today, happened again while i was exiting from torque. i've been using torque for maybe 2 months now, and everything was fine.
the symptoms also doesn't happen all the time.
anyone know what the problem is?
i have a rooted shift, stock rom, and bc's 1.8 kernel running @ 368-1401 on-demand.
it's also possible that the OBD2 blutooth adapter i'm using with torque is a cheap knock off elm327.
This is a bug with Torque and Pandora. If you uninstall Pandora or turn off the car Bluetooth in the Pandora settings it will fix it.
I use both Torque paid and a cheap knockoff adapter also.
Sent from my HTC EVO SHIFT 4G using XDA App
thanks for the response. are you able to elaborate on the bug? is it the combination of torque and pandora that triggers it? i do have pandora installed, but don't really use it.
finalhit said:
thanks for the response. are you able to elaborate on the bug? is it the combination of torque and pandora that triggers it? i do have pandora installed, but don't really use it.
Click to expand...
Click to collapse
This is from the Torque forum:
There is a good chance that you have another app or bluetooth pairing that is conflicting somehow – with quite a few EVO users (though it wasn’t limited to just the EVO), the ‘Pandora’ app was the culprit, but any app that stays active monitoring bluetooth could be the culprit.
Torque’s bluetooth code is rock solid, and it works on the Tab, so you’ll have some 3rd party app somewhere which is going crazy consuming all the available CPU power.
Click to expand...
Click to collapse
If you go into Pandora and go to Preferences then at the bottom is "Bluetooth for Automotive" turn that off and it fixes the issue. I rarely use Pandora myself and was bummed that I couldn't use both apps, until I found this workaround on the Torque forum.
Interesting. I also have my phone paired to my car...could that be an issue?
Is the fact that I've only experienced this recently inspite of 2+ mos of use, consistent with that thesis?
edit: nm. i went to the torque forums, and learned myself a thing or two. yup, definitely experiencing those symptoms. the dev was saying the newest version should have some workaround, so we'll see tommorow if it takes.
i dont need a signature
Hello!
I bought Nexus 10 at nearly two weeks, and since the beginning i have noticed an issue i thought would be Software related. As the device is on idle, everything works pretty well. Watching movies, web surfing, etc. Doesn't matter if it's for 5mins or 5 hours. But when it goes to sleep mode (automatically or forced by me), it just turns off consequently. I would say 90% of the times. An then Nexus just turn back to life after a long power button press, like 10 secs or more.
First i read about some people who have problems caused by autosleep function related with some cases. When i remove my tablet from the Poetic case, it keeps going off.
Then i read about Location services. It's turned off too. Such as the wi-fi in sleep mode. Didn't solve either.
Any idea?
PS: I'm from Portugal and my English is not the best. Sorry about that.
nando_pt said:
Hello!
I bought Nexus 10 at nearly two weeks, and since the beginning i have noticed an issue i thought would be Software related. As the device is on idle, everything works pretty well. Watching movies, web surfing, etc. Doesn't matter if it's for 5mins or 5 hours. But when it goes to sleep mode (automatically or forced by me), it just turns off consequently. I would say 90% of the times. An then Nexus just turn back to life after a long power button press, like 10 secs or more.
First i read about some people who have problems caused by autosleep function related with some cases. When i remove my tablet from the Poetic case, it keeps going off.
Then i read about Location services. It's turned off too. Such as the wi-fi in sleep mode. Didn't solve either.
Any idea?
PS: I'm from Portugal and my English is not the best. Sorry about that.
Click to expand...
Click to collapse
You can view my profile for my posts I've been working on that problem for over month. Sorry this is short reply - pressed for time right now.
bigmatty said:
You can view my profile for my posts I've been working on that problem for over month. Sorry this is short reply - pressed for time right now.
Click to expand...
Click to collapse
Thanks for the response anyway.
Is that thread about freezing? My Nexus is not freezing.
Hello! Yes, that is one of the threads Im talking about. I found it to hard to find people who posted with as good of detail as you did, so I had to "latch on" to the biggest group that was vocal about their problems. But mine manifests itsself almost always as sleep of death, and NOT reboot - just like yours. Here are some links:
Google: https://groups.google.com/a/googleproductforums.com/d/msg/mobile/-/GFnACv1nC0MJ
On of the XDA: http://forum.xda-developers.com/showthread.php?t=1998496&page=39
As I say on the Google thread:
My thoughts on the error:
1) The most logical explanation I've heard yet is the memory leak that B has been posting about
2) I think this memory leak/problem can manifest its self as crash, reboot, or sleep of death
Right now I am trying Stock 4.2.2, rooted, using KTmanta kernal. This is the second day Im on a non-stock kernal, too early to post any useful info.
Good luck on this,
bm
---------- Post added at 02:09 PM ---------- Previous post was at 02:05 PM ----------
say, quick question since you are in same boat as me - does your device's serial # start with R32C or R32D?
My device is R32D.
I guess i will call the seller tomorrow and figure out if it's possible to return the tablet. At this point, it's completely unusable.
nando_pt said:
My device is R32D.
I guess i will call the seller tomorrow and figure out if it's possible to return the tablet. At this point, it's completely unusable.
Click to expand...
Click to collapse
I agree that the inability of this device to reliably stay powered on is a deal breaker, at least in a work scenario.
I actually bought mine "just for games", but have been really concerned about trying to resolve this issue to verify its not a hardware issue and I miss my warranty period. I cant honestly say I think its a harware issue, so I am really trying to find a ROM/Kernal/settings combo that resolves this.
I have a lot of faith in the dev community for ROMs and kernels, but I think its absolutely scandalous and horrible that I have to click past a warning that says 'may void your warranty' to install softare on my device to make it perform AS IT SHOULD HAVE direct from Google.
If not for all these issues I would have NEVER gone custom recovery, root, and new kernel. Im glad this has forced me to do so because Ive loved finally having a justification for "risking" my expensive device, but again that learning experience is NOT what Google is taking $500 payments for here https://play.google.com/store/devices/details?id=nexus_10_32gb so Google should be SHAMED!
Thanks for the info on your serial number, that actually relieves a concern of mine that somehow the 'newer' units werent having this problem. Mine's a C.
bm
just bought my nexus 10 yesterday. it also turning off when sleepmode. but when i update it to 4.2.2 its gone.
jamir5 said:
just bought my nexus 10 yesterday. it also turning off when sleepmode. but when i update it to 4.2.2 its gone.
Click to expand...
Click to collapse
I hope it stays that way for you. It will take a few more days with the device to know for sure. If the problem comes back it'd be worth noting here for troubleshooting. :good:
I called back the seller, and they will do the return. Really bad situation...
i left my n10 in my house and its idle with 41% on battery i just got home and open the device it consume only 1% without random reboots. hope itll stay this way ill root this and install crom maybe nextweek.
So - now I am 2.5 days into testing 4.2.2 OS with a different kernel. And so far, NO sleep of death! AND I've been using the tablet a lot more than my "minimal use" in my other tests! This of course is the ultimate test - I'm posting/talking about it on the internet so certainly if its going to blow up in my face, now would be the time. But as of right now - it looks like the alternate kernal is better for my device than Google's...
I am using the KTmanta kernel.
It is important to note that the issue described in this thread does NOT involve the device turning itself off. Rather the issue is that the device is unresponsive when in sleep mode. You can tell this is the case in a few ways, but two obvious ones are that the notification light continues to function and the device requires a 10-second power button reset (the procedure for forcibly rebooting the device).
Personally, I am on CM10.1 night lies with Ktmanta kernel and still experiencing this problem.
Bigmatty, can you tell me what governor, i/o scheduler and clock settings you are using? Thanks.
neatchee said:
It is important to note that the issue described in this thread does NOT involve the device turning itself off. Rather the issue is that the device is unresponsive when in sleep mode. You can tell this is the case in a few ways, but two obvious ones are that the notification light continues to function and the device requires a 10-second power button reset (the procedure for forcibly rebooting the device).
Personally, I am on CM10.1 night lies with Ktmanta kernel and still experiencing this problem.
Bigmatty, can you tell me what governor, i/o scheduler and clock settings you are using? Thanks.
Click to expand...
Click to collapse
Well, the majority of the complaint threads do not specifically or mainly focus on the device turning its self off, but this thread actually does.
My sleep- of- death problem on my old unit persisted on any scheduler/clock settings I tried, and I tried a lot w/ KTmanta. But it was RMA my device to get a new one that fixed my SoD.
Oh, and the LED flashing does not mean the unit is actually on, you can test that by plugging in a charger before attempting a long (power on) press = if you get instant battery charge indicator your unit was actually off.
bigmatty said:
Well, the majority of the complaint threads do not specifically or mainly focus on the device turning its self off, but this thread actually does.
My sleep- of- death problem on my old unit persisted on any scheduler/click settings I tried, and I tried a lot w/ KTmanta. But it was RMA my device to get a new one that fixed my SoD.
Click to expand...
Click to collapse
That's REALLY weird, because based on a number of findings by a number of people, it turns out that this issue is related to a bug in the GPU driver that is causing a massive memory leak. You can check by opening a Terminal Emulator and running the command "ps su" This will show the memory usage for the "surfaceflinger" application, which is where the memory leak manifests. Memory usage should never go above ~70mb for that application, but on the N10 it balloons up above ~300mb before the system locks up.
Apparently we're all waiting on Samsung to fix the problem :\
neatchee said:
That's REALLY weird, because based on a number of findings by a number of people, it turns out that this issue is related to a bug in the GPU driver that is causing a massive memory leak. You can check by opening a Terminal Emulator and running the command "ps su" This will show the memory usage for the "surfaceflinger" application, which is where the memory leak manifests. Memory usage should never go above ~70mb for that application, but on the N10 it balloons up above ~300mb before the system locks up.
Apparently we're all waiting on Samsung to fix the problem :\
Click to expand...
Click to collapse
After my two months of trouble shooting I feel strongly that there are two main issues: memory leak and "something to do with power". Likely a software/driver/OS problem on the memory leak like the majority says. BUT - not everyone has the power problems. I think the power problems are hardware related.
Only a couple other users have talked about experiencing the power problems...
If I was going to place a bet, I'd say based on your description of symptoms you too have the power problem. Ask the others in threads you are following if they have the LED thing, I'm guessing they don't.
Rxnelson on these forms does. He's seen it on two physical units. For me, it didn't appear on my second physical unit.
Good luck!!
"LED thing?" The LED thing is just the notification light continuing to flash even when surfaceflinger has locked the system. Don't really see how that's related to power in any way. The way that LED notification lights work is that the system sends an "on" signal to the LED control chip which then just runs the notification light pattern in a loop until it receives the "off" signal from the system. If you don't have any notifications prior to surfaceflinger going ballistic, or if you have the notification light disabled (many people do) you'd never notice this particular symptom.
Also please note the tip I shared about diagnosing if it's off or on via the charger I posted above, handy trick another user taught me.
---------- Post added at 01:51 PM ---------- Previous post was at 01:48 PM ----------
neatchee said:
"LED thing?" The LED thing is just the notification light continuing to flash even when surfaceflinger has locked the system. Don't really see how that's related to power in any way. The way that LED notification lights work is that the system sends an "on" signal to the LED control chip which then just runs the notification light pattern in a loop until it receives the "off" signal from the system. If you don't have any notifications prior to surfaceflinger going ballistic, or if you have the notification light disabled (many people do) you'd never notice this particular symptom.
Click to expand...
Click to collapse
Not quite what it seems. If the unit was on, plugging in the charger would not instantly,w/out delay, display the powered off charging indicator.
Ahh, okay, bit of a miscommunication. I'm not referring the power-on notification light. I'm referring to the notification light flashing that occurs when you have a notification waiting (new email, new gTalk message, etc). The charging light is something different, and not what I was referencing
NOTE: This is a function of CyanogenMOD 10.1 that is not present in the stock ROM, I think, so that may be where the confusion lies. Sorry about that
neatchee said:
Ahh, okay, bit of a miscommunication. I'm not referring the power-on notification light. I'm referring to the notification light flashing that occurs when you have a notification waiting (new email, new gTalk message, etc). The charging light is something different, and not what I was referencing
NOTE: This is a function of CyanogenMOD 10.1 that is not present in the stock ROM, I think, so that may be where the confusion lies. Sorry about that
Click to expand...
Click to collapse
Yes dude, I understand. Just test what I am saying. When I saw my white gmail led flash, but then couldn't turn on I thought the exact same thing you typed. Then while discussing w/power users someone told me to try that. Next time it happened I tried it, was SHOCKED to see what happened, knew I had a problem (that was not just shell reboot.)
My tablet just started doing this as well. It's never done it before, it started about a week ago. What could be causing this? I just factory reset to see if it'll fix the problem. I'll report back in a few days to see if this fixes the issue.
Sent from my Nexus 10 using xda app-developers app
I'm planning on installing my Flo Nexus in my car to replace the outdated stock navigation system. I was quite interested in Timur's USB ROM but it doesn't support Flo and doesn't look like he'll be adding it after cancelling the indiegogo campaign he started to fund it.
I've spent some time searching and looking at the different kernels and roms available, and for now am running ElementalX 1.7beta with an older CM nightly.
I think this meets most of my needs, but I have one little nitpick - is there anything out there that separates the "Wake on plug" action into two separate functions? I'd like the screen to wake up when power is applied, but not when power is removed as this is going to leave the screen on when I get out of the vehicle. Ideally when power is removed I'd like it to go to deep sleep immediately.
Thanks.
I've never used the app Tasker. But isn't that what people use when trying to accomplish that?
Sent from my Nexus 7 using XDA Premium HD app
makers_mark said:
I've never used the app Tasker. But isn't that what people use when trying to accomplish that?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I've used tasker for different things, but have found it unreliable when it came to power events, at least in the past. I'll definitely give it a shot and see how it works for this scenario. Thanks for reminding me.
Any other suggestions out there in case Tasker doesn't do the trick, or other votes for Tasker?
I got an app called "Caffine" which keeps the screen on while plugged in/charging, and when I turn the car off I set the backlight to 15 seconds, that way it sleeps after 15 seconds. Works great.
If you don't mind me asking, how are you installing the tablet into your car?
Cl8rs said:
I got an app called "Caffine" which keeps the screen on while plugged in/charging, and when I turn the car off I set the backlight to 15 seconds, that way it sleeps after 15 seconds. Works great.
If you don't mind me asking, how are you installing the tablet into your car?
Click to expand...
Click to collapse
I have an '06 Acura TL with OEM Navi system. I'm having a car audio shop relocate the navi screen (as it's tied to climate functions but I don't need to see it) and they're putting the tablet in its place. The goal is to have things looking stock while be far from it.
r00ler said:
I have an '06 Acura TL with OEM Navi system. I'm having a car audio shop relocate the navi screen (as it's tied to climate functions but I don't need to see it) and they're putting the tablet in its place. The goal is to have things looking stock while be far from it.
Click to expand...
Click to collapse
How much are they charging you? Is it a common audio shop?
Cl8rs said:
How much are they charging you? Is it a common audio shop?
Click to expand...
Click to collapse
It's part of a complete stereo install I'm doing, and it's not cheap although it's not rip-off expensive either. I chose them because they are capable of doing good fabrication work and are going to need to put something together to hold the tablet securely in place behind the stock bezel.
Just wanted to update for people to know what I did. Tasker was the way to go to get exactly what I want, but I needed to add the Secure Settings plugin as well. With that plugin I was able to immediately turn on the screen when power is applied, as well as shut off the screen immediately when power is removed.
I've also attached other bits to these profiles, such as adjusting the CPU clock and disabling wifi/bluetooth when the screen is off. At this point I'm losing less than 10% battery for 24 hours of sleep, which is pretty good although I'd like to see if I can find any improvements. We'll see!
Hello, friends,
I own since August 2018 above mentioned radio from Joying. Unfortunately, I recently found out that the device resets itself to the factory settings. The whole thing happens completely by accident. It's happened twice in the last 3 weeks. My radio is rooted and I'm using the JET application, but I don't think it's related. Very briefly one sees a text, where something like that the memory had problems stands. I looks like a boot menu like in TWRP. But it's start with an normal loading popup while being in android.
Has anyone ever had a similar error? Many thanks in advance for any help.
I've found that my unit is sensitive to voltage transitions when starting my vehicle and also if the CPU gets hot.
Overheating is also a BIG factor. Use a hardware monitor app to verify the CPU is running below 70c.
If it's running hot it needs active cooling.
Hello!
I have purchased a V1 Pro 8 Core 4Gb 64Gb with 8259 processor. But it is very slow when starting, so I have activated the "Sleep Mode" option that means that when the vehicle starts the equipment is already on the launch screen (I have put agama car launcher), but I'm afraid that the battery of the vehicle will run out. The question is, does anyone of you have this option activated for a long time? Have you noticed a worrying battery consumption? Is there a risk of running out of battery by activating this option?
Thank you
JoTaSu said:
Hello!
I have purchased a V1 Pro 8 Core 4Gb 64Gb with 8259 processor. But it is very slow when starting, so I have activated the "Sleep Mode" option that means that when the vehicle starts the equipment is already on the launch screen (I have put agama car launcher), but I'm afraid that the battery of the vehicle will run out. The question is, does anyone of you have this option activated for a long time? Have you noticed a worrying battery consumption? Is there a risk of running out of battery by activating this option?
Thank you
Click to expand...
Click to collapse
Don't have trouble using sleep mode. After four days the head unit shuts down to prevent draining of the cars battery.
The sleep mode is implemented aggressively and an app preventing the heat unit from sleep will be killed.
TorstenH said:
Don't have trouble using sleep mode. After four days the head unit shuts down to prevent draining of the cars battery.
The sleep mode is implemented aggressively and an app preventing the heat unit from sleep will be killed.
Click to expand...
Click to collapse
Ok. Thanks for your answer.
TorstenH said:
Don't have trouble using sleep mode. After four days the head unit shuts down to prevent draining of the cars battery.
The sleep mode is implemented aggressively and an app preventing the heat unit from sleep will be killed.
Click to expand...
Click to collapse
Should that be the same for a V1 2Gb 32Gb model? Or is there any difference?
Unfortunately, the forum crystal ball doesnt know what you unit is and from the hundreds of made up models and brands, the seller could be selling units of different types, from different factories, despite branding with the same model name.
There are are a small number of active members in these forums, you want to be posting in a way that helps those people help you, they're likely tired of answering the same questions for new users that join, get the answer (often unanswered) and then leave.
Post screenshots from Android system information, including the MCU version when posting questions. Doing this will at least help others help you, or you might find the information has already been posted or discussed here, yourself.