[ROM] Hybrid 5.2 for 10 inch aPad (updated August 10th)

23964 Views 67 Replies 22 Participants Last post by tonyccn, Jan 21, 2012

rogerbraun

Discussion Starter · Jul 31, 2010 (Edited by Moderator)

UPDATE (August 10th):- Fixed video player full screen bug.This is the same firmware as for the 7 inch version, with small changes to make it run on the 10 inch.You can flash the 10 inch by holding down the right rocker switch (i guess it's "volume up") when attaching usb and the device is off.Download is here.Thanks again to The Tablet Store for providing me with a testing device.

1 - 20 of 68 Posts

dankybett

· #2 · Jul 31, 2010

Thank you so much! First time flashing, and it all worked perfectly. I have been playing around with this rom for 15-20 minutes, and the device is so much better!Things I have noticed so far:It's fasterThe screen now rotates!Android comic viewer works when downloaded from the marketplace, and it is far less buggy than the version which the developers kindly released on their site as a work around. I am going to download some more apps to see what else now works after the update. The only thing I can't work out so far is: Videos no longer seem to go full screen, they just close if you attempt to full screen them.And a very minor issue - the background wallpaper does not stretch full screen. All in all though it is far nicer than the default rom, and reading comics will now be far nicer than before which was why I wanted a tablet in the first place. So please have a beer on me

Cheers Roger.

rogerbraun

Discussion Starter · #3 · Aug 1, 2010

I was not aware of the video error. Should not be too hard to fix, though.

MapleLeaf Tablets

· #4 · Aug 1, 2010

Roger... does this mean the generic zt180 10 inch should now work? no wifi prob, no battery drain?thanks mate(i have put off getting a 10 inch because of those issues. an cant find a 7 inch with g-sensor and full size usb instead)

rogerbraun

Discussion Starter · #5 · Aug 1, 2010

This is for the 10 inch that has a rockchip. I don't have a ZT180.

balpeter

· #6 · Aug 1, 2010

Dear RogerBraun!I have ordered an 8 inch aPad from Ms. Wang. This is not a crap android tablet with VIA processor, it is equipped with a Rockchip RK2808. I asked Ms. Wang have the devices pre-installed with different software. She told me that they are similar, just the metal aPad has 7 inch screen and lower price. Also she told me that their screen resolution (800x400) is same also. What's your opinion ? Do you recommend upgrading the firmware on an 8 inch aPad or do you think it's a bad idea ? Peter

balpeter

· #7 · Aug 1, 2010

Dear RogerBraun!I have ordered an 8 inch aPad from Ms. Wang. This is not a crap android tablet with VIA processor, it is equipped with a Rockchip RK2808. I asked Ms. Wang have the devices pre-installed with different software. She told me that they are similar, just the metal aPad has 7 inch screen and lower price. Also she told me that their screen resolution (800x400) is same also. Here is a link of the device: http://www.aliexpress.com/product-gs/329121762-8inch-MID-with-Google-Android-CPU-Processor-Rockchip-2808-Dual-Core-600MHz-500-MHZ-DSP-tablet-wholesalers.htmlWhat's your opinion ? Do you recommend upgrading the firmware on an 8 inch aPad or do you think it's a bad idea ? Peter

campacavallo

· #8 · Aug 2, 2010

sorry but the link not work!! can you fix it? i need this custom as a water

See less See more

eist1

· #9 · Aug 2, 2010

Roger,Have you been able to look at the video fullscreen problem on the 10" apad ROM? I am planning on flashing this ROM, just want to make sure the issue is fixed before flashing. Thanks for the great work!

xaueious

· #10 · Aug 2, 2010

Wow props to tabletstoreuk for supplying development! Good stuff

eist1

· #11 · Aug 4, 2010

Roger,I'm seeing the same issues with the 10" Hybrid 5.1 FirmwareVideos no longer seem to go full screen, they just close if you attempt to full screen them.And a very minor issue - the background wallpaper does not stretch full screen. Can you please take a look at this? Other than those problems, this seems to be working well. Also, is it possible to create a Hybrid 6 beta for the 10" too, so we can also test the new version? Thanks!

xaueious

· #12 · Aug 4, 2010

Does someone have a review up for these units? What's the screen resolution?

okivimak

· #13 · Aug 4, 2010

Roger: Do you have the factory original .img also for the 10" aPad, where can I find it, or does someone else know?Btw. I have bought two 7" RK2808s and one 10" for me, wife and kid, got the 10" yesterday, seems that the 10" original FW does not map a "back"-key at all (volumes UP/DOWN, the menu button and the home key)..Roger: you are using different kernel(.img) in your 10" and 7" 5.1-revs? I am doing a difference between imgs (to learn, so you don't have to explain every single change you have made). My CodeWright has a very visual and good difference machine (file-wise and directory-wise also), easy to view differences in large projects also.My 10" (wife and kid got 7" models ;D) aPad seems to get much warmer than the 7" ones, display brightness, contrast and resolution is WAYYY better than in the 7" models. The usable viewing angle is quite small though (inverts the image quite soon, cheap TN panel?) Touchscreen sensitivity is very good (worst in my 7" iRobot with aluminium back).Got adb working, looking at /dev/input/event0 (dd if=/dev/input/event0 of=/flash/event0.tst)

- Olli

See less See more

eist1

· #14 · Aug 4, 2010

I'm also having an issue switching between Landscape and Portrait modes. When the screen goes to Landscape mode, to get it back to Portrait mode I need to turn the tablet upside down (drawer at the top) to get it to go into Portrait mode, then I can quickly flip it around so the drawer is at the bottom.Can you let us 10" users know what needs to be updated in the 7" image to get them to work on the 10" tablets. Thanks!

eist1

· #15 · Aug 4, 2010

Also, if you could post the original firmware that came on the 10" Tablet you got that would be great, as I am trying to get the tablet back to original firmware.

xaueious

· #16 · Aug 5, 2010

roger is doing this during his free time. You guys can help yourself by learning to use adb, and running'getevent' to get the keycodes for the buttons. then post the output here. that will save us some time.you wouldn't want the original firmware. it's much worse than anything roger can make for you guys.

eist1

· #17 · Aug 5, 2010

Not sure what you are looking for, but does this help any?Right Button Next to Power Switch (Makes screen goto Landscape for a second, at least show Notification Bar):/dev/input/event0: 0001 0073 00000001/dev/input/event0: 0000 0000 00000000/dev/input/event0: 0001 0073 00000000/dev/input/event0: 0000 0000 00000000Left Button Next to Power Switch:/dev/input/event0: 0001 0072 00000001/dev/input/event0: 0000 0000 00000000/dev/input/event0: 0001 0072 00000000/dev/input/event0: 0000 0000 00000000Center Button:/dev/input/event0: 0001 003e 00000001/dev/input/event0: 0000 0000 00000000/dev/input/event0: 0001 003e 00000000/dev/input/event0: 0000 0000 00000000/dev/input/event3: 0003 0001 ffffffd1/dev/input/event3: 0003 0002 000003ac/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0000 00000000/dev/input/event3: 0003 0001 00000000/dev/input/event3: 0003 0002 000003db/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0000 ffffffd1/dev/input/event3: 0003 0001 ffffffd1/dev/input/event3: 0003 0002 0000040a/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0000 00000000/dev/input/event3: 0003 0001 0000002f/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0001 00000000/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0000 ffffffd1/dev/input/event3: 0003 0002 000003db/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0000 0000002f/dev/input/event3: 0003 0001 0000002f/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0000 00000000/dev/input/event3: 0003 0001 00000000/dev/input/event3: 0003 0002 0000040a/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0000 ffffffd1/dev/input/event3: 0003 0001 0000005e/dev/input/event3: 0003 0002 00000439/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0001 ffffffd1/dev/input/event3: 0003 0002 0000040a/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0000 00000000/dev/input/event3: 0003 0001 00000000/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0000 ffffffa2/dev/input/event3: 0003 0002 000003ac/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0002 00000439/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0000 ffffffd1/dev/input/event3: 0003 0001 0000005e/dev/input/event3: 0003 0002 000003ac/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0001 0000002f/dev/input/event3: 0003 0002 000003db/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0000 ffffffa2/dev/input/event3: 0003 0001 0000005e/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0000 ffffffd1/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0001 ffffffd1/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0000 ffffffa2/dev/input/event3: 0003 0001 0000005e/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0000 ffffffd1/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0000 0000002f/dev/input/event3: 0003 0001 ffffffd1/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0000 00000000/dev/input/event3: 0003 0001 00000000/dev/input/event3: 0003 0002 00000000/dev/input/event3: 0000 0000 00000000Menu Button (Small Button on Side):/dev/input/event0: 0001 003b 00000001/dev/input/event0: 0000 0000 00000000/dev/input/event3: 0003 0000 00000000/dev/input/event3: 0003 0001 0000005e/dev/input/event3: 0003 0002 00000439/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0000 0000 00000000/dev/input/event0: 0001 003b 00000000/dev/input/event0: 0000 0000 00000000/dev/input/event3: 0003 0000 ffffffa2/dev/input/event3: 0003 0002 000004c6/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0000 ffffffd1/dev/input/event3: 0003 0002 000003ac/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0000 ffffffa2/dev/input/event3: 0003 0001 ffffffd1/dev/input/event3: 0003 0002 0000040a/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0000 00000000/dev/input/event3: 0003 0001 0000005e/dev/input/event3: 0003 0002 000003db/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0001 00000000/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0000 0000002f/dev/input/event3: 0003 0001 ffffffd1/dev/input/event3: 0003 0002 0000040a/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0000 ffffffd1/dev/input/event3: 0003 0001 00000000/dev/input/event3: 0003 0002 000003db/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0000 00000000/dev/input/event3: 0003 0002 0000040a/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0000 ffffffd1/dev/input/event3: 0003 0001 ffffffd1/dev/input/event3: 0003 0002 000003db/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0001 00000000/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0000 0000005e/dev/input/event3: 0003 0001 0000005e/dev/input/event3: 0003 0002 0000040a/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0000 ffffffd1/dev/input/event3: 0003 0001 0000008d/dev/input/event3: 0003 0002 000003db/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0000 0000002f/dev/input/event3: 0003 0001 0000002f/dev/input/event3: 0003 0002 000003ac/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0000 ffffffd1/dev/input/event3: 0003 0002 000003db/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0000 00000000/dev/input/event3: 0003 0001 00000000/dev/input/event3: 0003 0002 00000439/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0002 000003ac/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0000 ffffff73/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0000 ffffffd1/dev/input/event3: 0003 0001 0000008d/dev/input/event3: 0003 0002 000003db/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0000 00000000/dev/input/event3: 0003 0001 00000000/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0000 ffffffa2/dev/input/event3: 0003 0001 0000005e/dev/input/event3: 0000 0000 00000000/dev/input/event3: 0003 0000 00000000/dev/input/event3: 0003 0001 00000000/dev/input/event3: 0003 0002 00000000/dev/input/event3: 0000 0000 00000000Touching Screen:/dev/input/event2: 0001 014a 00000001/dev/input/event2: 0003 0000 00000109/dev/input/event2: 0003 0001 0000006b/dev/input/event2: 0000 0000 00000000/dev/input/event2: 0003 0000 00000108/dev/input/event2: 0003 0001 0000006c/dev/input/event2: 0000 0000 00000000/dev/input/event2: 0001 014a 00000000/dev/input/event2: 0000 0000 00000000

See less See more

xaueious

· #18 · Aug 5, 2010 (Edited by Moderator)

He should have based his 10" ROM on a stock 10" ROM, copying over /system/framework and /system/app. He might also have copied everything in /system/libIn Android, you can assign keycodes to specific actions in a file under /system/usr/keylayout (forgot which one exactly. qwerty.kl?)Here you need to assign the keycode (you need to covert the hex keycode to decimal) to a desired action. A list of assignable keyevents is here: KeyEvent | Android DevelopersThat will allow you to map keys. You may want to do something similar to the recovery image too.You need to figure out which event number corresponds to your keypad. It looks like event0, but I don't remember the exact method to acquire that information.

campacavallo

· #19 · Aug 5, 2010

i logcat events during videplayer failure on fullscreen..if someone are interesting, this is a portion where video crash.. out of memory error

D/VideoDisplayView( 985): mPlayTime = 0D/VideoDisplayView( 985): mMediaPlayer = [email protected]/VideoDisplayView( 985): reset duration to -1 in openVideoD/VideoMioRk28xx( 710): Creating Vendor(Rk28xx) Specific MIO componentD/ ( 710): 111input[0]= 11 input[1]=90D/ ( 710): input len 2D/ ( 710): util audioObject = 2 tmp = 35D/ ( 710): utls audioObjectType12 = 2 status = 0D/ ( 710): utls audioObjectType22 = 2 status = 0D/ ( 710): utls audioObjectType2 = 2 status = 0D/ ( 710): utils status = 0V/VideoMioRk28xx( 710): Vendor(Rk28xx) Speicif CloseFrameBufD/ ( 710): 111input[0]= 11 input[1]=90D/ ( 710): input len 2D/ ( 710): util audioObject = 2 tmp = 35D/ ( 710): utls audioObjectType12 = 2 status = 0D/ ( 710): utls audioObjectType22 = 2 status = 0D/ ( 710): utls audioObjectType2 = 2 status = 0D/ ( 710): utils status = 0D/VideoController( 985): Enter initControllerViewD/VideoController( 985): Videocontoller : BacklightValue = 78D/ ( 985): unable to unlink '/data/data/android.rk.RockVideoPlayer/shared_prefs/android.rk.RockVideoPlayer.xml.bak': No such file or directory (errno=2)D/VideoDisplayView( 985): Enter setScreenSize() and width = 0 height = 0D/VideoDisplayView( 985): setScreenSize : setFixedSize() EXEE/SurfaceFlinger( 742): not enough memory for layer bitmap size=2359296D/MemoryDealer( 742): LayerBitmap (0x240108, size=8388608)D/MemoryDealer( 742): 0: 00240140 | 0x00000000 | 0x00033000 | F D/MemoryDealer( 742): 1: 00242ac0 | 0x00033000 | 0x00240000 | A D/MemoryDealer( 742): 2: 00291b68 | 0x00273000 | 0x00240000 | A D/MemoryDealer( 742): 3: 001b3128 | 0x004B3000 | 0x00240000 | A D/MemoryDealer( 742): 4: 00284668 | 0x006F3000 | 0x0010D000 | F D/MemoryDealer( 742): size allocated: 7077888 (6912 KB)E/SurfaceFlinger( 742): resizing buffer 1 to (1024,576) failed [fffffff4] Unknown error: -12E/SurfaceComposerClient( 742): surface (id=2, identity=13) is invalid, err=-12 (Out of memory)W/WindowManagerService( 742): Failure showing surface Surface(native-token=2505952) in Window{43ab21e8 android.rk.RockVideoPlayer/android.rk.RockVideoPlayer.VideoPlayActivity paused=false}I/WindowManagerService( 742): Out of memory for surface! Looking for leaks...W/WindowManagerService( 742): No leaked surfaces; killing applicatons!W/ActivityManager( 742): Killing processes for memory at adjustment 0W/ActivityManager( 742): Killing for memory: ProcessRecord{43974770 985:android.rk.RockVideoPlayer/10019} (adj 0)I/Process ( 742): Sending signal. PID: 985 SIG: 9I/ActivityManager( 742): Process android.rk.RockVideoPlayer (pid 985) has died.can be useful?

See less See more

xaueious

· #20 · Aug 5, 2010

Batch 3 Apads and this product both seem to have buggy videoplayersTry swapping out the Rockvideoplayer with one from of the Hybrid ROMs.I don't know if it's another issue because I don't know how to debug otherwise.

1 - 20 of 68 Posts

This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.