Musings - Streak 5 Android Development

Musings - Streak 5 Android Development

I've been playing with quite a few apps lately and talking to a few of those developers.
they've written stuff that should be able to scale to our wvga resolution quite happily but doesn't with the streak.
So there's something odd going on, examples include aTakephone, shapewriter and several others.
Obvious candidate is that Dell did something odd when creating the custom UI, but [email protected] beginning to have a niggling suspicion that this isn't a 800x480 screen..
I may hasten to add that's pure conjecture, and most likely wrong, but there's something weird going on, anyone have any ideas?

everything scales REALLLY wierd.
i.e all icons are the same SIZE they would be on a 3.7" screen
surly these things are a set number of pixels in size ... which means they should scale up and be bigger.... but they don't everything is 3.7" sized ... in most app's
and is there any way you can actually get the resoultion
i think dell ahve done somthing to scale down objects so they look the correct size on the huge screen.. otherwise everything would be HUGE

there must be a way of detecting the real dpi and resolution of the screen, this is linux after all, but I haven't found it yet..
Dell could well have done something to stop the scaling, but I can't see what it is other than change the dpi.

thyd have to have the screen showing a larger dpi then it actually has to cause the objects to display the way they do
for example the adw launcher app drawer button is exactly the same size as my desire ... its not been stretched at all which means its been scaled down.

having gone through my entire repetoire of linux commands (lspci lsusb xdpyinfo etc etc) with no success I decided to dmesg > /sdcard/test.txt
guess what appeared right at the start?
Code:
[ 0.832653] load_565rle_image: Can not open /logo.rle
[ 0.834146] Registered led device: lcd-backlight
[ 0.834213] BootLog, -auo_init, ret=0
[ 0.834866] BootLog, +lcdc_adv7520_init
[ 0.834886] lcdc_adv7520_init(), HTX_720p_60
[ 0.836033] [Jackie] lcdc_probe(), pdev=0x9f000800, mfd=0x9faf8280
[ 0.846386] FrameBuffer[1] 1280x720 size=3686400 bytes is registered successfully!
[ 0.846460] load_565rle_image: Can not open /logo.rle
[ 0.847253] lcdc_hdmi_init(): i2c_add_driver...HDMI
now why does the HDMI get called so early, why is it called at all without the dock
and why is it the only reference to framebuffer?

Very very odd, just another reason I hope to see custom ROMs out there.
Is there a software program to take screenshots with of the device? That would give you the resolution.
.

screen shot shoot me, 480 x 800
so it is
we really need more support lol

yeah I did a clean boot today and dmesg again..
lots more interesting info and a 480x800 framebuffer call near the start
but also lots of debugger logging calls, is that normal with android devices?

Looking forward to seeing some custom roms for this, had another play with one today in O2 and its just amazing, but I am reluctant to give up my Desire with Android 2.2 without knowing when the Streak is getting either an official upgrade or custom roms.

Did "Logcat > dump.txt" and got a load more info
Code:
I/SurfaceFlinger( 1223): vendor : Android
I/SurfaceFlinger( 1223): version : 1.31 Android META-EGL
I/SurfaceFlinger( 1223): extensions:
I/SurfaceFlinger( 1223): Client API: OpenGL ES
I/EGLDisplaySurface( 1223): using (fd=23)
I/EGLDisplaySurface( 1223): id = msmfb31_10000
I/EGLDisplaySurface( 1223): xres = 480 px
I/EGLDisplaySurface( 1223): yres = 800 px
I/EGLDisplaySurface( 1223): xres_virtual = 480 px
I/EGLDisplaySurface( 1223): yres_virtual = 1600 px
I/EGLDisplaySurface( 1223): bpp = 16
I/EGLDisplaySurface( 1223): r = 11:5
I/EGLDisplaySurface( 1223): g = 5:6
I/EGLDisplaySurface( 1223): b = 0:5
I/EGLDisplaySurface( 1223): width = 76 mm (160.421051 dpi)
I/EGLDisplaySurface( 1223): height = 127 mm (160.000000 dpi)
and
Code:
W/HAL ( 1223): load: module=/system/lib/hw/copybit.qcom.so error=Cannot load library: load_library[986]: Library '/system/lib/hw/copybit.qcom.so' not found
W/HAL ( 1223): load: module=/system/lib/hw/copybit.8x50.so error=Cannot load library: load_library[986]: Library '/system/lib/hw/copybit.8x50.so' not found
W/SurfaceFlinger( 1223): ro.sf.lcd_density not defined, using 160 dpi by default.
I/SurfaceFlinger( 1223): OpenGL informations:
I/SurfaceFlinger( 1223): vendor : Android
I/SurfaceFlinger( 1223): renderer : Android PixelFlinger 1.0
I/SurfaceFlinger( 1223): version : OpenGL ES-CM 1.0
I/SurfaceFlinger( 1223): extensions: GL_OES_byte_coordinates GL_OES_fixed_point GL_OES_single_precision GL_OES_read_format GL_OES_compressed_paletted_texture GL_OES_draw_texture GL_OES_matrix_get GL_OES_query_matrix GL_ARB_texture_compression GL_ARB_texture_non_power_of_two GL_ANDROID_direct_texture GL_ANDROID_user_clip_plane GL_ANDROID_vertex_buffer_object GL_ANDROID_generate_mipmap
W/HAL ( 1223): load: module=/system/lib/hw/copybit.qcom.so error=Cannot load library: load_library[986]: Library '/system/lib/hw/copybit.qcom.so' not found
W/HAL ( 1223): load: module=/system/lib/hw/copybit.8x50.so error=Cannot load library: load_library[986]: Library '/system/lib/hw/copybit.8x50.so' not found
W/HAL ( 1223): load: module=/system/lib/hw/overlay.qcom.so error=Cannot load library: load_library[986]: Library '/system/lib/hw/overlay.qcom.so' not found
W/HAL ( 1223): load: module=/system/lib/hw/overlay.8x50.so error=Cannot load library: load_library[986]: Library '/system/lib/hw/overlay.8x50.so' not found
W/HAL ( 1223): load: module=/system/lib/hw/overlay.default.so error=Cannot load library: load_library[986]: Library '/system/lib/hw/overlay.default.so' not found
Wonder if those drivers are in the git...

I/EGLDisplaySurface( 1223): xres_virtual = 480 px
I/EGLDisplaySurface( 1223): yres_virtual = 1600 px
very strange
why would they scale only the yres....
anyway... we can pull the driver... if we got the kernel source thats the main thing

I'm now fairly convinced its using standard qualcomm surf kernel, don't even think we need specific dell drivers..
The yres_virtual is to allow screen panning I think and is fairly usual framebuffer behaviour.

well we could try and compile 2.1 or 2.2 and see what happens...
worst thing ... it wont boot....
not like were playing with radio so no chance of bricking.

finally got around to building from the codearoura git
kernel seems about same size as 4399 and I extracted ramdisk.img from the streak .
Thought I'd try fastboot boot zImage ramdisk.img as it appears to be a safe way of trying it (not writing permanently to device)
but "boot" gives me an error FAILED (remote: invalid command), so it may have been removed from the bootloader..
Don't really want to test flashing it as I'm away for a week on holibobs and would rather have a working streak than a non working one..

Related

[Q] Wildfire S Port.

Someone is successful to make a Porting, of the ROM of the Wildfire S, for our LG Optimus ONE?
It exists already for:
HTC Aria, Sony Ericsson X8, HTC myTouch 3G, HTC Wildfire, HTC Legend, LG Optimus GT540, Huawei IDEOS.
The Hardware of HTC Wildfire S, is similar to ours, but still nobody has been decided to carry this rom, for we.
Please, others members, of other forum, have already made it.

i agree having a Sense rom ported for Optimus One wud make me happy devs please look into it..+1 for above ..Also that way we get to have Adobe flashlite on our phones too i guess

Atm I don't think it will be to much interest in a Sense or a Miui rom since we are so close to GB. Afterwards maybe but we don't have to much of a workforce. Maybe if we set up a donation for acquiring dev phones it would be a start.

For LG GT540 port! And we no?
Sense ROM has been ported to LG Optimus GT540:
http://forum.xda-developers.com/showthread.php?t=1046051
And for our LG Optimus ONE, no, why??????????????

I'll try do a sense port. I need to start studying the GT540 sources and putting LG OO kernel in it

useless ... I have tried different kernel, but with negative results
-----
inutile... ho già provato con vari kernel ma con esiti negativi

Agreed, a ROM with sense would be juicy!

ciaox said:
I'll try do a sense port. I need to start studying the GT540 sources and putting LG OO kernel in it
Click to expand...
Click to collapse
We hope you do. Htc Sense gingerbread is the best port we can get. I hope some devs will also try.

Smells like useless work to me . In the end Sense is just a Launcher-like app with some improvements but those are meager and not something you would absolutely need

Zerobarat1 said:
Smells like useless work to me . In the end Sense is just a Launcher-like app with some improvements but those are meager and not something you would absolutely need
Click to expand...
Click to collapse
And what about the flash support ( or flashlite ) that sense has ... THAT would definitely be AWESOME if it could run on OO.

Even for IDEOS?
I communicate to you that the ROM Sense, has been ported for Huawei IDEOS
http://forum.xda-developers.com/showthread.php?t=927861
And for we nothing, that isn' t correct

Well I am trying to port Wildfire S official rom
I used the sys dump from Official ROM and after using modified boot.img with gingerbread kernel i find the Graphics lib's don't work
If anybody can give me a clue to fix this i can try to make this work on our beloved P500
Below is the logcat:
E/SurfaceFlinger( 1804): eglSwapBuffers: EGL error 0x3001 (EGL_NOT_INITIALIZED)
W/zipro ( 1814): Unable to open zip '/system/etc/customer/bootanimation.zip': No such file or directory
D/HtcBootAnimation( 1814): Get cid:SPCS_001
D/HtcBootAnimation( 1814): filepath:/system/customize/CID/SPCS_001.xml
D/HtcBootAnimation( 1814): Load /system/customize/CID/default.xml
D/HtcBootAnimation( 1814): Using OpenGL
E/HtcBootAnimation( 1814): Could not find width.
E/HtcBootAnimation( 1814): Could not find height.
E/HtcBootAnimation( 1814): Could not find framerate.
E/HtcBootAnimation( 1814): Could not find part1.
E/HtcBootAnimation( 1814): Could not find part2.
E/HtcBootAnimation( 1814): Could not find part3.
D/libEGL ( 1814): loaded /system/lib/egl/libGLES_android.so
D/libEGL ( 1814): loaded /system/lib/egl/libEGL_adreno200.so
D/libEGL ( 1814): loaded /system/lib/egl/libGLESv1_CM_adreno200.so
D/libEGL ( 1814): loaded /system/lib/egl/libGLESv2_adreno200.so
W/libEGL ( 1814): 0: eglInitialize(0x1) failed (EGL_SUCCESS)

Is here SENSE for O1 http://forum.xda-developers.com/showthread.php?t=1112398

by.adrian said:
Is here SENSE for O1 http://forum.xda-developers.com/showthread.php?t=1112398
Click to expand...
Click to collapse
That is froyo, he meant gingerbread wildfire s....
Sent using LGE Xda Secret phone

Bitter_Sugar said:
I used the sys dump from Official ROM and after using modified boot.img with gingerbread kernel i find the Graphics lib's don't work
If anybody can give me a clue to fix this i can try to make this work on our beloved P500
Below is the logcat:
E/SurfaceFlinger( 1804): eglSwapBuffers: EGL error 0x3001 (EGL_NOT_INITIALIZED)
W/zipro ( 1814): Unable to open zip '/system/etc/customer/bootanimation.zip': No such file or directory
D/HtcBootAnimation( 1814): Get cid:SPCS_001
D/HtcBootAnimation( 1814): filepath:/system/customize/CID/SPCS_001.xml
D/HtcBootAnimation( 1814): Load /system/customize/CID/default.xml
D/HtcBootAnimation( 1814): Using OpenGL
E/HtcBootAnimation( 1814): Could not find width.
E/HtcBootAnimation( 1814): Could not find height.
E/HtcBootAnimation( 1814): Could not find framerate.
E/HtcBootAnimation( 1814): Could not find part1.
E/HtcBootAnimation( 1814): Could not find part2.
E/HtcBootAnimation( 1814): Could not find part3.
D/libEGL ( 1814): loaded /system/lib/egl/libGLES_android.so
D/libEGL ( 1814): loaded /system/lib/egl/libEGL_adreno200.so
D/libEGL ( 1814): loaded /system/lib/egl/libGLESv1_CM_adreno200.so
D/libEGL ( 1814): loaded /system/lib/egl/libGLESv2_adreno200.so
W/libEGL ( 1814): 0: eglInitialize(0x1) failed (EGL_SUCCESS)
Click to expand...
Click to collapse
bootanimation directory is different for p500?

Yeah HTC seems to have all the settings and bootanimation.zip stored under /system/customize folder.
I am trying to port HTC Sense 2.1 (Gingerbread 2.3.3) to P500
So i need to start the port from the scratch as i don't have a reference to work on it.

Guys, Sense is not that great you know. My cousin bought a Wildfire S and after much inspection, its nothing great at all, the UI isn't that extraordinary. Sense even lack some basic commands that I'm used to on normal Gingerbread roms :/

[Q] archos detects my canon powershot camera but doesn't show the pictures

Hi,
When I plug my canon powershot camera into the archos 101 usb, it recognises my camera (message "external camera connected" or something like that) but when I look into the folder, it's empty... it doesn't show my pictures stored on the camera's sd card
anybody any ideas?
external hd drives, mouse, usb sticks etc all work fine
Cheers
B

berre said:
When I plug my canon powershot camera into the archos 101 usb, it recognises my camera (message "external camera connected" or something like that) but when I look into the folder, it's empty... it doesn't show my pictures stored on the camera's sd card
Click to expand...
Click to collapse
Most camera's have a setting to change the usb mode from PTP to USB STORAGE. Have you tried to change that?

I've went through the menu's of my camera but doesn't look like it has this setting...
cheers
B

berre said:
I've went through the menu's of my camera but doesn't look like it has this setting...
Click to expand...
Click to collapse
When You connect your camera to a computer what OS is the computer running?
How is the SD card in your camera formatted?

Are the photos take in RAW format and not JPG??? Your archos won't be able to view RAW, which is a shame...

OS is XP, pictures are jpeg format.
I'll see if I can find out how the SD is formatted tonight.
cheers
b

file system of the SD card is FAT
I've tried connecting a USB card reader to read the SD card but I get the same behaviour as when I try to connect my phone
see topic http://forum.xda-developers.com/showthread.php?t=1123491
so I'm kinda stuck on getting the images on my archos 101... a person in the other topic suggested installing urukdroid, would this help?
cheers
B

I have the same problem. It worked fine before, then one day I connected it and it wasn't working. Didn't change anything on the camera.

It is sadly a known problem with the 101 that the USB breaks.
The only chance you have is to RMA the device

fzelle said:
It is sadly a known problem with the 101 that the USB breaks.
The only chance you have is to RMA the device
Click to expand...
Click to collapse
There's nothing in this thread that says hardware failure. Why would you say the only choice is to RMA it?
berre: You should do some testing mate. Install OSMonitor and use it to watch the dmesg output when you plug in the usb devices. Test a few USB Flash Drives, wireless mice, etc. As I've said, I certainly have trouble with some USB devices, but it's not an RMA situation.
As for getting the pictures on your 101, copy them to your PC, then copy over wifi, or connect the A101 to your PC, or use a microSD card in your camera with a microsd adapter, then you can just put it straight into the 101. Or move them to a usb flash drive if you can find a working one.

this is my alogcat
seems like it's discovering my camera (detects that it's a canon) but there's an error message "Parameter 'INTERFACE' not found"
anybody any idea what this means?
D/dalvikvm(12735): GC_FOR_MALLOC freed 3809 objects / 173920 bytes in 115ms
W/InputManagerService( 1319): Window already focused, ignoring focus gain of: [email protected]
D/WifiService( 1319): ACTION_BATTERY_CHANGED pluggedType: 0
D/SiMiClock( 1717): onUpdate
I/cat ( 1174): <7>usb usb2: usb resume
I/cat ( 1174): <7>hub 2-0:1.0: hub_resume
I/cat ( 1174): <7>hub 2-0:1.0: port 1: status 0101 change 0001
I/cat ( 1174): <7>hub 2-0:1.0: state 7 ports 1 chg 0002 evt 0000
I/cat ( 1174): <7>hub 2-0:1.0: port 1, status 0101, change 0000, 12 Mb/s
I/cat ( 1174): <6>usb 2-1: new high speed USB device using musb_hdrc and address 4
I/cat ( 1174): <7>usb 2-1: default language 0x0409
I/cat ( 1174): <6>usb 2-1: New USB device found, idVendor=04a9, idProduct=30fc
I/cat ( 1174): <6>usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
I/cat ( 1174): <6>usb 2-1: Product: Canon Digital Camera
I/cat ( 1174): <6>usb 2-1: Manufacturer: Canon Inc.
E/NetlinkEvent( 1223): NetlinkEvent::FindParam(): Parameter 'INTERFACE' not found
I/Vold ( 1223): handleUsbEvent(): Missing property, ignoring event
I/cat ( 1174): <7>usb 2-1: uevent
I/cat ( 1174): <7>usb 2-1: usb_probe_device
I/cat ( 1174): <6>usb 2-1: configuration #1 chosen from 1 choice
I/cat ( 1174): <7>usb 2-1: adding 2-1:1.0 (config #1, interface 0)
I/cat ( 1174): <7>usb 2-1:1.0: uevent
I/Vold ( 1223): Starting gphotofs
I/StorageNotification( 1319): Media {/mnt/storage/extcamera} state changed from {unmounted} -> {mounted}
W/StorageNotification( 1319): setMediaStorageNotification type=4 icon=17302220 visible=true
D/MediaScannerReceiver( 4966): Just got intent Intent { act=android.intent.action.MEDIA_MOUNTED dat=file:///mnt/storage/extcamera cmp=com.android.providers.media/.MediaScannerReceiver (has extras) }
I/BootReceiver( 6648): Got intent with action android.intent.action.MEDIA_MOUNTED
I/cat ( 1174): <7>/mnt/flash/releases/G8A/v2.3.25-r85838/arcbuild/linux/drivers/usb/core/inode.c: creating file '004'
I/cat ( 1174): <7>hub 2-0:1.0: state 7 ports 1 chg 0000 evt 0002
I/cat ( 1174): <7>hub 2-0:1.0: port 1 enable change, status 00000503
D/AosUpdate:MediaMountReceiver(12628): android.intent.action.MEDIA_MOUNTED / file:///mnt/storage/extcamera
D/dalvikvm(28664): GC_EXPLICIT freed 17329 objects / 1063424 bytes in 77ms
D/WifiService( 1319): ACTION_BATTERY_CHANGED pluggedType: 0
D/SiMiClock( 1717): onUpdate
I/ActivityManager( 1319): Starting activity: Intent { act=archos.intent.action.FILE_MANAGER dat=file:///mnt/storage/extcamera flg=0x10000000 cmp=com.archos.fm/.FileManager bnds=[0,58][980,122] }
V/alogcat (12735): save instance
V/alogcat (12735): paused
D/FileManager(12638): onResume: register the ActivityBackgroundResizer
D/ActivityBackgroundResizer(12638): onGlobalLayout
D/ActivityBackgroundResizer(12638): onGLobalLayout: 980x600
D/ActivityBackgroundResizer(12638): onGlobalLayout: no resizing required (980x600)
I/ActivityManager( 1319): Displayed activity com.archos.fm/.FileManager: 533 ms (total 533 ms)
D/alogcat (12735): stopping ...
D/alogcat (12735): stopped
W/KeyCharacterMap(12638): No keyboard for id -1
W/KeyCharacterMap(12638): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
D/dalvikvm(12638): GC_EXTERNAL_ALLOC freed 3643 objects / 184896 bytes in 74ms
D/dalvikvm(12638): GC_EXTERNAL_ALLOC freed 678 objects / 38768 bytes in 55ms
D/dalvikvm(12638): GC_EXTERNAL_ALLOC freed 7 objects / 232 bytes in 27ms
D/dalvikvm(12638): GC_EXTERNAL_ALLOC freed 7 objects / 216 bytes in 27ms
D/dalvikvm(12638): GC_EXTERNAL_ALLOC freed 8 objects / 264 bytes in 27ms
D/dalvikvm(12638): GC_EXTERNAL_ALLOC freed 196 objects / 7064 bytes in 27ms
W/KeyCharacterMap(12638): No keyboard for id -1
W/KeyCharacterMap(12638): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
D/alogcat (12735): stopping ...
D/alogcat (12735): canceling periodic saves
V/alogcat (12735): started
V/alogcat (12735): resumed
D/alogcat (12735): starting ...
W/IInputConnectionWrapper(12638): showStatusIcon on inactive InputConnection
D/dalvikvm(31530): GC_FOR_MALLOC freed 310 objects / 443984 bytes in 124ms
D/dalvikvm(31530): GC_FOR_MALLOC freed 222 objects / 439856 bytes in 75ms
D/SiMiClock( 1717): onUpdate
D/dalvikvm(31530): GC_FOR_MALLOC freed 167 objects / 435048 bytes in 38ms
D/dalvikvm(31530): GC_FOR_MALLOC freed 73 objects / 430536 bytes in 76ms
D/dalvikvm(31530): GC_FOR_MALLOC freed 70 objects / 430424 bytes in 77ms
I/cat ( 1174): <7>hub 2-0:1.0: state 7 ports 1 chg 0000 evt 0002
I/cat ( 1174): <7>hub 2-0:1.0: port 1, status 0100, change 0001, 12 Mb/s
I/cat ( 1174): <6>usb 2-1: USB disconnect, address 4
I/cat ( 1174): <7>usb 2-1: unregistering device
I/cat ( 1174): <7>usb 2-1: usb_disable_device nuking all URBs
I/cat ( 1174): <7>usb 2-1: unregistering interface 2-1:1.0
I/Vold ( 1223): Stopping gphotofs
I/cat ( 1174): <7>usb 2-1:1.0: uevent
I/StorageNotification( 1319): Media {/mnt/storage/extcamera} state changed from {mounted} -> {unmounted}
D/VoldCmdListener( 1223): volume shared /mnt/storage ums
W/StorageNotification( 1319): setMediaStorageNotification type=4 icon=0 visible=false
D/MediaScannerReceiver( 4966): Just got intent Intent { act=android.intent.action.MEDIA_EJECT dat=file:///mnt/storage/extcamera cmp=com.android.providers.media/.MediaScannerReceiver }
E/NetlinkEvent( 1223): NetlinkEvent::FindParam(): Parameter 'INTERFACE' not found
I/Vold ( 1223): handleUsbEvent(): Missing property, ignoring event
I/cat ( 1174): <7>usb 2-1: uevent
I/BootReceiver( 6648): Got intent with action android.intent.action.MEDIA_EJECT
I/logwrapper(12750): /usr/bin/gphotofs terminated by exit(1)
I/cat ( 1174): <7>hub 2-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x100
I/cat ( 1174): <3>init: untracked pid 12770 exited
I/cat ( 1174): <7>hub 2-0:1.0: hub_suspend
I/cat ( 1174): <7>usb usb2: bus auto-suspend
D/dalvikvm( 4966): GC_EXPLICIT freed 1213 objects / 61504 bytes in 91ms
D/dalvikvm( 6648): GC_EXPLICIT freed 201 objects / 11520 bytes in 73ms
W/KeyCharacterMap(12735): No keyboard for id -1
W/KeyCharacterMap(12735): Using default keymap: /system/usr/keychars/qwerty.kcm.bin

The (1223) shows that message is actually a different process, so I don't think that's related. Look at this line though:
/StorageNotification( 1319): Media {/mnt/storage/extcamera} state changed from {unmounted} -> {mounted}
Notice it says /mnt/storage/extcamera? And "state changed from unmounted to mounted"? Have you looked in that directory? I bet your pics are there.

nope, I think I checked that yesterday and folder was empty... I'll double-check tonight but unless there's a second extcamera folder, it was empty
cheers
b

confirmed, that directory is empty as well.
brgds
b

Maybe i'm wrong, but i think that this isn't the pictures folder, but the access to the camera, maybe Android want to use your camera as a camera (and not as a storage)
I don't really know, but, with my little linux knowledge i think that it's possible.
(In Linux everything is a file, even the hardware)

eagleofdeath13 said:
Maybe i'm wrong, but i think that this isn't the pictures folder, but the access to the camera, maybe Android want to use your camera as a camera (and not as a storage)
I don't really know, but, with my little linux knowledge i think that it's possible.
(In Linux everything is a file, even the hardware)
Click to expand...
Click to collapse
Everything is possible in Linux, but in this case, the mount is being handled by gphotofs, which is a PTP camera storage driver. It's supposed to mount PTP cameras as R/W filesystems, allowing you to access the stored photos. It's independently developed though, so I'm not sure where it got built in.
Gphotofs does not fully support Canon cameras, supposedly Canon locked their PTP to read only, and it's looks like development stopped in 2008, but it seems like it should still show the files though.
I know it's a big step, but I'd try Urukdroid. I don't have a Canon around to test with, but I'd be interested to see what happens. The 1.0 easy install can be done and set up in less than 10 minutes, with no linux or even windows knowledge needed.
One question though. In the log it shows the camera being disconnected and then gphotofs unmounts it. Does this happen immediately after mounting, or did you unplug the usb? If the log shows "/StorageNotification( 1319): Media {/mnt/storage/extcamera} state changed from {mounted} -> {unmounted}" before you actually disconnect the camera, then at least I know why the extcamera directory is empty. That would just leave overamping and canon PTP incompatibilty as the prime suspects.

msticninja said:
One question though. In the log it shows the camera being disconnected and then gphotofs unmounts it. Does this happen immediately after mounting, or did you unplug the usb? If the log shows "/StorageNotification( 1319): Media {/mnt/storage/extcamera} state changed from {mounted} -> {unmounted}" before you actually disconnect the camera, then at least I know why the extcamera directory is empty. That would just leave overamping and canon PTP incompatibilty as the prime suspects.
Click to expand...
Click to collapse
I unplugged the usb so that's normal... first I'm gonna try another usb sd card reader as workaround
I'm not scared of urukdroid but a bit reluctant to void my warranty, especially seen the USB issue which seems to be quite common. I also want to see what the new firmware is all about (next week?)
But I think I might be going for urukdroid anyways as my storage for apps is running out
cheers
B

berre said:
I unplugged the usb so that's normal... first I'm gonna try another usb sd card reader as workaround
I'm not scared of urukdroid but a bit reluctant to void my warranty, especially seen the USB issue which seems to be quite common. I also want to see what the new firmware is all about (next week?)
But I think I might be going for urukdroid anyways as my storage for apps is running out
cheers
B
Click to expand...
Click to collapse
Hmm, I wonder about gphotofs then. If I get some time I'll research it. As far as Uruk, Archos trolls the forums. They've seen our firmware, and they can't really make a case for it doing any real damage. If you have to send it back for replacement, just reflash the original firmware. They don't bother asking, and so far everybody I know with the "SDE Watermark" has gotten a replacement without issue.

[GT-S5282] CM 10.1 Bugs, Disscussion, Questions,

Orginally, this was the thread for the rom, And this was a bug tracker and discussion board.
You can find the rom thread at here. http://forum.xda-developers.com/showthread.php?p=52641719
"Why didn't you create a dev-db?" You didn't read the above linked thread, did you?
THE ROM IS DISCONTINUED. ALL BUG REPORTS WILL BE IGNORED.

So this end...?!

LahKeda said:
So this end...?!
Click to expand...
Click to collapse
nah.. buddy this is not the end.. i'm just fed up with this phone..
anyone willing can continue from here.. or better build it from source,

If u can send some documents and resources to learn how to build roms please send it to me ...and I will try to build rom to this phone

psych.half said:
nah.. buddy this is not the end.. i'm just fed up with this phone..
anyone willing can continue from here.. or better build it from source,
Click to expand...
Click to collapse
Have any logs? I had given up due to the lack of the device.

Unjustified Dev said:
Have any logs? I had given up due to the lack of the device.
Click to expand...
Click to collapse
Logs.. oh logs.. hundreds of mb of logs.. @[email protected] Anyways latest log with h/w enabled is this..
Code:
E/libEGL ( 364): load_driver(/system/lib/egl/libEGL_mali.so): Cannot load library: soinfo_relocate(linker.cpp:1013):
cannot locate symbol "shim_eglSetBlobCacheFuncsANDROID" referenced by "libEGL_mali.so"...
E/libEGL ( 364): eglGetDisplay:121 error 300c (EGL_BAD_PARAMETER)
E/libEGL ( 364): eglInitialize:137 error 3008 (EGL_BAD_DISPLAY)

psych.half said:
Logs.. oh logs.. hundreds of mb of logs.. @[email protected] Anyways latest log with h/w enabled is this..
Code:
E/libEGL ( 364): load_driver(/system/lib/egl/libEGL_mali.so): Cannot load library: soinfo_relocate(linker.cpp:1013): cannot locate symbol "shim_eglSetBlobCacheFuncsANDROID" referenced by "libEGL_mali.so"...
E/libEGL ( 364): eglGetDisplay:121 error 300c (EGL_BAD_PARAMETER)
E/libEGL ( 364): eglInitialize:137 error 3008 (EGL_BAD_DISPLAY)
Click to expand...
Click to collapse
go into stock system it can be a dump and open a terminal in lib folder and type grep -R "shim_eglSetBlobCacheFuncsANDROID" then you should know the blob missing maybe

Unjustified Dev said:
go into stock system it can be a dump and open a terminal in lib folder and type grep -R "shim_eglSetBlobCacheFuncsANDROID" then you should know the blob missing maybe
Click to expand...
Click to collapse
I already arm-readel all the symbols and stuffs..
If i had found it in stock libs, i would already have added that blobs... There isn't that symbol in the stock libs too... like wtf..

psych.half said:
I already arm-readel all the symbols and stuffs..
If i had found it in stock libs, i would already have added that blobs... There isn't that symbol in the stock libs too... like wtf..
Click to expand...
Click to collapse
Are you trying to use hwcomposer? Because I read you switched to sw rendering? It might be better to back to jellybean 4.1.2 where you have a fighting chance.

Unjustified Dev said:
Are you trying to use hwcomposer? Because I read you switched to sw rendering? It might be better to back to jellybean 4.1.2 where you have a fighting chance.
Click to expand...
Click to collapse
f***** found it,,!!!! hwcomposer working..
Code:
I/SPRDhwcomposer( 96): type=0, flags=00000000, handle=0x41416970, tr=00, blend=0105, {0,0,240,19}, {0,0,240,19}
and seems to me like.. gralloc didnt crash this time
Code:
I/SurfaceFlinger( 96): SurfaceFlinger is starting
I/SurfaceFlinger( 96): use dithering
I/SurfaceFlinger( 96): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
I/run-parts( 98): run-parts: /system/etc/init.d/50selinuxrelabel exited with code 1
D/libEGL ( 96): loaded /system/lib/egl/libEGL_mali.so
D/libEGL ( 96): loaded /system/lib/egl/libGLESv1_CM_mali.so
D/libEGL ( 96): loaded /system/lib/egl/libGLESv2_mali.so
I/[Gralloc]( 96): using (fd=14)
I/[Gralloc]( 96): id = sc8810fb
I/[Gralloc]( 96): xres = 240 px
I/[Gralloc]( 96): yres = 320 px
I/[Gralloc]( 96): xres_virtual = 240 px
I/[Gralloc]( 96): yres_virtual = 640 px
I/[Gralloc]( 96): bpp = 32
I/[Gralloc]( 96): r = 0:8
I/[Gralloc]( 96): g = 8:8
I/[Gralloc]( 96): b = 16:8
I/[Gralloc]( 96): width = 50 mm (121.919998 dpi)
I/[Gralloc]( 96): height = 65 mm (125.046150 dpi)
I/[Gralloc]( 96): refresh rate = 60.00 Hz
I/SPRDhwcomposer( 96): fb_width = 240,fb_height = 320
E/SPRDhwcomposer( 96): alloc overlay buffer failed
E/SPRDhwcomposer( 96): tmp alloc overlay buffer failed
E/SurfaceFlinger( 96): composer device failed to initialize (Invalid argument)
I/SurfaceFlinger( 96): Using composer version 0.0
W/SurfaceFlinger( 96): getting VSYNC period from fb HAL: 16666666
W/SurfaceFlinger( 96): no suitable EGLConfig found, trying without EGL_FRAMEBUFFER_TARGET_ANDROID
W/Trace ( 96): error opening trace file: No such file or directory (2)
I/SurfaceFlinger( 96): EGL informations:
I/SurfaceFlinger( 96): vendor : Android
I/SurfaceFlinger( 96): version : 1.4 Android META-EGL
I/SurfaceFlinger( 96): extensions: EGL_KHR_image EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_fence_sync EGL_ANDROID_image_native_buffer
I/SurfaceFlinger( 96): Client API: OpenGL_ES
I/SurfaceFlinger( 96): EGLSurface: 8-8-8-8, config=0x6000000a
I/SurfaceFlinger( 96): OpenGL ES informations:
I/SurfaceFlinger( 96): vendor : ARM
I/SurfaceFlinger( 96): renderer : Mali-300
I/SurfaceFlinger( 96): version : OpenGL ES-CM 1.1 Spreadtrum Build
I/SurfaceFlinger( 96): extensions: GL_EXT_debug_marker 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 GL_EXT_robustness
I/SurfaceFlinger( 96): GL_MAX_TEXTURE_SIZE = 4096
I/SurfaceFlinger( 96): GL_MAX_VIEWPORT_DIMS = 4096 x 4096
D/SurfaceFlinger( 96): Screen acquired, type=0 flinger=0x40a80318
This means? Hw rendering will also work?? right??/
Well... screen now feels snappier..

Is This ROM Stable now ? Or ready to use ??

does it shows network .. i mean the data service is working or not??

pratyush02 said:
does it shows network .. i mean the data service is working or not??
Click to expand...
Click to collapse
fixing network is next to impossible... every time i try bootloop..

Om! Lp ChazZ said:
Is This ROM Stable now ? Or ready to use ??
Click to expand...
Click to collapse
not really... at least now hw rendering works...

Hi.No news about cm?

this is it
so this is it right
we all tried guys network can not be fixed by us
we need a real hardcore samsung cm dev who can fix it
but no other dev i know is ready to work for star
i hope we recieve a stable cm in the future
anyways thx to
all who helped to develop cm to what it is right now

@rchit said:
so this is it right
we all tried guys network can not be fixed by us
we need a real hardcore samsung cm dev who can fix it
but no other dev i know is ready to work for star
i hope we recieve a stable cm in the future
anyways thx to
all who helped to develop cm to what it is right now
Click to expand...
Click to collapse
this post was made when.. hw rendering seemed impossible to be fixed.. now that i have fixed it.. i realized that if you give up then everything is impossible...
check the upated OP and my new thread at dev section.. i am planning to continue.. not giving up this time..
and yeah.. samsung doesn't give sources of their proprietary libs.. so any real developer will have difficulties in fixing stuffs.. but they didn't give up on their devices.. and neither should we..
sammy doesnt give a s**t about this device, the devs don't give a s**t about this device.. just hoping that this may change doesnt do much.. we gotta step up ourselves and work for our own device...

psych.half said:
this post was made when.. hw rendering seemed impossible to be fixed.. now that i have fixed it.. i realized that if you give up then everything is impossible...
check the upated OP and my new thread at dev section.. i am planning to continue.. not giving up this time..
and yeah.. samsung doesn't give sources of their proprietary libs.. so any real developer will have difficulties in fixing stuffs.. but they didn't give up on their devices.. and neither should we..
sammy doesnt give a s**t about this device, the devs don't give a s**t about this device.. just hoping that this may change doesnt do much.. we gotta step up ourselves and work for our own device...
Click to expand...
Click to collapse
but we do give a s**t about the device so lets rock!!!
M down to help when m on pc

Really appreciate your hard work :good:
Hoping you can fix the RIL too :fingers-crossed:

work on single sim?

[Q] Dell Venue 8 7840 - Need factory ROM image (NANDROID, flashable ZIP, etc.)

UPDATE (02 Apr 2016): The Dell Venue 7840 Android 4.4.4 NAndroid image has been posted should anyone need it. It is around 920MB in size. You can flash this using the tethered Clockworkmod Recovery procedure. CLICK HERE
ROM image has been found. A thread will be created so others can have access
I have a very weird situation that could usually be resolved by performing a full reflash of the ROM. However, Dell doesn't make this available anywhere.
While I was installing new apps via Google Play, a handful of apps would not install. Google Play through up the Insufficient storage error. Confirmed that plenty of space was available all around. I researched the issue and carried out a few steps (clean Dalvik cache, Services->Apps->Google Framework data clear, Google Play data clear and uninstall update, manual review of /data/app and /data/app-lib regarding filenames). The issue still persisted. Using Lucky Patcher, I ran the option to manually install the latest stock Google Play (5.1.11). Afterward, I used Dell's built-in recovery to perform a factory reset and wipe the cache partition.
After all of that, I rebooted and received the usual New User screen. However, Google Keyboard keeps crashing. I connected a keyboard via USB-OTG, but since Google Keyboard is still the default input, the crash will not allow the hardware keyboard to work.
By some luck, I was able to bring up the Settings while in New User mode. Once in to Android proper, a handful of Google-related apps continued to crash (Chrome, Pinyin input, Keyboard). For some apps, I could uninstall via Titanium Backup and then perform a fresh install via Google Play. Even this wasn't a guarantee that the apps wouldn't crash. Reviewed logcat and app logs, and I found some Java exceptions and issues with certain /data/app /data/app-lib files/objects not being available.
I tried installing a few GApps packages from recovery, but they didn't work citing incompatibility with the existing version.
I had a CWM NANDROID backup of the system taken just as soon as I unboxed the unit and installed SuperSU. Irony: the drive containing the backup was formatted by mistake - used as a bootable recovery drive for another computer.
I also have a week's worth of full Titanium Backup jobs, but no manner of system app restores fixed the problem.
So, now, when you perform a factory reset, the system is still plagued with the Google app-related crashes.
With past devices, of course, you could download the ROM for a nice, clean reinstall. Dell has nothing on their support site. If I had a NANDROID (or similar) of the factory image, I should be able to fix the issue. My system received two Dell OTA updates and was at OS 4.4.4.
From DroidBoot recovery:
IFWI Version: 0004.F271
DroidBoot Version: 2.0
Product: Blackburn
If anyone has a copy of the factory ROM image or can suggest any tricks with the errant Google Apps/framework, please let me know. I'd be happy to send a PayPal donation for an official NANDROID of the factory image.
Thanks in advance for your help.

Mine isn't completely factory (i.e., I rooted it), but it will probably be better off than what you have... Let's see what I can do with it tonight...

jeffreycentex said:
Mine isn't completely factory (i.e., I rooted it), but it will probably be better off than what you have... Let's see what I can do with it tonight...
Click to expand...
Click to collapse
That would be perfect. I was *finally* able to get to the start Android desktop. I followed some steps to quiet the Google Apps down. Something is still amiss, but it is unable.
Rooted is perfect. Thanks!

Try this...
https://drive.google.com/file/d/0B93OVIVOHimsTHBqTDB4U1c2NzQ/view?usp=sharing

jeffreycentex said:
Try this...
https://drive.google.com/file/d/0B93OVIVOHimsTHBqTDB4U1c2NzQ/view?usp=sharing
Click to expand...
Click to collapse
THANKS! I will try it today. If this works, you could post it proper as a stock (rooted) ROM. I am trying to drum up as much 7840 activity as possible so XDA will create a standalone forum
I will return to let you know how it went. Thank you so much.

@jeffreycentex - Here are the steps i am taking:
1. Boot to tethered CWM
2. Perform a full backup of my current system as it is.
3. Reboot to Android OS, copy backup job to a secondary location for safe keeping
4. Performed MD5 comparison with the files to confirm copy
5. Copied your CWM backup to the Venue external SD
6. Kick off another tethered CWM
7. Perform Wipe data/factory reset, wipe cache and wipe dalvik cache. I was hesitant about formatting /system or anything of the sort for the time being.
8. Kick off CWM restore
After restore is complete, I will fire up the Venue and take it through the motions. If all is well, we should create another post with an offering of this image. It will hopefully encourage more research and experimentation to see what can be done.
Once I ran into the plethora of weird crashes and errors, I almost exchanged my Venue for a Galaxy Pro S 8.4. I am happy to have stayed the course. Being out of my comfort zone, I did a lot of researching an learned so much more about the Android instance on the venue.
Just some info on how I'm doing it. I shall let you know ASAP how things turn out. Also, PM me your email for PayPal email address for a donatino. I don't have a ton of money to send, but I will send you a $20 donation if you're cool with this.
Thanks again!
Jay

We are happy to report the transplant was a full success!
The only issue I ran into was with SuperSU claiming that the SU binaries were not present. I think that's because I forgot to choose the pre-restart option in CWM to double check the root process. Simply kick off another tethered CWM, installl SuperSU, and all is well.
This ROM solved all of the weirdness that I had. I even restored my favorite backups using Titanium. I'm now running some diagnostic utiilities to get all the relevant information (Build, revision, firmware info, etc.).
Would you mind if I created a post for this factory ROM. It would be the first. I would be more than happy to host it on a few of the usual free download sites. You would receive full credit. I just did not want to do this without your backing.
Thanks again, mate. Talk to you soon!
Jay

Here is the result of a system inventory for this ROM:
DELL VENUE 8 7840
SYSTEM (Android 4.4.4)
Model: Venue 8 7840
Manufacturer: Dell
Device: BB
Product: Venue8
Brand: Dell
Android Version: 4.4.4 (Kit Kat)
API Level: 19
Build ID: KTU84P
Fingerprint: Dell/Venue8/BB:4.4.4/KTU84P/eng.BBP803A138500DEL.20150123.184606:user/release-keys
DISPLAY (2560x1600)
Size: 2560x1600
Refresh Rate: 60 Hz
Default Orientation: Portrait
Physical Size: 8.78" (22.31 cm)
Logical Size: Extra Large
Density: 320 dpi (Extra High)
Pixels Per Inch: X: 312; Y: 359
PROCESSOR (Intel Atom)
Processor: Intel(R) Atom(TM) CPU Z3580 @ 1.33GHz
Cores: 4
Max Frequency: 2333 Mhz
Instruction Sets: x86, armeabi-v7a
SIMD Instructions: SSSE3
MEMORY (1954 MB)
System RAM: 1954 MB
JVM Max Memory: 192 MB
Internal Storage: 9462 MB
External Storage: 9462 MB (Emulated)
BACK CAMERA (8 megapixel)
SUMMARY
Max Picture Size: 3264x2448 (4:3)
Zoom: 16x
Autofocus: Supported (Continuous)
Orientation: 90°
PICTURE
Picture Format: Jpeg
Picture Format Values: Jpeg
Picture Size: 320x240
Picture Size Values: 320x240, 640x480, 1024x768, 1280x720, 1920x1080, 2048x1536, 2560x1920, 3264x1836, 3264x2448
PREVIEW
Preview Format: Yuv420sp
Preview Format Values: Yuv420sp, Yuv420p
Preview Fps Range: 10500, 30304
Preview Fps Range Values: (10500, 30304), (11000, 30304), (11500, 30304)
Preview Frame Rate: 30
Preview Frame Rate Values: 30, 15, 10
Preview Size: 640x480
Preview Size Values: 1440x1080, 1920x1080, 960x720, 1280x720, 720x480, 640x480, 640x360, 352x288, 320x240, 176x144
VIDEO
Preferred Preview Size For Video: 1920x1080
Video Frame Format: Yuv420sp
Video Size: 1920x1080
Video Size Values: 176x144, 320x240, 352x288, 640x480, 720x480, 1280x720, 1920x1080
Video Snapshot Supported: True
Video Stabilization: True
Video Stabilization Supported: True
FOCUS
Focus Areas: (0, 0, 0, 0, 0)
Focus Distances: 2, 2, Infinity
Focus Mode: Auto
Focus Mode Values: Auto, Infinity, Fixed, Macro, Continuous Video, Continuous Picture
Max Num Focus Areas: 9
ZOOM
Max Zoom: 476
Zoom: 0
Zoom Ratios: 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 144, 145, 146, 147, 148, 149, 150, 151, 152, 153, 154, 155, 156, 157, 158, 159, 160, 161, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 181, 182, 183, 184, 185, 186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 196, 197, 198, 199, 200, 201, 202, 203, 204, 205, 206, 207, 208, 209, 210, 211, 212, 213, 214, 215, 216, 217, 218, 219, 220, 221, 222, 223, 224, 225, 226, 227, 228, 229, 230, 231, 232, 233, 234, 235, 236, 237, 238, 239, 240, 241, 242, 243, 244, 245, 246, 247, 248, 249, 250, 251, 252, 253, 254, 255, 256, 257, 258, 259, 260, 261, 262, 263, 264, 265, 266, 267, 268, 269, 270, 271, 272, 273, 274, 275, 276, 277, 278, 279, 280, 281, 282, 283, 284, 285, 286, 287, 288, 289, 290, 291, 292, 293, 294, 295, 296, 297, 298, 299, 300, 301, 302, 303, 304, 305, 306, 307, 308, 309, 310, 311, 312, 313, 314, 315, 316, 317, 318, 319, 320, 321, 322, 323, 324, 325, 326, 327, 328, 329, 330, 331, 332, 334, 335, 336, 337, 338, 339, 340, 341, 342, 344, 345, 346, 347, 348, 349, 351, 352, 353, 354, 356, 357, 358, 359, 361, 362, 363, 364, 366, 367, 368, 370, 371, 372, 374, 375, 376, 378, 379, 381, 382, 384, 385, 386, 388, 389, 391, 392, 394, 395, 397, 398, 400, 402, 403, 405, 406, 408, 410, 411, 413, 415, 416, 418, 420, 421, 423, 425, 427, 428, 430, 432, 434, 436, 438, 439, 441, 443, 445, 447, 449, 451, 453, 455, 457, 459, 461, 463, 465, 468, 470, 472, 474, 476, 479, 481, 483, 485, 488, 490, 492, 495, 497, 500, 502, 504, 507, 509, 512, 515, 517, 520, 522, 525, 528, 531, 533, 536, 539, 542, 545, 548, 551, 554, 557, 560, 563, 566, 569, 572, 575, 579, 582, 585, 589, 592, 595, 599, 602, 606, 610, 613, 617, 621, 624, 628, 632, 636, 640, 644, 648, 652, 656, 661, 665, 669, 674, 678, 683, 687, 692, 697, 701, 706, 711, 716, 721, 726, 731, 737, 742, 747, 753, 759, 764, 770, 776, 782, 788, 794, 800, 806, 813, 819, 826, 833, 839, 846, 853, 861, 868, 875, 883, 890, 898, 906, 914, 923, 931, 939, 948, 957, 966, 975, 985, 994, 1004, 1014, 1024, 1034, 1045, 1056, 1067, 1078, 1089, 1101, 1113, 1125, 1138, 1151, 1164, 1177, 1191, 1205, 1219, 1234, 1249, 1264, 1280, 1296, 1313, 1330, 1347, 1365, 1384, 1403, 1422, 1442, 1463, 1484, 1506, 1528, 1552, 1575, 1600
Zoom Supported: True
WHITEBALANCE
Auto Whitebalance Lock: False
Auto Whitebalance Lock Supported: True
Whitebalance: Auto
Whitebalance Values: Auto, Incandescent, Fluorescent, Daylight, Cloudy Daylight
EXPOSURE COMPENSATION
Exposure Compensation: 0
Exposure Compensation Step: 0.33333333
Max Exposure Compensation: 6
Min Exposure Compensation: 6
SCENE
Scene Mode: Auto
Scene Mode Values: Auto, Portrait, Sports, Landscape, Night, Barcode, Hdr
MISC
Antibanding: Auto
Antibanding Values: Off, 50hz, 60hz, Auto
Auto Exposure Lock: False
Auto Exposure Lock Supported: True
Effect: None
Effect Values: None, Mono, Negative, Sepia
Focal Length: 2.940000
Horizontal View Angle: 63.7
Jpeg Quality: 80
Jpeg Thumbnail Height: 240
Jpeg Thumbnail Quality: 50
Jpeg Thumbnail Size Values: 320x240, 240x320, 320x180, 180x320, 160x120, 120x160, 0x0
Jpeg Thumbnail Width: 320
Max Num Detected Faces Hw: 32
Max Num Metering Areas: 1
Metering Areas: (0, 0, 0, 0, 0)
Rotation: 0
Vertical View Angle: 50
Xnr: True
FRONT CAMERA (2.1 megapixel)
SUMMARY
Max Picture Size: 1920x1080 (16:9)
Zoom: 16x
Autofocus: Not supported
Orientation: 270°
PICTURE
Picture Format: Jpeg
Picture Format Values: Jpeg
Picture Size: 320x240
Picture Size Values: 320x240, 640x480, 1280x720, 1920x1080
PREVIEW
Preview Format: Yuv420sp
Preview Format Values: Yuv420sp, Yuv420p
Preview Fps Range: 10500, 30304
Preview Fps Range Values: (10500, 30304), (11000, 30304), (11500, 30304)
Preview Frame Rate: 30
Preview Frame Rate Values: 30, 15, 10
Preview Size: 640x480
Preview Size Values: 1280x960, 1280x720, 1024x576, 720x480, 640x480, 640x360, 352x288, 320x240, 176x144, 184x104
VIDEO
Preferred Preview Size For Video: 1024x576
Video Frame Format: Yuv420sp
Video Size: 1920x1080
Video Size Values: 176x144, 320x240, 352x288, 640x480, 720x480, 1280x720, 1920x1080
Video Snapshot Supported: True
Video Stabilization: False
Video Stabilization Supported: False
FOCUS
Focus Areas: (0, 0, 0, 0, 0)
Focus Distances: 0.3, 0.65, Infinity
Focus Mode: Fixed
Focus Mode Values: Fixed
Max Num Focus Areas: 0
ZOOM
Max Zoom: 476
Zoom: 0
Zoom Ratios: 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 144, 145, 146, 147, 148, 149, 150, 151, 152, 153, 154, 155, 156, 157, 158, 159, 160, 161, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 181, 182, 183, 184, 185, 186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 196, 197, 198, 199, 200, 201, 202, 203, 204, 205, 206, 207, 208, 209, 210, 211, 212, 213, 214, 215, 216, 217, 218, 219, 220, 221, 222, 223, 224, 225, 226, 227, 228, 229, 230, 231, 232, 233, 234, 235, 236, 237, 238, 239, 240, 241, 242, 243, 244, 245, 246, 247, 248, 249, 250, 251, 252, 253, 254, 255, 256, 257, 258, 259, 260, 261, 262, 263, 264, 265, 266, 267, 268, 269, 270, 271, 272, 273, 274, 275, 276, 277, 278, 279, 280, 281, 282, 283, 284, 285, 286, 287, 288, 289, 290, 291, 292, 293, 294, 295, 296, 297, 298, 299, 300, 301, 302, 303, 304, 305, 306, 307, 308, 309, 310, 311, 312, 313, 314, 315, 316, 317, 318, 319, 320, 321, 322, 323, 324, 325, 326, 327, 328, 329, 330, 331, 332, 334, 335, 336, 337, 338, 339, 340, 341, 342, 344, 345, 346, 347, 348, 349, 351, 352, 353, 354, 356, 357, 358, 359, 361, 362, 363, 364, 366, 367, 368, 370, 371, 372, 374, 375, 376, 378, 379, 381, 382, 384, 385, 386, 388, 389, 391, 392, 394, 395, 397, 398, 400, 402, 403, 405, 406, 408, 410, 411, 413, 415, 416, 418, 420, 421, 423, 425, 427, 428, 430, 432, 434, 436, 438, 439, 441, 443, 445, 447, 449, 451, 453, 455, 457, 459, 461, 463, 465, 468, 470, 472, 474, 476, 479, 481, 483, 485, 488, 490, 492, 495, 497, 500, 502, 504, 507, 509, 512, 515, 517, 520, 522, 525, 528, 531, 533, 536, 539, 542, 545, 548, 551, 554, 557, 560, 563, 566, 569, 572, 575, 579, 582, 585, 589, 592, 595, 599, 602, 606, 610, 613, 617, 621, 624, 628, 632, 636, 640, 644, 648, 652, 656, 661, 665, 669, 674, 678, 683, 687, 692, 697, 701, 706, 711, 716, 721, 726, 731, 737, 742, 747, 753, 759, 764, 770, 776, 782, 788, 794, 800, 806, 813, 819, 826, 833, 839, 846, 853, 861, 868, 875, 883, 890, 898, 906, 914, 923, 931, 939, 948, 957, 966, 975, 985, 994, 1004, 1014, 1024, 1034, 1045, 1056, 1067, 1078, 1089, 1101, 1113, 1125, 1138, 1151, 1164, 1177, 1191, 1205, 1219, 1234, 1249, 1264, 1280, 1296, 1313, 1330, 1347, 1365, 1384, 1403, 1422, 1442, 1463, 1484, 1506, 1528, 1552, 1575, 1600
Zoom Supported: True
WHITEBALANCE
Auto Whitebalance Lock: False
Auto Whitebalance Lock Supported: True
Whitebalance: Auto
Whitebalance Values: Auto, Incandescent, Fluorescent, Daylight, Cloudy Daylight
EXPOSURE COMPENSATION
Exposure Compensation: 0
Exposure Compensation Step: 0.33333333
Max Exposure Compensation: 6
Min Exposure Compensation: 6
SCENE
Scene Mode: Auto
Scene Mode Values: Auto, Portrait, Sports, Landscape, Barcode
MISC
Antibanding: Auto
Antibanding Values: Off, 50hz, 60hz, Auto
Auto Exposure Lock: False
Auto Exposure Lock Supported: True
Effect: None
Effect Values: None, Mono, Negative, Sepia
Focal Length: 3.690000
Horizontal View Angle: 48.5
Jpeg Quality: 96
Jpeg Thumbnail Height: 240
Jpeg Thumbnail Quality: 50
Jpeg Thumbnail Size Values: 320x240, 240x320, 320x180, 180x320, 160x120, 120x160, 0x0
Jpeg Thumbnail Width: 320
Max Num Detected Faces Hw: 32
Max Num Metering Areas: 1
Metering Areas: (0, 0, 0, 0, 0)
Rotation: 0
Vertical View Angle: 29.4
Xnr: True
OPENGL 1.1 (PowerVR Rogue Hood)
GENERAL
Renderer: PowerVR Rogue Hood
Version: OpenGL ES-CM 1.1
Vendor: Imagination Technologies
LIMITS
Texture Size: 4096x4096
Texture Units: 4
Viewport Size: 4096x4096
Modelview Stack Depth: 16
Projection Stack Depth: 2
Texture Stack Depth: 4
Lights: 8
COMPRESSED TEXTURE FORMATS
ETC1, Paletted
EXTENSIONS
GL_EXT_debug_marker 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_sprite GL_OES_point_size_array GL_OES_matrix_palette GL_OES_draw_texture GL_OES_query_matrix GL_OES_texture_env_crossbar GL_OES_texture_mirrored_repeat GL_OES_texture_cube_map GL_OES_blend_subtract GL_OES_blend_func_separate GL_OES_blend_equation_separate GL_OES_stencil_wrap GL_OES_extended_matrix_palette GL_OES_framebuffer_object GL_OES_rgb8_rgba8 GL_OES_depth24 GL_OES_stencil8 GL_OES_compressed_ETC1_RGB8_texture GL_OES_mapbuffer GL_OES_EGL_image GL_EXT_multi_draw_arrays GL_OES_required_internalformat GL_EXT_texture_filter_anisotropic GL_APPLE_texture_2d_limited_npot GL_IMG_read_format GL_IMG_texture_compression_pvrtc GL_IMG_texture_format_BGRA8888 GL_EXT_texture_format_BGRA8888 GL_OES_egl_sync GL_IMG_vertex_array_object GL_OES_EGL_image_external
OPENGL 3.0 (PowerVR Rogue Hood)
GENERAL
Renderer: PowerVR Rogue Hood
Version: OpenGL ES 3.0 build [email protected]
Vendor: Imagination Technologies
GLSL Version: OpenGL ES GLSL ES 3.00 build [email protected]
LIMITS
Texture Size: 8192x8192
Texture Units: 16
Vertex Textures: 16
Combined Textures: 32
Viewport Size: 8192x8192
Renderbuffer Size: 8192x8192
Cubemap Size: 8192x8192
Vertex Attributes: 16
Vertex Uniforms: 256
Varying Vectors: 15
Fragment Uniforms: 224
VERTEX NUMERIC PRECISION
Low Int: [-2^8, 2^8]
Medium Int: [-2^11, 2^11]
High Int: [-2^24, 2^24]
Low Float: [-2^1, 2^1], 2^-8
Medium Float: [-2^14, 2^14], 2^-10
High Float: [-2^126, 2^126], 2^-23
FRAGMENT NUMERIC PRECISION
Low Int: [-2^8, 2^8]
Medium Int: [-2^11, 2^11]
High Int: [-2^24, 2^24]
Low Float: [-2^1, 2^1], 2^-8
Medium Float: [-2^14, 2^14], 2^-10
High Float: [-2^126, 2^126], 2^-23
COMPRESSED TEXTURE FORMATS
ETC1
EXTENSIONS
GL_EXT_debug_marker GL_OES_rgb8_rgba8 GL_OES_depth24 GL_OES_vertex_half_float GL_OES_texture_float GL_OES_texture_half_float GL_OES_element_index_uint GL_OES_mapbuffer GL_OES_fragment_precision_high GL_OES_compressed_ETC1_RGB8_texture GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_EGL_sync GL_OES_required_internalformat GL_OES_depth_texture GL_OES_get_program_binary GL_OES_packed_depth_stencil GL_OES_standard_derivatives GL_OES_vertex_array_object GL_OES_texture_npot GL_OES_surfaceless_context GL_EXT_discard_framebuffer GL_EXT_multi_draw_arrays GL_EXT_multisampled_render_to_texture GL_EXT_shader_texture_lod GL_EXT_texture_filter_anisotropic GL_EXT_texture_format_BGRA8888 GL_EXT_blend_minmax GL_EXT_texture_rg GL_EXT_occlusion_query_boolean GL_EXT_color_buffer_float GL_EXT_shader_framebuffer_fetch GL_EXT_separate_shader_objects GL_EXT_robustness GL_EXT_draw_buffers GL_IMG_shader_binary GL_IMG_texture_compression_pvrtc GL_IMG_texture_compression_pvrtc2 GL_IMG_texture_npot GL_IMG_texture_format_BGRA8888 GL_IMG_read_format GL_IMG_program_binary GL_IMG_multisampled_render_to_texture GL_KHR_debug
GRAPHIC MODES (RGBA 32bit)
RGB 16bit (565)
RGB 16bit (565), Depth 24bit, Stencil 8bit
RGB 16bit (565), Depth 24bit, Stencil 8bit, Samples x4
RGB 32bit (888)
RGB 32bit (888), Depth 24bit, Stencil 8bit
RGB 32bit (888), Depth 24bit, Stencil 8bit, Samples x4
RGBA 32bit (8888)
RGBA 32bit (8888), Depth 24bit, Stencil 8bit
RGBA 32bit (8888), Depth 24bit, Stencil 8bit, Samples x4
SENSORS (12)
PSH ACCELEROMETER
Vendor: Intel Inc.
Range: 19.6133 m/s²
Resolution: 0.0047884006 m/s²
Power: 0.006 mA
Delay: 10000 μs
PSH AMBIENT LIGHT SENSOR
Vendor: Intel Inc.
Range: 6553.5 lx
Resolution: 0.1 lx
Power: 0.35 mA
Delay: On Trigger
PSH PROXIMITY SENSOR
Vendor: Intel Inc.
Range: 5.0 cm
Resolution: 5.0 cm
Power: 0.35 mA
Delay: On Trigger
PSH GYROSCOPE SENSOR
Vendor: Intel Inc.
Range: 34.906586 rad/s
Resolution: 0.0017453306 rad/s
Power: 6.1 mA
Delay: 10000 μs
PSH GRAVITY SENSOR
Vendor: Intel Inc.
Range: 19.6133 m/s²
Resolution: 0.0047884006 m/s²
Power: 0.006 mA
Delay: 10000 μs
PSH LINEAR ACCELERATION SENSOR
Vendor: Intel Inc.
Range: 19.6133 m/s²
Resolution: 0.0047884006 m/s²
Power: 0.006 mA
Delay: 10000 μs
PSH ORIENTATION SENSOR
Vendor: Intel Inc.
Range: 360.0°
Resolution: 1.0°
Power: 0.106 mA
Delay: 10000 μs
PSH TERMINAL SENSOR
Vendor: Intel Inc.
Range: 7.0
Resolution: 1.0
Power: 0.35 mA
Delay: On Trigger
PSH MOVE DETECT SENSOR
Vendor: Intel Inc.
Range: 3.0
Resolution: 1.0
Power: 0.35 mA
Delay: 10000 μs
PSH WAKE UP SENSOR
Vendor: Intel Inc.
Range: 1.0
Resolution: 1.0
Power: 0.35 mA
Delay: On Trigger
PSH SLEEP SENSOR
Vendor: Intel Inc.
Range: 1.0
Resolution: 1.0
Power: 0.35 mA
Delay: On Trigger
SENSOR FOR CALIBRATION
Vendor: Intel Inc.
Range: 100.0
Resolution: 1.0
Power: 0.001 mA
Delay: 10000 μs
CODECS (40)
OMX.INTEL.VIDEODECODER.MPEG4
MEDIA TYPE: VIDEO/MP4V-ES
Profiles: : Simple(3) AdvancedSimple(5)
OMX.INTEL.VIDEODECODER.H263
MEDIA TYPE: VIDEO/3GPP
Profiles: : Baseline(70)
OMX.INTEL.VIDEODECODER.AVC
MEDIA TYPE: VIDEO/AVC
Profiles: : Baseline(42) Main(42) High(42)
OMX.INTEL.VIDEODECODER.WMV
MEDIA TYPE: VIDEO/X-MS-WMV
OMX.INTEL.VIDEODECODER.VP8
MEDIA TYPE: VIDEO/X-VND.ON2.VP8
OMX.INTEL.SW_VD.H265
MEDIA TYPE: VIDEO/HEVC
OMX.INTEL.MP3.DECODER
MEDIA TYPE: AUDIO/MPEG
CIPMP3DECODER
MEDIA TYPE: AUDIO/MPEG
OMX.GOOGLE.MP3.DECODER
MEDIA TYPE: AUDIO/MPEG
CIPAMRNBDECODER
MEDIA TYPE: AUDIO/3GPP
OMX.GOOGLE.AMRNB.DECODER
MEDIA TYPE: AUDIO/3GPP
CIPAMRWBDECODER
MEDIA TYPE: AUDIO/AMR-WB
OMX.GOOGLE.AMRWB.DECODER
MEDIA TYPE: AUDIO/AMR-WB
OMX.INTEL.AAC.DECODER
MEDIA TYPE: AUDIO/MP4A-LATM
CIPAACDECODER
MEDIA TYPE: AUDIO/MP4A-LATM
OMX.GOOGLE.AAC.DECODER
MEDIA TYPE: AUDIO/MP4A-LATM
OMX.GOOGLE.AAC.DECODER
MEDIA TYPE: AUDIO/MP4A-AACEXTENDED
OMX.GOOGLE.G711.ALAW.DECODER
MEDIA TYPE: AUDIO/G711-ALAW
OMX.GOOGLE.G711.MLAW.DECODER
MEDIA TYPE: AUDIO/G711-MLAW
CIPVORBISDECODER
MEDIA TYPE: AUDIO/VORBIS
OMX.GOOGLE.VORBIS.DECODER
MEDIA TYPE: AUDIO/VORBIS
OMX.INTEL.ALAC.DECODER
MEDIA TYPE: AUDIO/ALAC
OMX.GOOGLE.MPEG4.DECODER
MEDIA TYPE: VIDEO/MP4V-ES
OMX.GOOGLE.H263.DECODER
MEDIA TYPE: VIDEO/3GPP
OMX.GOOGLE.H264.DECODER
MEDIA TYPE: VIDEO/AVC
OMX.GOOGLE.VP8.DECODER
MEDIA TYPE: VIDEO/X-VND.ON2.VP8
OMX.GOOGLE.VP9.DECODER
MEDIA TYPE: VIDEO/X-VND.ON2.VP9
CIPWMADECODER
MEDIA TYPE: AUDIO/X-MS-WMA
OMX.INTEL.VIDEOENCODER.MPEG4
MEDIA TYPE: VIDEO/MP4V-ES
Color Formats: : YUV420SemiPlanar
Profiles: : Simple(5)
OMX.INTEL.VIDEOENCODER.H263
MEDIA TYPE: VIDEO/3GPP
Color Formats: : YUV420SemiPlanar
Profiles: : Baseline(45)
OMX.INTEL.VIDEOENCODER.AVC
MEDIA TYPE: VIDEO/AVC
Color Formats: : YUV420SemiPlanar
Profiles: : Baseline(41) High(42)
OMX.INTEL.VIDEOENCODER.VP8
MEDIA TYPE: VIDEO/X-VND.ON2.VP8
Color Formats: : YUV420SemiPlanar
CIPAMRNBENCODER
MEDIA TYPE: AUDIO/3GPP
OMX.GOOGLE.AMRNB.ENCODER
MEDIA TYPE: AUDIO/3GPP
CIPAMRWBENCODER
MEDIA TYPE: AUDIO/AMR-WB
OMX.GOOGLE.AMRWB.ENCODER
MEDIA TYPE: AUDIO/AMR-WB
OMX.GOOGLE.AAC.ENCODER
MEDIA TYPE: AUDIO/MP4A-LATM
OMX.GOOGLE.FLAC.ENCODER
MEDIA TYPE: AUDIO/FLAC
AACENCODER
MEDIA TYPE: AUDIO/MP4A-LATM
OMX.GOOGLE.RAW.DECODER
MEDIA TYPE: AUDIO/RAW
FEATURES (33)
GRAPHICS
OpenGL 3.0
AMAZON
com.amazon.canary.feature.preload
ANDROID HARDWARE
android.hardware.bluetooth
android.hardware.bluetooth_le
android.hardware.camera
android.hardware.camera.any
android.hardware.camera.autofocus
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.gyroscope
android.hardware.sensor.light
android.hardware.sensor.proximity
android.hardware.touchscreen
android.hardware.touchscreen.multitouch
android.hardware.touchscreen.multitouch.distinct
android.hardware.usb.accessory
android.hardware.usb.host
android.hardware.wifi
android.hardware.wifi.direct
ANDROID SOFTWARE
android.software.app_widgets
android.software.device_admin
android.software.home_screen
android.software.input_methods
android.software.live_wallpaper
android.software.sip
android.software.sip.voip
Created with Hardware Info 4.2.2

jeffreycentex said:
Mine isn't completely factory (i.e., I rooted it), but it will probably be better off than what you have... Let's see what I can do with it tonight...
Click to expand...
Click to collapse
How did you root your device? Just picked up my 7840 and I'm considering rooting it. Pretty sure it's running 4.4.4.

Dan Again said:
How did you root your device? Just picked up my 7840 and I'm considering rooting it. Pretty sure it's running 4.4.4.
Click to expand...
Click to collapse
@Dan Again - You can root it using a tethered CWM Recovery method that was designed with Intel x86 Androids in mind. Check out this forum entry: http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096

I have new venue7840
jumpup said:
I have a very weird situation that could usually be resolved by performing a full reflash of the ROM. However, Dell doesn't make this available anywhere.
While I was installing new apps via Google Play, a handful of apps would not install. Google Play through up the Insufficient storage error. Confirmed that plenty of space was available all around. I researched the issue and carried out a few steps (clean Dalvik cache, Services->Apps->Google Framework data clear, Google Play data clear and uninstall update, manual review of /data/app and /data/app-lib regarding filenames). The issue still persisted. Using Lucky Patcher, I ran the option to manually install the latest stock Google Play (5.1.11). Afterward, I used Dell's built-in recovery to perform a factory reset and wipe the cache partition.
After all of that, I rebooted and received the usual New User screen. However, Google Keyboard keeps crashing. I connected a keyboard via USB-OTG, but since Google Keyboard is still the default input, the crash will not allow the hardware keyboard to work.
By some luck, I was able to bring up the Settings while in New User mode. Once in to Android proper, a handful of Google-related apps continued to crash (Chrome, Pinyin input, Keyboard). For some apps, I could uninstall via Titanium Backup and then perform a fresh install via Google Play. Even this wasn't a guarantee that the apps wouldn't crash. Reviewed logcat and app logs, and I found some Java exceptions and issues with certain /data/app /data/app-lib files/objects not being available.
I tried installing a few GApps packages from recovery, but they didn't work citing incompatibility with the existing version.
I had a CWM NANDROID backup of the system taken just as soon as I unboxed the unit and installed SuperSU. Irony: the drive containing the backup was formatted by mistake - used as a bootable recovery drive for another computer.
I also have a week's worth of full Titanium Backup jobs, but no manner of system app restores fixed the problem.
So, now, when you perform a factory reset, the system is still plagued with the Google app-related crashes.
With past devices, of course, you could download the ROM for a nice, clean reinstall. Dell has nothing on their support site. If I had a NANDROID (or similar) of the factory image, I should be able to fix the issue. My system received two Dell OTA updates and was at OS 4.4.4.
From DroidBoot recovery:
IFWI Version: 0004.F271
DroidBoot Version: 2.0
Product: Blackburn
If anyone has a copy of the factory ROM image or can suggest any tricks with the errant Google Apps/framework, please let me know. I'd be happy to send a PayPal donation for an official NANDROID of the factory image.
Thanks in advance for your help.
Click to expand...
Click to collapse
i have a brand new 7840 that i totally intend on rooting....if someone could help me root it safely or help me get the rom backed up without rooting it. i'd be happy to help
---------- Post added 6th March 2015 at 12:03 AM ---------- Previous post was 5th March 2015 at 11:59 PM ----------
justory85 said:
i have a brand new 7840 that i totally intend on rooting....if someone could help me root it safely or help me get the rom backed up without rooting it. i'd be happy to help
Click to expand...
Click to collapse
also i have only about 10 or 11 rooted devices under my belt....and every time it says insufficient storage for app download from the play store it's cause something has switched (somehow) where the apps download to....it usually causes a mess which forces me to rewipe and reinstall as well but maybe you just need to reset the switch where your apps are downloaded too....like if it is set to auto or whatever the other option is it doesn't work properly. i imagine that has alot to do with google removing and returning sd card privilages. however i'm not a good enough android dev or modder to say for sure....

jumpup said:
THANKS! I will try it today. If this works, you could post it proper as a stock (rooted) ROM. I am trying to drum up as much 7840 activity as possible so XDA will create a standalone forum
I will return to let you know how it went. Thank you so much.
Click to expand...
Click to collapse
Can you share this Rom again ! I really need it .
Thank you very much !
---------- Post added at 07:47 AM ---------- Previous post was at 07:43 AM ----------
Can you share DELL VENUE 8 7840 Rom again ! I really need it .
Thank you very much !

Here is the link to 4.4.4 NAndroid
pipo6868 said:
Can you share this Rom again ! I really need it .
Thank you very much !
---------- Post added at 07:47 AM ---------- Previous post was at 07:43 AM ----------
Can you share DELL VENUE 8 7840 Rom again ! I really need it .
Thank you very much !
Click to expand...
Click to collapse
@pipo6868 - Here you go: Dell Venue 7840 - Android 4.4.4 - Factory NAndroid (~920MB)

help
jumpup said:
@jeffreycentex - Here are the steps i am taking:
1. Boot to tethered CWM
2. Perform a full backup of my current system as it is.
3. Reboot to Android OS, copy backup job to a secondary location for safe keeping
4. Performed MD5 comparison with the files to confirm copy
5. Copied your CWM backup to the Venue external SD
6. Kick off another tethered CWM
7. Perform Wipe data/factory reset, wipe cache and wipe dalvik cache. I was hesitant about formatting /system or anything of the sort for the time being.
8. Kick off CWM restore
After restore is complete, I will fire up the Venue and take it through the motions. If all is well, we should create another post with an offering of this image. It will hopefully encourage more research and experimentation to see what can be done.
Once I ran into the plethora of weird crashes and errors, I almost exchanged my Venue for a Galaxy Pro S 8.4. I am happy to have stayed the course. Being out of my comfort zone, I did a lot of researching an learned so much more about the Android instance on the venue.
Just some info on how I'm doing it. I shall let you know ASAP how things turn out. Also, PM me your email for PayPal email address for a donatino. I don't have a ton of money to send, but I will send you a $20 donation if you're cool with this.
Thanks again!
Jay
Click to expand...
Click to collapse
Hey guys am new to this forum even though I have been using your advice for some years now This time I finally encounter my self in really really big trouble with my brand new dell venue 7840 , what happens is that i got the freaking updated for lollipop out of the box, next to that i followed all steps to root lollipop it took some time but everything went 'right'. But 3 days later my tab started to drastically drain Battery, to the point were i cant actually see it going from 100% to 0% in just a minute or two, i hope making some kind of a downgrade to 4.4.4 could fix this issue , but im afraid that when I try to get in to tethered cmw it just show this :
=======================================================================
DEVICE STATUS: FASTBOOT-ONLINE
DEVICE INFORMATION: 56900EFA01 fastboot
=======================================================================
copy needed files to our device
target reported max download size of 536870912 bytes
sending '/tmp/recovery.zip' (3477 KB)...
OKAY [ 0.384s]
writing '/tmp/recovery.zip'...
FAILED (remote: Bootloader must not be locked)
finished. total time: 0.655s
target reported max download size of 536870912 bytes
sending '/tmp/recovery.launcher' (400 KB)...
OKAY [ 0.276s]
writing '/tmp/recovery.launcher'...
FAILED (remote: Bootloader must not be locked)
finished. total time: 0.545s
we need to stop logcat before replacing it
...
FAILED (remote: command not allowed in this device state)
finished. total time: 0.376s
target reported max download size of 536870912 bytes
sending '/system/bin/logcat' (178 KB)...
OKAY [ 0.269s]
writing '/system/bin/logcat'...
FAILED (remote: Bootloader must not be locked)
finished. total time: 0.537s
issue fastboot oem "stop_partitioning" command to start cwm recovery:
...
FAILED (remote: command not allowed in this device state)
finished. total time: 0.367s
even though the bootloader is not locked , and if i try to unlocked it again in order to enter cmw it says this:
.......................................................................................................................................................................................................................................................................................
C:\Users\Hugo Sanchez\Desktop\IntelAndroid-FBRL-05-16-2015-PTR\resources\platfor
m-tools_aosp>fastboot devices
56900EFA01 fastboot
C:\Users\Hugo Sanchez\Desktop\IntelAndroid-FBRL-05-16-2015-PTR\resources\platfor
m-tools_aosp>fastboot oem unlock
...
(bootloader) Checking unlock authorization.
FAILED (remote: couldn't change state)
finished. total time: 0.309s
I hope some one can help me to fix this

Please see my answer on the other post and please don't double post...

jumpup said:
@pipo6868 - Here you go: Dell Venue 7840 - Android 4.4.4 - Factory NAndroid (~920MB)[/URL][/SIZE][/B]
Click to expand...
Click to collapse
Thank you for your help !
but it said " Installtion aborted. "
Can you fix it ! Please !

pipo6868 said:
Thank you for your help !
but it said " Installtion aborted. "
Can you fix it ! Please !
Click to expand...
Click to collapse
Let me double check. Unfortunately, I don't have a 7840 to test this with

NEED Recovery
I need a CWM/TWRP Recovery for my venue 8 7840.
I can't find a efficient file.

currently in bootloop (dell venue 8 7840)
hi,I'm having the same device and recently I installed gravitybox or some app of that kind and it offered an option to install xposed framework.I was skeptical if my device was compatible but did it anyway.Next it went into a bootloop at the intel logo and has been there ever since.my present condition is,I can get into fastboot menu but cannot install the xposed uninstaller.zip since the sd card is not recognised anymore.I tried to adb sideload it but only errors follow.I understand this device has a temporary recovery and right now there is no custom recovery installed I guess(?).I am new to android so kindly help me get the device to function again by this nandroid backup.thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

there is
hugo.s.l said:
Hey guys am new to this forum even though I have been using your advice for some years now This time I finally encounter my self in really really big trouble with my brand new dell venue 7840 , what happens is that i got the freaking updated for lollipop out of the box, next to that i followed all steps to root lollipop it took some time but everything went 'right'. But 3 days later my tab started to drastically drain Battery, to the point were i cant actually see it going from 100% to 0% in just a minute or two, i hope making some kind of a downgrade to 4.4.4 could fix this issue , but im afraid that when I try to get in to tethered cmw it just show this :
=======================================================================
DEVICE STATUS: FASTBOOT-ONLINE
DEVICE INFORMATION: 56900EFA01 fastboot
=======================================================================
copy needed files to our device
target reported max download size of 536870912 bytes
sending '/tmp/recovery.zip' (3477 KB)...
OKAY [ 0.384s]
writing '/tmp/recovery.zip'...
FAILED (remote: Bootloader must not be locked)
finished. total time: 0.655s
target reported max download size of 536870912 bytes
sending '/tmp/recovery.launcher' (400 KB)...
OKAY [ 0.276s]
writing '/tmp/recovery.launcher'...
FAILED (remote: Bootloader must not be locked)
finished. total time: 0.545s
we need to stop logcat before replacing it
...
FAILED (remote: command not allowed in this device state)
finished. total time: 0.376s
target reported max download size of 536870912 bytes
sending '/system/bin/logcat' (178 KB)...
OKAY [ 0.269s]
writing '/system/bin/logcat'...
FAILED (remote: Bootloader must not be locked)
finished. total time: 0.537s
issue fastboot oem "stop_partitioning" command to start cwm recovery:
...
FAILED (remote: command not allowed in this device state)
finished. total time: 0.367s
even though the bootloader is not locked , and if i try to unlocked it again in order to enter cmw it says this:
.......................................................................................................................................................................................................................................................................................
C:\Users\Hugo Sanchez\Desktop\IntelAndroid-FBRL-05-16-2015-PTR\resources\platfor
m-tools_aosp>fastboot devices
56900EFA01 fastboot
C:\Users\Hugo Sanchez\Desktop\IntelAndroid-FBRL-05-16-2015-PTR\resources\platfor
m-tools_aosp>fastboot oem unlock
...
(bootloader) Checking unlock authorization.
FAILED (remote: couldn't change state)
finished. total time: 0.309s
I hope some one can help me to fix this
Click to expand...
Click to collapse
a setting for this option. it's called like factory unlock protection it's in options so you need to have device booted to use it.

Question Is there a way to observe whether Intel Bridge Technology works and how it works? I want to find out why a game fails to start on WSA.

I have a surface pro X running Windows 11 ARM64 version but it only has 8GB of RAM. I tried to install a game and play it. After the game is started, it always crashes because there isn't enough memory.
Now I'm trying to install it on my desktop PC and I find it is worse than my surface pro X. It crashed when trying to start!
I read the log from both sides and find out what was happening.
On my SPX, it has something like this so it successfully started up:
Code:
12-17 10:27:12.583 2150 2150 I da1vikvn: ** find native path :/data/app/~~R-xigkqQf-lfITZnwn6meQ==/com.netease.pes-ScXe4Q0r9zt9zNpkgow-tw==/lib/arm64
12-17 10:27:12.584 2150 2150 I da1vikvn: try path /data/app/~~R-xigkqQf-lfITZnwn6meQ==/com.netease.pes-ScXe4Q0r9zt9zNpkgow-tw==/lib/arm/libunisec2.so
12-17 10:27:12.584 2150 2150 I da1vikvn: try path /data/app/~~R-xigkqQf-lfITZnwn6meQ==/com.netease.pes-ScXe4Q0r9zt9zNpkgow-tw==/lib/arm64/libunisec2.so
12-17 10:27:12.585 2150 2150 I da1vikvn: try path /data/user/0/com.netease.pes/app_ntp0/libunisec2.so
12-17 10:27:12.585 2150 2150 I da1vikvn: opt so path /data/user/0/com.netease.pes/app_ntp0/libunisec2.so
12-17 10:27:12.588 2150 2150 I OpenGLRendor: =====>init Native start!!!
On my desktop PC, it has something like this so it failed to start up:
Code:
12-17 02:42:06.745 2035 2035 I da1vikvn: ** find native path :/data/app/~~jyuD0007qWrH6coCzhhp4g==/com.netease.pes--f5miRm7o3vziki2QlCirw==/lib/arm64
12-17 02:42:06.745 2035 2035 I da1vikvn: ** find native path :/data/app/~~jyuD0007qWrH6coCzhhp4g==/com.netease.pes--f5miRm7o3vziki2QlCirw==/lib/arm64
12-17 02:42:06.745 2035 2035 I da1vikvn: running on x86 platform, loading /data/user/0/com.netease.pes/app_ntp0/libunisec_x86.so
12-17 02:42:06.745 2035 2035 I da1vikvn: run on x86 platform, load x86 so!
12-17 02:42:06.757 533 533 I ShellRedirectionHandler: onTaskAppeared taskId: 46
--------- beginning of crash
12-17 02:42:06.757 2035 2035 E AndroidRuntime: FATAL EXCEPTION: main
12-17 02:42:06.757 2035 2035 E AndroidRuntime: Process: com.netease.pes, PID: 2035
12-17 02:42:06.757 2035 2035 E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: "/data/user/0/com.netease.pes/app_ntp0/libunisec_x86.so" has unexpected e_machine: 3
Obviously, the reason for the crash is that it detects the WSA on my desktop PC is x86 so it tries to load the x86 version of libunisec and failed.
So why is Intel Bridge Technology not working? Does it mean IBT can only work if a loader loads ARM64 libraries and fail to work if the loader tries to load x86 libraries?
Is there a way to trick da1vikvn so it no longer tries to load x86 so? (By the way, I have no experience in Android App development. I know there is a Dalvik VM. Is this da1vikvn the Dalvik VM or just a similar name thing that the app developer uses?)

If computer's OS architecture is ARM64 then WSA runs ARM64 apps natively: HOUDINI - the ARM-To_Intel-Translator - then isn't used at all.
Take note that WSA is gonna crash as soon as it launches since it reserves 4 GB of RAM for the VM. If you have less than 12 GB RAM then WSA will not flawlessly work.

jwoegerbauer said:
If computer's OS architecture is ARM64 then WSA runs ARM64 apps natively: HOUDINI - the ARM-To_Intel-Translator - then isn't used at all.
Take note that WSA is gonna crash as soon as it launches since it reserves 4 GB of RAM for the VM. If you have less than 12 GB RAM then WSA will not flawlessly work.
Click to expand...
Click to collapse
Thank you.
My desktop PC has 24GB RAM so it should be enough. (I have four 8GB RAMs. Using 3 of them is not a perfect dual-channel RAM solution but I have to use the other one to build another PC)
I'm just wondering whether IBT is designed only for those ARM apps that will never dynamically load libraries based on OS architecture. Or maybe this game is developed too weirdly so IBT failed to handle it?

As I already mentioned: HOUDINI is used to translate ARM64 code to X86_64 code.

Better Mobile App

welcome