Guys
2 quirks
1) sometimes when entering my PIN on voicemail, the screen just blanks out - it doesn't happen every time but probably 1 out of 3 times. I tested dialing 611 and entering digits and it never happens
2) Flipping screens on widgets or apps, sometimes it doesn't move to the next screen. I have to make sure my finger goes all the way to the right of the screen to flip it to the next page. Not sure if this has anything to do with the XO skin protector I put on but don't recollect this problem started right after I installed the protector
Any of you guys seen this?
What version of ICS you have on your phone, custom rom etc..? Also GSM or Verizon?
I notice sometimes the screen goes off when talking on phone, and it doesn't come back on when I move it away from my face (like it's supposed to right?).
Also I just tested flipping pages in the browsing all apps/widgets, and I only have to slide my finger as little as a half inch, to flip pages. However if you do this slowly it will not flip pages, so it depends on the speed to slide and let go of the screen. This is also true for the launcher, flipping screens. So not sure why this would be happening to you?? I also have a screen protector as well (cheap dry application one $1.99 from ebay)
Try turning off the screen next time if happens and then back on and see if it goes back to normal behavior...? Does the phone accurately follow your finger completely? If not it might be some hardware issue with the touchscreen. If it doesn't then I would definitely remove your screen protector and test for the issue.
is there an app i can use to test if the screen is following my finger properly?
verizon and using stock os (rooted it of course)
sam008 said:
is there an app i can use to test if the screen is following my finger properly?
Click to expand...
Click to collapse
It's built in, just go to settings, developer options, show touches (check this)
It will show a small circle following where your finger is touching.
Also there is an even better setting above that called "show pointer location" Which will draw a line showing where you have been touching the screen.
Working fine
sam008 said:
Working fine
Click to expand...
Click to collapse
Strange, is this something new to ICS 4.0.3? Can anyone else confirm? I've only used 4.0.2 and 4.0.1.
If its following your finger accurately the only thing that would make sense to me is the ROM or kernel/drivers...??
i'm on 4.0.2 with verizon - there aren't any other updates available when i check
sam008 said:
i'm on 4.0.2 with verizon - there aren't any other updates available when i check
Click to expand...
Click to collapse
Ah for some reason I thought 4.0.3 was already pushed out to Verizon Galaxy Nexus phones, turns out that is not the case... ignore what I said earlier about it being associated with 4.0.2 I guess..
If you really want to get this fixed one suggestion would be to back up your phone (nandroid and/or titanium backup), and do a factory reset... if the page flipping issue goes away then you can at least isolate it the issue a little better...
I'm curious to see exactly the extent of the page/screen flipping issue you have, if you have the means, and have some time to blow, make a youtube video of the issue in action and maybe it will be a little clearer to see whats happening...
Okay this has bugged the heck out of me for ages, maybe someone knows the answer to it.
The top notification bar (and sometimes the row underneath in certain apps) sometimes is completely unpressable, as if it's being blocked. I should note this happens on my Note 7, but has also occurred on my Note 3, my old S2 and even the S7. Which makes me think it must be a setting I choose, or an app I install.
Sometimes, I'll turn on my phone, go past the lock screen and I won't be able to drag the notification bar down. I found a workaround (which has worked on all my old phones).
- Turn the phone off
- Turn it back on
- On the lock screen try to drag the notification bar down (which doesn't do anything)
- Unlock the phone
- Then it works again!!
My mrs had this too, and my workaround fixed it.
This issue has spanned over multiple versions of Android and is now doing my head in.
Any ideas?
Some app overlay is on top of it such as: Flux, blue light filter, and things like that. Once disable the issue is gone. That might be your issue.
jonboyuk said:
Okay this has bugged the heck out of me for ages, maybe someone knows the answer to it.
The top notification bar (and sometimes the row underneath in certain apps) sometimes is completely unpressable, as if it's being blocked. I should note this happens on my Note 7, but has also occurred on my Note 3, my old S2 and even the S7. Which makes me think it must be a setting I choose, or an app I install.
Sometimes, I'll turn on my phone, go past the lock screen and I won't be able to drag the notification bar down. I found a workaround (which has worked on all my old phones).
- Turn the phone off
- Turn it back on
- On the lock screen try to drag the notification bar down (which doesn't do anything)
- Unlock the phone
- Then it works again!!
My mrs had this too, and my workaround fixed it.
This issue has spanned over multiple versions of Android and is now doing my head in.
Any ideas?
Click to expand...
Click to collapse
I would place a 90% bet on this being a carried over app problem. Have you tried a fresh reset and reproduced the problem?
Have you also tried the service test for Touch ans S Pen? *#0*#
Kansatsusha said:
Some app overlay is on top of it such as: Flux, blue light filter, and things like that. Once disable the issue is gone. That might be your issue.
Click to expand...
Click to collapse
I thought as much. I used to have Twilight installed but I deleted it and it hasn't solved my issue!
alltaken123 said:
I would place a 90% bet on this being a carried over app problem. Have you tried a fresh reset and reproduced the problem?
Have you also tried the service test for Touch ans S Pen? *#0*#
Click to expand...
Click to collapse
I think so too. One example I have an issue with is the offscreen memo function. I pull the stylus out and can write on the screen off, but the row of buttons along the top NEVER work! But, I should say on a hard reset it was fine until all the apps were installed and logged into, or a setting was put in place. The service test for S Pen and Touch works perfectly. All I can think is trying to install 1 app at a time, and seeing what happens as a result. Will be painful with 100+ apps though. I'm about to replace my N7 on the recall too so I want to hold off on a hard reset too.
I feel your pain, if it were me I would rather discover the erroneous app now than later. Perhaps a backup via smartswitch on PC (very fast over USB 3) and when you know which app restore the backup and delete the app accordingly?
alltaken123 said:
I feel your pain, if it were me I would rather discover the erroneous app now than later. Perhaps a backup via smartswitch on PC (very fast over USB 3) and when you know which app restore the backup and delete the app accordingly?
Click to expand...
Click to collapse
By pure luck. I found it. 3 years of pain and I nailed the bugger! Something you said triggered a thought process.
It was....
Cerberus security! An app that automatically hides itself from the draw once it's installed so usually never crossed my mind.
Disabling the "Block Status bar" feature in Cerberus fixed it.
PHEW!!!!!!!!!!! Thanks for this (both of you).
good for you!
I emailed Joying again yesterday to ask about UL128N2, and they responded by adding the unit to their webpages and accepting orders.
Canada website (Canadian $):
http://www.joying.ca/best-joying-ne...t-pip-sleep-model-bluetooth-4-0-dab-obd2.html
Global website (US $):
https://www.carjoying.com/new-andro...h-4-0-gps-navigation-professional-head-u.html
and the website is down. As usual.
If the website isn't down, it's their forum. Sigh.
morgish said:
and the website is down. As usual.
If the website isn't down, it's their forum. Sigh.
Click to expand...
Click to collapse
Well its back up now. Or at least its working for me.
Sometimes international routing through the great firewall can be a bit.... spotty.
Has anyone bought already?
Is it better than the ones with bezel and volume knob?
KamaL said:
Has anyone bought already?
Is it better than the ones with bezel and volume knob?
Click to expand...
Click to collapse
My two units arrived. Played with one of them on the kitchen table late last night.
The row of capacitive buttons are thoroughly pointless -- touches to them don't register at all if your finger doesn't touch it absolutely perfectly.
Having said that, I like them better than the one with the knobs, for the reason I've already mentioned to you -- the lack of deep bezels.
Better? It is definitely a matter of preference. I don't need the capacitive button row, so that doesn't bother me at all.
Note: they have this weird dot thing stuck in the UI as configured by default. Touching the dot brings up a set of buttons -- back, home, menu, etc. So.... CHINA. Obviously, unless you have AT LEAST three copies (SystemUI header bar, row of buttons, the weird dot thing, steering wheel controls) of every button, somebody is going to miss it. Fortunately, there is a control application in the application menu that allows you to disable the stupid dot.
doitright said:
My two units arrived. Played with one of them on the kitchen table late last night.
Click to expand...
Click to collapse
I am sitting on the fence with this purchase, any-chance you could do a video review with these units?
doitright said:
My two units arrived. Played with one of them on the kitchen table late last night.
The row of capacitive buttons are thoroughly pointless -- touches to them don't register at all if your finger doesn't touch it absolutely perfectly.
Having said that, I like them better than the one with the knobs, for the reason I've already mentioned to you -- the lack of deep bezels.
Better? It is definitely a matter of preference. I don't need the capacitive button row, so that doesn't bother me at all.
Note: they have this weird dot thing stuck in the UI as configured by default. Touching the dot brings up a set of buttons -- back, home, menu, etc. So.... CHINA. Obviously, unless you have AT LEAST three copies (SystemUI header bar, row of buttons, the weird dot thing, steering wheel controls) of every button, somebody is going to miss it. Fortunately, there is a control application in the application menu that allows you to disable the stupid dot.
Click to expand...
Click to collapse
That dot was terrible. I also disabled it immediately, thankfully they gave an easy option to turn it off, unlike many of the other things that are obfuscated(such as disclosing to owners the hardware keycombo to boot into recovery).
Upon receiving my unit the capacitive buttons weren't always responding even when pressed perfectly, but after holding down RST till reboot they haven't had the issue again.
When inquiring about a larger touch area for the capacitive buttons I got "Hi friend, Nice day Yes, you can choose the bigger or small touch area in below settings:" with this picture attached.
Increasing the delta values in Settings of the Key Study app doesn't seem to do a whole lot but I think the trigger area is a bit bigger. Unfortunately the border values are for the entire touch screen not per button area.
tally3tally said:
I am sitting on the fence with this purchase, any-chance you could do a video review with these units?
Click to expand...
Click to collapse
No. I don't do video.
rcll said:
That dot was terrible. I also disabled it immediately, thankfully they gave an easy option to turn it off, unlike many of the other things that are obfuscated(such as disclosing to owners the hardware keycombo to boot into recovery).
Upon receiving my unit the capacitive buttons weren't always responding even when pressed perfectly, but after holding down RST till reboot they haven't had the issue again.
When inquiring about a larger touch area for the capacitive buttons I got "Hi friend, Nice day Yes, you can choose the bigger or small touch area in below settings:" with this picture attached.
Increasing the delta values in Settings of the Key Study app doesn't seem to do a whole lot but I think the trigger area is a bit bigger. Unfortunately the border values are for the entire touch screen not per button area.
Click to expand...
Click to collapse
That one looks like the buttons (and their corresponding areas) are considerably larger than with the 7". They are surprisingly small on this! I might see if I can disable them altogether, since I suspect that it would likely interfere with "slide finger in from left" gestures.
Ok, so got the thing installed last night.
Well, sortof.
Seems that China can't make up its mind regarding how far the front of the radio sticks forward relative to the mounting holes. So my first attempt to mount it resulted in the radio's face sticking so far forward that my DDIN face plate wouldn't have been able to make it down to the dashboard.... assuming that the holes fit. More on that later.
Second attempt, I moved the radio back to the next set of holes on the mounting bracket, which are a bit more than 1/2" behind the holes that I had the UL135 mounted with. Ok, well depth is *better*, but now a bit too far back. Middle of the night, so as long as I can use the thing to route my way to work in the morning, I'm ok with that. Maybe on the weekend, I'll drill another set of holes about half way between the two sets I tried so far. That should line it up OK.
So the DDIN sizing. Another thing that China can't make up its mind on. The UL135 fit in the Toyota Tacoma Metra dash kit... very snugly in horizontal direction, roughly 1mm clearance in the vertical direction. This UL128N2 is about 2-3 mm too big to fit in that dash kit in BOTH directions. They *claimed* the UL135 to be 100mm x 178mm. They *claim* the UL128N2 to be 102mm x 178mm. I will tell you that the UL128N2 is WIDER than the UL135, despite the claimed equal width. And given the 2mm (actually more) increase in height and that I had at least 1mm of available vertical space, I *should* have been able to force it in. NOPE. The difference is much greater than that, and in both directions. If the UL135 really is 100mm x 178mm, then the UL128N2 is probably 104mm x 180mm. WHY? Oh, the reason is absolutely HILARIOUS, it is because they have a thin plastic ring around the glass digitizer. They ordered the GLASS to have dimensions matching the DDIN target, but didn't compensate for the thin (~1mm) plastic ring around it! Very typical of the way that China manufacturing works. Ok, so I was able to grab a file and open up the dash kit a little bit to make it fit, and now its ok.
So next up... actual functionality.
First observation; the AM radio frequency standard is set to something that is most decidedly NOT North American standard. The closest frequency I could get to my preferred station was off by 2 kHz. While it was adequate to get the station and understand, without TYPICALLY an overabundance of noise or added sound from the next station over, it definitely sounds bad. Thanks so much China, for giving me a well working AM radio tuner! With any luck, I'll be able to hack the program to tune the proper frequencies.
On the physical utility of the unit, when you look past the "size" issue, its not bad. As expected, the screen is much more convenient without the deep bezel around it as the UL135 had. In order to achieve this, they replaced the physical control buttons with a row of capacitive buttons. Those buttons are pretty well useless, you can't reliably press them without focusing carefully on them. That is what is often called "distracted driving". I would go so far as to say that this row of buttons is DANGEROUS to try to use. Not only that, but the row of buttons is ***COMPLETELY REDUNDANT***. After all, they are just duplicates of the home/back/volume buttons that are already present on the SystemUI upper panel anyway, and, of course, the STEERING WHEEL BUTTONS (for those who have them hooked up). Why did they even bother to include that row of buttons? Because.... CHINA! Oh well.
Next up; there are some serious bugs when it comes to AUDIO ROUTING. If the radio is playing, and GPS voice comes on; radio mutes. Oh, it STAYS muted until you go BACK into the radio application, which seems to trigger a reset of the audio routing. This improved once I set google maps as the default nav application, now it just volumes down the radio to "pretend" to play the GPS sounds, and volumes it back up after.
Well, starting with the "included" ancient version of google maps... while it does make sound, it gets clipped by about 3 seconds at the start of the sound. So you miss about the first 3 seconds of the instruction. Update google maps to the latest version, and no sound comes out at all. Ok, what is happening with the newer one is that it is trying to use an audio pathway that is obviously BROKEN on these units. So that means that there isn't going to be any voice nav from google maps until either (a) THEY fix the audio routing problems, or (b) WE fix the audio routing problems. I'm not sure yet if there is an audio routing policy file that we can configure, or if this is something hard baked in somewhere. That's very annoying, but something I can live with for now. I prefer the newer google maps enough to live with the lack of voice guidance, rather than to try to use the ancient version.
DPI: Obviously, Android believes that the screen is as large as a TELEVISION. The fonts are all incredibly small, even if you set it to HUGE font. Ok, so right angle triangle has H = root(1024*1024+600*600)=1186.83 pseudopixels. Divide that by 7, makes 170 DPI. Its set to 160 DPI, so Android thinks that the screen is 7.4 inches. Ok, that's not really too far off from reality, but it IS in the wrong direction, to make everything look SMALLER than it should be. The problem is that the screen is roughly 3 feet away from your face. Take a tablet and how far do you hold it away? Roughly 1.5 foot. So lets figure out how big Android should *THINK* the screen is, in order to blow things up to the same scale as a 7" tablet at 1.5 foot.
We're dealing with right triangles again, 7:3 = x:1.5, x = 3.5. Android should think that the screen is 3.5 inches. That puts it up at 338 DPI. Ok, so these numbers are pretty rough, since I'm just guessing the viewing distances, but you get the idea. Crank that DPI WAAAAAAAY UP! Only problem I see, however, is regarding how they coded the SystemUI. If they followed the Android design guidelines, then they coded it with DP's (density independent pixels), which means that when you crank the DPI far enough to make applications look proper, it will make the CHINA look HUGE. Think about it -- they designed their SystemUI panels to show at a "normal" size when the DPI is set way too low. I can see bad things happening.
I wonder if it would be practical to just SWAP OUT the chinese SystemUI for one built from source? That might actually be a practical way of repairing the UI. Might also be nice to rebuild the System Settings application from source. I'll have to go over it again, but I don't recall there being anything special about System Settings -- they just colorized it, broke the bluetooth part, and added a password to developer options. WHY???!?!
Like the American proverb says... "if it ain't broke, don't fix it!" That ESPECIALLY goes for China, since if it ain't broke, they're GOING to break it.
And now, to BLUETOOTH.
Well, knew going into it that they futzed up the bluetooth settings as badly as they possibly could. Why? Because... CHINA. The good news is that they tried so hard to break it as badly as they could, that it was EASY to fix.
In fact, I had written up the most important fix WELL before I even had these head units. I will refer to my fix thread HERE: http://forum.xda-developers.com/and...elopment/bluetooth-settings-launcher-t3504526
There are two obvious problems with bluetooth on these units;
1) They deleted the System Settings button that brought up the Bluetooth settings. That is what I fixed in above thread.
2) They BROKE the bluetooth pairing pin prompt. On a normal Android device, when you try to pair with something from it, it will first try one or two "standard" pairing pins, and they don't work, then it will pop up a dialog requesting that you enter the device's pin. This one does NOT do that. It JUST tries to pair using whatever pin is hardcoded in the CHINESE bluetooth application. So while I haven't "fixed" this, there is at least a reasonably easy (if not particularly convenient) workaround. When it doesn't pair, you go into the chinese bluetooth application, change the pin there, and try again.
So the good news is this; the REAL MEAT of the bluetooth stack, is the product of INTEL. Not China. That means that once you work around the severely broken UI (again, WHY BREAK it when you can just leave it be and have it ACTUALLY WORK?), it actually works WONDERFULLY! That means you can connect to AND USE multiple devices at the same time. I.e., torque + **ANY** OBD device, while simultaneously a voice call AND bluetooth data tethering.
Hmm, what else....
Bootup.... this is a very dramatic change from the UL135.
A full bootup takes about 20 seconds.
So when you get into your car in the morning to go to work, after it has been sitting all day, you turn the key, and it is IMMEDIATELY UP. Wait, what? Its wired correctly -- if the +12 and IGN were reversed, then it would lose power with the ignition switch off, which means that it would have to do a full bootup. If the IGN wasn't connected at all, then the screen will never turn on -- when the IGN turns off, the screen goes off, radio stops playing, and another thing I observe, is that bluetooth connections are lost. So, either the thing is only doing a partial shutdown and proceeding to "drain the battery" mode, or they have actually made it sleep *correctly*, switch off all the parts that suck down the power, put the CPU into deep sleep (clock off), and sit there draining negligible power until it receives a wakeup interrupt (IGN line powers up). If that is so, then I am VERY pleased, at least with this element.
On performance and stability;
Its better than the UL135 across the board here. This thing is no rocket, the CPU is actually quite a TURD, though definitely better than RK3188 (despite lower benchmarks). The increased RAM helps with keeping things in memory and responsive. The stability is a night and day improvement over the UL135, which I believe to be attributable to the INTEL element. eMMC performance is abysmal.
Summary so far;
1) The front panel is bigger than DDIN.
2) The front panel sticks out a different amount than UL135.
3) The audio routing policy is BORKED.
4) The UI is ALL CHINA.
5) The Bluetooth stack is INTEL
6) Performance is "OK". Nothing special.
7) Wakeup after sitting all night is INSTANTANEOUS.
More on the GMaps audio routing.
While I haven't yet tried out the latest system update, I HAVE found a way to make GMaps actually speak.
Unfortunately, the "way" is by being on a PHONE CALL.
Yep. When you're on a PHONE call, google maps is HAPPY to speak to you. In fact, the damned thing will NEVER SHUT UP. Obviously. When better to harass you then when you're trying to listen to someone else? Or when you're trying to speak, since it shuts off the microphone in order not to echo back the nav prompts.
(fortunately, there is a setting to tell it not to issue nav sounds during call).
Oh yeah, gmaps also speaks LOUDER than the phone call.
EDIT: people on the joying forum are indicating that the newest update will fix the gmaps voice.
Ok, on to the December 8th UPDATE.
First off, I have NOT really run the update yet. Supposedly, it fixes the GMaps sound problem.
I can confirm that they have NOT (yet) caught on to Blueballs.apk that I wrote (and shared) to regain access to the System Settings --> Bluetooth activity, so bluetooth functionality has not been degraded.
First the install process;
Take their install archive and EXTRACT it to a uSD or USB disk. Either is fine. I used USB.
msdos type partition table, ONE partition, formatted as fat32.
Power on the vehicle, stick in the card or USB, and wait until it prompts you to install the update.
Now is where things get scary....
Starts by updating the MCU, fine, then proceeds to update the Android image. The progress bar moves about a 3rd of the way across, and STOPS. And it just sits there. For about 10 minutes. The only indication that the device isn't completely crashed out is that the little websphere thing is still spinning in the little robot's hands. Ok, eventually it goes, then it says to yank out the disk and it will reboot itself. OK, no problem.
You do it. And it reboots. It plays the boot animation, right up to the last frame... and stops. It just sits there saying "ANDROID" across the screen. Now you're thinking to yourself that THIS THING IS JAMMED UP AND YET WE HAVE NO WAY TO GET INTO RECOVERY!!!!! Crap. Ok, lets just let it be. It sits, and it sits, and about 15 minutes later, the panel lights go out. Ok, at least something changed. Wait another minute and it finally boots. So WHAT THE BLOODY HELL CHINA? Obviously, it must have been optimizing application number 27 of 258, so WHY DID YOU DELETE THE PROGRESS DIALOG, CHINA? WHY?????
So it boots back up, and you notice something funny right off the bat. It has returned to the china launcher. Ok, that's minor. Keep on moving, we can reset it to google launcher momentarily. So now you go into something like k9mail, and it asks you to sign in.
HUH?
But the program remained installed.
THE BLOODY MORONS..... THEY DELETED EVERYTHING FROM /data/data/. They kept /data/app/, but they deleted /data/data/. So everything you've set up now has to be reset. GEE, THANKS SO BLOODY MUCH, CHINA.
So my suggestion... if you're going to update to the Dec8 system image, the sooner you do it, the less of your settings you will lose, because the less of your settings you will have actually SET.
Quick observations;
1) They have NOT fixed the frequency selection on the AM radio. I'm still stuck 2 kHz away from my target frequency.
2) There were THREE phases to the system install; MCU, Android, and "Allapp.pkg".
3) Allapp.pkg contains Settings.apk. Yet there was a Settings.apk in the Android update. Hmmmmm..... wonder if we could just force back the REAL Settings.apk and have a proper functioning system?
4) Allapp.pkg *also* has a SystemUI.apk. Could it be? Could the one in the Android update actually be... no, it couldn't. There's no way that they would actually *include* an AOSP SystemUI, is there?
This is the list of all of the apk files in Allapp.pkg:
Code:
EasyConnectedFY07.apk
assets/CarMan.apk
assets/CarManNotChinese.apk
assets/EasyConnServer.apk
Gmail2.apk
JY-1-C9-BT-V1.0.apk
JY-1-C9-Guide-V1.0.apk
JY-1-C9-Launcher-V1.0.apk
JY-1-C9-MUSIC-V1.0.apk
JY-1-C9-Radio-V1.0.apk
JY-1-C9-Video-V1.0.apk
JY-2-C9-Launcher-V1.0.apk
Maps.apk
PlatformServerSofia.apk
Settings.apk
SFY-1-C9-Steer-V1.0.apk
Sofia-1-C9-Aux-V1.0.apk
sofia-1-C9-CarMark-V1.0.apk
Sofia-1-C9-FileManager-V1.0.apk
Sofia-1-C9-Gallery-V1.0.apk
Sofia-1-C9-RightCamera-V1.0.apk
Sofia-1-C9-Server-V1.0.apk
Sofia-1-C9-TV-V1.0.apk
SystemUI.apk
SYU-1-5009-FloatBtn-V1.0.apk
SYU-1-C9-Calculator-V1.0.apk
SYU-1-C9-Caliration-V1.0.apk
SYU-1-C9-Canbus-V1.0.apk
SYU-1-C9-CarRadio-V1.0.apk
SYU-1-C9-CarUi-V1.0.apk
SYU-1-C9-Graphics-V1.0.apk
SYU-1-C9-Navi-V1.0.apk
SYU-1-C9-SubServer-V1.0.apk
SYU-1-C9-UIServer-V1.0.apk
SYU-1-C9-Update-V1.0.apk
SYU-1-C9-Widget-V1.0.apk
SYU-2-C9-CMSettings-V1.0.apk
SYU-2-C9-EQ-V1.0.apk
Notice... CarMan.apk and CarManNotChinese.apk, LOL.
Oh, and "SYU-1-C9-Caliration-V1.0.apk" is also pretty cool.... ***CALIRATION***
doitright said:
My two units arrived. Played with one of them on the kitchen table late last night.
The row of capacitive buttons are thoroughly pointless -- touches to them don't register at all if your finger doesn't touch it absolutely perfectly.
Having said that, I like them better than the one with the knobs, for the reason I've already mentioned to you -- the lack of deep bezels.
Better? It is definitely a matter of preference. I don't need the capacitive button row, so that doesn't bother me at all.
Note: they have this weird dot thing stuck in the UI as configured by default. Touching the dot brings up a set of buttons -- back, home, menu, etc. So.... CHINA. Obviously, unless you have AT LEAST three copies (SystemUI header bar, row of buttons, the weird dot thing, steering wheel controls) of every button, somebody is going to miss it. Fortunately, there is a control application in the application menu that allows you to disable the stupid dot.
Click to expand...
Click to collapse
I have the 10" version and I got the buttons to work 100% after relearning the touch keys. Open "carmediasettings" then click on Panel keys assignment. Hope that helps =)
xlinkx said:
I have the 10" version and I got the buttons to work 100% after relearning the touch keys. Open "carmediasettings" then click on Panel keys assignment. Hope that helps =)
Click to expand...
Click to collapse
The issue on the 7" isn't the button calibration, just the physical size of the touch areas.
Doesn't matter anyway, since the buttons are all available in other places -- systemui bar and steering wheel.
So today installed the second UL128N2 into the wife's Subaru Forester.
Popped out a parrot asteroid smart (obsolete). The dimensions of the parrot are about a full quarter of an inch in both horizontal and vertical directions. Really had to do a job on the ddin dash adapter on that one, but fortunately was able to avoid having to cut up the actual dashboard.
doitright said:
Summary so far;
1) The front panel is bigger than DDIN.
2) The front panel sticks out a different amount than UL135.
3) The audio routing policy is BORKED.
4) The UI is ALL CHINA.
5) The Bluetooth stack is INTEL
6) Performance is "OK". Nothing special.
7) Wakeup after sitting all night is INSTANTANEOUS.
Click to expand...
Click to collapse
Any news on the instantaneous wake up after a full night? No car battery issues after several nights? I would be very interested in measurements of power consumption when the car is switched off.
Regarding the small font settings, would you suggest to buy the 8" unit if it fits in the car? I guess that the UL138N2 has the same hardware as the UL128N2 only with an 8" screen? And I hope that it has also the instantaneous wake up?
Sent from my SM-N910F using XDA-Developers mobile app
nomailing said:
Any news on the instantaneous wake up after a full night? No car battery issues after several nights? I would be very interested in measurements of power consumption when the car is switched off.
Regarding the small font settings, would you suggest to buy the 8" unit if it fits in the car? I guess that the UL138N2 has the same hardware as the UL128N2 only with an 8" screen? And I hope that it has also the instantaneous wake up?
Sent from my SM-N910F using XDA-Developers mobile app
Click to expand...
Click to collapse
No, I wouldn't suggest that. I would just suggest changing the DPI setting on the 7" to something more suitable.
The UL138N2 WILL NOT fit in a DDIN dash adapter. Its basically a DDIN *box*, with a TABLET bolted out in front of it. Unless your car is an ugly beater, you probably won't want to install something that ugly into it.
As far as overnight power consumption, I have not had any opportunity to test more than a 24 hour stretch. No issues, nor, frankly, do I expect any. They appear to be sleeping the unit correctly, so all of the wireless signals are turned off, and CPU is in clock stopped mode, so like a good quality tablet with the wifi turned off, it'll go for months like that. On a battery as big as a car has, possibly years (assuming that the car battery didn't self discharge in that time, which it will).
doitright,
With your help I was able to get full system menu. Thank you! I was wondering if you were able to get "Ok Google" to work on any screen. It only works on the home screen for my 10" head unit.
xlinkx said:
doitright,
With your help I was able to get full system menu. Thank you! I was wondering if you were able to get "Ok Google" to work on any screen. It only works on the home screen for my 10" head unit.
Click to expand...
Click to collapse
I have no interest in retard mode, so no. I have not.
doitright said:
DPI: Obviously, Android believes that the screen is as large as a TELEVISION. The fonts are all incredibly small, even if you set it to HUGE font. Ok, so right angle triangle has H = root(1024*1024+600*600)=1186.83 pseudopixels. Divide that by 7, makes 170 DPI. Its set to 160 DPI, so Android thinks that the screen is 7.4 inches. Ok, that's not really too far off from reality, but it IS in the wrong direction, to make everything look SMALLER than it should be. The problem is that the screen is roughly 3 feet away from your face. Take a tablet and how far do you hold it away? Roughly 1.5 foot. So lets figure out how big Android should *THINK* the screen is, in order to blow things up to the same scale as a 7" tablet at 1.5 foot.
We're dealing with right triangles again, 7:3 = x:1.5, x = 3.5. Android should think that the screen is 3.5 inches. That puts it up at 338 DPI. Ok, so these numbers are pretty rough, since I'm just guessing the viewing distances, but you get the idea. Crank that DPI WAAAAAAAY UP! Only problem I see, however, is regarding how they coded the SystemUI. If they followed the Android design guidelines, then they coded it with DP's (density independent pixels), which means that when you crank the DPI far enough to make applications look proper, it will make the CHINA look HUGE. Think about it -- they designed their SystemUI panels to show at a "normal" size when the DPI is set way too low. I can see bad things happening.
Click to expand...
Click to collapse
I tried some changes to the dpi in build.prop. I went up to 180 and the ui looks alright still. Then I decided what the heck and went to 300 since my galaxy s5 is at 480...bad idea. The screen gets stuck on the kill apps screen and you can't open anything. Luckily I was able to open es file explorer using adb and edit the build.prop. After rebooting, all os well again.
Moral of the story, don't try anything over...maybe 200?
The Pixel Stand is not working as designed. When I place it on the stand and set it up to do photo frame/slideshow, nothing happens. It just sits on an ambient screen and doesn't even move around that ambient screen to avoid screen burn-in.
I spent a good amount of time on a remote session with Google with doing various cache/data cleans and removing updates and things like that and nothing is resolving it.
I also had a problem completing setup with my Google Home Hub and I am wondering if perhaps this is a Google Assistant issue. The Google Home app kept prompting me to complete the step to Enable VoiceMatch and it would just go into a perpetual PLEASE WAIT. I had to grab another non-pixel 3 phone to complete that setup in the Google Home app.
It charges but does nothing else as it should.
Anyone else encounter this?
I just received my Pixel Stand as well. During setup I set it to turn on the Always On Display when on the stand. However, like you, I'm noticing that it just sits there with the same screen, just dimmed. I'm afraid of premature screen burn in because of this.
So, I tried turning 'Always On Display' while on the Pixel Stand off but that option is nowhere in settings. Under Settings > Display > Ambient Display, it's turned off but still stays on when on the stand. So it has to be a second setting somewhere else. I just can't find it and I've dug through everything. Until I can figure this out I'm hesitant to even use the Pixel Stand.
sn0warmy said:
I just received my Pixel Stand as well. During setup I set it to turn on the Always On Display when on the stand. However, like you, I'm noticing that it just sits there with the same screen, just dimmed. I'm afraid of premature screen burn in because of this.
So, I tried turning 'Always On Display' while on the Pixel Stand off but that option is nowhere in settings. Under Settings > Display > Ambient Display, it's turned off but still stays on when on the stand. So it has to be a second setting somewhere else. I just can't find it and I've dug through everything. Until I can figure this out I'm hesitant to even use the Pixel Stand.
Click to expand...
Click to collapse
This for sure isn't the fix but I did a factory reset and this time when I set up the stand, I got a new prompt that I didn't see the first time...it was about Google Assistant...completed the setup and bam, it works. Even the ambient display dims better. So, as I kind of suspected, it was a Google Assistant issue.
for the record, you can find the settings at: settings > connected devices > previously connected devices > then tap the cog next to 'pixel stand'
Yikes. I really don't want to factory reset. My setup screens all worked perfectly fine. It's just that during the setup, when it asked me to enable Always On Display while the phone is on the stand, I said 'Yes'. Now I can't turn it off. If I have to factory reset to fix that I'm going to be quite annoyed.
sn0warmy said:
Yikes. I really don't want to factory reset. My setup screens all worked perfectly fine. It's just that during the setup, when it asked me to enable Always On Display while the phone is on the stand, I said 'Yes'. Now I can't turn it off. If I have to factory reset to fix that I'm going to be quite annoyed.
Click to expand...
Click to collapse
see my above reply, then simply forget the stand, and re-add it again with the settings you desire.
uicnren said:
see my above reply, then simply forget the stand, and re-add it again with the settings you desire.
Click to expand...
Click to collapse
I'm not sure how I missed your comment but that did the trick. Thanks!
uicnren said:
see my above reply, then simply forget the stand, and re-add it again with the settings you desire.
Click to expand...
Click to collapse
Cant wait to try this when I get home. My google photos only show about 50% of the time. I was trying to show my wife the "awesome" pixel stand and it didnt work lol hope this fixes my isssue.
vwgti18 said:
Cant wait to try this when I get home. My google photos only show about 50% of the time. I was trying to show my wife the "awesome" pixel stand and it didnt work lol hope this fixes my isssue.
Click to expand...
Click to collapse
My photos only showed up once = and then never again and I couldn't figure out how to get them to show again. Will try Forgetting in Connected Devices as recommended above - shouldn't have to jump thru hoops to make an 80 dollar charging stand do it's tricks
Geekser said:
My photos only showed up once = and then never again and I couldn't figure out how to get them to show again. Will try Forgetting in Connected Devices as recommended above - shouldn't have to jump thru hoops to make an 80 dollar charging stand do it's tricks
Click to expand...
Click to collapse
I found that forgetting and adding back didn't resolve this...a full factory reset was my only fix...something wonky going on with their software. Hope it gets updated soon.
garak0410 said:
I found that forgetting and adding back didn't resolve this...a full factory reset was my only fix...something wonky going on with their software. Hope it gets updated soon.
Click to expand...
Click to collapse
Me too - watching my photos while the phone is charging is not worth a reset to me - but it might be enough to make me want to return the damn charger - 80 bucks and this is what we get? Damn!
Geekser said:
My photos only showed up once = and then never again and I couldn't figure out how to get them to show again. Will try Forgetting in Connected Devices as recommended above - shouldn't have to jump thru hoops to make an 80 dollar charging stand do it's tricks
Click to expand...
Click to collapse
Geekser said:
Me too - watching my photos while the phone is charging is not worth a reset to me - but it might be enough to make me want to return the damn charger - 80 bucks and this is what we get? Damn!
Click to expand...
Click to collapse
I've thought a lot about the stands...beyond the slide show, I really don't want "always on" all the time...and there is no way to turn it off unless room is dark. So it truly may not be an $80 value, though most OEM wireless chargers are pricey. I just prefer the OEM accessories. I'd still be on a Note 9 if the camera wasn't such a letdown.
Not very happy with my $80 wireless charging stand so far, so hoping that future software updates will fix: 1) Photo frame only working in a lit room, 2) Time not moving around screen (like clock screensaver) and notifications not appearing unless I double tap to view regular lock screen. Fingers crossed...
ogarlen said:
Not very happy with my $80 wireless charging stand so far, so hoping that future software updates will fix: 1) Photo frame only working in a lit room, 2) Time not moving around screen (like clock screensaver) and notifications not appearing unless I double tap to view regular lock screen. Fingers crossed...
Click to expand...
Click to collapse
Agreed...the only notifications that appear over the slideshow or ambient screen is text messages. Nothing else pops up.
Guess I'm trying to understand the concern with screen burn-in though. The dim stand mode is not much different than the typical always on display screen, so how could it make the phone more susceptible to burn-in?
ogarlen said:
Guess I'm trying to understand the concern with screen burn-in though. The dim stand mode is not much different than the typical always on display screen, so how could it make the phone more susceptible to burn-in?
Click to expand...
Click to collapse
strange, the pixel stand puts the clock and notifications in one place and doesnt move them around.
is there a way to make the clock move around the screen?
shouldnt the clock be moving instead of always in the middle?
---------- Post added at 01:09 AM ---------- Previous post was at 01:04 AM ----------
garak0410 said:
I found that forgetting and adding back didn't resolve this...a full factory reset was my only fix...something wonky going on with their software. Hope it gets updated soon.
Click to expand...
Click to collapse
did the clock start moving around afterwards?
i cant get the clock to move around teh screen even after a fact reset.
The only workaround I've found for now is to turn on the standard clock screensaver from settings, which is a moving dim clock, however it cancels the extra functionality of the stand app.
ogarlen said:
The only workaround I've found for now is to turn on the standard clock screensaver from settings, which is a moving dim clock, however it cancels the extra functionality of the stand app.
Click to expand...
Click to collapse
so everytime we dock we'd have to start it manually?
abit counter intuitive, seems like this was rushed without much of it thought through
I dont know if anyone else is really REALLY let down by the amount of continual problems with regard to the Pixel 3?? I mean wow, there are all kinds of problems again with this phone??? I have had the og Pixel, Pixel 2, and the Pixel 3 and each phone has had more than its share of problems. I have noticed that the "Pixel" excitement has calmed down a lot too probably because of these problems. I had a Galaxy S9 before this Pixel 3 and NEVER had any issues with it at all. I mean this is "Google" shouldn't we expect more?? Or has everyone just come to expect problems and the usual answers of "fix incoming", "thats not a bug its a feature", and my favorite "were looking into this" LOL!!!!!!!!!!!!!!!
beginning to miss my op6 right about now haha
just forget the pixel stand and don't go through the set up and it keeps the display off while charging.
other than that this phone is great,I do notice it's a littleslower than my op6 sometimes (opening apps sometimes instant sometimes not, maybe an EAS feature) but I think that's because my op6 had a kernel installed from the get go.
Been using the phone for the last 12 hours and I noticed something towards the end of my use last night.
The screen seemed to become unresponsive. And when it would work it would start to make its own input when scrolling and opening any app or link my finger would drag over while scrolling.
Changed refresh rates, changed resolutions, even seen if the blue light filter was the issue. Nothing.
Almost seems like the screen drops frames when scrolling, like it gets caught on something.
New development. Fingerprint sensor doesn't respond at all and inputting a pattern is damn near impossible. Going to try removing the screen protector to see if that could also be the issue
Did a factory reset
Issue seems to be where the finger print scanner is
It's almost like a dead or unresponsive zone.
Sounds like a factory defect, better have it replaced if resetting didn't worked.
Small video showing when scrolling over the fingerprint reader, the screen almost loses input
Defect.
Samsung has been little help lol. They want me to send it in for repair instead of an exchange. They also said to just order a whole new one and return the one I have now except the black 128 is sold out
imtjnotu said:
Samsung has been little help lol. They want me to send it in for repair instead of an exchange. They also said to just order a whole new one and return the one I have now except the black 128 is sold out
Click to expand...
Click to collapse
Sounds like Samsung support LOL...sorry you're having issues
Did you remove the factory installed screen protector? Maybe it's the cause of the issue
Return that pal, that doesn't sound good at all.
lovers74 said:
Did you remove the factory installed screen protector? Maybe it's the cause of the issue
Click to expand...
Click to collapse
one of the first things i did to trouble shoot. still having the issue. sometimes the screen completely loses all touch registration and it doesnt even know im trying to swipe or push on things. just realized it did this also after tmobiles new software update.
im still waiting here to hear back from samsung on how they are going to fix this issue
The same thing happens to me. Pulling down the notification shade seems to be the only thing that still works. It seems to goose the phone and it starts working again.
Test using the *#0*# diagnostic menu and use the Touch test.