I've looked at all the the settings under Factory Settings on my Joying PX/5 unit and can't find where the setting for length of time before sleep actually is. Saw a couple Youtube videos, but my unit doesn't have the Sleep Time delay option they show. All I'd like to do is set Sleep time for an hour or so and not have the unit boot for 30-40 seconds every time I leave the car for 5 minutes.
What am I missing here?
Which PX5? That makes a big difference
A model ending on PX5S or another PX5?
Not sure, how do I find out?
To make things worse it started actin up today, periodically shutting down, not restarting and not responding to Reset. A few times it cam up in calibration mode and did not respond to screen touch. A few times it was blank and flashing the screen and blank again after ignition. One thing after another with this unit...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
nile13mx5 said:
Not sure, how do I find out?
Click to expand...
Click to collapse
Well, you ordered it, didn't you?
So what model did you order?
But looking at the images being it a Android 8.1 on a PX5, it is almost sure a QD model ending on PX5??, where ?? is some 1 or 2-character extension.
These models only know cold boot. No 1,2,3 hours sleep delay before being switched off either.
All the other Joying models are FYT models. They always go into deep-sleep and can stay there for 25-30 days without draining your battery, but will switch off after 5-7 days just to make sure.
They always wake up within 1-3 seconds within those "deep sleep" period.
The unit came with the car I've purchased. Not sure where else to look for a model number other than the screens I've posted. Is there another place?
So, I should't hope for a boot faster than 30-40 seconds after every ignition off? It seems to vary, sometimes a little faster, sometimes a little slower, but about that long, which is pretty inconvenient. That is, if the damn unit ever works (I have my doubts after its behavior today). I've been pretty frustrated by how buggy it's been and now it seems to exhibit a hardware failure if my instincts are right. Time for something else?
Related
I have the chance to compare my 10.1v with an Ipad 1 so here is the first picture (both devices with medium brightness).
It'll be a work in progress. Tomorrow I'll have more time and I'll post a full review, with images and videos.
I'll post videos here.
Looking forward to seeing the review. I'm more interested in the 10.1 but the screen quality definitely interests me here.
i guess samsung tab should vs ipad 2
I don't have an Ipad 2, just the first one.
I returned my 10.1v, it became a brick.
myself11 said:
I don't have an Ipad 2, just the first one.
I returned my 10.1v, it became a brick.
Click to expand...
Click to collapse
What happened ?
As a stated on another thread, I played around for half an hour. Due to a lot of forced closes on browser, decided to turn off the device. It froze on "Do you want to shut down?".
Pressed a couple of times the power button and the first screen "Samsung GALAXY Tab 10.1v" appeared, but it never passed from there.
Tryed power + vol down and entered unlock mode with no problems. Pressed the power button to get out and restart, but same issue ocurred. The only way to turn it off is power + volume up and down for 10 secs.
I think even charging was affected, because when I plugged it, the symbol of a battery appeared, but nothing happened afterward.
myself11 said:
I think even charging was affected, because when I plugged it, the symbol of a battery appeared, but nothing happened afterward.
Click to expand...
Click to collapse
Sounds to me like....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
early adopters penalty!
Are you getting it replaced? I'm sure it was just a dodgy unit. I've not heard of anyone else with that issue - the only issue that I know of is the light-bleed issue for which Vodafone AU have been replacing them.
I know of 2 Tabs here in Portugal whose screen, after 4 days of normal use, started malfunctioning. An error like mine, I never heard of it, not even in another tabs' fora.
I got a refund. Imagine if it happened again... The store might say I've been messing with something or trying to install custom Rom (there isn't any, I know eheh). My unit had bleeding too, I think they all have.
I've seen this somewhat similar issue posted a few times but just wondering how many other people are experiencing it. My Nexus 7 just randomly died with the battery plummeting.
I had an issue with my first Nexus 7 (2013) unit that arrived DOA. Holding the power button does nothing but flash the LED. Today, I got home and it did the same thing with my new unit despite having worked for the past 2 weeks. I read some posts here that suggested to plug it in and hold the power button for 30+ seconds. I did that and it seemed to do the trick after letting it charge a while. When I checked the battery history, I saw this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm running stock Android, stock kernel, stock everything.
Why would it do this? The battery instantly died at that one exact moment...
chug said:
Why would it do this? The battery instantly died at that one exact moment...
Click to expand...
Click to collapse
Left completely alone long enough, the battery level doesn't update accordingly, this is somewhat an issue on the N4 as well. I think what you're seeing here is that the battery level, pre crash, is lying to you, although this looks like a very extreme case. Just a guess with the info at hand.
You might be right. I'll try doing a factory reset to clear out the battery stats maybe... (I consciously chose not to root this device)
chug said:
You might be right. I'll try doing a factory reset to clear out the battery stats maybe... (I consciously chose not to root this device)
Click to expand...
Click to collapse
I wouldn't bother, it does get better with time, at least in the case of the N4. It was a HUGE annoyance for me when I first got the phone, over time the issue became less obvious. The battery stats only contain your per charge usage, so that won't "fix" it.
Please take a look at this picture. This is "pointer location" option in Developer Options. The red line is an arch I made with a single stroke, but as you see it is broken in two places. There is a part on the screen where it happens at the entire width of display. It is not constant, but happens many, many times a day. I also get screen freezes, and ghost touches which run apps, make random phone calls, etc.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Malarz said:
Please take a look at this picture. This is "pointer location" option in Developer Options. The red line is an arch I made with a single stroke, but as you see it is broken in two places. There is a part on the screen where it happens at the entire width of display. It is not constant, but happens many, many times a day. I also get screen freezes, and ghost touches which run apps, make random phone calls, etc.
Click to expand...
Click to collapse
I think this is a known symptom of degradation for the Nexus 4. Two of my friends already had this problem and nothing but a replacement screen could fix their problems. As I did research for them I came across many people who suffered from the same issues.
I have the same problem , it'a just about a month that is happening and it doesn't recognize the right part of the screen
Here I have the same problem, about 1 month ago started to have some touch parts dead, but it has been worsening, now its almost useless.
I too had the same problem. I had to change the screen. It cost about £30 from ebay for a new one. On the replacement I noticed that the version number of the screen was higher and also the manufacturing date was a few months younger than the broken original. Also the digitizer lines look different when light shines on them. Perhaps they realized that there was an issue with some of the earlier models.
Surprisingly the issue lessened for me. It is not gone completely, but for the last 5-6 days it does not happen as often as it used to, now maybe only once a day. A week ago I started using _only_ the original charger. I had read somewhere that a faulty battery or charger may be causing erratic screen. Not sure if the change of charger has anything to do with it, or if that's just a fluke.
Hi All,
not sure if this is normal (dont think so) but i have annoying battery drain and dont know what i can do to fix it.
My screen on time is around the 2hr 30 mins mark before i will need to recharge - ive seen people getting 6 hours some how??
ive uninstalled all useless apps, wiped cache and all the normal things but still not worked (even location services off)
I just had a look today on WakeLockDectector and it appears it has something to do with the google app?
Does anyone know a solution to this battery drain? - cell mobile radio seems to keep my phone awake??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You're not the only one. I'm struggling with it since I bought this bloody phone. Had even exchanged battery.
Facing the same problems as you do. Perhaps our models are broken somehow?
It's hard to say...
Anyway, no clue what's going on.
Same problem just started. Was doing great after factory reset but along the way it's slipped
xmatharux said:
Hi All,
not sure if this is normal (dont think so) but i have annoying battery drain and dont know what i can do to fix it.
My screen on time is around the 2hr 30 mins mark before i will need to recharge - ive seen people getting 6 hours some how??
ive uninstalled all useless apps, wiped cache and all the normal things but still not worked (even location services off)
I just had a look today on WakeLockDectector and it appears it has something to do with the google app?
Does anyone know a solution to this battery drain? - cell mobile radio seems to keep my phone awake??
Click to expand...
Click to collapse
mine does vary alot.lowest was 1.5hr and max was 5hr.
i guess the problem is with marshmallow.hopefully it will be fixed with next update
Hi everyone
I have a no-brand unit directly purchased in China. It is a Sofia 3GR, 2GB ram, Android 6.0.1.
It is more or less the same as the Joying unit, for what I saw on this forums.
One day I factory-reset the unit, and the sleep function is gone. I then tried updating the ROM to a Joying ROM (2018-01-10 Android 6.0.1), but still the sleep function is gone.
I tried clean install by wiping all data in the internal storage.
The sleep function is not there even when no other apps are installed (just the stock/system apps), neither not rooted nor rooted.
The unit will shut down after 5-10 seconds when I turned off the ignition. Before I factory reset the unit at the first time, it can stay at sleep for around 2-4 days.
What could I do to make it back? Any suggestions would be appreciated. Thank you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my iPad using Tapatalk
One of the first options in the Settings is whether the unit needs to switch off, or go to sleep mode. Did you check that?
surfer63 said:
One of the first options in the Settings is whether the unit needs to switch off, or go to sleep mode. Did you check that?
Click to expand...
Click to collapse
Yes go to sleep mode is on
Sent from my iPhone using Tapatalk
Actually it is not JOYING unit
SummerLiu said:
Actually it is not JOYING unit
Click to expand...
Click to collapse
I know it is NOT. For what I saw on this forums, all Joying problems/solutions can be applied to my unit. So I just said it is a no-brand but more or less a Joying.
And I guess Joying and my unit are made by the same factory. It is usual in China that many shops are actually selling the same products (with their own brand name) made by the same factory.
And it looks like Joying is one of the popular units here. That’s why I tried to ask if anyone had this problem before on his/her Joying or “no-brand but Joying like” unit. And I hope the same solution can be applied to my unit, or at least I am open to try.
Sent from my iPad using Tapatalk