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?
Related
I installed the Android OS on my phone that was found on this post:
http://forum.xda-developers.com/showpost.php?p=5480057&postcount=7353
I updated it and everything to what he has but occasionally my hard buttons at the bottom will either stay lit or not respond at all. Or it will even go crazy as if I were sitting there spinning my finger around the middle hard button thus making it highlight everything on my menu. That also causes trouble because then it thinks that when I press the home key it decides to bring up the call log screen.
Is there anyway to disable the "iPod Scroll" on the center hard key?
Dude. You should update to the newest build. And update Rootfs and zImages.
everything is in the XDAndroid thread in this forum.
I updated to the one found here:
http://forum.ppcgeeks.com/showthread.php?t=104276
And my scroll wheel and hard buttons still mess up from time to time.
What device do you have? RAPH100?
Sorry I don't know the developer names but its the HTC Fuze for AT&T so it's either the RAPH100 or just the RAPH. The start up config I'm using for Droid is the RAPH config.
Its best not to touch the capacitive DPAD and scroller during boot up. (safe time is when you can see a n d r o i d or the bootscreen.) This and having the pad clean is very crucial if you don't want it going crazy.
Try cleaning it with a wet cloth/tissue and try again.
I also had a screen protector which was massively scratched which caused problems. Ever since removing it the DPAD has been working great.
dude i totally have the same problem.
i ve tried wipe it clean but no luck.
sometimes everything work great but all of a sudden the buttons go wild and start flashing. after that, nothing will bring it back to normal. maybe after a few minutes if will stop blinking, lefting one or two LEDs on, and the button is then less responsive, though still works if you place your finger on the button you want for a few seconds before pressing.
I've seen a few people complaining about this but other says its because of our own device...
However everything works normally in WM... so i guess it might be about the sensitivity or something like that.
no matter it get fixed or not, I do want a method to disable the scrolling too, and maybe the left and right buttons, because they never work even under WM...
Yeah, mine does that too. Its random, sometimes not happening for days, then all of the sudden it starts. And this is within the same boot. Very odd. BTW, I keep up on all builds, always update asap, and my pad is spotless. I can't really figure it out.
also getting the exact same problem a lot, with everything up to date, clean, and not touching on bootup. would it be difficult to implement a code where we could just disable the middle scroll wheel? thats the thing that causes the most problems, and its not really that useful anyway.
@reverendkjr
This may be off topic but, you say you leave your phone running Droid all the time? How do you not drain your battery in like 4 hours unless you leave it charging all day?
But I'm pretty sure I'm as up to date as I can be and I still get this issue.
twiggy159 said:
@reverendkjr
This may be off topic but, you say you leave your phone running Droid all the time? How do you not drain your battery in like 4 hours unless you leave it charging all day?
But I'm pretty sure I'm as up to date as I can be and I still get this issue.
Click to expand...
Click to collapse
Its not off topic at all. I have been using Xandroid as my one and only OS for about a month now. I do charge it quite often, and I leave it on my desk at work on a charger. I also charge it at night as I sleep. I start off the day with 100% and can go 6 or so hours without issue. I continuously get 3-4 days in a row without a reboot or a failure. I find that it has become a suitable alternative to Winmo. The difficulty that I have is that there are primary functions which I miss a bit (camera mostly). But I feel that in order for me to fully understand and appreciate this, and to be able to contribute as a quasi beta tester, I must be willing to spend as much time with it as possible. I keep up with these forums on a regular basis , checking them sometimes 2-3 times a day. It is difficult to distinguish helpful info sometimes, since there are several versions floating around, and not everyone has the same setup & environment. I search as much as I can to find my own solutions, and for the most part, I'm relatively proud of myself. I usually only chime in when something is really bugging me, or I see something valuable that I can add to a conversation.
This issue was one that I had seen a few people talk about, and it had always been chalked up to being a dirty sensor type of thing, or someone touching the pad while it was booting. Having tried all of these solutions with no success, I had come to the determination that it was not constant, it could be ignored or dealt with, and eventually someone would fix it. It is most definitely not a "hot" item, so I never made a stink about it. Now that others have brought it forward, I decided to add my experiences.
I have loads of respect for the developers, and realize that they are not doing this for me. They are doing it for themselves, and fortunately, they share it with us. I am envious of their ability to make this project possible, and have no expectation or demands. I just take what they give us, and try to make it work for me.
Just my two sense, I'll step away from the pulpit now.
+1 for Navigation Wheel or capacitive D-pad issue
reverendkjr said:
Yeah, mine does that too. Its random, sometimes not happening for days, then all of the sudden it starts. And this is within the same boot. Very odd. BTW, I keep up on all builds, always update asap, and my pad is spotless. I can't really figure it out.
Click to expand...
Click to collapse
May I appeal to the developers to move Raph110 Navigation wheel to "Not working" so further development can occur. I do not touch the wheel during boot, but it still randomly flips out. My screen is clean. I did the clean cloth thing. The Navigation wheel not only flips out going all over the place. It actually rarely works the way it should in any application.
All I really need is to turn it off or disable the Navigation wheel if at all possible. Is it necessary to load the Nav-wheel capacitive drivers or can we disable them? Would it disrupt the function of the D-pad if disabled because all I need is the D-pad.
Chime in RAPH110 guys. Would you care if the Nav-wheel was disabled, because I actually think this is what is causing the issue.
I just want to make sure that I communicate to any developers that this is not a major issue. To me, I feel as though this is the only issue that I have at all. With the build I use, I honestly have no other issue which means that the Raph110 Android end product is 99% complete. To be direct, Thank you! I feel as though you purchased me a new phone, so this is no way a complaint. It is only the last 1% quality assurance analysis. ;-)
Edit: I just re-read this thread and the common denominator is HTC Fuze or RAPH110 users are having this minor issue. RAPH100 posting are saying "Just read the thread" or "use updated packages" or "clean the screen" which I think may all work and be valid for you RAPH100 users. I can indeed say without a doubt that this does not work for RAPH110.
In order for me to stop the random D-pad/Nav-wheel random scrolling, I have to screen lock it, let it go to sleep, then it might stop. It does stop mind you, but it is quite random how I am able to stop it.
spideyngo said:
May I appeal to the developers to move Raph110 Navigation wheel to "Not working" so further development can occur. I do not touch the wheel during boot, but it still randomly flips out. My screen is clean. I did the clean cloth thing. The Navigation wheel not only flips out going all over the place. It actually rarely works the way it should in any application.
All I really need is to turn it off or disable the Navigation wheel if at all possible. Is it necessary to load the Nav-wheel capacitive drivers or can we disable them? Would it disrupt the function of the D-pad if disabled because all I need is the D-pad.
Chime in RAPH110 guys. Would you care if the Nav-wheel was disabled, because I actually think this is what is causing the issue.
I just want to make sure that I communicate to any developers that this is not a major issue. To me, I feel as though this is the only issue that I have at all. With the build I use, I honestly have no other issue which means that the Raph110 Android end product is 99% complete. To be direct, Thank you! I feel as though you purchased me a new phone, so this is no way a complaint. It is only the last 1% quality assurance analysis. ;-)
Edit: I just re-read this thread and the common denominator is HTC Fuze or RAPH110 users are having this minor issue. RAPH100 posting are saying "Just read the thread" or "use updated packages" or "clean the screen" which I think may all work and be valid for you RAPH100 users. I can indeed say without a doubt that this does not work for RAPH110.
In order for me to stop the random D-pad/Nav-wheel random scrolling, I have to screen lock it, let it go to sleep, then it might stop. It does stop mind you, but it is quite random how I am able to stop it.
Click to expand...
Click to collapse
I think mine is a RAPH100... i cant take out the battery and double check... but mine is a unbranded version fron 3 australia... which i remember is raph100. and i totally have the same issue so this is not only happening on raph110 i believe.
Hey guys,
I was having the same problem in wm6.5 using many different energyroms, i disabled the scrollwheel altogether within the registry, never used it anyway. I am now getting the same problem in Android. is there is a registry parallel in android?
btw using a RAPH100 (all above fixes did not work)
devs, is there no easy way to implement a disable scroll wheel setting?? i swear that wheel will drive me crazy at times
While this could be an issue with all Raph 110's (AT&T Fuze), I think it is just a subset due to hardware problems. For me, the problem only happens occasionally and it does not only occur in xdandroid, but also in WM. There is an HTC tool (for WM) named NavDbgTool.exe that will show you what is happening with the capacitive buttons/touch area on the Raph. For me, when I have issues it lights up all over and shows touches occurring that are not occurring. I know of at least one XDA member (Captain Throwback) who was able to get a replacement phone (a Tilt2) from the insurance carrier because of this issue.
Perhaps this is a problem that eventually happens with all Raph 110's due to a hardware flaw. If that is the case, maybe enough complaints to AT&T will cause them to replace all of the devices (similar to how Sprint is replacing all their Touch Pro's due to overheating issues). In the meantime, if you have insurance, you should be able to get a replacement phone, just use the NavDbgTool.exe to document the problem in WM.
Also, due to this issue, it would be nice to have the option to disable the capacitive touch area on the Raph 110 in xdandroid (while keeping the D-pad working). I don't use it for anything now that zooming doesn't work for recent versions of Opera in WM.
I'm starting to think that this is Winmo ROM related. I noticed that since I've used the ROM that I have installed right now, the amount of times this issue has affected me has been slim to none. I am currently running the an NRG rom from june 12 with sense 2.5.
link: http://hotfile.com/dl/47992175/ccd8b44/Energy.RAPHAEL.21905.Sense2.5.Jun.12.7z.html
I'm not guaranteeing anything, but its working for me.
Maybe it has something to do with a package that is built into certain roms. I have noticed a few times where the winmo ROM i have loaded will affect Android's performance as well. The ROM that I am currently running was also what provided me with the ability to get GPS working in Android.
I hope this helps some of you.
I don't think it has anything to do with WM. For me, it only happens in Android.
firstly i have a raph100 that has this issue too, so its not just raph110
secondly, for me, this happens in wm too but a lot less frequently and seems to repair itself. It happens in android 70% of time when i boot, the 30% else happens later...
newly released zimages seem to shutdown the capacitive panel when sleeping, and this solved my problem a little bit since every time it goes crazy I can put the device in sleep then resume it...
But when it goes asleep the two buttons on the right act as back, the two on the left act as home. I think there is only one physical button on both sides, the touch figures if you are pressing back or end.
Sent from my AOSP on XDANDROID MSM using XDA App
Problem summary
Known cause (might be others): selecting an app from the Recents list (Task Switcher)
Temporary fix: turn the screen off, then back on
Workaround: avoid using Recents list (you can use a 3rd party task switcher instead)
How to test: open Messaging, hit Home, hit Recents, select Messaging from the list. Your screen will be less sensitive until you turn the screen off and back on. You can view the pressure by going to Settings -> Developer Options -> turn on Pointer Location. This will allow you to see the Prs of each tap in your status bar. Normally your lightest taps that register will show anywhere from 0.28 to 0.32. However, after this bug is activated, you will mostly get values over 0.40 for your light taps. This is actually a very noticeable increase, especially when trying to type quickly.
Please report any other known methods to "activate" this bug. After re-assigning my Recents button to a 3rd party app (I'm using Simple Task Switcher), I haven't seen this bug at all. It seems that a couple of people have seen it produced by something other than Recents, but they haven't narrowed it down (or reliably reproduced it on purpose).
Please star this issue officially so Google can fix:
Link is http://code.google.com/p/android/issues/detail?id=29734
Note: Downloading & using Screen filter application from play store, with brightness set to
Your hands are really dirty or really dry. Try moisturizer or something.
Been using my screen for almost hour straight now. No issues.
--------+++--------
iphone. helping computer illiteracy become popular since 2007.
Hehe yes this s gonna be a difficult one to confirm. But it is definitely not dirty hands. To clarify, a quick press of the power button to lock then unlock completely fixes the issue. Same fingers suddenly register perfectly. This is driving me nuts as the phone is not even usable right now. Literally.
@rbiter said:
Been using my screen for almost hour straight now. No issues.
--------+++--------
iphone. helping computer illiteracy become popular since 2007.
Click to expand...
Click to collapse
ios 6.2 doesnt get issues.
I don't know about your other experiences, but as far as the browser goes I have the same scrolling effects as you do. I think this is how it is meant to be. They tightened the scrolling a lot and I kinda like it. Before one small flick would send me across the whole page, which was kinda annoying. Just my preference.
I'm not having this problem. It would drive me crazy too. Been using my phone alot over the past two days and I didn't run into this problem even after almost 1h of continuous surfing. Also a few checkpoints of Shadowgun didn't trigger it.
But you can confirm your problem if you enable "cursor position" in the dev options (hope that's what it 's called in english). "Prs" and "Size" should need a lot more than around 0.30-0.40 to register your touch if you have the problem you describe.
I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.
My wife had this issue once.
It was the third party launcher she was using.
I don't think its a matter of touch sensitivity dropping, its a matter of the system just being too slow to really work right.
It was ADW EX, fwiw.
kristovaher said:
I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.
Click to expand...
Click to collapse
Lol that is hilarious. You forgot the step where its the OS that actually processes the input data, so in that process, a ton of problems can arise.
And personally, since 4.0.4 I have also been experiencing a "similar" issue. When scrolling down (and only down), I experience a kind of "lag" like if it only registers the swipe movement half an inch lower. Its not a big deal, but still an issue.
Edit : What he explains as "pressing very hard" is most likely the fact that when you press harder you actually cover more surface, so the amount of extra input data can definitely impact the behavior.
I had issues for a few hours after the 4.0.4 update, where my softkey buttons weren't responding. Thankfully, it seems to be fine now, but it was a cause for concern.
Sent from my Galaxy Nexus
gokpog said:
I'm not having this problem. It would drive me crazy too. Been using my phone alot over the past two days and I didn't run into this problem even after almost 1h of continuous surfing. Also a few checkpoints of Shadowgun didn't trigger it.
But you can confirm your problem if you enable "cursor position" in the dev options (hope that's what it 's called in english). "Prs" and "Size" should need a lot more than around 0.30-0.40 to register your touch if you have the problem you describe.
Click to expand...
Click to collapse
Thank you my friend, I should have thought of this; now I have numbers to confirm this. So with cursor option enabled I can get down to 0.30, managed 0.28 once. However when the bug starts, I can confirm that I cannot get below 0.60. It just refuses to register that input for some reason.
I lock the screen, 1 second is all it takes, and now it registers down to 0.30 again and all touch works properly. Its almost like some type of memory leak issue is the way it feels to me. It only starts happening after a few min of use.
Its definitely an issue now that I can see the pressure numbers. The question is what the hell can I do about it. I flashed aokp29 with the latest 4.0.4 ota merged in, problem still occurs. I'm gonna try stock 4.0.2 or 4.0.1 just to see. Thanks.
I have never had much luck upgrading Linux versions. That's why I start fresh every time with Android. Lol
Sent from my Galaxy Nexus using Tapatalk
Before I start digging, anyone know specifically which driver controls the touch input? I'll try looking thru github.
Also I was on stock 4.0.1 prior to this. So this could be normal behavior for everyone but everybody is used to it since nobody stayed on 4.0.1 like me. Cause I can easily say this is difficult to notice if you aren't paying attention. The question is, why does locking the screen temporarily change it back...
I can confirm some of what you are saying..sometimes when I'm browsing the scrolling tightens up..I lock the phone then unlock it and it is smooth again..doesn't happen all the time tho..doesn't bother me but I've noticed it
Sent from my Galaxy Nexus using XDA
I can also confirm. This morning I found the Swiftkey was lagging on Facebook. Something like the phone did not receive the touch. Then I rebooted and now it is ok.
I did not get this issue on 4.0.2 and I don't install anything new on 4.0.4.
The way I installed 4.0.4 was from the official factory image, so my phone is fresh! I reinstalled all apps manually as well. Nothing fancy apps.
I know this is my first post, but I can definitely confirm this issue.
I use my Galaxy Nexus for development, so the screen is always on. The sensitivity goes down very quickly.
My phone was an International GNEX that I loaded the US firmware on and then I flashed the OTA 4.0.4 update.
kristovaher said:
I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.
Click to expand...
Click to collapse
Just to point out, the phone is all digital. It does not get an analog signal from touching the screen. Also to that point you said analog but then described digital with the 1 and 0
Has anyone affected tried going between 4.0.2 and 4.0.4? To check the possibility of a driver or some related value changing.
Also, if not fixed by going back to 4.0.2, this could be due to current leakage from somewhere causing the touch to not work properly. I've seen it on other capacitive touch devices, though mainly when a non-compatible charger is connected. When you shut the screen off, the charge causing the problem/interference with the touch is temporarily dissapated, but then comes back after you use it again. Probably very unlikely in this case, unless Google changed something in the touch driver that makes it more sensitive to interference, which in turn messes with actual input from fingers.
TechNoir said:
Has anyone affected tried going between 4.0.2 and 4.0.4? To check the possibility of a driver or some related value changing.
Also, if not fixed by going back to 4.0.2, this could be due to current leakage from somewhere causing the touch to not work properly. I've seen it on other capacitive touch devices, though mainly when a non-compatible charger is connected. When you shut the screen off, the charge causing the problem/interference with the touch is temporarily dissapated, but then comes back after you use it again. Probably very unlikely in this case, unless Google changed something in the touch driver that makes it more sensitive to interference, which in turn messes with actual input from fingers.
Click to expand...
Click to collapse
Its possible. I was on 4.0.1 so perhaps this issue originated in 4.0.2 but I never noticed since I didn't update then. I can add that I did multiple wipes and clean flashes, and also tried both aokp 28 and 29 (new 4.0.4 ota merged), and happened on both.
I'll post what I just sent to arbiter which gives more insight.
From my extra testing under normal use my light touches register 0.28-0.33. Especially on swipes, the end of the swipe registers 0.28 as the finger travel breaks contact with the screen giving that swipe extra input which pushes the swipe motion further extra boost. When the bug starts the touch swipe won't even break 0.38-0.40, and that extra swipe data is lost resulting in the end of the swipe data points being excluded and swipes travel half the distance.
This gets exacerbated on the keyboard when fast typing light pressed. Its so bad it frustrates my face off cause typing just ceases to be possible. Such a difficult issue to diagnose.
Click to expand...
Click to collapse
Yes my face literally flew off!
So Nokia is going to fix the " memory management " of the Lumia 900 to fix the data loss issue. I hope they also fix the following issues, and please feel free to add to it.
1. Volume control for music play back doesn't work with screen locked.
2. Camera button doesn't wake the phone every time.
3. In lower light (like 1/2 the lights off in an office) level the screen for the camera looks blue and like there is electrical interference. Like white noise on a TV, but blue.
4. Power management, when plugging into a power source it sometimes takes up to 10 seconds for it to chime and recognize its being charged. Also when it runs out of power it just shuts off, no graceful " Good Bye ". Also, it has no idea how much power is left. Will say 1 day 15 hours for a full charge, and 2 hours for 25% left.
5. The touch sensitivity is not as good as other handsets. It takes more thumb swipes to get top to bottom of home screen then it should. The screen should keep scrolling even after you remove your thumb.
6. The volume level of "1" is waaaaaay too loud. I like the max volume (30), but there needs to be something between "kind of loud" @ 1 and "mute" @ 0.
Seed 2.0 said:
So Nokia is going to fix the " memory management " of the Lumia 900 to fix the data loss issue. I hope they also fix the following issues, and please feel free to add to it.
1. Volume control for music play back doesn't work with screen locked.
2. Camera button doesn't wake the phone every time.
3. In lower light (like 1/2 the lights off in an office) level the screen for the camera looks blue and like there is electrical interference. Like white noise on a TV, but blue.
4. Power management, when plugging into a power source it sometimes takes up to 10 seconds for it to chime and recognize its being charged. Also when it runs out of power it just shuts off, no graceful " Good Bye ". Also, it has no idea how much power is left. Will say 1 day 15 hours for a full charge, and 2 hours for 25% left.
Click to expand...
Click to collapse
It was bound to happen.
I would highly suspect the fix coming will be extremely limited to the memory managment issue. Its the only way many assume the speedy release has gotten past AT&T testing.
The other 'bugs', are only bugs if Nokia says they are. Will they be fixed? Good question. I cannot imagine seeing them next week. Maybe in a Tango or pre Apollo release.
" Memory Management " is a pretty vague reason for something not working. I can see that affecting all of the above issues.
P.S> Also At$t is planning a update to Windows phones them selves that would present another chance for Nokia to use Firmware to fix issues.
Seed 2.0 said:
" Memory Management " is a pretty vague reason for something not working. I can see that affecting all of the above issues.
P.S> Also At$t is planning a update to Windows phones them selves that would present another chance for Nokia to use Firmware to fix issues.
Click to expand...
Click to collapse
The constraints involved in how they release this quick fix, I cetainly don't know...nor would anyone here. What you say sounds right, and I personally would love to see everyones issues resolved, do you reasonably think they will be on this fix update?
alodar1 said:
The constraints involved in how they release this quick fix, I cetainly don't know...nor would anyone here. What you say sounds right, and I personally would love to see everyones issues resolved, do you reasonably think they will be on this fix update?
Click to expand...
Click to collapse
it is very possible
Nokia is pushing an update on 4/16. Perhaps it will fix some of these things - we'll see.
Seed 2.0 said:
So Nokia is going to fix the " memory management " of the Lumia 900 to fix the data loss issue. I hope they also fix the following issues, and please feel free to add to it.
1. Volume control for music play back doesn't work with screen locked.
2. Camera button doesn't wake the phone every time.
3. In lower light (like 1/2 the lights off in an office) level the screen for the camera looks blue and like there is electrical interference. Like white noise on a TV, but blue.
4. Power management, when plugging into a power source it sometimes takes up to 10 seconds for it to chime and recognize its being charged. Also when it runs out of power it just shuts off, no graceful " Good Bye ". Also, it has no idea how much power is left. Will say 1 day 15 hours for a full charge, and 2 hours for 25% left.
Click to expand...
Click to collapse
1. that's by design of the OS, so probably not. volume does change with screen off if using a headset with volume controls though.
2. are you holding it for a few seconds and pushing all the way in? i haven't had this issue come up personally.
3. that noise is because the camera is bumping the ISO higher to compensate for the low light, if you manually choose a lower ISO it should go away and also result in a clearer picture (but you will have to hold the phone more steady if you don't use a flash with low ISO)
4. i hope they can fix this one all other windows phones i've had have the charging chime come almost instantly after plugging in. the reason the time remaining quote is inconsistent is that it recalculates it based on actual usage, so if you use the phone heavily for a while and then check, it's going to show much less time remaining because it assumes similar usage patterns. it's the way the OS works and not something nokia can really change.
I get the feeling that Nokia, At$t, and Microsoft have a pretty tight relationship at the moment. Concessions are made, Microsoft backs down on over all updates in exchange for critical update to be expedited. Nokia pays a premium for At$t to adopt their flagship phone, At$t will let them expedite the fixes needed for the phone, and all of theirs investment to succeed.
One more issue I've noticed: The volume level of "1" is waaaaaay too loud. I like the max volume (30), but there needs to be something between "kind of loud" @ 1 and "mute" @ 0.
adiliyo said:
1. that's by design of the OS, so probably not. volume does change with screen off if using a headset with volume controls though.
Click to expand...
Click to collapse
With the other windows phones I've tried if you are listing to music with plane-jane headphones, you can turn vol up and down with the screen off. The NL900 is the first one I've had this issue with. It's an issue cause I have plane-jane headphones that don't support anything but listening to music.
slojko said:
it is very possible
Click to expand...
Click to collapse
I think not. I hope so. In order for these things to get included, it means they must have been working on them awhile. Heck, think about it, for them to fix this memory issue so quick, they had to be aware of it....before the device went on sale. If thats the case, you could reasonably say, they shipped defective devices...knowingly.
I'm keeping mines anyway. Best defective device I've ever had....since my last android.
I also hope they give you an option to turn off haptic feedback of the hardware capacitive buttons in case it's not an OS limitation.
Seed 2.0 said:
3. In lower light (like 1/2 the lights off in an office) level the screen for the camera looks blue and like there is electrical interference. Like white noise on a TV, but blue.
Click to expand...
Click to collapse
I notice this very clearly too but I've come to realize that if I change the setting of "Scenes" from Auto to any other different value (except Night) this problem goes away.
My assumption is that the phone is getting the auto setting to Night mode in lower light conditions (although it should be calibrated for even lower light because night mode is not really needed for a 1/2 light situation).
Lower the ISO or change your scene mode and I think this problem will be corrected. I use the "Landscape" mode as it seems to compensate well the white balance for internal conditions.
Regards
Just wanted to start a thread to discuss this device. For those not familiar with it, it's a very inexpensive 11.6" laptop that runs RemixOS 2.0 from the factory. It does NOT have a touchscreen and the display is a low resolution (1366x768) TN panel display. The CPU is an Allwinner A64 Cortex A53 quad-core 64-bit processor.
The device I purchased (via their Kickstarter campaign) has 2gb RAM and 32gb storage - and it costs me $89.
Some interesting things I've found so far...
1. To disable the damn "click" sound every time you select something (via the touchpad or a mouse), download the QuickShortcutMaker application from the play store. Then expand the Settings items under the Activities section and find the "Other Sounds" activity. Once you click on the Other Sounds activity, click on "Try" on the right-hand side - this will open the "Other Sounds" dialog where you disable "Touch Sounds"! You can also disable some other sounds here. No idea why Remix doesn't allow access to these sound options. Explore the other Settings activities - there are some other cool things you can do. I also used this app to create "Shortcuts" to specific forums in Tapatalk (something that you do via widgets in standard Android). This QuickShortcutMaker app is pretty damn useful on this device!
2. I've found that I was able to connect my Apple USB->Ethernet adapter to this device and it works! However, it doesn't seem to work with ALL apps. For example, Tapatalk doesn't work with it for some reason - but so far, every other app has worked. You can also access ethernet settings via the QuickShortcutMaker app mentioned above.
3. Enable "Experimental Features" by clicking on the "Kernel Version" section of Settings->About. Once you do this, enable the "Use mouse wheel to simulate swipe gesture". This allows you to zoom in and out of things like web pages, images, etc. To do this, hold down CTRL+ALT while moving the mouse wheel. Apparently, the touchpad on this device does NOT provide pinch-to-zoom functionality, so without this setting, there is no way to zoom in and out in most apps! Kind of a big issue! Unless there is another way that I just don't know about. I know you can CTRL- and CTRL+ to zoom in and out in web pages, but that really just increases the size of the text - not really a true zoom in/out.
4. Gmail app. If you open the Gmail app as a window, you don't get the "split-screen" that you get if you open the app in full screen. But if you open in as a full-screen window and then "restore" it to a smaller window, the split-sceen function still works. I usually just leave Gmail minimized in order to keep the split-screen function active for Gmail.
5. Sometimes, the screen comes back on if you put the device into standby with the power button and then close the lid. I haven't been able to find the exact circumstances where the screen comes back on when closed, but it seems that when it does come on when it's closed, it stays on! Need to figure out why this occurs..
6. Bottom of device gets REALLY hot after any extended use. May be a long-term issue...
7. By default, wifi is set to turn off when in standby (unlike tablets) - unless the device is plugged in - then wifi will stay on. This can all be changed under Settings->Wifi->Advanced. I actually set mine to always turn wifi off when in standby since it seems that the device doesn't actually work while in standby anyway (again, unlike tablets). May help avoid wifi failure over the long-term.
8. I have run into websites (such as microcenter.com) where when you open a drop-down list, there is no way to "scroll" the list if it goes off the screen. To see what I mean, go to microcenter.com and try to set the store location - it opens a drop-down list that goes off the screen and there is no way to scroll down in the list! The "work-around" is to use the down arrow key, but it doesn't work very well (web page wants to update every time you press the down arrow)....
That's about it off the top of my head... It's a shame that this device cannot upgrade to RemixOS 3.0, like was stated in the kickstarted campaign (and later "retracted").
Anyone know how to root this thing?
It's an interesting device for the cost, but what I *really* want is a similar, large'ish device with a higher-quality, higher-resolution touchscreen that is removable from the keyboard - with at least 2gb of RAM (10" and 1gb of RAM isn't enough for RemixOS!) and runs RemixOS 3.0 - so far, I can't seem to find such a device...
Sent from my A1160 using Tapatalk
I got the same model 2GB w/32GB storage. Do you or anyone know how to get it to charge and or power on. Mine only worked for 2 days, now nothing. I contacted Azpen over a week ago about it and still haven't heard from them. Please help.
Cerealius said:
I got the same model 2GB w/32GB storage. Do you or anyone know how to get it to charge and or power on. Mine only worked for 2 days, now nothing. I contacted Azpen over a week ago about it and still haven't heard from them. Please help.
Click to expand...
Click to collapse
I just plugged mine in and it charged fine (blue LED next to charging port turns on when charging and turns off when fully charged).
To turn mine on, I just held down the power button on the keyboard for a while... You can also fully power it off that way as well (if it gets hung or something, which I have managed to do a few times now).
I've *really* put this thing through it's paces over the last few days. Overall, it's a decent device for the price. Personally, I'd rather spend a little more for one with a better, higher-res, removable touchscreen though.
I also have a HP Slatebook 10 x2 - and it's a great device, but stuck on Android 4. Otherwise, it has a MUCH nicer, removable touchscreen and even an extra battery in the keyboard (that charges the tablet when attached). Just wish it was a little bigger (13" or so) and was running Remix OS.
But, for $89, I can't complain, my A1160 actually runs pretty well for what it is...Luckily, I haven't had any issues with mine.
Sent from my HP SlateBook 10 x2 PC using Tapatalk
Hello...
@jtrosky, thanks for starting this thread, i've already gotten something out of it... getting rid of that damn clicking every keypress.
It was also nice to find that quickshortcutmaker, thats really a cool app that seems to allow more access than I could find...
Everyone else, hello!
I am an PC user since 84' and an Apple iPad user since, well the day the ipad 2 came out and now I'm on the iPad now. The only reason I say any of this is because the reason I got this Azpen A1160 was to help learn a bit about android and linux. I would also like to figure out how to get to the root...
Knock on wood but I got this three days ago and have literally beaten the software out of it loading, looking, deleting, and I thought I had screwed it up several times but it just keeps on ticking. The back does get a little warm, I haven't actually measured it yet but I'm going to, but I dont think it's too bad. I've run six full charges on battery and worked on it plugged in. (which it doesn't seem to like)
I'm happy with it right now and I think its going be a fun ride. I bet this is going to be a fun place to be in the next couple of months...
Buddy
Oh - one more thing I found out - and this may be well known already for those more familiar with RemixOS. If you click and hold on the little icons on the bottom-right of the taskbar, you can move them around. So, for example, you can make it so the brightness, volume, bluetooth and wifi icons are always visible, even when that section is "collapsed"...
Also - I *love* having the key to disable the touchpad (the key next to the arrow keys). Since I usually use a bluetooth mouse, it's so nice being able to disable the trackpad so quickly and easily!
Oh - and the Prtscr button on the keyboard brings up the very cool screen capture tool, which let's you select what area of the screen to capture. Very handy tool!
Still not sure what the "Pausc" button does - I'm assuming it's actually a misprint and it's supposed to say "Pause". Gotta love cheap electronics that are made in China!
So far, this device is definitely working well for me. Although, I'm not so sure the screen is big enough to truly take advantage of the RemixOS windowing capabilities... But, it's still better than not having any windowing capabilities.
Sent from my A1160 using Tapatalk
One more quick tip - there are apps out there that will let you boost the volume of the device. Right now, I'm using Music Volume EQ to boost the volume, but there are probably better apps out there for this purpose... Will explore more later and post an update if I find a better app.
Sent from my A1160 using Tapatalk
Hello guys, thank you for creating this thread.
Did anyone have any issue by setting up a password for the lock screen?
I did, and it worked for a couple of times, then it started not to recognize the password (password was correct, no caps lock...). Of course it didn't work after reboot as well.
The only option was to remotely reset the device using the google's tool from another pc. Very annoying. Since then never tried to set another security system for the screen lock.
I'm also getting an a problem after turning off the screen: when I try to turn it on again, most of the time I get a blank screen. I have to try several times to get back to remix os.
Did anyone faced this issue as well?
Regards
sephitoor said:
Hello guys, thank you for creating this thread.
Did anyone have any issue by setting up a password for the lock screen?
I did, and it worked for a couple of times, then it started not to recognize the password (password was correct, no caps lock...). Of course it didn't work after reboot as well.
The only option was to remotely reset the device using the google's tool from another pc. Very annoying. Since then never tried to set another security system for the screen lock.
I'm also getting an a problem after turning off the screen: when I try to turn it on again, most of the time I get a blank screen. I have to try several times to get back to remix os.
Did anyone faced this issue as well?
Regards
Click to expand...
Click to collapse
I have not tried setting up the lock screen (I just leave mine unlocked). And no, I have not had any issues with a blank screen when turning the device back up. What's strange is that the device does not automatically turn on when opening the screen - at least not on my device - I have to press the power button.
Your issues are probably because of the poor quality control with these device. Somehow, I lucked out and got a "good one", but many people seem to be having build-quality issues with them...
Sent from my A1160 using Tapatalk
Great posts and many thanks to the OP.
I got a US 2 pin power plug instead of a UK plug. Does anyone know of a similar products power lead that will fit our A1160?
Need help...
Hi,
First, thanks for creating this thread and posting your tips. Obviously there are not a lot of people using this device yet so it is great to find useful info on it.
Since there is no known root solution yet, I tried installing NetGuard as an adbllocking solution that does not require root. I have used it before without any issues. Unfortunately, on the Azpen, every time that I enable it, it blocks all internet access (it is obviously not supposed to do that). I even tried alternative apps like AdClear and got the exact same result. There is something strange going on with the Azpen. I would really appreciate it if anyone had any pointers as to how I could resolve this.
Thanks...
Welp! I had much higher hopes for this device and I haven't even received mine yet! Will this be rootable?
Thanks for creating this, used both your sound clicking tip and the pinch to zoom in. A bit annoying having your fingers in multiple place to zoom in, but what can you do? I'm a college student and have found that I can't access the net with this device due to it's mac address changing each time. I'm not sure if anyone else has noticed this or if mine is the only one. Just thought I would share that.
HyugaSho said:
Thanks for creating this, used both your sound clicking tip and the pinch to zoom in. A bit annoying having your fingers in multiple place to zoom in, but what can you do? I'm a college student and have found that I can't access the net with this device due to it's mac address changing each time. I'm not sure if anyone else has noticed this or if mine is the only one. Just thought I would share that.
Click to expand...
Click to collapse
That is *really* interesting! Sure enough, if I disable and re-enable the wifi, the MAC address does change!! That makes absolutely no sense - I've never seen such a thing!
I'll look into that a little more - but without root, I doubt there is anything that can be done about it. So strange!
One possible option - set wifi to stay enabled all of the time - maybe that way the MAC will stay the same. You can set that in the wifi settings advanced options. I've found that you have to reboot after setting it to always stay active....
Sent from my A1160 using Tapatalk
So far I have been impressed for the cost of this unit. I have a few concerns and wanted to see if anyone had input:
1. Since the length of the power chord is so short. Is it possible to use a USB to Barrel jack type of adapter to power this? That way you can attach to a portable power bank?
2. battery power, I find it to not last that long and I find it takes forever to charge. I thought that this would last 5-7 hours unplugged, nope. It was supposed to charge within in a hour, nope. Any ideas on this?
I use an external mouse and click on the trackpad disable button. I find it much easier to use the computer when typing.
I'm looking at Pinebook, a notebook having the same AllWinner processor (CortexA53).
It seems this notebook can run all OSs suppoted by Pine64, such as Android, some linux distro, Windows IOT and they are working on a Chroimum porting (try to have a look at the pin64 forum).
Do you think it would be possible to do the same with A1160 ?
Another solution could be PhoenixOs (as pointed out in some comment on Kickstarter).
There are already some devices with CortexA53 processor running PhoenixOS out of the box.
I honestly don't know what OS's can be ported over to this device yet. I have a feeling that it's never going to have a huge user base though, so I wouldn't expect much from the developers out there.
Now that Chromebooks can run Android apps, this device just isn't quite as interesting as it once was. Basically, you can now get an inexpensive, *high quality* Chromebook and still have most of the advantages of this device, plus the high quality and frequent updates part.
To be completely honest, I have very low expectations for this device in the long-term. With how hot it gets after any real usage, I expect the mainboard to fail in short order. We'll see. Although, so far, I've really been using it pretty heavily and it does seem to be holding up, but it's only been about a week....
Sent from my A1160 using Tapatalk
Something else I recently noticed - and this may already be a well-known thing with RemixOS... If you close an app by clicking the back arrow on the top-left of the window, you continue to get notifications for that app. But if you close it by clicking the "X" in the top-right of the window, it seems to completely the kill the process and you no longer receive notifications (or if it's an app that stays around and puts a "permanent" notification in the notification tray, the "x" seems to completely stop the app as well and removes its notification item).
At least that's what seems to happen...
Also noticed that even if you setup wifi to stay active even with power off, the unit eventually goes into a "deep sleep" where you will no longer get new email notifications, etc. It even seems to turn wifi off after a while (even though it's set to stay on all of the time).
Lastly, if you have an external mouse connected, close the laptop lid and then move the mouse, it turns the screen back on - even while closed!
Sent from my A1160 using Tapatalk
Hi All,
Saw this in the comments and thought I would chip in with my experience so far.
I got the 64GB version and so far it is the computer I have paid for.
The track pad as everyone said is very crappy, but I just use an external mouse instead so its not a big problem.
I seem to have a good unit and don't have any problems with the unit.
My only gripe is that the battery kinda sucks and after using it intensive for like 3-4 hrs, it will have almost no battery. I wish it came with my UK adapter instead of the US one, but its okay.
Furthermore, is there anyway to put widgets on it? or Use another launcher?
Has anyone tried to root it or tried to install another OS on top of it? I heard that PhoenixOs is possible?
MindlessManiacs said:
Hi All,
The track pad as everyone said is very crappy, but I just use an external mouse instead so its not a big problem.
Furthermore, is there anyway to put widgets on it? or Use another launcher?
Has anyone tried to root it or tried to install another OS on top of it? I heard that PhoenixOs is possible?
Click to expand...
Click to collapse
For what it's worth, my trackpad actually works really well. I was surprised to read all of the complaints about it. I'm guessing that a lot of them are defective?
Regarding the widgets, no - there is no way to use Widgets in Remix OS 2.0 (not sure about 3.0), which is a huge limitation. Widgets are one of the things that make Android so powerful - and I miss them big time in Remix OS...
I too would like to know if there is a way to load PhoenixOS on this device. I thought I saw it mentioned somewhere that it would be possible (maybe one of the updates on Kickstarter?). I will see if I can email Azpen about this. RemixOS 2.0 is really good, but not quite "finished" in my opinion...
Sent from my A1160 using Tapatalk
Hi! Does somebody receive a blank white screen when laptop booting or waking up?
Every time when I push power button I get a blank white screen... How I can fix it?
I wanted to throw this one out here because XDA likely hasn't looked into this one yet. Best Buy is offering the Tracfone Wireless ZTE Cymbal Android FlipPhone for $50 (on Tracfone's website, it's $100). I had it shipped to my house and it arrived today, so I wanted to give my thoughts.
It ships with similar specs to the LG K3/K4 models. Snapdragon 210 CPU, 1GB RAM, 8GB ROM, expandable microSD (32GB) slot. Touchscreen is 3.5 inches (low resolution), it has two speakers AND two microphones, a physical keypad (FLIP PHONE), a headphone jack, and a modest battery for its size. The OS is Stock Android 5.1.1 Lollipop. There's also an external display for clock. Because it's a CDMA phone, it has an MEID for 3G and an LTE SIM for 4G. It MUST be activated through Tracfone or used with some kind of Mobile Hotspot.
The device features physical Android keys (Home, Back, Recent), a camera key, mute key, messaging key, favorite app key, D-Pad with center button, and a backspace/C key. I swapped the launcher with NOVA Prime and mapped the home key to the app drawer. Because of the small screen, I made it so desktop is 4x5, but app drawer is 3x4. Arrow keys can then be used to navigate, or you can touch the screen directly.
The internal antenna is wicked powerful. Most phones do not get signal at my house, yet this phone can occasionally detect VZW's 3G network while inside. More crazy is that the internal GPS includes something called IZat and gets a lock-on while indoors. I have rarely seen a phone do that. This phone does have a proximity sensor and an ambient light sensor, though the latter isn't the best. I disabled Auto-brightness because the phone was changing brightness to often for my liking. That said, the backlight is really bright even at low settings.
That said, there are a few things I am not liking. The messaging key does not map to your default messaging app. It goes to the stock messaging app, no exceptions, even if you select a different app like Hangouts as the default. Additionally, the physical keyboard modes aren't exactly the best laid-out. You have your legacy modes, but instead of using the 1 key for symbols, you use the * key and navigate a small menu on the screen. There's also a "T12" mode which is similar to T9 though requires you to select the word using the center button every time before hitting space. I'm still trying to figure out if that can be modified.
Thankfully, you can also install touchscreen keypads like Google Keyboard or use the included TouchPal keyboard. Its layout is not too bad for a 3.5 inch screen, but it kind of defeats the purpose of using a physical keypad. I would say the only advantage of having it is being able to dial a number without having to open the dialer app. Plus, if you press the Green (call) key from the home screen, it takes you to your contacts list.
All in all, it was a great way to implement Android flip phones into the North American market, but I don't know if I would use this as a daily driver just yet. I still have my Moto G4 Play running Lineage 14.1, and I need that for work anyway (certain apps would not do well on the ZTE). But for $50, this phone gives my Moto a serious run for its money.
I picked this device up on discount as well.
It's far more phone than I expected for the money, that is for sure. It would be great to see a software update to at least 6.0, but I doubt it will happen.
I think the only thing missing from the device is a convertible style hinge. being able to flip the screen around and close the clamshell would be really amazing.
All in all, punching above its $50 weight class.
I was looking at this online today. I'm on AT&T though so while there are some "unlocked" offered online, I'm not sure it would work with my sim card. This is really the kind of thing I am hoping for though, a blast from the past that can slip into my pocket and still do Android. I wonder if you can play Pokemon Go on it...
To bump up this thread, I bought mine at local K-Mart recently for $49.99, had been hoping to run across one of these. It's a great little phone for the money I paid, considering it's features and appearance. I could see this type of phone being tweaked into a great daily driver. The speaker is pretty clear and surprisingly loud. My eyes aren't what they used to be, but the screen is clear and bright. It's a budget phone, but it's a great one. I currently use it with my Safelink account (via Tracfone) and it seems to get good cellular reception (verizon 4g LTE towers), as I stay in my underground basement most of the time, working on Computers and such. I want to get another just to experiment on with a custom launcher and some other apps. I'm curious if it can be rooted, and if it would even be worth it if it can. It's a pretty cool phone, hope to see more phones similar to it soon here in the US...
Unlock zte cymbal t tracfone ,it's not prompting for unlock code with diff sim triedd
Phone Fan said:
To bump up this thread, I bought mine at local K-Mart recently for $49.99, had been hoping to run across one of these. It's a great little phone for the money I paid, considering it's features and appearance. I could see this type of phone being tweaked into a great daily driver. The speaker is pretty clear and surprisingly loud. My eyes aren't what they used to be, but the screen is clear and bright. It's a budget phone, but it's a great one. I currently use it with my Safelink account (via Tracfone) and it seems to get good cellular reception (verizon 4g LTE towers), as I stay in my underground basement most of the time, working on Computers and such. I want to get another just to experiment on with a custom launcher and some other apps. I'm curious if it can be rooted, and if it would even be worth it if it can. It's a pretty cool phone, hope to see more phones similar to it soon here in the US...
Click to expand...
Click to collapse
Can anyone help plz
Hi,
FYI, in case anyone is interested, QVC has these for sale for like $49.98 incl 1 year and 1200 mins on Tracfone.
I found that while I was searching for a backup battery for the one I bought my wife (from bestbuy - I messed up and paid more for that one !).
Anyway, beware though. It does not seem possible to buy just the battery anywhere nowadays (as of Aug 2017 anyway).
Jim
Zte Cymbal T Root and Battery
jimcpl said:
Hi,
FYI, in case anyone is interested, QVC has these for sale for like $49.98 incl 1 year and 1200 mins on Tracfone.
I found that while I was searching for a backup battery for the one I bought my wife (from bestbuy - I messed up and paid more for that one !).
Anyway, beware though. It does not seem possible to buy just the battery anywhere nowadays (as of Aug 2017 anyway).
Jim
Click to expand...
Click to collapse
Yeh anyone know if a tracphone can be rooted? I also looking for batteries.
unlock help
anyone know how to unlock this tracphone
mkollersms said:
I wanted to throw this one out here because XDA likely hasn't looked into this one yet. Best Buy is offering the Tracfone Wireless ZTE Cymbal Android FlipPhone for $50 (on Tracfone's website, it's $100). I had it shipped to my house and it arrived today, so I wanted to give my thoughts.
It ships with similar specs to the LG K3/K4 models. Snapdragon 210 CPU, 1GB RAM, 8GB ROM, expandable microSD (32GB) slot. Touchscreen is 3.5 inches (low resolution), it has two speakers AND two microphones, a physical keypad (FLIP PHONE), a headphone jack, and a modest battery for its size. The OS is Stock Android 5.1.1 Lollipop. There's also an external display for clock. Because it's a CDMA phone, it has an MEID for 3G and an LTE SIM for 4G. It MUST be activated through Tracfone or used with some kind of Mobile Hotspot.
The device features physical Android keys (Home, Back, Recent), a camera key, mute key, messaging key, favorite app key, D-Pad with center button, and a backspace/C key. I swapped the launcher with NOVA Prime and mapped the home key to the app drawer. Because of the small screen, I made it so desktop is 4x5, but app drawer is 3x4. Arrow keys can then be used to navigate, or you can touch the screen directly.
The internal antenna is wicked powerful. Most phones do not get signal at my house, yet this phone can occasionally detect VZW's 3G network while inside. More crazy is that the internal GPS includes something called IZat and gets a lock-on while indoors. I have rarely seen a phone do that. This phone does have a proximity sensor and an ambient light sensor, though the latter isn't the best. I disabled Auto-brightness because the phone was changing brightness to often for my liking. That said, the backlight is really bright even at low settings.
That said, there are a few things I am not liking. The messaging key does not map to your default messaging app. It goes to the stock messaging app, no exceptions, even if you select a different app like Hangouts as the default. Additionally, the physical keyboard modes aren't exactly the best laid-out. You have your legacy modes, but instead of using the 1 key for symbols, you use the * key and navigate a small menu on the screen. There's also a "T12" mode which is similar to T9 though requires you to select the word using the center button every time before hitting space. I'm still trying to figure out if that can be modified.
Thankfully, you can also install touchscreen keypads like Google Keyboard or use the included TouchPal keyboard. Its layout is not too bad for a 3.5 inch screen, but it kind of defeats the purpose of using a physical keypad. I would say the only advantage of having it is being able to dial a number without having to open the dialer app. Plus, if you press the Green (call) key from the home screen, it takes you to your contacts list.
All in all, it was a great way to implement Android flip phones into the North American market, but I don't know if I would use this as a daily driver just yet. I still have my Moto G4 Play running Lineage 14.1, and I need that for work anyway (certain apps would not do well on the ZTE). But for $50, this phone gives my Moto a serious run for its money.
Click to expand...
Click to collapse
Hi, you mentioned that you installed hangouts and the NOVA prime launcher, i've been trying to install apps on this phone and wasnt able too, i tried via apk files and via ADB and wasnt succesfull,
if you can please advise
Thanks!
lazer7598 said:
Hi, you mentioned that you installed hangouts and the NOVA prime launcher, i've been trying to install apps on this phone and wasnt able too, i tried via apk files and via ADB and wasnt succesfull,
if you can please advise
Thanks!
Click to expand...
Click to collapse
i tried rooting it and wasn't successful either