It is about the soft of JS Landscape.
IS anybody had used the soft of JS Landscape that it's an adjustment ppc show software, you can rotate the screen orientation, you can also adjust the screen resolution. Makes you more suited to their browsing habits to use ppc, it supports 320 * 240/480 * 320/640 * 480/800 * 600 standard resolution, you can set yourself.
It can work well in WM2003 but can't work in WM6.X .
Hello everyone.
I would like to help one, I'm white screen problem on my device, it connects but the screen just turns white, I think it's just wrong ROM problem.
These are the specifications of the unit, who are the manufacturer's website:
Processor - 460 MHz 3611 Hisilicon k3
MHz - ROM: 256 MB
RAM: 128 MB DDR
Type LCD display - 2.8 inch TFT-LCD touch screen.
Resolution - 240 x 320 resolution with 65.536 colors
Alignment - Portrait and landscape.
Functionality - GSM / GPRS / EDGE: Quad-band (850, 900, 1800, and 1900MHz).
Type - 2.0 Megapixel CMOS color camera with mechanical macro function definition
Definition - Photo: 1600x1200 (UXGA), 1280x960 (SXGA), 640x480 (VGA), 320x240 (QVGA)
(QQVGA)
Video: 160x120, 176x144 (QCIF), 128x96 Zoom (SubQCIF)
Digital zoom - Up to 10X
the device name is Aegis Kaiomy 1288.
Please could someone provide me a ROM compatible with this device?
I can use the RTD Firstaidkit and to change the device ROM, although the screen goes blank when I turn it works normally, it can synchronize with activesync
I believe this should be a similar device with the T3238 processor described above, a rom like this unit, I think it should work.
Thank you in advance.
White screen
Hi do you resolve your probleme? I have the same now...
Thank you!
I've always used ui tuner, and i've used 289 ppi for more screen estate. But a z3 runs a 1080 screen at 424 ppi. So we know the hardware in the z3c can that. But i can't set my dpi to 424 as it would make everything larger and not smaller. So i have to use negative ppi. So i go from 320 to 289. When i lower the ppi it makes things smaller which also means the hardware has to draw more content.
But how do you figure out the relation between these. How does 289 ppi on 720 resolution relate to 1080 at 424 ppi?
Does this even make sense to you ?
System and apps use both resolution and dpi values to determine screen size, so they can figure out how much space to dedicate for interface stuff (bars, etc).
size (inches) = resolution (pixels) / dpi (pixels / inch) = (resolution / dpi) inches
The bigger the screen size, the more “zoomed out” default/interface view a device usually has.
The pitiful thing with certain world wide web sites is they use this information to determine your screen size and decide zoom level, usually resulting in jackassilly bigass screen items and little onscreen content, sometimes further sabotaged with squatter behemoth search bars and dumbass Twitsh1t and Fakeb00k buttons.
In my honest opinion, this is kind of stupid. I prefer fully zoomed out classic desktop pages, I'll zoom in where required, thanks.
Cheers :laugh:
- Please install this app on your phone > https://play.google.com/store/apps/details?id=com.crystalmissions.dpichecker
- Set display size to default settings
- Open DPI Checker app
- Take a screenshot (Volume Down + Power Button)
- Post Screenshot here (Under the 'Attach Files' Section)
After the latest update, about a week or two ago, I noticed a fuzziness to my display with jagged icon edges and odd font sizes. I downloaded the above app, and when I opened it, it stated something like 320x533, I really cant remember, but it was a really far off display density from the Moto E4 Plus' reported 720p - 720x1280.
I just want to see if other are having this issue or if it was just me. Thanks.
The below screenshot is an example. I have already set my display back to 720x1280.
Code:
adb shell
Code:
wm size 720x1280
Code:
wm density 320
Anybody?
I can't seem to find the attachments button
photos.app.goo.gl/Tu7PhsYgOxX1NM0y2
Hmmm... Wonder why my display is so off...
Thanks for posting.
@qweedleguy screenshot:
Hey folks,
I am using this module to enable AA on my BMW headunit:
a.aliexpress.com/_U4Jz5
It kinda works nice except for one thing, resolution is not so clear due to dpi settings. Someone else dug into the system and found that in
etc/androidauto/androidauto_config.xml
The resolution is set to 480p instead of 720p and dpi is set to 150 instead of 180.
We have no SSH access but can only upload .bin update files as we dont know the password.
Does anyone know if it would be possible to change 720p to true and up the dpi somehow?
Carplay apparantly is 720p on this unit.
<DisplayWindow><!-- Head Unit side configuration--> <X_Coordinate value="0"/> <Y_Coordinate value="0"/> <DisplayWidth value="1280"/> <DisplayHeight value="480"/> </DisplayWindow> <Display><!-- Phone side configuration--> <DisplayWidth value="232"/><!-- Physical width--> <DisplayHeight value="87"/><!-- Physical height--> <Density value="170"/> <RealDensity value="153"/> <ViewingDistance value="400"/> <Resolution480P value="true"><!-- fps: 30 or 60--> <fps value="30"/> </Resolution480P> <Resolution720P value="false"> <fps value="30"/> </Resolution720P>
Nobody?
Anyone?
Do you have a copy of the BIN? My guess is unpacking and repacking the BIN will be the hardest part of this. You probably won't be able to do this without source scripts. You are in the right place regarding the XML file inside. All android head units, regardless of what they are, have to tell our phones what resolution to serve up. If the head unit says to run 1024x600 then that is what you are getting.
An alternative would be to ask the manufacture to release an update set to the proper settings.
---------- Post added at 09:12 PM ---------- Previous post was at 09:09 PM ----------
Here you go The Andream unit you have should likely work with one of these firmwares. Do a lot of reading there before you proceed. I cannot be responsible for you flashing the wrong software to your unit.
I have a similar unit to yours and was able to get mine running at the proper resolution.
@heresy_fnord, when you say the proper resolution, what resolution are you referring to? I have the Andream (version: NBT-02B) unit myself, and flashed the latest .BIN with the AA Widescreen fix, but I feel the scale is slightly off. Text and elements are too small compared to the screen size (I have 8.8", 1280x480).
ckarv said:
@heresy_fnord, when you say the proper resolution, what resolution are you referring to? I have the Andream cool:unit myself, and flashed the latest .BIN with the AA Widescreen fix, but I feel the scale is slightly off. Text and elements are too small compared to the screen size (I have 8.8", 1280x480).
Click to expand...
Click to collapse
OK, my guess is the physical screen size is the issue. If you are certain the 8.8" screen also runs 1280x480 then the settings for DPI are probably not appropriate. Here is what I see for a 10.25" screen:
<Display>
<DisplayWidth value="244"/> 244mm is 9.6" width
<DisplayHeight value="92"/> 92mm is 3.62" height
<WidthMargin value="0"/>
<HeightMargin value="0"/>
<Density value="220"/>
<RealDensity value="133"/> This calculator indicates a real density of just a hair over 133PPI
So for example, your real density should be set to 155PPI based on that logic. I don't know what your update file was set to. I don't know what your display width and height should be set to since I don't know how the 8.8" screen measures length and width. Finally, I think they are setting the Density of the widescreen fixed update to 210 and you might try 220 which is as big as it can be set before it cuts back over to the non-widescreen view, and see if that works.
heresy_fnord said:
OK, my guess is the physical screen size is the issue. If you are certain the 8.8" screen also runs 1280x480 then the settings for DPI are probably not appropriate. Here is what I see for a 10.25" screen:
<Display>
<DisplayWidth value="244"/> 244mm is 9.6" width
<DisplayHeight value="92"/> 92mm is 3.62" height
<WidthMargin value="0"/>
<HeightMargin value="0"/>
<Density value="220"/>
<RealDensity value="133"/> This calculator indicates a real density of just a hair over 133PPI
So for example, your real density should be set to 155PPI based on that logic. I don't know what your update file was set to. I don't know what your display width and height should be set to since I don't know how the 8.8" screen measures length and width. Finally, I think they are setting the Density of the widescreen fixed update to 210 and you might try 220 which is as big as it can be set before it cuts back over to the non-widescreen view, and see if that works.
Click to expand...
Click to collapse
I've put some effort into looking into this now, basically reading 100 odd pages in the "Andream MMI Box - Wireless CarPlay & Android Auto" thread (starting on pg. 135), over at the Bimmerpost forum.
Findings:
- 720p = true setting is required to display AA in "Wide" format (ie. clock, second app on the right side of the display, map and vertical bar with "home", active app, notification and assistant buttons on the left).
- From reading results of testing over at the other forum, the Physical width/height settings did not seem to make a difference to output.
- Density on the other hand is used to scale the elements on screen, and this also impacts readability and sharpness of the objects/text.
-- from some testing, the conclusion was that "200" is the optimum value for the 1280x480, 8.8" screen, although eg. "210" was tested.
-- unsure if changing "Real Density" will make a difference to output (similar to physical measurements)
* Also, I think my scale is correct, or as specified in the firmware. Text and elements just seems so small compared to CarPlay that wife uses.
* Attached a picture of my screen with 200 dpi.
You are using a "Density" value of 220, do you have an example of what that looks like in practice?
Thanks
ckarv said:
I've put some effort into looking into this now, basically reading 100 odd pages in the "Andream MMI Box - Wireless CarPlay & Android Auto" thread (starting on pg. 135), over at the Bimmerpost forum.
Findings:
- 720p = true setting is required to display AA in "Wide" format (ie. clock, second app on the right side of the display, map and vertical bar with "home", active app, notification and assistant buttons on the left).
- From reading results of testing over at the other forum, the Physical width/height settings did not seem to make a difference to output.
- Density on the other hand is used to scale the elements on screen, and this also impacts readability and sharpness of the objects/text.
-- from some testing, the conclusion was that "200" is the optimum value for the 1280x480, 8.8" screen, although eg. "210" was tested.
-- unsure if changing "Real Density" will make a difference to output (similar to physical measurements)
* Also, I think my scale is correct, or as specified in the firmware. Text and elements just seems so small compared to CarPlay that wife uses.
* Attached a picture of my screen with 200 dpi.
You are using a "Density" value of 220, do you have an example of what that looks like in practice?
Thanks
Click to expand...
Click to collapse
- 720p = true setting is required to display AA in "Wide" format (ie. clock, second app on the right side of the display, map and vertical bar with "home", active app, notification and assistant buttons on the left).
This is accurate.
- From reading results of testing over at the other forum, the Physical width/height settings did not seem to make a difference to output.
I don't know, perhaps this is true.
- Density on the other hand is used to scale the elements on screen, and this also impacts readability and sharpness of the objects/text.
-- from some testing, the conclusion was that "200" is the optimum value for the 1280x480, 8.8" screen, although eg. "210" was tested.
-- unsure if changing "Real Density" will make a difference to output (similar to physical measurements)
* Also, I think my scale is correct, or as specified in the firmware. Text and elements just seems so small compared to CarPlay that wife uses.
Your scale of text is set by the DPI essentially. Its a combination of resolution and DPI. Basic example, if I was to set my DPI to 200, the text on my screen would be smaller.
* Attached a picture of my screen with 200 dpi.
This is a 10.25" screen with 220DPI
In your case, the one update file was made for a 10.25" screen. The thing is, there will be a DPI difference between the two even if the resolution is the same. I suspect you need check with that community to see if there is an update that maintains widescreen mode but uses the different DPI.
EDIT: To be fair, I think your screen looks "normal" but then, it looks like your clock and such are the same scale as mine. Maybe AA is just smaller text in general?