#101
|
||||
|
||||
Ami me pasa exactamente lo mismo, a parte de que en la 4919712 la camara tampoco funciona, yo tambien he decidido volverme a la 20120409, aunque hay la mitad de app en market y vaya mas lenta, pero es lo que hay..si alguie supiera alguna solucion, bienvenido sea.
http://www.htcmania.com/showthread.p...=1#post4933840 Para ver si sale alguna solucion a el problema de actualizar a la compilacion 4919712 |
|
#102
|
||||
|
||||
pues no instalé el protab test.
No lo hice porque directamente instalé la cyanogen que ya pones en el post que está parcheada para la protab, por lo tanto en teoria no hace falta. Ahora lo que he hecho es modificar el boot.img y crear un zip con este bootimg mas los modules pero me falta saber como grabarlo, necesito crear lo de la carpeta META.... y no se si hay que seguir algun protocolo para ello, he mirado esta carpeta en otros zips y hay hasta una secuencia de comandos batch que no entiendo bien bien como deberia ser. Saludos |
#103
|
||||
|
||||
Tranqui la comunidad es eso gente que se encuentra y al final actuan todos a uno para mejorar un bien comun.
Estos son los modulos que carga nuestra tablet al iniciar ,me refiero con la cyanogem,todo esta escrito en el initsun4i.rc esta en la raiz de la tabla editalo y veras los modulos de los dispositivos que carga,modulo tactil, on boot insmod /system/vendor/modules/ump.ko ( Son drivers para la mali ) insmod /system/vendor/modules/mali.ko insmod /system/vendor/modules/ft5x_ts.ko insmod /system/vendor/modules/goodix_touch_3F.ko ( drivers o modulos de la pantalla tactil ) insmod /system/vendor/modules/bma250.ko (sensor drivers) insmod /system/vendor/modules/videobuf-core.ko insmod /system/vendor/modules/videobuf-dma-contig.ko insmod /system/vendor/modules/gc0308.ko insmod /system/vendor/modules/gt2005.ko insmod /system/vendor/modules/sun4i_csi0.ko insmod /system/vendor/modules/usbnet.ko insmod /system/vendor/modules/asix.ko insmod /system/vendor/modules/qf9700.ko insmod /system/vendor/modules/mcs7830.ko insmod /system/vendor/modules/rtl8150.ko on post-fs-data mkdir /data/misc/sensors 0777 system system El resultado es que tengo una rom modificada porque lo he comprobado editando el rc en la tablet y viendo que los ko estan cargados como Inmod, pero giro la tablet y ni caso Vamos, que algo más toca cambiar y no solo los drivers... alguna idea?
__________________
HectorziN
|
#104
|
||||
|
||||
Mira a ver si los módulos que has cambiado corresponden a la compilación del Kernel del boot.img (3.0.8, 3.0.8+...)
Otra cosa.... dentro de system.img, en etc hay carpeta llamada permissions con archivos xml, que son los que dan permisos al hardware, mira si dentro hay un archivo llamado android.hardware.sensor.accelerometer.xml con la linea: <permissions> <feature name="android.hardware.sensor.accelerometer" /> </permissions> Otro que se llama platform.xml, en su interior: <permissions> <feature name="android.hardware.location" /> <!-- feature name="android.hardware.location.network" --> <!-- feature name="android.hardware.sensor.compass" --> <feature name="android.hardware.sensor.accelerometer" /> <feature name="android.hardware.touchscreen" /> <feature name="android.hardware.touchscreen.multitouch" /> <feature name="android.hardware.touchscreen.multitouch.dist inct" /> <feature name="android.hardware.microphone" /> <feature name="android.hardware.screen.portrait" /> <feature name="android.hardware.screen.landscape" /> <!-- devices with GPS must include android.hardware.location.gps.xml --> <!-- devices with a rear-facing camera must include one of these as appropriate: android.hardware.camera.xml or android.hardware.camera.autofocus.xml or android.hardware.camera.autofocus-flash.xml --> <!-- devices with a front facing camera must include android.hardware.camera.front.xml --> <!-- devices with WiFi must also include android.hardware.wifi.xml --> <!-- devices with an ambient light sensor must also include android.hardware.sensor.light.xml --> <!-- devices with a proximity sensor must also include android.hardware.sensor.proximity.xml --> <!-- devices with a barometer must also include android.hardware.sensor.barometer.xml --> <!-- devices with a gyroscope must also include android.hardware.sensor.gyroscope.xml --> <!-- GSM phones must also include android.hardware.telephony.gsm.xml --> <!-- CDMA phones must also include android.hardware.telephony.cdma.xml --> </permissions> Y otro tablet_core_hardware.xml, en su interior: <permissions> <!-- ================================================== ================ --> <!-- ================================================== ================ --> <!-- ================================================== ================ --> <!-- The following tags are associating low-level group IDs with permission names. By specifying such a mapping, you are saying that any application process granted the given permission will also be running with the given group ID attached to its process, so it can perform any filesystem (read, write, execute) operations allowed for that group. --> <permission name="android.permission.BLUETOOTH_ADMIN" > <group gid="net_bt_admin" /> </permission> <permission name="android.permission.BLUETOOTH" > <group gid="net_bt" /> </permission> <permission name="android.permission.INTERNET" > <group gid="inet" /> </permission> <permission name="android.permission.CAMERA" > <group gid="camera" /> </permission> <permission name="android.permission.READ_LOGS" > <group gid="log" /> </permission> <permission name="android.permission.WRITE_EXTERNAL_STORAGE" > <group gid="sdcard_rw" /> </permission> <permission name="android.permission.WRITE_MEDIA_STORAGE" > <group gid="media_rw" /> </permission> <permission name="android.permission.ACCESS_MTP" > <group gid="mtp" /> </permission> <permission name="android.permission.NET_ADMIN" > <group gid="net_admin" /> </permission> <!-- The group that /cache belongs to, linked to the permission set on the applications that can access /cache --> <permission name="android.permission.ACCESS_CACHE_FILESYSTEM" > <group gid="cache" /> </permission> <!-- RW permissions to any system resources owned by group 'diag'. This is for carrier and manufacture diagnostics tools that must be installable from the framework. Be careful. --> <permission name="android.permission.DIAGNOSTIC" > <group gid="input" /> <group gid="diag" /> </permission> <!-- Group that can read detailed network usage statistics --> <permission name="android.permission.READ_NETWORK_USAGE_HISTOR Y"> <group gid="net_bw_stats" /> </permission> <!-- Group that can modify how network statistics are accounted --> <permission name="android.permission.MODIFY_NETWORK_ACCOUNTING "> <group gid="net_bw_acct" /> </permission> <!-- ================================================== ================ --> <!-- ================================================== ================ --> <!-- ================================================== ================ --> <!-- The following tags are assigning high-level permissions to specific user IDs. These are used to allow specific core system users to perform the given operations with the higher-level framework. For example, we give a wide variety of permissions to the shell user since that is the user the adb shell runs under and developers and others should have a fairly open environment in which to interact with the system. --> <!-- Standard permissions granted to the shell. --> <assign-permission name="android.permission.WRITE_EXTERNAL_STORAGE" uid="shell" /> <assign-permission name="android.permission.SEND_SMS" uid="shell" /> <assign-permission name="android.permission.CALL_PHONE" uid="shell" /> <assign-permission name="android.permission.READ_CONTACTS" uid="shell" /> <assign-permission name="android.permission.WRITE_CONTACTS" uid="shell" /> <assign-permission name="android.permission.READ_CALENDAR" uid="shell" /> <assign-permission name="android.permission.WRITE_CALENDAR" uid="shell" /> <assign-permission name="android.permission.READ_USER_DICTIONARY" uid="shell" /> <assign-permission name="android.permission.WRITE_USER_DICTIONARY" uid="shell" /> <assign-permission name="android.permission.ACCESS_FINE_LOCATION" uid="shell" /> <assign-permission name="android.permission.ACCESS_COARSE_LOCATION" uid="shell" /> <assign-permission name="android.permission.ACCESS_LOCATION_EXTRA_COM MANDS" uid="shell" /> <assign-permission name="android.permission.ACCESS_NETWORK_STATE" uid="shell" /> <assign-permission name="android.permission.ACCESS_WIFI_STATE" uid="shell" /> <assign-permission name="android.permission.BLUETOOTH" uid="shell" /> <!-- System tool permissions granted to the shell. --> <assign-permission name="android.permission.GET_TASKS" uid="shell" /> <assign-permission name="android.permission.CHANGE_CONFIGURATION" uid="shell" /> <assign-permission name="android.permission.REORDER_TASKS" uid="shell" /> <assign-permission name="android.permission.SET_ANIMATION_SCALE" uid="shell" /> <assign-permission name="android.permission.SET_PREFERRED_APPLICATION S" uid="shell" /> <assign-permission name="android.permission.WRITE_SETTINGS" uid="shell" /> <assign-permission name="android.permission.WRITE_SECURE_SETTINGS" uid="shell" /> <assign-permission name="android.permission.BROADCAST_STICKY" uid="shell" /> <!-- Development tool permissions granted to the shell. --> <assign-permission name="android.permission.SET_DEBUG_APP" uid="shell" /> <assign-permission name="android.permission.SET_PROCESS_LIMIT" uid="shell" /> <assign-permission name="android.permission.SET_ALWAYS_FINISH" uid="shell" /> <assign-permission name="android.permission.DUMP" uid="shell" /> <assign-permission name="android.permission.SIGNAL_PERSISTENT_PROCESS ES" uid="shell" /> <assign-permission name="android.permission.KILL_BACKGROUND_PROCESSES " uid="shell" /> <!-- Internal permissions granted to the shell. --> <assign-permission name="android.permission.FORCE_BACK" uid="shell" /> <assign-permission name="android.permission.BATTERY_STATS" uid="shell" /> <assign-permission name="android.permission.INTERNAL_SYSTEM_WINDOW" uid="shell" /> <assign-permission name="android.permission.INJECT_EVENTS" uid="shell" /> <assign-permission name="android.permission.RETRIEVE_WINDOW_CONTENT" uid="shell" /> <assign-permission name="android.permission.SET_ACTIVITY_WATCHER" uid="shell" /> <assign-permission name="android.permission.READ_INPUT_STATE" uid="shell" /> <assign-permission name="android.permission.SET_ORIENTATION" uid="shell" /> <assign-permission name="android.permission.INSTALL_PACKAGES" uid="shell" /> <assign-permission name="android.permission.CLEAR_APP_USER_DATA" uid="shell" /> <assign-permission name="android.permission.DELETE_CACHE_FILES" uid="shell" /> <assign-permission name="android.permission.DELETE_PACKAGES" uid="shell" /> <assign-permission name="android.permission.ACCESS_SURFACE_FLINGER" uid="shell" /> <assign-permission name="android.permission.READ_FRAME_BUFFER" uid="shell" /> <assign-permission name="android.permission.DEVICE_POWER" uid="shell" /> <assign-permission name="android.permission.INSTALL_LOCATION_PROVIDER " uid="shell" /> <assign-permission name="android.permission.BACKUP" uid="shell" /> <assign-permission name="android.permission.FORCE_STOP_PACKAGES" uid="shell" /> <assign-permission name="android.permission.STOP_APP_SWITCHES" uid="shell" /> <assign-permission name="android.permission.MODIFY_AUDIO_SETTINGS" uid="media" /> <assign-permission name="android.permission.ACCESS_DRM" uid="media" /> <assign-permission name="android.permission.ACCESS_SURFACE_FLINGER" uid="media" /> <assign-permission name="android.permission.WAKE_LOCK" uid="media" /> <assign-permission name="android.permission.ACCESS_SURFACE_FLINGER" uid="graphics" /> <!-- This is a list of all the libraries available for application code to link against. --> <library name="android.test.runner" file="/system/framework/android.test.runner.jar" /> <library name="javax.obex" file="/system/framework/javax.obex.jar"/> </permissions> Todo esto está sacado de la rom original de POV que le funciona el acelerometro. |
#105
|
||||
|
||||
prueba a meterle el programa que dije que se llama a10 de la store y dale atodas las pestañas ahi te guarda toda la infornacion de la tablet,permisos,fallos,formas de montar la sparticiones y asi los puedes mirar y ver el fallo
|
#106
|
||||
|
||||
Mira a ver si los módulos que has cambiado corresponden a la compilación del Kernel del boot.img (3.0.8, 3.0.8+...)
Otra cosa.... dentro de system.img, en etc hay carpeta llamada permissions con archivos xml, que son los que dan permisos al hardware, mira si dentro hay un archivo llamado android.hardware.sensor.accelerometer.xml con la linea: ................ Todo esto está sacado de la rom original de POV que le funciona el acelerometro. La parte del kernel es la que no tengo ni idea, claro, y si ese es el problema pues el solucionarlo, menos todavía
__________________
HectorziN
|
#107
|
||||
|
||||
Errores no indica ninguno
__________________
HectorziN
|
#108
|
||||
|
||||
Aqui una posible solucion al menos a ellos les ha funcionado:
Hi, I had a similar problem, get the protab2xxl_compatibility_1.1.0.zip and then follow the instructions in this post: you should unzip the protab2xxl_compatibility_1.1.0.zip, mount /dev/block/nanda and push script.bin and script0.bin, after reboot you should be able to see the display again (and you can use cwm to flash the whole compatibility zip) place script.bin and script0.bin in the folder where you have adb (I used QTadb) Then follow these commands (you should still have root) adb shell su mkdir /sdcard/nanda mount -t vfat /dev/block/nanda /sdcard/nanda exit exit adb push script.bin /sdcard/nanda adb push script0.bin /sdcard/nanda adb shell su umount /sdcard/nanda and then reboot Worked for me Dime si te va ....espero que si Última edición por Pedroa Día 22/06/12 a las 12:08:28. |
#109
|
||||
|
||||
Aqui una posible solucion al menos a ellos les ha funcionado:
Hi, I had a similar problem, get the protab2xxl_compatibility_1.1.0.zip and then follow the instructions in this post: you should unzip the protab2xxl_compatibility_1.1.0.zip, mount /dev/block/nanda and push script.bin and script0.bin, after reboot you should be able to see the display again (and you can use cwm to flash the whole compatibility zip) place script.bin and script0.bin in the folder where you have adb (I used QTadb) Then follow these commands (you should still have root) adb shell su mkdir /sdcard/nanda mount -t vfat /dev/block/nanda /sdcard/nanda exit exit adb push script.bin /sdcard/nanda adb push script0.bin /sdcard/nanda adb shell su umount /sdcard/nanda and then reboot Worked for me Dime si te va ....espero que si hace falta un compatibility especial para la 4.1 lo he comentado en el foro ese pero me han ignorado
__________________
HectorziN
|
#110
|
||||
|
||||
prueba con este : http://www.mediafire.com/?rg0dz2a7b4pmzl5
@knet it seems very similar to protab2xxl (but has some more touchscreens defined), btw i've created a dedicated compatibility zip, try it and report Si no va dimelo enseguida para que se lo diga a christian auque ya esta mirando hacer otro |
#111
|
||||
|
||||
dice que en un par de dias sacara el compatibillty zip para la nueva protab 4.1 al menos ya se ha comprometido ya solo os toca esperar si este que os puse no va.
|
#112
|
||||
|
||||
prueba con este : http://www.mediafire.com/?rg0dz2a7b4pmzl5
@knet it seems very similar to protab2xxl (but has some more touchscreens defined), btw i've created a dedicated compatibility zip, try it and report Si no va dimelo enseguida para que se lo diga a christian auque ya esta mirando hacer otro gracias
__________________
HectorziN
|
#113
|
||||
|
||||
GRACIAS!
__________________
HectorziN
|
#114
|
||||
|
||||
ya lo vi y es normal,atiende casi siempre a los que conoce o le suenan,como veras alli soy un usuario avanzado y es por eso que quizas me haga un poquito mas de caso,ya le sueno algo de lo pesaito que soy aunque alguna vez le eche una mano con los nuevos que llegan preguntando por alli,ni te imaginas la de peticiones que recibe al dia,es de locos.
Yo en su caso estaria superquemao,estara pagado por cyanogem,sino no me lo explico. Saludos Última edición por Pedroa Día 26/06/12 a las 00:41:22. |
#115
|
||||
|
||||
La camara es cuestion de probar con las diferentes de alli,de todas maneras ya he preguntado a los demas y el boton back es tan facil como iniciar en recovery,meterte en advance y pulsar keytest,pulsa el boton back y te aparecera un nuemro copialo,luego einicia,con la tablet encendida edita el fichero sun4i-keyboard.kl que esta metido en el comprimido test protab compatibility en system\usr\keylayout y cambias el numero que viene describiendo al boton back por el que has copiado. Luego reinicias en recovery y le metes el test protab y al menos el boton back deberia rular. |
#116
|
||||
|
||||
Bueno ya ha sacado vuestro test de compatibilidad en breve lo cuelgo en el apartado cyanogem y aokp.
Saludos |
#117
|
||||
|
||||
Decirme si os va cuanto antes ya que christian me lo ha preguntado dos veces si va o no,a la tercera se desentendera de mi
|
#118
|
||||
|
||||
|
#119
|
||||
|
||||
lo habeis echo todo segun los pasos?
wipe dalvik cache,wipe data luego instalo rom,gapps y test sin salir del recovery y reinicio |
|
#120
|
||||
|
||||
si la cosa sigue asi pasare de vosotros y no es por ti nailuj pero si no teneis interes vosotros menos lo voy a tener yo.
|
Estás aquí | ||||||
|
Herramientas | |