Related
Hi everyone.
Does anyone faced a problem with Real Racing 3 ? Brakes (tap on the left part of display) sometimes doesn't respond. I have to tap twice or even triple to brake. Acceleration seems to be working good. From another side I don't need to tap it so frequently as brakes.
At this moment I didn;t notice anything like that in any other app.
My ROM is JSS15R + ROOT
LOCKDOC_UA said:
Hi everyone.
Does anyone faced a problem with Real Racing 3 ? Brakes (tap on the left part of display) sometimes doesn't respond. I have to tap twice or even triple to brake. Acceleration seems to be working good. From another side I don't need to tap it so frequently as brakes.
At this moment I didn;t notice anything like that in any other app.
My ROM is JSS15R + ROOT
Click to expand...
Click to collapse
Yes mate, I've experienced this with RR3 and CSR Racing but only a handful of times.
I cant quite narrow it down, but i believe that when you are tapping very quickly, maybe a couple of times a second in the same area, this seems to then stop the touch from working for a second or two in that area, perhaps the whole screen but I've not really played around with it.
Again i get the same issues with CSR as you need to feather the throttle just before launch for the best RPM range.
That's the only niggle I've had since buying the Nexus 7.
ddelamareuk said:
Yes mate, I've experienced this with RR3 and CSR Racing but only a handful of times.
I cant quite narrow it down, but i believe that when you are tapping very quickly, maybe a couple of times a second in the same area, this seems to then stop the touch from working for a second or two in that area, perhaps the whole screen but I've not really played around with it.
Again i get the same issues with CSR as you need to feather the throttle just before launch for the best RPM range.
That's the only niggle I've had since buying the Nexus 7.
Click to expand...
Click to collapse
Do you think it is game optimization issue or touch screen issue? I'm crossing my fingers it's optimization... and will be fixed soon. Otherwise I;ll be quite disappointed ((
Presently I've stopped playing RR3 as it's nearly impossible ((
LOCKDOC_UA said:
Do you think it is game optimization issue or touch screen issue? I'm crossing my fingers it's optimization... and will be fixed soon. Otherwise I;ll be quite disappointed ((
Presently I've stopped playing RR3 as it's nearly impossible ((
Click to expand...
Click to collapse
I wouldnt surprised be surprised if there are still a few screen issues considering the update they pushed out to fix the initial issues but for me, I'm not really being affected. At least in games I just need to hit the corners a little faster so I'm not hitting the brake like ABS
For the most part, gaming wise, I think there are issues with certain games picking up the new nexus as a different device from the original. Hence why RR3 has a terrib resolution. Apart from that, everything looks and works great.
As a side note, if you haven't yet, install Ultimate Rotation Control (free) from the Play Store. Open it and set the mode to Auto Forced. Go back to your desktop, hold your nexus in portrait mode like a book and open RR3. When you see the EA blue logo, turn it into landscape and that should improve how RR3 looks. Should help in the short term
How can we solve it
Just got this tablet yesterday. A big part of my usage will be playing clash of clans (just too addicting). So, when I got home with the Tab last night I played a couple hours of CoC, running stock.
First thing I noticed, the screen is in fact beautiful. Even on the lower brightness settings the colors pop which is amazing.
But... I started to notice touch sensitivity issues in CoC almost immediately. In the game you have to click little buildings to select them / collect resources and such. I noticed that the screen seemed to not be registering some of my clicks. In the most extreme case I'd have to touch a building 2-3 times before it would actually register. Has anyone else had this issue? I've got a couple theories:
1) The screen may be registering my clicks as little tiny swipes instead of presses. Is there any way to adjust the sensitivity on this?
2) Screen may be defective (seems worse on the left side, but could be my imagination)
3) This is just a CoC issue / compatability with the Tab S
Clear Data,Cache and retry maybe it's just a lag?did you face any heating problem?
I recommend you to 'tick' show touches option in Developers Options!
echoboomer said:
Just got this tablet yesterday. A big part of my usage will be playing clash of clans (just too addicting). So, when I got home with the Tab last night I played a couple hours of CoC, running stock.
First thing I noticed, the screen is in fact beautiful. Even on the lower brightness settings the colors pop which is amazing.
But... I started to notice touch sensitivity issues in CoC almost immediately. In the game you have to click little buildings to select them / collect resources and such. I noticed that the screen seemed to not be registering some of my clicks. In the most extreme case I'd have to touch a building 2-3 times before it would actually register. Has anyone else had this issue? I've got a couple theories:
1) The screen may be registering my clicks as little tiny swipes instead of presses. Is there any way to adjust the sensitivity on this?
2) Screen may be defective (seems worse on the left side, but could be my imagination)
3) This is just a CoC issue / compatability with the Tab S
Click to expand...
Click to collapse
I play clash of clans. This is happening because you are lagging. Just close all other apps before playing. Its all smooth for me
DUHAsianSKILLZ said:
I play clash of clans. This is happening because you are lagging. Just close all other apps before playing. Its all smooth for me
Click to expand...
Click to collapse
Hmm, still happening tonight. I did a fresh reboot and made sure only CoC was running in the task manager. Still had the issue with missed clicks, maybe about 1 in every 8.
enable the deiveloper options (google if you don't know how, it is easy and required to be able to playdeus ex the fall for reasons)
Under developer options there are 2 options under input enable both of them. That will give you a graphical representation of your touches and swipes.
While we are in settings check device/display for touch sensitivity and try checking or unchecking the box to see if that helps you out.
one last thing if you are comming from a smaller screen device you may not have have noticed but touch screens are not pixel perfect in the best of worlds. And on a smaller screen with less pixels it tends to be easier to hit the area you want. Check to see if you are not hitting somethine else by a building by placing walls surrounding a building like a mine or a pump then touch to collect.
This is happening for me also, and it is really annoying. Clash of Clans is the main thing I use the tablet for.
I tried enabling the developer options like was suggested, and it is still happening. Even with the graphical touch and swipe showing where I tapped on something, Clash of Clans is apparently ignoring the action.
Use stylus
It works better if you use a stylus. I have the same problem but I have not yet found the ideal solution. Therefor most of the time, I keep on using my Motorola Xoom to play with CoC.
echoboomer said:
Just got this tablet yesterday. A big part of my usage will be playing clash of clans (just too addicting). So, when I got home with the Tab last night I played a couple hours of CoC, running stock.
First thing I noticed, the screen is in fact beautiful. Even on the lower brightness settings the colors pop which is amazing.
But... I started to notice touch sensitivity issues in CoC almost immediately. In the game you have to click little buildings to select them / collect resources and such. I noticed that the screen seemed to not be registering some of my clicks. In the most extreme case I'd have to touch a building 2-3 times before it would actually register. Has anyone else had this issue? I've got a couple theories:
1) The screen may be registering my clicks as little tiny swipes instead of presses. Is there any way to adjust the sensitivity on this?
2) Screen may be defective (seems worse on the left side, but could be my imagination)
3) This is just a CoC issue / compatability with the Tab S
Click to expand...
Click to collapse
I bet you guys using marshmallow os wright ? I have this problem too.. i suspect thr os isnt compatible to coc, or the coc isnt compatible to marshmallow. We need some fixes from both.
echoboomer said:
Just got this tablet yesterday. A big part of my usage will be playing clash of clans (just too addicting). So, when I got home with the Tab last night I played a couple hours of CoC, running stock.
First thing I noticed, the screen is in fact beautiful. Even on the lower brightness settings the colors pop which is amazing.
But... I started to notice touch sensitivity issues in CoC almost immediately. In the game you have to click little buildings to select them / collect resources and such. I noticed that the screen seemed to not be registering some of my clicks. In the most extreme case I'd have to touch a building 2-3 times before it would actually register. Has anyone else had this issue? I've got a couple theories:
1) The screen may be registering my clicks as little tiny swipes instead of presses. Is there any way to adjust the sensitivity on this?
2) Screen may be defective (seems worse on the left side, but could be my imagination)
3) This is just a CoC issue / compatability with the Tab S
Click to expand...
Click to collapse
I have a Samsung Tab 3 and recently the touch screen has gone haywire. I drop a troop at 12oc and heal spell drops randomly at 6oc or wherever. I click on the screen and the screen zooms in and out irradictly . Trying to do a raid must less a war attack is impossible. Anyone have the same issues? Can't play at all atm. Really frustrating
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?
Hi there,
So I finally got my beautiful panda Pixel 2 XL and I absolutely love it, except for one thing - touch latency or sensitivity.
UPDATE
If you're having similar issues, be sure to "+1" the following thread on Google forum and also comment: https://productforums.google.com/forum/#!topic/phone-by-google/3XDqX3LgpvQ;context-place=topicsearchin/phone-by-google/category$3Agoogle-pixel-2%7Csort:relevance%7Cspell:false
I took off the glass screen protector and I'm now using it naked. I feel some improvement BUT this is still far from perfect. I was expecting such phone coming straight from Google to blow me away in terms of touch latency and such, but for now it feels like my Oneplus 3 is actually more responsive. Super strange.
I'm not entirely sure what's going on, but basically I feel like I'm having a hard time registering a touch on the first try TOO OFTEN. Sometimes I would even try to scroll up or down a web page and it wouldn't register for a few tries.
Things to note I'm NOT using the screen naked, I'm rocking an AmFilm tempered glass screen protector, it's a dot matrix kind of screen protector, one that doesn't actually stick to the screen entirely, only at the edges. Could this be the issue?
Is anyone else having similar issues with or without a screen protector?
Again, other than that, the device is perfect. Also very minimal blue shift that doesn't bother me at all.
Thanks for your help
How is the sensitivity with the screen protector off?
Sent from my [device_name] using XDA-Developers Legacy app
Patch7 said:
How is the sensitivity with the screen protector off?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I know it's silly, but I don't want to take off the screen protector because I got it aligned perfectly and the only replacement I have is a different type - a tpu film.
The thing is, I didn't even have a chance to try out the phone without a protector since this was the first thing I did when I unboxed it :/
Was mainly wondering if anyone else is having touch screen issues with a tempered glass screen protector of any kind?
UPDATE I took off the glass screen protector and I'm now using it naked. I feel some improvement BUT this is still far from perfect. I was expecting such phone coming straight from Google to blow me away in terms of touch latency and such, but for now it feels like my Oneplus 3 is actually more responsive. Super strange.
You on latest 8.1?
I notice some touch sensitivity issues in the far edges of the screen. I'm not using any screen protection at the moment.
galaxys said:
You on latest 8.1?
Click to expand...
Click to collapse
Yep, I'm on the stable 8.1 all stock not rooted or anything.
This is mostly apparent when scrolling, I would sometimes scroll down and the page would move downward and sideways altogether, as if it is registered as a swipe to the side with a scroll down. Same when scrolling up. Very annoying.
nimrodiny said:
Yep, I'm on the stable 8.1 all stock not rooted or anything.
This is mostly apparent when scrolling, I would sometimes scroll down and the page would move downward and sideways altogether, as if it is registered as a swipe to the side with a scroll down. Same when scrolling up. Very annoying.
Click to expand...
Click to collapse
What's your Animation Scale set to in Developer settings? I changed mine to .5x and noticed improvements in scrolling & response...
galaxys said:
What's your Animation Scale set to in Developer settings? I changed mine to .5x and noticed improvements in scrolling & response...
Click to expand...
Click to collapse
Yeah, definitely. I'm already on 0.5 scale unfortunately so this can't be it. Thanks for your help anyways! Appreciate it
Same problem after the 8.1 update answering a call is so hard. even unlocking my phone with a swipe up is very difficult. Swiping away notification takes 3 tries. I'm actually regretting the 128gb with google protect! So much money with so many problems. I came from a GS7 edge and it was way better performance wise then this phone. Feels like I'm just a beta tester for google. Seems like every update fixes one thing and breaks 4 more.
mikepopo99 said:
Same problem after the 8.1 update answering a call is so hard. even unlocking my phone with a swipe up is very difficult. Swiping away notification takes 3 tries. I'm actually regretting the 128gb with google protect! So much money with so many problems. I came from a GS7 edge and it was way better performance wise then this phone. Feels like I'm just a beta tester for google. Seems like every update fixes one thing and breaks 4 more.
Click to expand...
Click to collapse
Agreed. I actually miss my Oneplus 3 in terms of performance and fluidity. I can't type or browse with this phone without having weird glitches. Sometimes the tap wouldn't register, sometimes it's the scrolling acting up.. Very annoying as I said
I'm having similar issues. Randomly my phone decides I touched somewhere in the middle of the screen I didn't at all, or when scrolling down a list eg. YouTube or Twitter, it suddenly jumps me back to the top as if I swiped down at super human speed.
More over the most consistent issues I'm having is tapping on the edge. Eg. The elipsis (3 vertical dots) when looking at 'my channel' or a playlist such as my attached screenshot. I cannot touch the elipsis at all even with a stylist.
My device is Google Pixel 2 XL, 8.1.0, build OPM 1.171019.011
P.S I'm using the phone 'naked', no case, no screen protector.
Damn. Looks like we've got an actual issue here.
For me it is most consistent when I'm scrolling up or down a list that can also go sideways, like Instagram Stories stickers for example, or an email on Gmail where you can swipe left to get to the next message. It will randomly go right/left when I'm actually swiping up/down.
It also happens to me, sometimes, while scrolling up or down, 5 or 6 times successively, it doesn't recognizes one of the touches.
nimrodiny said:
Damn. Looks like we've got an actual issue here.
For me it is most consistent when I'm scrolling up or down a list that can also go sideways, like Instagram Stories stickers for example, or an email on Gmail where you can swipe left to get to the next message. It will randomly go right/left when I'm actually swiping up/down.
Click to expand...
Click to collapse
Nimrodiny, would you mind trying to go on the YouTube app, and either on your 'my channel' list or a playlist try to tap on the ellipse?
It's completely impossible for me, every time either nothing happens or it decides I touched the video itself to play it. I'd like to know if my issue is not unique.
Addendum: I tried viewing this page in desktop view mode in Chrome and zoomed in. I was able to scroll up and down over and over without any side scrolling happening at least.
I have noticed sometimes it freezes when loadng a web page thought it was chrome but updated to the beta.
Same effect, something is off with the touch sensitivity but not always.
Dav_Edward said:
Nimrodiny, would you mind trying to go on the YouTube app, and either on your 'my channel' list or a playlist try to tap on the ellipse?
It's completely impossible for me, every time either nothing happens or it decides I touched the video itself to play it. I'd like to know if my issue is not unique.
Addendum: I tried viewing this page in desktop view mode in Chrome and zoomed in. I was able to scroll up and down over and over without any side scrolling happening at least.
Click to expand...
Click to collapse
Yep. I can definitely tap on the ellipse on YouTube via my channel.
BTW, just made a scrolling comparison - same website, same browser, on my Pixel 2 XL vs the OP3 and... The OP3 absolutely killed it. It was way smoother and never stuttered while the Pixel had tons of stutters and misreading of my swipes
Thanks for testing Nimrodiny. In that case I best go back to the store and exchange my phone, as edge tapping is definitely broken for me.
Ya. Happens to me.. not acurate touch.. try touching that 3 dots on YouTube app on full screen ( where u change resolution of youtube play back)
Ufff fed up with this.. display, speaker, touch.. how many more
I came from OnePlus 3 n got panda pixel 2 xl. I faced some touch sensitive issue while typing n sometimes browsing. M using my pixel with iq shield screen protector film. I did a factory reset it did helped with swipe issues to some extent. Also I disabled vibration n sound for touch and feel bit better while typing. Mostly while typing I had hard time pressing space bar , most of the time I had to press twice to register a space. lts like phone is unable to keep up with my typing speed(m not that fast though). It doesn't feel like using a flagship phone . I would say touch is good but definitely not great.
Other than that I face no display issues like screen burn in or weird sound issues . Ya blue tint is there but it's part of the display not an issue.
I would suggest try factory reset once n disable sound and vibration on touch and see if it does help some how.
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.