Database Info

hdmi 1080p to hdtv

i read in nvidia developer forum that you can set manually a resolution of hdmi when is attached to hdtv.
the procedure is:
Examples:
To set the resolution to 1680x1050 with an HDMI monitor:
adb wait-for-device
adb shell setprop persist.tegra.dpy5.mode.width 1680
adb shell setprop persist.tegra.dpy5.mode.height 1050
adb shell reboot
To set the resolution to 1280x1024 with a CRT monitor:
adb wait-for-device
adb shell setprop persist.tegra.dpy3.mode.width 1280
adb shell setprop persist.tegra.dpy3.mode.height 1024
adb shell reboot
is working for you?
you can create a tool to change the resolution without adb?
p.s. you can reboot for apply the new resolution

On my Note3 running Lollipop I was able to check for supported external resolutions by running ( via a terminal app or adb shell )
Code:
>dmesg
and ( filtering with grep ) looking for the lines:
Code:
<6>[ 581.051746] hdmi_edid_add_sink_video_format: EDID: format: 1 [640x480 p60 4/3], Supported
<6>[ 581.051756] hdmi_edid_add_sink_video_format: EDID: format: 1 [640x480 p60 4/3], Supported by MHL
<6>[ 581.051767] hdmi_edid_add_sink_video_format: EDID: format: 16 [1920x1080 p60 16/9], Supported
<6>[ 581.051777] hdmi_edid_add_sink_video_format: EDID: format: 16 [1920x1080 p60 16/9], Not-Supported by MHL
<6>[ 581.051790] hdmi_edid_add_sink_video_format: EDID: format: 4 [1280x 720 p60 16/9], Supported
<6>[ 581.051801] hdmi_edid_add_sink_video_format: EDID: format: 4 [1280x 720 p60 16/9], Supported by MHL
<6>[ 581.051812] hdmi_edid_add_sink_video_format: EDID: format: 133 [1280x1024 p60 5/4], Not-Supported
<6>[ 581.051822] hdmi_edid_add_sink_video_format: EDID: format: 133 [1280x1024 p60 5/4], Not-Supported by MHL
<6>[ 581.051833] hdmi_edid_add_sink_video_format: EDID: format: 132 [1024x768 p60 4/3], Not-Supported
<6>[ 581.051843] hdmi_edid_add_sink_video_format: EDID: format: 132 [1024x768 p60 4/3], Not-Supported by MHL
which you'll note correspond to supported resolutions in:
Code:
>cat /sys/devices/virtual/graphics/fb1/edid_modes
1,4
then select your preferred output using :
Code:
>setprop hw.hdmi.resolution 1
and then re-plug the mhl adapter.
which in my case resulted in 640x480 which was the only option supported by my 800x600 projector.
Thanks to this stackexchange post.

[Q] Allwinner A13 nuclear_evb touch screen driver

I have tried to get my touch screen working after completely bricking my china tablet. Managed to get stable ROM+kernel running, but the touch screen isn't working.
http://forum.xda-developers.com/showthread.php?t=2343531
that is what I am running, but none of those screen drivers worked. It gave error;
Verifying update package...
E:signature verification failed
Installation aborted.
My device is black on the screen side and the backplate is white and it has metal stripe on the back. Also it has 760 written inside the backplate.
It is Wi-Fi only model with front camera.
I may be able to give you further info if I can get my mouse plugged and working to the tablet.
Thanks in advance. :highfive:

Here is my lsmod data
[email protected]:/ $ su
[email protected]:/ # lsmod
8192cu 575431 0 - Live 0x00000000
8188eu 581006 0 - Live 0x00000000
rtl8150 10305 0 - Live 0x00000000
mcs7830 7581 0 - Live 0x00000000
qf9700 9152 0 - Live 0x00000000
asix 24601 0 - Live 0x00000000
sun5i_csi0 33255 0 - Live 0x00000000
cedarx 11869 0 - Live 0x00000000
ov5640 31583 0 - Live 0x00000000
mt9m112 15359 0 - Live 0x00000000
gt2005 19412 0 - Live 0x00000000
gc0308 18408 1 - Live 0x00000000
videobuf_dma_contig 6251 1 sun5i_csi0, Live 0x00000000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0x00000000
mma7660 6857 0 - Live 0x00000000
mxc622x 6088 1 - Live 0x00000000
mecs 4078 1 - Live 0x00000000
bma250 7545 0 - Live 0x00000000
dmard06 7987 0 - Live 0x00000000
ft5x_ts 44577 0 - Live 0x00000000
mali 150572 12 - Live 0x00000000
ump 48978 23 mali, Live 0x00000000
hid_sony 2377 0 - Live 0x00000000
hid_gaff 2817 0 - Live 0x00000000
xpad 9358 0 - Live 0x00000000

murmeli said:
Here is my lsmod data
[email protected]:/ $ su
[email protected]:/ # lsmod
8192cu 575431 0 - Live 0x00000000
8188eu 581006 0 - Live 0x00000000
rtl8150 10305 0 - Live 0x00000000
mcs7830 7581 0 - Live 0x00000000
qf9700 9152 0 - Live 0x00000000
asix 24601 0 - Live 0x00000000
sun5i_csi0 33255 0 - Live 0x00000000
cedarx 11869 0 - Live 0x00000000
ov5640 31583 0 - Live 0x00000000
mt9m112 15359 0 - Live 0x00000000
gt2005 19412 0 - Live 0x00000000
gc0308 18408 1 - Live 0x00000000
videobuf_dma_contig 6251 1 sun5i_csi0, Live 0x00000000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0x00000000
mma7660 6857 0 - Live 0x00000000
mxc622x 6088 1 - Live 0x00000000
mecs 4078 1 - Live 0x00000000
bma250 7545 0 - Live 0x00000000
dmard06 7987 0 - Live 0x00000000
ft5x_ts 44577 0 - Live 0x00000000
mali 150572 12 - Live 0x00000000
ump 48978 23 mali, Live 0x00000000
hid_sony 2377 0 - Live 0x00000000
hid_gaff 2817 0 - Live 0x00000000
xpad 9358 0 - Live 0x00000000
Click to expand...
Click to collapse
hi the lsmod wont be any good unless it was run on a firmware with a working touchscreen... as this this only shows loaded modules etc... so if your ts was not working it wont tell us the name of the correct driver for your TS..
so was this run on a firmware with a working TS??

Inside 4ndroid said:
so was this run on a firmware with a working TS??
Click to expand...
Click to collapse
No I used mouse & keyboard, the device is nuclear_evb, but I can't find drivers for that exact model

murmeli said:
No I used mouse & keyboard, the device is nuclear_evb, but I can't find drivers for that exact model
Click to expand...
Click to collapse
right i need to explain something before we carry on basically the nuclear_evb is just a name there are 1000's of tablets with same name but different hardware as they are clones.. (cheap chinese knock offs)
now because you do not have a firmware with a working touchscreen when you run lsmod it doesnt actually tell us your TS driver because the correct driver is not a loaded module..
the only way to find a working driver is to test every driver you can out there or go through all firmwares one by one until you find one where the TS works and then run lsmod on that firmware to find out your TS driver..
i hope this makes sense...
if you need access to a full range of firmwares for these tablets you could visit my support forum and sign up for a free account..
www.insideforums.tk

[Q] YFTECH ME-12 Development Help

Hello everyone!
I have been trying to compile a cyanogenmod kernel and rom for a cheap chinese tablet: yftech-me12. A clone of that tablet is Arnova 7h G3.
Tablet specs:
Capacity • Flash memory: 4 GB*
• Expandable via micro SDHC Slot up to 32 GB
Operating system • ANDROID™ 4.0 “Ice Cream Sandwich”
Processor • ARM Cortex A8 @ 1 GHz
RAM • 512 MB
Display characteristics • 7 inch - Capacitive points MultiTouch Screen 16 million colors
• 800 x 480 screen resolution
Video Playback1 • H.264, MPEG-42 up to 1080p resolution
With the above codecs, the device can play video files with the following extensions: .avi .mp4 and mkv
Audio Playback1 • MP3, WAV, APE, OGG, FLAC
Photo viewer3 • JPEG, BMP, GIF, PNG
Interfaces • Micro USB slave 2.0
• Audio Jack 3.5mm
• Micro SD slot
Communication protocols • WiFi
Miscellaneous • Front camera
• Built-in speaker
• Microphone
• G-sensor
I have downloaded the kernel source code from arnova.. Compiled the stock kernel to make sure it works and it does..
My problem is that i cannot compile a cyanogenmod kernel for my device! errors i cannot even understand!!
I've tried to install cyanogenmod for allwinner a13 tablets from here: http://forum.xda-developers.com/showthread.php?p=43072957
but the kernel will not boot! Plus i had to delete a few apks because my system partition is approx. 260mb and it would not copy the /system since there was not enough free space!
some other details about my device such as lsmod output:
8188eu 621096 0 - Live 0xbf103000
YFdecrypt 22118 0 - Live 0xbf0f8000
kt080x 5983 0 - Live 0xbf0f3000
mc32x0 7726 0 - Live 0xbf0ed000
dmt0567 10125 0 - Live 0xbf0e6000
bma250 7521 0 - Live 0xbf0e0000
byd693x_ts 9491 0 - Live 0xbf0d9000
pixcir_jc 13381 0 - Live 0xbf0d1000
sitronix_ts 23687 0 - Live 0xbf0c6000
goodix_gt82x 21242 0 - Live 0xbf0bc000
rtl8150 10305 0 - Live 0xbf0ab000
mcs7830 7589 0 - Live 0xbf0a5000
qf9700 9152 0 - Live 0xbf09e000
asix 24601 0 - Live 0xbf092000
usbnet 26253 3 mcs7830,qf9700,asix, Live 0xbf085000
sun5i_csi0 33604 0 - Live 0xbf077000
hi704 19664 1 - Live 0xbf06e000
hi253 21036 0 - Live 0xbf064000
videobuf_dma_contig 6251 1 sun5i_csi0, Live 0xbf05f000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0xbf055000
cedarx 9479 0 - Live 0xbf04e000
mali 151198 10 - Live 0xbf01c000
ump 48898 19 mali, Live 0xbf009000
sw_ts 18329 0 - Live 0xbf000000
cat /proc/partitions output:
ajor minor #blocks name
93 0 16384 nanda
93 8 2048 nandb
93 16 32768 nandc
93 24 262144 nandd
93 32 1048576 nande
93 40 1024 nandf
93 48 32768 nandg
93 56 261120 nandh
93 64 1024 nandi
93 72 2232320 nandj
93 73 2231296 nandj1
179 0 3872256 mmcblk0
179 1 3122070 mmcblk0p1
179 2 500000 mmcblk0p2
179 3 249007 mmcblk0p3
dumps of my partitions /system /boot etc. : http://www69.zippyshare.com/v/97403369/file.html
Could someone PLEASE help me out.. I used a13_nuclear_defconfig from my stock kernel's source code to compile cm kernel and i get errors that it can not find certain files in the /drivers section.. copied files from stock source code and then some other errors occured.. so it fails..
Could someone give me some pointers? How do you guys start porting a rom to a new device without ANY previous support? Do you rewrite the modules source code to fit the cm kernel? how do you configure/find ramdisks to pack with your zlimage? can i use stock ramdisk with cyanogenmods lzimage to boot my device?
I'm not a developer and i just started learning about compiling kernels and modules etc..
STOCK ICS 4.03 is VERY SLOW even with nothing installed..
I hoped that Cyanogenmod 10 would run better on my device that's why i started all this but i'm seriously stuck...
Thanks in advance!!

inject touch screen modules (compability patch)

Hello everyone,
I has a Chinese tablet "luxya MID702-sc" with the base android 4.0.4.
I find many rom cyanogenmod 4.2.2,4.1.2 but the modules are not the same results the touch screen does not respond.
I adb install and uberizer to retrieve the list of modules, I have to recover the original rom but I still can not inject a properly ...
Here are the modules loaded in the original version:
Modules:
mxc622x 6326 1 - Live 0xbf153000
mecs 4078 2 - Live 0xbf14f000
rtl8150 10305 0 - Live 0xbf148000
mcs7830 7581 0 - Live 0xbf142000
qf9700 9152 0 - Live 0xbf13b000
asix 24601 0 - Live 0xbf12f000
sun5i_csi0 33271 0 - Live 0xbf121000
gt2005 36907 0 - Live 0xbf111000
gc0308 22312 1 - Live 0xbf107000
videobuf_dma_contig 6251 1 sun5i_csi0, Live 0xbf102000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0xbf0f8000
cedarx 9351 0 - Live 0xbf0f1000
mali 115122 8 - Live 0xbf0c7000
ump 34209 11 mali, Live 0xbf0b8000
byd693x_ts 9094 0 - Live 0xbf043000
zet622x 19182 0 - Live 0xbf035000
ssd253x_ts 21452 0 - Live 0xbf02b000
ft5x_ts 93593 0 - Live 0xbf004000
inet_ctp 2227 4 byd693x_ts,zet622x,ssd253x_ts,ft5x_ts, Live 0xbf000000
_________________________________________
cyanogenmod 10 release:
Modules:
8188eu 581006 0 - Live 0x00000000
rtl8150 10305 0 - Live 0x00000000
mcs7830 7581 0 - Live 0x00000000
qf9700 9152 0 - Live 0x00000000
asix 24601 0 - Live 0x00000000
cedarx 11869 0 - Live 0x00000000
videobuf_dma_contig 6251 0 - Live 0x00000000
videobuf_core 20242 1 videobuf_dma_contig, Live 0x00000000
mali 150572 8 - Live 0x00000000
ump 48978 11 mali, Live 0x00000000
mxc622x 6088 0 - Live 0x00000000
mecs 4078 1 - Live 0x00000000
sp0838 20079 0 - Live 0x00000000
gc0329 18016 0 - Live 0x00000000
gc0308 18408 0 - Live 0x00000000
ft5x_ts 44577 0 - Live 0x00000000
hid_sony 2377 0 - Live 0x00000000
hid_gaff 2817 0 - Live 0x00000000
xpad 9358 0 - Live 0x00000000
I need some help to find out what drivers ts is used and created a patch with these modules for injection, I tested many patch and its still not working I think there are missing modules. ..
here is the rom I try to install:
http://forum.xda-developers.com/showthread.php?t=2343531
sorry for my english :android-displeased:

Need help with A13 tablet Android 4.0.4

Hi guys
I have a A13 7 inch chinese tablet which got stuck on the logo and wont boot. Looking around forums I learned I need to know the kind of G sensor, camera, and TS my tablet has. Typing a couple of commands I got this. I'd like someone to tell me which are the sensors appropriate for my tablet so I can look for the right firmware. Any help would be very appreciated
export PATH=/data/local/bin:$PATH
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ lsmod
cdc_subset 1588 0 - Live 0xbf0e9000
cdc_eem 2915 0 - Live 0xbf0e5000
cdc_ether 7651 0 - Live 0xbf0df000
rtl8150 10305 0 - Live 0xbf0d8000
mcs7830 7581 0 - Live 0xbf0d2000
qf9700 9152 0 - Live 0xbf0cb000
asix 24601 0 - Live 0xbf0bf000
usbnet 26229 6 cdc_subset,cdc_eem,cdc_ether,mcs7830,qf9700,asix, Live 0xbf0b2000
sun5i_csi0 30803 0 - Live 0xbf0a5000
gt2005 20634 1 - Live 0xbf09b000
gc0308 18408 1 - Live 0xbf092000
videobuf_dma_contig 6251 1 sun5i_csi0, Live 0xbf08d000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0xbf083000
cedarx 9351 0 - Live 0xbf07c000
mali 150902 4 - Live 0xbf04a000
ump 49026 15 mali, Live 0xbf037000
mma7660 7219 0 - Live 0xbf031000
ssd2533_ts 9832 0 - Live 0xbf02a000
nt11003 50228 0 - Live 0xbf019000
goodix_ts 13732 0 - Live 0xbf011000
ft5x_ts 45793 0 - Live 0xbf000000
[email protected]:/ $
---------------------------
[email protected]:/ # getevent
getevent
add device 1: /dev/input/even
name: "mma7660"
add device 2: /dev/input/even
name: "ssd253x_ts"
add device 3: /dev/input/even
name: "sun4i-keyboard"
could not get driver version
add device 4: /dev/input/even
name: "axp20-supplyer"