Related
Today Lumos 1.0 final is released, besides other changes now has better support for HVGA in settings dialog.
never tried this on other phones, but it sounds fantastic
going to give it a whirl and see if anything improves
Well, I was about 6 monthes with previous release and it really helps to save battery.
Just played a little to make own backlight profile.
to be quite honest, cant really get the hang of it. keeps changing the level almost randomly with little to no reason as to why (lightning outside the phone remains the same).
any ideas as to what im doing wrong?
I’ve tried ‘LumosWizard’ 5 month ago but I’ve never managed to make it work correctly
So that, I use ‘Mylostblog Mylight’ now.
Not the same but its easy to use with a shortcut in "Cookie’s Home Tab".
Well, just try run calibration correctly, my sensor's range is 0..1904,
minimum level 1, maximum level 5.
There are issues with g-sensor games - lookup the original Lumos thread.
tkur said:
to be quite honest, cant really get the hang of it. keeps changing the level almost randomly with little to no reason as to why (lightning outside the phone remains the same).
any ideas as to what im doing wrong?
Click to expand...
Click to collapse
I got the NEW & UPDATED Lumia 900(Green Dot) Here's what I found different. Good Job!
Just got home with the updated Lumia 900. They are identified by a green dot sticker on the IMEI label of the At&t box. Let me say right off the bat, the " Memory Management " issue in my humble opinion affected more then the connection issues; or I had defective hardware with my first Lumia 900.
1. The touch response is now equal to that of my Samsung Focus. One to two thumb swipes gets me top to bottom of the home screen. THANK YOU!!!
2. My WiFi will auto connect once I reenter a WiFi area I had accessed before with out me hitting " Connect"
3. Camera wakes phone up from sleep every time. It also wakes up faster then it did before.
4. When I have several apps open and I uses the back button to get back to the home screen, the phone no longer hangs on any one page, it simple flies through each till arriving at the home page.
5. The boot up time and shut down time of the phone has increase dramatically.
6. The response of the back button its self is better in general.
7. Looks like more web pages have been added to the stock favorites, Support pages via Nokia and AT&t.
8. None of the Version numbers changed, i.e OS, Firmware, Hardware, Radio Software, Bootloader, Chip SOC.
I'll post here if I find other differences. They told me at the store more then once the update is coming out on Monday, the 16th.
Had you previously purchased the other version, then traded it in for the one you have now? I assume you did, but wanted to see what hassle if any they gave you? What did you have to do to swap out?
Hey!!! Thanks for reporting!!
---------- Post added at 02:32 PM ---------- Previous post was at 02:20 PM ----------
Seed 2.0 said:
Just got home with the updated Lumia 900. They are identified by a green dot sticker on the IMEI label of the At&t box. Let me say right off the bat, the " Memory Management " issue in my humble opinion affected more then the connection issues; or I had defective hardware with my first Lumia 900.
1. The touch response is now equal to that of my Samsung Focus. One to two thumb swipes gets me top to bottom of the home screen. THANK YOU!!!
2. My WiFi will auto connect once I reenter a WiFi area I had accessed before with out me hitting " Connect"
3. Camera wakes phone up from sleep every time. It also wakes up faster then it did before.
4. When I have several apps open and I uses the back button to get back to the home screen, the phone no longer hangs on any one page, it simple flies through each till arriving at the home page.
5. The boot up time and shut down time of the phone has increase dramatically.
6. The response of the back button its self is better in general.
7. Looks like more web pages have been added to the stock favorites, Support pages via Nokia and AT&t.
8. None of the Version numbers changed, i.e OS, Firmware, Hardware, Radio Software, Bootloader, Chip SOC.
I'll post here if I find other differences. They told me at the store more then once the update is coming out on Monday, the 16th.
Click to expand...
Click to collapse
Boot up and shut down time has increased or decreased?
i don't know how much faster the bootup time can be, it doesn't even have time to cycle through the windows dots once before it's at my lock screen.
that being said, good to hear they have improved the device
Seed 2.0 said:
Just got home with the updated Lumia 900. They are identified by a green dot sticker on the IMEI label of the At&t box. Let me say right off the bat, the " Memory Management " issue in my humble opinion affected more then the connection issues; or I had defective hardware with my first Lumia 900.
1. The touch response is now equal to that of my Samsung Focus. One to two thumb swipes gets me top to bottom of the home screen. THANK YOU!!!
2. My WiFi will auto connect once I reenter a WiFi area I had accessed before with out me hitting " Connect"
3. Camera wakes phone up from sleep every time. It also wakes up faster then it did before.
4. When I have several apps open and I uses the back button to get back to the home screen, the phone no longer hangs on any one page, it simple flies through each till arriving at the home page.
5. The boot up time and shut down time of the phone has increase dramatically.
6. The response of the back button its self is better in general.
7. Looks like more web pages have been added to the stock favorites, Support pages via Nokia and AT&t.
8. None of the Version numbers changed, i.e OS, Firmware, Hardware, Radio Software, Bootloader, Chip SOC.
I'll post here if I find other differences. They told me at the store more then once the update is coming out on Monday, the 16th.
Click to expand...
Click to collapse
LOOKS like the UPdate is live in Zune right now. I got it about 10 minutes ago.
Everything as Seek said...appears to be so....
There was no hassle, but they tell you they can't exchange it again. That said I'm unfortunately going to write Nokia. My original phone that I returned today had a speaker issue or I wouldn't have returned it in the first place. The replacement that had all the wonderful improvements had one major flaw, the vibration mode on it didn't just vibrate, it made an awful metallic/knocking sound. I had it home for 20 minutes and took it back, knowing they couldn't exchange it again. After about an hour and all the employees confirming the defect I was granted a 3rd exchange. This time before even leaving the store I activated the Nokia Diagnostics App and tried the vibrate mode, and in my opinion it was even worse then then one I returned. I however exhausted the patience of the staff member who helped me, and he was a great guy. I expressed that I thought it sounded worse then the other, and he explained that they had no other stock, and made me feel like they couldn't help me any further.
*** While typing this I just received a message that there is an update available for my phone. I have a green dot on my box and was told this phone was already updated***
Updating my phone now.
i updated as well, and still notice the lag, the back button as well, still unresponsive at times. even after hard reset. i'll be going to att in the morning to see if i can swap it out.
out of curiosity, what is the country of manufacture of your new phone?
Still Korea, my guess is they just tested phones at the at&t distribution point put a green sticker on them, and shipped them to stores. I ended up getting another replacement from a different store, with no hassle at all. It was a green dot box too, and it to was offered and received an update. I have used 4 different NL900's in the last 18 hours and I think my original one must of had a faulty digitizer. My original NL900 was so so to swipe, all that followed it I'm able to swipe my full home page in 2 thumb strokes.
I didn't have the connection issue, but did update my phone last night. The scrolling has improve and is faster now. Everthing seems to run fast and smooth.
Only thing is the camera button still doesn't wake the phone up at times but that is the same with my samsung focus s...hit and miss...last is the volume button...it seems that your not able to adjust the volume when the screen goes off even with the music playing in the background.
IF you have concern please dial ##634# and run test. This will put your mind at rest because you will be able to test each part of the phone out. Remember you can still return the phone and get a new one, if the test fail.
I'm hoping Tango release will fix all these minor bugs...
I noticed that volume can be changed with the lock screen on if its through an app, i.e. WPFandora, MixTapes, 8Tracks but not through Zune. I know it works with headphones, but not all headphones have controls on them. That said my crappy headphones sound way better connected to the Nokia then my Focus.
My camera button doesn't wake up the phone either after the update, should i exchange the phone?
romeo0119 said:
My camera button doesn't wake up the phone either after the update, should i exchange the phone?
Click to expand...
Click to collapse
I had this problem before the update but now it works after the update. Strange.
romeo0119 said:
My camera button doesn't wake up the phone either after the update, should i exchange the phone?
Click to expand...
Click to collapse
Go to 'Settings' -> 'applications' -> 'pictures+camera' -> 'Press and hold camera button to wake up the phone' -> 'On'
And remember the camera button is a two-stage button.
The option was turn on and I hold it for at least 5 secs, still nothing.
romeo0119 said:
The option was turn on and I hold it for at least 5 secs, still nothing.
Click to expand...
Click to collapse
First stage or second stage of the camera button? You have to press it all the way down, first stage won't unlock the phone.
I'm not sure that the green dot means they've updated. I just picked on up yesterday that has the green dot and I was prompted to install the update within 2 hours of receiving it.
BooR4dley said:
I'm not sure that the green dot means they've updated...
Click to expand...
Click to collapse
That's exactly what I'm thinking
riffraffer said:
That's exactly what I'm thinking
Click to expand...
Click to collapse
they had said that not all phones were impacted by the problem. Perhaps they had a way to differentiate them. Hence the marker.
Green sticker simply means it was re-checked for hardware and software issues. The connections issue seemed to be the APN setting being wrong. Who ever check the hardware failed though. On my forth Lumia 900 and only my first one had a good working vibra unit. These other ones sound like metal clanking/rattle when they vibe. Nokia is supposed to call me today at 230 pm to discuss the camera issue, and the volume buttons not working with lock screen, and the vibra units sounding defective.
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?
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 bought this used s9 for quite affordable price. Everything looked fine during testing except a greenish shade which happens only when unlocked and happens for like a second.
On searching internet, i found threads, yt videos by a number of people, almost all claiming that it is an update consequence. My questions are
1. Is it a software issue? If yes, can I expect some wayto solve - official ota or root and custom or old rom (if possible at all)?
2. If not software issue, is it a software induced hardware issue? Any way to repair without paying full for display?
2.1 If i get it replaced somehow, will itcome back again?
3. In any case, if I don't get it repaired, how long can I expect the deviceto be functional; ie before this green shade becomes permanent instead of being intermittent making device unusable?
Thank you
If it only happens for a second the only thing I be concerned about by the possibility of a rootkit or virus.
If running on Android 9 or higher and you did a factory reset already, that should have killed any unwanted critters.
Do a display check with ScreenTest. If it passes it should be good to go and just a transient glitch.
You've heard of The Matrix, right?
blackhawk said:
If it only happens for a second the only thing I be concerned about by the possibility of a rootkit or virus.
If running on Android 9 or higher and you did a factory reset already, that should have killed any unwanted critters.
Do a display check with ScreenTest. If it passes it should be good to go and just a transient glitch.
You've heard of The Matrix, right?
Click to expand...
Click to collapse
Hahah
This is something different. I asked a reseller and he said that such displays may last anywhere from 1 hour to 1 year.
Internet is filled with such questions.
Can you please help answering other questions if not this one, like if downgrading to older android possible or not?
The green only lasts for a second or so when opening the lock screen?
Never any other time?
Then it's not hardware.
AMOLED displays can last for many years. ScreenTest gives you a good idea of it's condition. Generally failure is gradual with the blue pixels failing first, red last.
The boot loader version dictates if you can downgrade or not.
...
blackhawk said:
The green only lasts for a second or so when opening the lock screen?
Never any other time?
Then it's not hardware.
AMOLED displays can last for many years. ScreenTest gives you a good idea of it's condition. Generally failure is gradual with the blue pixels failing first, red last.
The boot loader version dictates if you can downgrade or not.
Click to expand...
Click to collapse
So far, only immediately after unlocking. Haven't used much tho.
People say temp fix to all such issues is to Enable Always On display and double tap to wake screen instead of using Power button.
Can you ease tell which ScreenTest app it is? Playstore shows several with similar names.
tarun0 said:
So far, only immediately after unlocking. Haven't used much tho.
People say temp fix to all such issues is to Enable Always On display and double tap to wake screen instead of using Power button.
Can you ease tell which ScreenTest app it is? Playstore shows several with similar names.
Click to expand...
Click to collapse
Like I said if it's transient it's no issue.
This is the one I use:
Hi.
My s9 has this problem which everything turns green or worst, depending on the brightness level.
I can repeat the bug 100% of the time: just use the power button to turn off the phone two times: one to put into black screen and again to turn on. Then the screen misses some horizontal lines and is all buggy.
I shall record a video to share my problem but again, this can only be avoided by using aways on display to turn on the phone and then all goes back to normal.
spamtoaster said:
Hi.
My s9 has this problem which everything turns green or worst, depending on the brightness level.
I can repeat the bug 100% of the time: just use the power button to turn off the phone two times: one to put into black screen and again to turn on. Then the screen misses some horizontal lines and is all buggy.
I shall record a video to share my problem but again, this can only be avoided by using aways on display to turn on the phone and then all goes back to normal.
Click to expand...
Click to collapse
Try clearing the system cache.
A hard reboot.
Try in safe mode.
A factory reset may help but if that fails try flashing to the same version. If Android 8 or lower it could be caused by a rootkit that a factory reset won't purged. However this isn't a typical symptom nonetheless the firmware maybe corrupted.
If none of the above works it's a hardware failure, likely the display.