Ramos W30HD is working well
Custom Firmware by darevix
drx v X.XX
// Old
Hello,
I bought a Ramos W30HD, and its great, but the Youtube app doesnt show video, just some strange stripes over the screen. The other thing is the H/W acceleration on Videos. Same thing like Youtube, Audio is fine but no video. The moment i rotate the screen the picture appears for sec.
Device model: w30hd(QuadCore)
Firmware version: 4.0.4
Kernel version: 3.0.15-svn124
[email protected] )
#11 SMP PREEMPT Thu Dec 13 13:44:05 CST 2012
Build number: W30hd.eng.ramos0.20121213.100641
Is there someone who could help? Iam not the only one with this problem, and is spoils the otherwise incredible machine.
Thank You
Yes, I can also confirm that. There is problem with hw decoding in Ramos W30HD - all above 720p and streaming apps like youtube. I received confirmation from Ramos support service. We need wait for new firmware. There is no ETA now.
Other way is find and support custom ROM developer
Problem is that retina display drivers (LCD Panel).
Anyone knows a place to find them?
I dont know where to find that :-/ We need to know the name or model of the lcd, right?
MeXx87 said:
I dont know where to find that :-/ We need to know the name or model of the lcd, right?
Click to expand...
Click to collapse
Can you install from market an app that reports thoroughly the board information and post it here or pm me the results, thanks.
https://play.google.com/store/apps/details?id=pl.pawelbialecki.smartsysteminfo&feature=search_result
https://play.google.com/store/apps/details?id=com.jphilli85.deviceinfo&feature=search_result
https://play.google.com/store/apps/details?id=com.fivasim.androsensor&feature=search_result
https://play.google.com/store/apps/details?id=com.dama.hardwareinfo&feature=search_result
I you need any more infos, just ask.
RAMOS W30HD(QUADCORE)
SYSTEM (Android 4.0.4)
Model: W30hd(QuadCore)
Manufacturer: Ramos
Device: W30hd
Product: W30hd
Brand: Ramos
Android Version: 4.0.4 (Ice Cream Sandwich)
API Level: 15
Fingerprint: Ramos/w30hd/w30hd:4.0.4/W30hd/eng.ramos0.20121213.100641:user/test-keys
DISPLAY (1920x1128)
Size: 1920x1128
Refresh Rate: 42,28 Hz
Default Orientation: Portrait
Physical Size: 13,93" (35,39 cm)
Density: 240 dpi (High)
Pixels Per Inch: X: 159,9; Y: 159,58
PROCESSOR (ARMv7)
Processor: ARMv7 Processor rev 0 (v7l)
Cores: 4
Max Frequency: 1400 Mhz
Instruction Sets: armeabi-v7a, armeabi
NEON Supported: Yes
MEMORY (1616 MB)
System RAM: 1616 MB
JVM Max Memory: 48 MB
Internal Storage: 26883 MB
External Storage: 26883 MB (Emulated)
BACK CAMERA (1,9 megapixel)
Antibanding: Off
Antibanding Values: Auto, 50hz, 60hz, Off
Brightness: 0
Brightness Max: 2
Brightness Min: 2
Contrast: 0
Effect: None
Effect Values: None, Mono, Negative, Sepia
Exposure Compensation: 0
Exposure Compensation Step: 1
Flash Mode: Off
Flash Mode Values: None, Mono, Negative, Sepiaoff, Torch
Focal Length: 0.9
Focus Distances: 0.10, 1.20, Infinity
Focus Mode: Fixed
Focus Mode Values: Fixed
Horizontal View Angle: 51.2
Hue: 0
Hue Max: 2
Hue Min: 2
Iso: Auto
Jpeg Quality: 100
Jpeg Thumbnail Height: 240
Jpeg Thumbnail Quality: 100
Jpeg Thumbnail Size Values: 320x240, 0x0
Jpeg Thumbnail Width: 320
Max Exposure Compensation: 4
Max Num Detected Faces Hw: 0
Max Zoom: 0
Metering: Center
Min Exposure Compensation: 4
Orientation: 90
Picture Format: Jpeg
Picture Format Values: Jpeg
Picture Size: 1600x1200
Picture Size Values: 1600x1200, 1280x1024, 1280x960, 640x480
Preferred Preview Size For Video: 1280x960
Preview Format: Yuv420sp
Preview Format Values: Yuv420p, Yuv420sp
Preview Fps Range: 15000, 30000
Preview Fps Range Values: (15000, 30000)
Preview Frame Rate: 30
Preview Frame Rate Values: 7, 15, 30
Preview Size: 1280x960
Preview Size Values: 1280x960
Recording Hint: False
Rotation: 0
Saturation: 0
Saturation Max: 2
Saturation Min: 2
Scene Mode: Auto
Sharpness: 0
Sharpness Max: 2
Sharpness Min: 2
Vertical View Angle: 39.4
Video Frame Format: Yuv420sp
Video Size Values: 1280x720, 640x480
Wdr: 0
Whitebalance: Auto
Whitebalance Values: Auto, Incandescent, Fluorescent, Daylight, Cloudy Daylight
Zoom Ratios: 100
Zoom Supported: True
FRONT CAMERA (0,3 megapixel)
Antibanding: Off
Antibanding Values: Auto, 50hz, 60hz, Off
Brightness: 0
Brightness Max: 2
Brightness Min: 2
Contrast: 0
Effect: None
Effect Values: None, Mono, Negative, Sepia
Exposure Compensation: 1
Flash Mode: Off
Flash Mode Values: None, Mono, Negative, Sepiaoff, Torch
Focal Length: 0.9
Focus Distances: 0.20, 0.25, Infinity
Focus Mode: Fixed
Focus Mode Values: Fixed
Horizontal View Angle: 51.2
Hue: 0
Hue Max: 2
Hue Min: 2
Iso: Auto
Jpeg Quality: 100
Jpeg Thumbnail Height: 120
Jpeg Thumbnail Quality: 100
Jpeg Thumbnail Size Values: 160x120, 0x0
Jpeg Thumbnail Width: 160
Max Num Detected Faces Hw: 0
Max Zoom: 0
Metering: Center
Orientation: 270
Picture Format: Jpeg
Picture Format Values: Jpeg
Picture Size: 640x480
Picture Size Values: 640x480
Preferred Preview Size For Video: 1280x960
Preview Format: Yuv420sp
Preview Format Values: Yuv420p, Yuv420sp
Preview Fps Range: 15000, 30000
Preview Fps Range Values: (15000, 30000)
Preview Frame Rate: 30
Preview Frame Rate Values: 30
Preview Size: 1280x960
Preview Size Values: 1280x960
Recording Hint: False
Rotation: 0
Saturation: 0
Saturation Max: 2
Saturation Min: 2
Scene Mode: Auto
Sharpness: 0
Sharpness Max: 2
Sharpness Min: 2
Vertical View Angle: 39.4
Video Frame Format: Yuv420sp
Video Size Values: 640x480
Wdr: 0
Whitebalance: Auto
Zoom Ratios: 100
Zoom Supported: True
SENSORS (7)
MPL ROTATION VECTOR
Vendor: Invensense
Range: 10240.0
Resolution: 1.0
Power: 0.5 mA
MPL LINEAR ACCELERATION
Vendor: Invensense
Range: 10240.0
Resolution: 1.0
Power: 0.5 mA
MPL GRAVITY
Vendor: Invensense
Range: 10240.0
Resolution: 1.0
Power: 0.5 mA
MPL GYROSCOPE
Vendor: Invensense
Range: 2000.0
Resolution: 1.0
Power: 0.5 mA
MPL ACCELEROMETER
Vendor: Invensense
Range: 10240.0
Resolution: 1.0
Power: 0.5 mA
MPL MAGNETIC FIELD
Vendor: Invensense
Range: 10240.0
Resolution: 1.0
Power: 0.5 mA
MPL ORIENTATION
Vendor: Invensense
Range: 360.0
Resolution: 1.0
Power: 9.7 mA
OPENGL 1.X (Mali-400 MP)
GENERAL
Renderer: Mali-400 MP
Version: OpenGL ES-CM 1.1
Vendor: ARM
LIMITS
Texture Size: 4096x4096
Texture Units: 8
Viewport Size: 4096x4096
Modelview Stack Depth: 32
Projection Stack Depth: 32
Texture Stack Depth: 32
Lights: 8
COMPRESSED TEXTURE FORMATS
ETC1, Paletted
EXTENSIONS
GL_OES_byte_coordinates GL_OES_fixed_point GL_OES_single_precision GL_OES_matrix_get GL_OES_read_format GL_OES_compressed_paletted_texture GL_OES_point_size_array GL_OES_point_sprite GL_OES_texture_npot GL_OES_query_matrix GL_OES_matrix_palette GL_OES_extended_matrix_palette GL_OES_compressed_ETC1_RGB8_texture GL_OES_EGL_image GL_OES_draw_texture GL_OES_depth_texture GL_OES_packed_depth_stencil GL_EXT_texture_format_BGRA8888 GL_OES_framebuffer_object GL_OES_stencil8 GL_OES_depth24 GL_ARM_rgba8 GL_OES_EGL_image_external GL_OES_EGL_sync GL_OES_rgb8_rgba8 GL_EXT_multisampled_render_to_texture GL_OES_texture_cube_map GL_EXT_discard_framebuffer
OPENGL 2.0 (Mali-400 MP)
GENERAL
Renderer: Mali-400 MP
Version: OpenGL ES 2.0
Vendor: ARM
GLSL Version: OpenGL ES GLSL ES 1.00
LIMITS
Texture Size: 4096x4096
Texture Units: 8
Vertex Textures: 0
Combined Textures: 8
Viewport Size: 4096x4096
Renderbuffer Size: 4096x4096
Cubemap Size: 1024x1024
Vertex Attributes: 16
Vertex Uniforms: 256
Varying Vectors: 12
Fragment Uniforms: 256
VERTEX NUMERIC PRECISION
Int: [-2^24, 2^24]
Float: [-2^127, 2^127], 2^-23
FRAGMENT NUMERIC PRECISION
Low Int: [-2^11, 2^11]
Medium Int: [-2^11, 2^11]
High Int: Not available
Low Float: [-2^15, 2^15], 2^-10
Medium Float: [-2^15, 2^15], 2^-10
High Float: Not available
COMPRESSED TEXTURE FORMATS
ETC1
EXTENSIONS
GL_OES_texture_npot GL_OES_compressed_ETC1_RGB8_texture GL_OES_standard_derivatives GL_OES_EGL_image GL_OES_depth24 GL_ARM_rgba8 GL_ARM_mali_shader_binary GL_OES_depth_texture GL_OES_packed_depth_stencil GL_EXT_texture_format_BGRA8888 GL_EXT_blend_minmax GL_OES_EGL_image_external GL_OES_EGL_sync GL_OES_rgb8_rgba8 GL_EXT_multisampled_render_to_texture GL_EXT_discard_framebuffer
GRAPHIC MODES (RGBA 32bit)
RGB 16bit (565)
RGB 16bit (565), Non-Conformant
RGB 16bit (565), Depth 24bit, Stencil 8bit
RGB 16bit (565), Depth 24bit, Stencil 8bit, Samples x4
RGB 16bit (565), Depth 24bit, Stencil 8bit, Samples x16, Non-Conformant
RGBA 16bit (5551), Depth 24bit, Stencil 8bit
RGBA 16bit (5551), Depth 24bit, Stencil 8bit, Samples x4
RGBA 16bit (5551), Depth 24bit, Stencil 8bit, Samples x16, Non-Conformant
RGBA 16bit (4444), Depth 24bit, Stencil 8bit
RGBA 16bit (4444), Depth 24bit, Stencil 8bit, Samples x4
RGBA 16bit (4444), Depth 24bit, Stencil 8bit, Samples x16, Non-Conformant
RGB 32bit (888)
RGB 32bit (888), Non-Conformant
RGB 32bit (888), Depth 24bit
RGB 32bit (888), Depth 24bit, Stencil 8bit
RGB 32bit (888), Depth 24bit, Stencil 8bit, Non-Conformant
RGBA 32bit (8888)
RGBA 32bit (8888), Non-Conformant
RGBA 32bit (8888), Depth 24bit, Stencil 8bit
RGBA 32bit (8888), Depth 24bit, Stencil 8bit
RGBA 32bit (8888), Depth 24bit, Stencil 8bit, Samples x4
RGBA 32bit (8888), Depth 24bit, Stencil 8bit, Samples x16, Non-Conformant
FEATURES (33)
GRAPHICS
OpenGL 2.0
ANDROID HARDWARE
android.hardware.audio.low_latency
android.hardware.bluetooth
android.hardware.camera
android.hardware.camera.autofocus
android.hardware.camera.flash
android.hardware.camera.front
android.hardware.faketouch
android.hardware.location
android.hardware.location.gps
android.hardware.location.network
android.hardware.microphone
android.hardware.screen.landscape
android.hardware.screen.portrait
android.hardware.sensor.accelerometer
android.hardware.sensor.compass
android.hardware.sensor.gyroscope
android.hardware.sensor.light
android.hardware.sensor.proximity
android.hardware.telephony
android.hardware.telephony.gsm
android.hardware.touchscreen
android.hardware.touchscreen.multitouch
android.hardware.touchscreen.multitouch.distinct
android.hardware.touchscreen.multitouch.jazzhand
android.hardware.usb.accessory
android.hardware.usb.host
android.hardware.wifi
android.hardware.wifi.direct
ANDROID SOFTWARE
android.software.live_wallpaper
android.software.sip
android.software.sip.voip
GOOGLE
com.google.android.feature.GOOGLE_BUILD
Created with Hardware Info 2.1.0
SENSORS (7) we have drivers.
What info still missing.
1.Touch Panel (touch controller)
2.Led controller (backlight)
3.wifi chip
4.bluetooth chip (might be same chip as wifi )
5. power regulator chip
6. charger chip
7. usb controller chip (again might be the same as power regulator chip)
8. Run parted binary from CWM and report partition layout (p) print command, so we can update cwm to latest version or port twrp recovery and also able to make ROM flashing script.
Assuming the bootloader is unlocked ofc
How can we get the missing infos and what can we do then? What does all this mean?
gesendet von meinem Ramos W30HD
astkibo said:
How can we get the missing infos and what can we do then? What does all this mean?
gesendet von meinem Ramos W30HD
Click to expand...
Click to collapse
Cyanogenmod/AOKP/AOSP + new recoveries+ Unofficial support+Ubuntu from sdcard.
Here are some infos from a different info tool. It shows mountpoints and strangely an other screenresolution. But how do we get the infos about all the chips? Opening that thing up?
CPU
Processor ARMv7 Processor rev 0 (v7l)
processor 0
BogoMIPS 1992.29
processor 2
BogoMIPS 1992.29
processor 3
BogoMIPS 2789.21
Features swp half thumb fastmult vfp edsp neon vfpv3 tls
CPU implementer 0x41
CPU architecture 7
CPU variant 0x3
CPU part 0xc09
CPU revision 0
Hardware SMDK4X12
Revision 0000
Serial 0000000000000000
Frequency range: 200.0 -> 1400.0MHz
Current Frequency: 1100.0MHz
Frequency Stats (time):
- 1400.0 MHz 9.31% (401619)
- 1300.0 MHz 0.72% (31081)
- 1200.0 MHz 4.09% (176738)
- 1100.0 MHz 0.58% (25137)
- 1000.0 MHz 2.62% (113118)
- 900.0 MHz 0.66% (28552)
- 800.0 MHz 0.65% (28117)
- 700.0 MHz 0.73% (31305)
- 600.0 MHz 0.94% (40438)
- 500.0 MHz 1.35% (58101)
- 400.0 MHz 1.94% (83893)
- 300.0 MHz 2.66% (114627)
- 200.0 MHz 73.76% (3183378)
Screen
Resolution: 1200 x 1848
Refresh Rate: 42.282
X factor for DIP: 1.5
Density: 240 dpi
Pixel per inch X: 159.89508 dpi Y: 159.58115 dpi
OpenGL
OpenGL Version supported : 2.0
OpenGL Version supported : OpenGL ES-CM 1.1
Vendor : ARM
Renderer : Mali-400 MP
Extensions :
GL_OES_byte_coordinates GL_OES_fixed_point GL_OES_single_precision GL_OES_matrix_get GL_OES_read_format GL_OES_compressed_paletted_texture GL_OES_point_size_array GL_OES_point_sprite GL_OES_texture_npot GL_OES_query_matrix GL_OES_matrix_palette GL_OES_extended_matrix_palette GL_OES_compressed_ETC1_RGB8_texture GL_OES_EGL_image GL_OES_draw_texture GL_OES_depth_texture GL_OES_packed_depth_stencil GL_EXT_texture_format_BGRA8888 GL_OES_framebuffer_object GL_OES_stencil8 GL_OES_depth24 GL_ARM_rgba8 GL_OES_EGL_image_external GL_OES_EGL_sync GL_OES_rgb8_rgba8 GL_EXT_multisampled_render_to_texture GL_OES_texture_cube_map GL_EXT_discard_framebuffer
Environment
Root Directory: /system
Data Directory: /data
Download Cache Directory: /cache
External Storage State: mounted
External Storage Directory: /mnt/sdcard
Mount points
MountPoint
Name Type Options
- /
rootfs rootfs rw,relatime
- /dev
tmpfs tmpfs rw,nosuid,relatime,mode=755
- /dev/pts
devpts devpts rw,relatime,mode=600
- /proc
proc proc rw,relatime
- /sys
sysfs sysfs rw,relatime
- /acct
none cgroup rw,relatime,cpuacct
- /mnt/asec
tmpfs tmpfs rw,relatime,mode=755,gid=1000
- /mnt/obb
tmpfs tmpfs rw,relatime,mode=755,gid=1000
- /dev/cpuctl
none cgroup rw,relatime,cpu
- /system
/dev/block/mmcblk0p2 ext4 rw,relatime,barrier=1,data=ordered
- /data
/dev/block/mmcblk0p3 ext4 rw,nosuid,nodev,noatime,barrier=1,nomblk_io_submit,data=ordered,noauto_da_alloc
- /cache
/dev/block/mmcblk0p4 ext4 rw,nosuid,nodev,noatime,barrier=1,nomblk_io_submit,data=ordered
- /mnt/sdcard
/dev/fuse fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other
- /mnt/ext_sd
/dev/block/vold/179:25 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
Is someone registered in the Ramosfans-forum?
There they have a custom rom for the W30, maybe we can get more information about our tablet.
gesendet von meinem Ramos W30HD
Hi,
we got bored today so we decided to open Astkibo's Tablet. We made some Pictures :
"plus.google.com/photos/106232491218909622771/albums/5831145649458927761?authkey=COWSyL71-NjUxQE"
Maybe thats the name of the Display ? [email protected] FPC-M6151A-V00
MeXx87 said:
Hi,
we got bored today so we decided to open Astkibo's Tablet. We made some Pictures :
"plus.google.com/photos/106232491218909622771/albums/5831145649458927761?authkey=COWSyL71-NjUxQE"
Maybe thats the name of the Display ? [email protected] FPC-M6151A-V00
Click to expand...
Click to collapse
Good efford there guys but you only scratch the surface.
What comes from those pictures is a custom made board from ramos it self with quality components Samsung DDR RAM with Samsung NAND.
There should be more components under the board and also a wild guess on the audio chip that might be yamaha.
demetris_I said:
Good efford there guys but you only scratch the surface.
What comes from those pictures is a custom made board from ramos it self with quality components Samsung DDR RAM with Samsung NAND.
There should be more components under the board and also a wild guess on the audio chip that might be yamaha.
Click to expand...
Click to collapse
There are some good and some bad news...
I opened my tablet and on the backside there was nothing... just black Tape, i tried to feel something with my fingers, but it is completly flat.
Now the good news ( I hope), I found the Display Manufacturer...
Modelnr: B101UAN021
AU OPTRONICS
HW 2A FW 0A
Hey buddy, welldone!
http://www.taiwantrade.com.tw/resou...0a-e5e1-487a-a109-150131d8a30f_B101UAN021.pdf
No driver to be found anywhere though
We need to pressure Ramos for releasing Source code.
---------- Post added at 12:21 AM ---------- Previous post was at 12:05 AM ----------
https://plus.google.com/photos/106232491218909622771/albums/5831145649458927761/5831145785346543698
What is the white chip upleft and what chip lies in the middle under the 2 cables that are blocking the view?
Also i didnt see any wifi wire connection so i guessed that more are in the bottom of the board. (wild guess on wifi chip atheros )
Thanks
MeXx87 opened it again, he found 2 more chips. The chip who was covered is the "Maxim 77686" I don't really know what he does, than he found another, the "invensense mpu 6050" this is for accelerometer, gyroscope and a few other things.
"invensense.com/mems/gyro/mpu6050.html"
The "white one" has no caption. I think it's the sound chip, because there are the speakers connected.
astkibo said:
MeXx87 opened it again, he found 2 more chips. The chip who was covered is the "Maxim 77686" I don't really know what he does, than he found another, the "invensense mpu 6050" this is for accelerometer, gyroscope and a few other things.
"invensense.com/mems/gyro/mpu6050.html"
The "white one" has no caption. I think it's the sound chip, because there are the speakers connected.
Click to expand...
Click to collapse
Maxim 77686 is the power regulator and driver exist.
Invensense chip drivers can be taken from Google Nexus released drivers.
Edit:
Look what google brings to us
http://www.techrepublic.com/photos/cracking-open-the-samsung-galaxy-note-101/6381753?seq=57
Edit2:
mpu6050 driver
https://github.com/wtfuzz/linux/commit/87b72e6fb705025042b9607271f369a56de291e2
Edit3 Nexus 7 mpu6050 :
http://guide-images.ifixit.net/igi/cXraFOHXUWIItNnO.huge
Driver JB4.2.1:
https://dl.google.com/dl/android/aosp/invensense-grouper-jzo54k-aae1cd0c.tgz
Ok cool but we really don't know what to do with all that stuff xD I hope we find one who can help us build a new working rom.
gesendet von meinem Ramos W30HD
Once again good news, and bad news...
Bad news is, we maybe never see the source code for the W30 / HD . The guy who made the Customromfor the W30 ( Librehat ) tried to persuade Ramos to release the source code for other models, but they didnt.
Good news is, he spoke to a Ramos guy and he got told, they realy are working on a fix, and he believs that the update could be out this month.
If we identify all the onboard components am sure there is a driver for them already out there, what is badly needed is the OPTRONICS B101UAN021 driver.
please help me , my phone pixcom
pesifikasi Pixcom Life Fun
Network: Dual GSM 900/1800 (2G)
Display: LCD capacitive touchscreen, 3.5 inch, 320 x 480 pixels, 2 point touch
Operating System: Android 4.2.2 Jelly Bean
Processor: MT6572, Dual Core 1 GHz, GPU Mali 400
Camera: 2 MP (rear), VGA (front), flash
Audio Player: MP3/WAV
Video Player: MP4/3GP
Connections: EDGE, WiFi, Bluetooth, data cable, audio jack
Internal Memory: 512 MB ROM, 256 MB RAM
External Memory: microSD up to 32 GB
Messaging: messages, email, BBM
Other Features: 100% Game from Gameloft, fuel, File Manager, Clock, Calendar, Calculator, FM Radio
Battery: 1300 mAh
Price: USD 514 000
i need sistem rom because my android medium bootloop:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
ryannprtaama said:
please help me , my phone pixcom
pesifikasi Pixcom Life Fun
Network: Dual GSM 900/1800 (2G)
Display: LCD capacitive touchscreen, 3.5 inch, 320 x 480 pixels, 2 point touch
Operating System: Android 4.2.2 Jelly Bean
Processor: MT6572, Dual Core 1 GHz, GPU Mali 400
Camera: 2 MP (rear), VGA (front), flash
Audio Player: MP3/WAV
Video Player: MP4/3GP
Connections: EDGE, WiFi, Bluetooth, data cable, audio jack
Internal Memory: 512 MB ROM, 256 MB RAM
External Memory: microSD up to 32 GB
Messaging: messages, email, BBM
Other Features: 100% Game from Gameloft, fuel, File Manager, Clock, Calendar, Calculator, FM Radio
Battery: 1300 mAh
Price: USD 514 000
i need sistem rom because my android medium bootloop:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
You should go to service center because i don't think there's any forum for this device that can help you.
ryannprtaama said:
please help me , my phone pixcom
pesifikasi Pixcom Life Fun
Network: Dual GSM 900/1800 (2G)
Display: LCD capacitive touchscreen, 3.5 inch, 320 x 480 pixels, 2 point touch
Operating System: Android 4.2.2 Jelly Bean
Processor: MT6572, Dual Core 1 GHz, GPU Mali 400
Camera: 2 MP (rear), VGA (front), flash
Audio Player: MP3/WAV
Video Player: MP4/3GP
Connections: EDGE, WiFi, Bluetooth, data cable, audio jack
Internal Memory: 512 MB ROM, 256 MB RAM
External Memory: microSD up to 32 GB
Messaging: messages, email, BBM
Other Features: 100% Game from Gameloft, fuel, File Manager, Clock, Calendar, Calculator, FM Radio
Battery: 1300 mAh
Price: USD 514 000
i need sistem rom because my android medium bootloop:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Find a similar phones ROM flash it without flashing preloader.
Sent from my Moto G using XDA Premium 4 mobile app
i have a similar phone.... Pixcom Life Fun - MT6572..... brick also
need info for similar flash-file for this phone...
HP Touchpad AnTuTu Benchmark v7.1.0
The ROM: (Only the ROM is install and the stand alone AnTuTu Benchmark v7.1.0 apk )
du_tenderloin-v12.5.1-20180920-1118-RC.zip
The extra Kernel:
SKZ-tenderloin-kernel-DU-Linaro_10_02_2018.zip
Du Original: Score 14542
scaling_max_freq
1512000
scaling_min_freq
648000
Governor: Interactive
zRAM 128M
gpu_available_frequencies
266667000 228571000 200000000 177778000 (No other options,defaults will be use on all test)
All the optimization changes are done in the Ramdisk and repack for a new boot image:
The “performance” governor will be use in all the following test:
Both cpu cores will be working at the highest frequency all the time.
Du Maximum frequency allow: Score 16827
scaling_max_freq
1782000
scaling_min_freq
648000
zRAM 128M
Each zRAM size setting is done in the (fstab.tenderloin) file in Ramdisk, new boot image created for each test.(I know it can be change inside Android Terminal )
Testing zRAM size performance: Score 16773
No zRAM 0
zRAM 1 Gigabyte: Score 16898
zRAM 1.5 Gigabyte: Score 16696
zRAM 2 Gigabytes: Score 16907
zRAM 3 Gigabytes: Score 16563
The maximum allow zRAM size is 3 Gigabytes, if more is created it will show as zero size in Android. The system works perfectly fine with 3g.
From doing the test with DU Kernel, the best results is with a 2g zRAM, the following will be to test the SKZ Kernel at maximum frequency with default zRAM and 2g.
SKZ_Kernel Maximum freqency: Score 17127
scaling_max_freq
1836000
scaling_min_freq
192000
zRAM 128M
GPU are set to maximum 3d 320000000 2d 266667000
zRAM 2 Gigabytes 17257
Technically it does not make any sense that a 1 Gigabytes of RAM device with 2 Gigabytes of zRAM performs better. But that was my curiosity of doing all the benchmark. When I made the changes to a 3g zRAM, I notice faster browsing, video loading and playing, then wanted to find out if it made a difference and the optimal size for the zRAM.
The maximum temperature for the CPU at 1890mHz both cores running all time was 63 Celsius which is 145 Fahrenheit.
I have screen shots of all the benchmark with more details.
Thanks. How do you root your TP to change values ? SuperSU ?
To make system read and write
https://forum.xda-developers.com/hp-touchpad/development/make-root-permanet-read-write-to-t3846567
To set CPU settings at boot.
https://forum.xda-developers.com/hp-touchpad/development/set-maximum-cpu-frequency-android-rom-t3850492
If need it to be change after boot inside Android terminal, then superSu is need it.
Nothing needs to be done if using ADB, to make CPU changes.
Interesting.
HP_TOUCHPAD said:
HP Touchpad AnTuTu Benchmark v7.1.0
The ROM: (Only the ROM is install and the stand alone AnTuTu Benchmark v7.1.0 apk )
du_tenderloin-v12.5.1-20180920-1118-RC.zip
The extra Kernel:
SKZ-tenderloin-kernel-DU-Linaro_10_02_2018.zip
Du Original: Score 14542
scaling_max_freq
1512000
scaling_min_freq
648000
Governor: Interactive
zRAM 128M
gpu_available_frequencies
266667000 228571000 200000000 177778000 (No other options,defaults will be use on all test)
All the optimization changes are done in the Ramdisk and repack for a new boot image:
The “performance” governor will be use in all the following test:
Both cpu cores will be working at the highest frequency all the time.
Du Maximum frequency allow: Score 16827
scaling_max_freq
1782000
scaling_min_freq
648000
zRAM 128M
Each zRAM size setting is done in the (fstab.tenderloin) file in Ramdisk, new boot image created for each test.(I know it can be change inside Android Terminal )
Testing zRAM size performance: Score 16773
No zRAM 0
zRAM 1 Gigabyte: Score 16898
zRAM 1.5 Gigabyte: Score 16696
zRAM 2 Gigabytes: Score 16907
zRAM 3 Gigabytes: Score 16563
The maximum allow zRAM size is 3 Gigabytes, if more is created it will show as zero size in Android. The system works perfectly fine with 3g.
From doing the test with DU Kernel, the best results is with a 2g zRAM, the following will be to test the SKZ Kernel at maximum frequency with default zRAM and 2g.
SKZ_Kernel Maximum freqency: Score 17127
scaling_max_freq
1836000
scaling_min_freq
192000
zRAM 128M
GPU are set to maximum 3d 320000000 2d 266667000
zRAM 2 Gigabytes 17257
Technically it does not make any sense that a 1 Gigabytes of RAM device with 2 Gigabytes of zRAM performs better. But that was my curiosity of doing all the benchmark. When I made the changes to a 3g zRAM, I notice faster browsing, video loading and playing, then wanted to find out if it made a difference and the optimal size for the zRAM.
The maximum temperature for the CPU at 1890mHz both cores running all time was 63 Celsius which is 145 Fahrenheit.
I have screen shots of all the benchmark with more details.
Click to expand...
Click to collapse
> I am wondering if this is a downloadable process or a inside replacement? I am a Novice, just currious and learning.. I have a 16 gig tp.. two others I got to de brick, or replace batt.. but this sounds interesting,
I tried downloading it and using DoubleStuffs toolbox to install it, I guessing that is wrong. it won't show in the SD card my question is how do I install it?
There is no hardware replacement or modification that can be done internally to the Touchpad.
All changes, tweaks or modifications are done using software.
If the tablet battery is not charge, then make sure you have a "Genuine HP charger that came with it" or the wireless charger.
Then plug it to charge, when you see the led lights blinking from side to side, let it charge for until it turns on. It can take very long time, could be a couple of days.
Happy learning all the information you need is on this Forum!
AnTuTu Benchmark is an app to test only performance, it will not change or make any modifications.
There are so many questions asked over and over again about how to configure the kernel for a desired outcome..... max performance, best battery holdup, fix freezing etc.
I will post this for those who did not attend school just for the bus ride or playtime. All dumb questions ignored so if I don't respond, you asked a dumb question or made a dumb comment.
We have a choice of 1 custom kernel (Eureka) that can be comprehensively tweaked thanks to many of the settings being moved into the DTB partition. Currently, there are 20 versions of the DTB image that can be selected on kernel installation - 10 enforcing and 10 permissive with 10 different mixes of cpu and gpu frequencies to suit most needs. The default sets everything to maximum and is the cause of the majority of freezing / crashing on an A205 phone that has a lower quality SoC than the other A series compatible phones. Most will end up using DTB2 to fix instability but even this might not be enough. You then have to consider a lower frequency DTB which lessens the attractiveness of using this custom kernel. Why not make your own flavor of DTB that can more accurately reflect what you can run on your specific SoC? Here's how:
Open up the Eureka Kenel zip file in whatever zip extractor you use.
Extract DTB2.img from the zip file (either permissive or enforcing version depending on what your chosen ROM needs)
Now open DTB2.img using a hex editor
Now look at the following which is a list of addresses (in hex), what the value at this address is defining and a list of possible settings. Frequencies are in MHz and the hex code to set it is the frequency in kHz example: 343MHz is 343000kHz, 053BD8 is hex for 343000.
GPU:
5CA5 GPU max freq
5CB5 GPU boost freq
5CC7 GPU boost %load
Possible freqs (MHz):
343 053BD8
450 06DDD0
545 0850E8
676 0A50A0
845 0CE4C8
1001 0F4628
1100 10C8E0
1200 124F80
1300 13D620
CPU smalls:
71B1 CPU min freq
71C1 CPU min freq
71D1 CPU max freq
71E1 CPU max freq
71F1 CPU boost freq
Possible freqs (MHz):
208 032C80
343 053BD8
449 06D9E8
546 0854D0
676 0A50A0
757 0B8D08
839 0CCD58
902 0DC370
1014 0F78F0
1144 1174C0
1248 130B00
1352 14A140
1482 169D10
1586 183350
1690 19C990
1794 1B5030
CPU bigs:
73B9 CPU min freq
73C9 CPU min freq
73D9 CPU max freq
73E9 CPU max freq
73F9 CPU boost freq
Possible freqs (MHz):
208 032C80
312 04C2C0
520 07EF40
728 0B1BC0
936 0E4840
1144 1174C0
1352 14A140
1560 17CDC0
1664 196400
1768 1AFA40
1872 1C9080
1976 1E26C0
2080 1FBD00
2184 215340
2288 22E980
First thing: The default min freq of 208MHz does not save any more battery than setting this to 343MHz (for small cpus) and 312MHz for bigs.
Next thing: The A205 more than likely will become unstable at anything above 2080MHz for the big cpus but can probably cope with 1794MHz on the small cpus. Each SoC is slightly different so you must test what your phone can handle, not what someone else's phone can do!
Next: It is highly unlikely that your A205 will be stable with the GPU maxxing out at 1300MHz. You will not be aware of this until the gpu governor actually cranks the gpu up to that frequency i.e. you can remain oblivious to it for some time and incorrectly assume something else is causing freezes / crashes / glitching.
Next: There are many more settings in the DTB relating to boost frequencies on various input conditions i.e. screen touches, keyboard clicks, mouse clicks etc. Most of these are set to peak at 1144MHz which seems quite reasonable so I have not sought to specifically identify and edit these.
Edit: So here are the input boost frequencies: (address, name, function, freqs)
I assume the first addresses in each block are for BIGS and the 2nd lot are for SMALLS. It seems to work well to set all the BIG freqs to 936 and all the SMALLS to 839 since there is an abundance of upward boosting from other sources such as the Governor and Exynos specific drivers.
50B1 key1 IKEY 1144
5181 key2 ITOUCHKEY 1144
5255 5259 525D 5285 5289 528D key3 ITOUCH 1144 1144 936 839 839 839
5369 536D 5391 5395key4 IMULTITOUCH 1144 936 839 839
545D 5461 5485 5489 key5 IKEYBOARD 1144 936 839 839
554D 5551 5575 5579 key6 IMOUSE 1144 936 839 839
5641 5669 key7 IMOUSE WHEEL 1144 839
5735 5739 575D 5761 key8 IPEN HOVER 1144 936 839 839
5821 5825 5849 584D key9 IPEN 1560 936 839 839
58E5 key10 IKEY_TWO 1872
Recommendations:
Min Freqs:
Set GPU to 343MHz, small CPUs to 343MHz and big CPUs to 312MHz. This is the maximum power saving you will get and offer minimal lag as the frequencies scale up to meet demand.
Set the GPU max freq to 845MHz while you are establishing what is stable for the CPUs.
Set GPU boost to 545 or 676MHz (depending on your compromise between battery and performance)
Set GPU boost load trigger level from the stock 75% down to 50~60%. Again depending on your compromise between battery and performance. Lowering this setting has a significant impact on reducing perceived lag so the stock setting was probably far to high.
Set big CPU max freq down to 2080MHz. This solves most crashing that is due to the cpu being overclocked too far.
Set small CPU max freq to 1794MHz unless your SoC proves to be unstable at this.
Set the CPU boost freqs to something quite low (around 700~900MHz). There are other boosts that override this basic CPU boost freq so you will almost never see it.
Note: If you want maximum battery savings, setting the max freqs lower seems like a logical thing to do but it is not! If you halve the cpu freqs, you double the amount of time they must remain on but you do not halve the power consumption so you end up consuming more power....
Make the changes and save the DTB.img file and flash it in recovery to DTB partition and reboot.
Install hKtweaks_v2.2.2 or your favorite kernel tweaker that can deal with Exynos SoCs (not many can)
Take a look at the cpu and gpu settings to confirm that your edited DTB file is producing the expected results i.e. min and max freqs agree with what you set.
You are done!
Err..... only kidding there is more to do.
Now back to the issue of the GPU max freq. In hKtweaks you can override the settings inherited from the DTB (within the limits set by the DTB). The max GPU freq is also associated with a core voltage. Lowering the voltages will make the GPU run cooler (use less power) but also it will not overclock as far as if the voltage is higher. Here is the dangerous bit - you can increase the voltage to make it overclock higher but cause it to overheat quicker which will make it throttle back to a lower freq. There is also an error in the DTB: Look at the settings for throttling the frequency back at certain temps. Set GPU LEVEL 3 Throttling Freq to 343MHz to fix the error.
Have a play with the GPU settings in hKtweaks without setting Apply on boot so if you set something that crashes the phone, it will revert to normal on a reboot. When you are positive you have the best GPU settings. then set Apply on boot.
Now you are done!
Err..... not quite, there is more.
O.K, assuming you have your custom DTB set up exactly how you want it, it is time to look at some important settings available through hKTweaks.
Firstly we will look at the CPU Governor selection. Interactive is the stock setting and if you watch what the CPU cores are doing with no background activities (kill all unnecessary apps), you will see the frequencies will be dancing around without settling down to the minimum freqs. This is partly due to a dodgy implementation of this governor by Samsung and also the excessive amount of invisible running services that allow Samsung and Google to plunder your personal data in realtime.
Touch the screen, scoll the screen etc. and you will see the various CPU boost features adding to the overall freqs.
The Eureka kernel has extra CPU Governors added - not all function correctly... be warned. Some Governors apply to all CPUs (big and small) and can't be configured separately. Some Governors can have separate configurations for big and smalls.
The way this works is whatever is set for cpu0 is applied to all smalls (cpu0~5) and whatever is set for cpu6 is set for all bigs (cpu6~7).
In a root filemanager, take a look at /sys/devices/system/cpu/cpufreq If you see a folder with the Governor's name, the Governor is applied to all cpus big and small with the same settings. If the Governor does not have a folder here, look in policy0 and policy6 folders. If the Governor has folders in there, the Governor can have separate settings for big and smalls. This is determined by however the Governor was set up at the kernel level.
I can't tell you what Governor is best for your usage patterns - I have already warned you that some are borked so all you can do is try them all while watching their behavior. until you find one that works for you.
Let's use Smartmax as an example. It is not aware of bigs and smalls so any settings are applied to all cpus. If you set this Governor for both big and small cpus, changing the settings in big will change the settings in small as well. The default settings will automatically pick up on the settings you made in your DTB. The remaining settings are not bad as they are but can be improved on.
Try it out, set Smatmax as the governor both both big and small and observe the cpu freqs on idle and when touching / wiggling the screen. You should see it scale up rapidly and scale down to min freqs much better than Interactive was doing. Have a play with other settings if you want - I tend to speed up the ramp down rate and increase the ramp down step to make the cpus return to min freq quicker (for battery saving). Once you have experimented with Smartmax, have a play with the remaining Governors to see if there is anything you like. Something I learnt from a previous phone with a MTK octa core SoC is that there is no power penalty for readily scaling the cpus up to a (sensible) maximum freq. This gives the phone a fast, lag free feel that everyone wants and the cpu will complete its tasks faster so it can return to idle faster. A foolish overclock freq will burn more power - usually when the core voltage is cranked up stupidly high to get the overclock - bad for phone, bad for battery! A bad Governor setup will chew battery if it doesn't pull the frequencies back to idle at low loads but view this in light of the amount of background services you are running. MyAndroidTools is an excellent app to view and take control of pesky services.
The GPU also has a choice of Governors but I recommend sticking with the default Interactive. You get to choose the GPU Highspeed freq and load and both of these settings can be embedded in your DTB. Play with the freq / voltage tables at your own risk!
More to come....
Latest additions:
HMP Settings:
689C 0000020C up threshold
68AC 000000D6 down threshold
68BC 000000FE semiboost_up_threshold
68CC 000000A3 semiboost_down_threshold
68DC 02625A00 bootboost-duration us
68EC 0000001E down_compensation_timeout mS
68FC 0016E360 down_compensation_high_freq uS
690C 000F4240 down_compensation_mid_freq uS
691C 000C3500 down_compensation_low_freq uS
A final note:
If you want to know which CPU, GPU governors are best and what the difference is between them, there is loads of information already gathered on this topic. Most of it is quite dated but still relevant. Here is a good starting point:
[REF][GUIDE]Saber's guide on CPU governors, I/O schedulers and more!
Collective guide of CPU governors, I/O schedulers and other kernel variables I present to you a wonderful collection of descriptions, comparisons and graphs of common kernel variables. Before continuing on the wonderful journey of Linux kernel...
forum.xda-developers.com
There is a lot of misunderstanding on Eureka Kernel and ROM forums around the issue of memory management - LMK, Virtual Memory etc. Many users want something for nothing like running every known Samsung, Google and Social Media app in the background on a A12.1 or 13 ROM on a phone with 3GB RAM.
The basics of virtual memory have not changed - set ZRAM to no more than 50% of the available memory and set ZSWAP Memory pool to no more than 30%. Swappiness is best at 100% and vfs_cache_pressure set to 50. These settings are the favorite targets for abuse in tweaks offered by people of little knowledge.
Once you have your virtual memory sorted and have made smart decisions on what services/apps you are going to allow to self start on boot and hide in the background, it is a simple case of looking at the free memory to figure out how many more apps can run before killing occurs. It should surprise no-one when it occurs..... blame yourself, not the kernel, not the ROM, but your decisions on what you run and how you configure the phone.......