Bounty Link:
Use this to Donate to the Project Itself for all of those involved in the hardwork Jface,Doniqq, and myself
Bugs List (Last updated 9/5/11)
Code:
-FFC Squished on some versions
-FFC roatated 90 Degrees CW on V1.5 & Up
-FFC @ Full Res Video still shows green boxes (missing libs?)
Update (9/5/11): LG Cam V3.0 -Major Fixes in this one
Testing now... if all goes well expect update package shortly. 2:42AM EST
Stitch Shot: Confirmed working
Panorama Shot: Confirmed Working
Continuous Shot: Confirmed Working
Zoom while recording Video in all modes : Confirmed working
Touch to focus : Confirmed Working
Taking Pictures in portrait flipped : Confirmed working
Recording at 1080P @ 24 FPS / 720P @ 30 FPS : Confirmed Working
Download LG Cam V3.0: Here
Update (8/5/11): LGCam V1.5 - Fxied for Real This Time - for the trolls i mean the update package
Download LGCam V1.5: Here
THIS WILL NOT WORK ON CM7 OR ANYTHING BASED ON CM7/AOSP FOR NOW
Restore AOSP/OTA GB Cam
V1.4
Don't want to talk about it
Code:
V1.5 Updates:
-Fixed ZIP Package, now flashable, I promise (Damn Signtool replaced the com folder :/) :o
-Fixed 1080P @ 24FPS/30 FPS same as stock FROYO
-Fixed Zoom while recording Video
- Stock Cam Icon
- Still needs to fix FFC
-Enjoy, Report any bugs in the thread
-Donate and help me buy a bottle of Belevedere Black:)
V1.4
Burning in hell somewhere
Click to expand...
Click to collapse
flak0 said:
Hey Devs and ofcourse Doniqq first off amazing work on EB i love it. Im using the FR version. Ok so basically I am posting this thread because I figured out for sure why the LG Camera will not work on GB. It is not a lack of drivers like everyone has said. Basically when the Camera.Apk(LG Camera) is launched it looks for Libamce.so (i figured this out by reverse engineering the LG Camera and found the referrence on where it looks for the shared library libamce.so.) I went ahead and tried to push the LG Camera with the libamce.so yet still got a force close, this time the error was a reloc lbrary error looking for a _NZCamera6Connect function. I then went ahead an decompiled the libamce.so and found that it depends on libnvomx.so, then I decompiled libnvomx.so and found that it depends on libm.so, then I tried pushing all three libs to GB and still got a force close. After digging deep enough I found that libm.so depends on libcamera_client.so which I also decompiled and then I found the _NZCamera6Connect fuction is contained here. I attempted to push the libcamera_cleint.so to to GB and boot failed, then I tried editing the update-zip file to include the libcamera_client.so (From Froyo) and boot also failed. I am positive that once we get this libcamera_client.so ported from FROYO to GB the LG Camera will work. Luckily there is no dependency on the framework. This is where I need your help since I know your the dev who made EB possible or any Dev thats out there Faux, Morific Thanks.
Here is the header of the decompiled libamce.so just in case:
Click to expand...
Click to collapse
I'm no dev, but I just want to thank you for continuing to try and bring the LG cam to Gingerbread. Hopefully a dev will gladly help you out with this issue. Once again thank you for taking the time to try and get this hard headed app to work.
Sent from my LG-P999 using XDA Premium App
[depricated as of 9/5/11 - history of lgcam on gb]
Update (8/3/11): LG CAM for CM7 removed until fixed. Too many people were flashing on MIUI and CM7 Based ROMS
New Version for Stock OTA based ROMS coming out tonight.
Proposed fixes include -> 24/30 FPS @ 1080P and Zoom while video recording
Also moved some of the original OP two posts down to clean up the OP.
Update(8/2/11): LG Cam for CM 7 Beta
Below is what you have all been asking for, it is a beta of LG Cam for CM7. If you are willing to take the risk go ahead and flash BUT FIRST MAKE SURE YOU NANDROID. I have also attached CM7 Cam again if it fails to work and/or if you wish to go back. Please update the thread with any errors, logcats preferred.
Edit: Update(8/2/11 @ 4:42AM EST) below.
I was able to Port the LGE folder from GB to CM7 into the framework successfully however now when I open the CAM I am getting a null pointer exception. Anyone willing to help here please.
Code:
I/ActivityManager( 1074): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.camera/.ArcCamera } from pid 1279
I/ActivityManager( 1074): Start proc com.android.camera for activity com.android.camera/.ArcCamera: pid=3750 uid=10034 gids={1006, 1015}
D/ ( 984): NVRM_DAEMON(819): rt_exist=2, add client ref
D/ ( 984): set continue (1280x960)
D/ ( 984): set continue (1280x1024)
D/ ( 984): set continue (1280x1024)
D/ ( 984): set continue (1360x768)
D/ ( 984): set continue (1440x900)
D/ ( 984): set continue (1680x1050)
D/ ( 984): set BetterMode (1280x720)
D/ ( 984): set BetterMode (1920x1080)
D/ ( 984): set BetterMode (1280x720)
D/ ( 984): set BetterMode (1920x1080)
D/ ( 984): set BetterMode (1920x1080)
D/ ( 984): set BetterMode (1920x1080)
D/ ( 984): set BetterMode (1920x1080)
I/WindowManager( 1074): Setting rotation to 1, animFlags=1
I/ActivityManager( 1074): Config changed: { scale=1.0 imsi=310/260 loc=en_US touch=3 keys=1/1/2 nav=1/1 orien=2 layout=34 uiMode=17 seq=7 themeResource=null}
I/PowerWidget( 1243): Clearing any old widget stuffs
I/PowerWidget( 1243): Setting up widget
I/PowerWidget( 1243): Default buttons being loaded
I/PowerWidget( 1243): Button list: toggleWifi|toggleBluetooth|toggleGPS|toggleSound
I/PowerWidget( 1243): Setting up button: toggleWifi
I/PowerWidget( 1243): Setting up button: toggleBluetooth
I/PowerWidget( 1243): Setting up button: toggleGPS
I/PowerWidget( 1243): Setting up button: toggleSound
D/szipinf ( 3750): Initializing inflate state
I/===ArcCamera=== 1.1.0.1( 3750): Performance log:Load so2011-08-02 08:36:10.376 cost:6ms
I/===ArcCamera=== 1.1.0.1( 3750): Performance log:Launch camera
[color="blue"][size="4"]major update 7/28/11[/size]
[/color]
working lg cam on 2.3.3 ota & xborders stock rom (huge thanks to jumaaneface) once the cam is confirmed working on cm7 & aosp the bounty will be paid. I will also be looking into the actual cam app by decompiling source to see if we can fix the 1080p recording to make it record at 30 fps.
Again thanks to all the supporters and to jumaaneface who made this possible.
:d hey devs and ofcourse doniqq first off amazing work on eb i love it. Im using the fr version. Ok so basically i am posting this thread because i figured out for sure why the lg camera will not work on gb. It is not a lack of drivers like everyone has said. Basically when the camera.apk(lg camera) is launched it looks for libamce.so (i figured this out by reverse engineering the lg camera and found the referrence on where it looks for the shared library libamce.so.) i went ahead and tried to push the lg camera with the libamce.so yet still got a force close, this time the error was a reloc lbrary error looking for a [b]_nzcamera6connect[/b] function. I then went ahead an decompiled the libamce.so and found that it depends on libnvomx.so, then i decompiled libnvomx.so and found that it depends on libm.so, then i tried pushing all three libs to gb and still got a force close. After digging deep enough i found that libm.so depends on libcamera_client.so which i also decompiled and then i found the [b]_nzcamera6connect[/b] fuction is contained here. I attempted to push the libcamera_cleint.so to to gb and boot failed, then i tried editing the update-zip file to include the libcamera_client.so (from froyo) and boot also failed. I am positive that once we get this libcamera_client.so ported from froyo to gb the lg camera will work. Luckily there is no dependency on the framework. This is where i need your help since i know your the dev who made eb possible or any dev thats out there faux, morific thanks.
[b]update(7/27/11): Bounty increased to $100.00 thanks to:
[quote]eleeo037037 :$10
adevilfish :$10
bakedpatato : $5.00[/quote][/b]
[b]major update (7/26/11)
since the ota is official and the lg cam is not contained i am starting a bounty at $75.00 for the first person who can figure this out. I have tried numerous attempts using different approaches to no avail. There are others in the thread who mentioned they will also put up a bounty. I alone will pay $75.00 plus whatever anyone else decides to throw in the pot. [/b]
[b]update 3 (7/22/11): Attempted again to change some files in the framework and upon boot logcat threw error for missing decl from the camera$files in the framework. I pushed the libcamera_client.so from froyo and then the messaged changed to this:
[quote]i//system/xbin/busybox( 1015): Sysctl: /etc/sysctl.conf: No such file or directory
i//system/xbin/busybox( 1015): -k: No such file or directory
i//system/xbin/busybox( 1015): [: 61m: Bad number[/b][/quote]
[b]update 2(7/22/11) : Flashing eb 1.0.5 gr v21e rom with modified framework and it failed, so i pushed libcamera_client.so and it failed, error below [/b]
[quote]- waiting for device -
--------- beginning of /dev/log/main
i/netd ( 1018): Netd 1.0 starting
--------- beginning of /dev/log/system
i/vold ( 1017): Vold 2.1 (the revenge) firing up
d/vold ( 1017): Usb_configuration switch is not enabled in the kernel
d/vold ( 1017): Volume extsdcard state changing -1 (initializing) -> 0 (no-media)
d/vold ( 1017): Volume sdcard state changing -1 (initializing) -> 0 (no-media)
d/vold ( 1017): Volume extsdcard state changing 0 (no-media) -> 1 (idle-unmounted)
w/vold ( 1017): Duplicate state (1)
d/vold ( 1017): Volume sdcard state changing 0 (no-media) -> 1 (idle-unmounted)
w/vold ( 1017): Duplicate state (1)
w/vold ( 1017): Duplicate state (1)
i/debug ( 1019): Debuggerd: Jul 15 2011 10:15:43
d/ ( 1029): Open is ok, now, we are in user_land!
D/ ( 1029): Set continue (1280x960)
d/ ( 1029): Set continue (1280x1024)
d/ ( 1029): Set continue (1280x1024)
d/ ( 1029): Set continue (1360x768)
d/ ( 1029): Set continue (1440x900)
d/ ( 1029): Set continue (1680x1050)
d/ ( 1029): Set bettermode (1280x720)
d/ ( 1029): Set bettermode (1920x1080)
d/ ( 1029): Set bettermode (1280x720)
d/ ( 1029): Set bettermode (1920x1080)
d/ ( 1029): Set bettermode (1920x1080)
d/ ( 1029): Set bettermode (1920x1080)
d/ ( 1029): Set bettermode (1920x1080)
d/kipc ( 1020): Kipc_init()
d/kipc ( 1020): Address is 127.0.0.1, port is 45211
d/kipc ( 1020): Binding...
D/kipc ( 1020): Listening...
D/kipc ( 1020): Accepting...
D/ganril ( 1020): Gan ril starting
d/ganril ( 1020): Entering main loop
d/ganat ( 1020): 65 6e 74 65 72 69 6e 67 20 6d 61 69 6e 4c 6f 6f
d/ganat ( 1020): 70 28 29
d/ganat ( 1020): Gan_at_open
d/ganpsat ( 1020): Gan_ps_at_open
d/ganat ( 1020): Additional logging enabled. Going to call readline()
d/ganat ( 1020): Readline
d/ganat ( 1020): Readline : Before read
i/ ( 1030): Screencaptured accept lsocket: 9
i/vold ( 1017): Usb_mass_storage function disabled
e/netlinkevent( 1017): Netlinkevent::findparam(): Parameter 'switch_name' not found
e/netlinkevent( 1017): Netlinkevent::findparam(): Parameter 'switch_state' not found
w/vold ( 1017): Switch /devices/virtual/switch/usb_mass_storage event missing name/state info
i/rescuestarter( 1026): Rescuestarter 6.3.274 starts
i/rescuestarter( 1026): Ready, waiting for connection
e/netlinkevent( 1017): Netlinkevent::findparam(): Parameter 'switch_name' not found
e/netlinkevent( 1017): Netlinkevent::findparam(): Parameter 'switch_state' not found
w/vold ( 1017): Switch /devices/virtual/switch/usb_mass_storage event missing name/state info
i//system/xbin/busybox( 1015): Sysctl: /etc/sysctl.conf: No such file or directory
i//system/xbin/busybox( 1015): -k: No such file or directory
i//system/xbin/busybox( 1015): [: 61m: Bad number
i/vold ( 1017): Usb_mass_storage function enabled
d/vold ( 1017): Share method ums now available
i//system/xbin/busybox( 1015): Mount: Invalid argument
i//system/xbin/busybox( 1015): Run-parts: /system/etc/init.d/10ext4tuneup exited with code 255
i//system/xbin/busybox( 1015): Starting automatic zipalign 07-22-2011 22:21:12
i//system/xbin/busybox( 1015): Zipalign: Not found
i//system/xbin/busybox( 1015): Zipalign already completed on /data/app/*.apk
i//system/xbin/busybox( 1015): Zipalign: Not found
i//system/xbin/busybox( 1015): Zipalign already completed on /system/app/accountandsyncsettings.apk
i//system/xbin/busybox( 1015): Zipalign: Not found
i//system/xbin/busybox( 1015): Zipalign already completed on /system/app/applicationsprovider.apk
i//system/xbin/busybox( 1015): Zipalign: Not found
i//system/xbin/busybox( 1015): Zipalign already completed on /system/app/bluetoothopp.apk
i//system/xbin/busybox( 1015): Zipalign: Not found
i//system/xbin/busybox( 1015): Zipalign already completed on /system/app/bluetoothpbap.apk
i//system/xbin/busybox( 1015): Zipalign: Not found[/quote]
[b]update 7/22/11 - working on patching and porting elements from the froyo framework to gb[/b]
[img]http://forum.xda-developers.com/attachment.php?attachmentid=662618&stc=1&d=1311355083[/img]
[b](7/21/11)major update: Lg releases stock gb rom v21e however lg cam is not on board. This thread will.continue until we can successfully port the lg cam to gb. [/b]
[b]update 7/20/2011:
[quote]status update: Spoke with doniqq via pm he is working hard for us (so please thank him) to port the lg cam from froyo to gb. I am going to take another stab at this tonight and check 1 more thing. For those that had/have the nexus 1, i was the one who successfully ported the cm camera to rodriguez miui when everyone thought it was impossible. I am pretty sure the framework.jar is not part of this however when i moved the cm 7 cam to miui i did modify the framework, so i will take a look at this tonight before ruling it out completely.
[/quote][/b]
[b]here is the header of the decompiled libamce.so just in case:[/b]
[quote].plt:000459f4 ;
.plt:000459f4 ; +-------------------------------------------------------------------------+
.plt:000459f4 ; | this file has been generated by the interactive disassembler (ida) |
.plt:000459f4 ; | copyright (c) 2009 by hex-rays, |
.plt:000459f4 ; | license info: B3-ada1-9d85-df |
.plt:000459f4 ; | licensed user |
.plt:000459f4 ; +-------------------------------------------------------------------------+
.plt:000459f4 ;
.plt:000459f4 ; input md5 : 2ebb5ff4c8e8cf34c40ffc3aed9e8042
.plt:000459f4
.plt:000459f4 ; ---------------------------------------------------------------------------
.plt:000459f4 ; file name : C:\users\flak0-hpn3\downloads\libamce.so
.plt:000459f4 ; format : Elf (shared object)
.plt:000459f4 ; imagebase : 8000
.plt:000459f4 ; needed library 'libcamera_client.so'
.plt:000459f4 ; needed library 'libsurfaceflinger_client.so'
.plt:000459f4 ; needed library 'libui.so'
.plt:000459f4 ; needed library 'liblog.so'
.plt:000459f4 ; needed library 'libcutils.so'
.plt:000459f4 ; needed library 'libutils.so'
.plt:000459f4 ; needed library 'libhardware.so'
.plt:000459f4 ; needed library 'libmedia.so'
.plt:000459f4 ; needed library 'libandroid_runtime.so'
.plt:000459f4 ; needed library 'libc.so'
.plt:000459f4 ; needed library 'libm.so'
.plt:000459f4 ; needed library 'libstdc++.so'
.plt:000459f4 ; needed library 'libdl.so'
.plt:000459f4 ; needed library 'libbinder.so'
.plt:000459f4 ; needed library 'libskia.so'
.plt:000459f4 ; needed library 'libicuuc.so'
.plt:000459f4 ; needed library 'libegl.so'
.plt:000459f4 ; needed library 'libnvomx.so'
.plt:000459f4 ;
.plt:000459f4 ; eabi version: 5
.plt:000459f4 ;
.plt:000459f4
[/quote][/quote]
Click to expand...
Click to collapse
anybody try contacting faux or morfic to see if they could take a look? They are both very cool guys. I can talk to them if you want.
I have a silly question? If you use titanium back up and restore the LG camera would that work? If not, why?
I contacted both of them plus numerous devs.
jdkackley said:
anybody try contacting faux or morfic to see if they could take a look? They are both very cool guys. I can talk to them if you want.
Click to expand...
Click to collapse
Sent from my LG-P999 using XDA App
ClausMontoya said:
I have a silly question? If you use titanium back up and restore the LG camera would that work? If not, why?
Click to expand...
Click to collapse
I know it wont work but I couldnt tell you why. I thought the same thing and have tried it.
bls2633 said:
I know it wont work but I couldnt tell you why. I thought the same thing and have tried it.
Click to expand...
Click to collapse
Doesn't Titanimum just back up the apk file and not the compiled shared object?
Even so it'd be scary to think that it would somehow overwrite shared objects, potentially breaking the OS.
ClausMontoya said:
I have a silly question? If you use titanium back up and restore the LG camera would that work? If not, why?
Click to expand...
Click to collapse
I believe that what has been explained above is that there are libraries that the apk depend on to function that are not available on CM7 at the moment. (I could be wrong though)
yeah it's a similar reason if you backup DSP Manager from CM7 and try to install it on stock it will basically do nothing.
hey everyone i am still waiting for some devs to respond. Doniqq said he would take a look and let me know. We are 90% to having the LG Cam on GB.
If anyone else is good with shared objects in Android let me know.
Can you post the libcamera_client.so decompiled?
In theory this should be fairly simple to compile under gingerbread.
Scyth3 said:
Can you post the libcamera_client.so decompiled?
In theory this should be fairly simple to compile under gingerbread.
Click to expand...
Click to collapse
I can post it but i don't think it will compile, Remember i used a deconplier to reveal the source.
Sent from my LG-P999 using XDA App
I'll join in on this when I get home later. Has anyone tried contacting LG? They seem pretty reasonable.
Nah he means like talking to them about the camera drivers and what not I'm sure he wont say he'd trying to convert there froyo camera app to work with gingerbread lol they should be pretty reasonable
Yeah that's what I meant. I figure if there's something we need they might be able to help us. OP PM me
Status Update: 7/20/2011 US EST
Status Update: Spoke with Doniqq via PM he is working hard for us (so please thank him) to port the LG Cam from Froyo to GB. I am going to take another stab at this tonight and check 1 more thing. For those that had/have the Nexus 1, I was the one who successfully ported the CM Camera to Rodriguez MIUI when everyone thought it was impossible. I am pretty sure the framework.jar is not part of this however when I moved the CM 7 cam to MIUI I did modify the framework, so I will take a look at this tonight before ruling it out completely.
Thank u everyone, your thank yous motivate that much more. I will keep u updated.
Sent from my LG-P999 using XDA App
Its solved because i believe the reason why the LG cam won't work has been found and the culprit is the libcamera_client.so from Froyo to GingerBread. Its now requires the work of a dev to port. Just saying
Sent from my LG-P999 using XDA App
Thanks to Chuckhriczko who is also jumping on board to help.
Faux responded and respectfully informed me that he is working on several projects however if he has some spare time he will take a look for us.
Sent from my LG-P999 using XDA App
I'm trying to find resources for building Jelly Bean from AOSP for Nexus S 4G. I realize that updated binaries haven't been posted yet, and I've been trying to use the proprietaries from ICS. I've pulled down AOKP, CM and a JB ROM ported to the NS4G for reference. I've tried using the extract-files.sh from AOKP against ICS as well. Right now, my rom, built using make otapackage, doesn't boot. It goes into a loop. I'm excluding the recovery. I guess that I'm looking for a little guidance into how people build ROMs for any device, whether or not binaries are explicitly delivered. I've been comparing sources, makefiles and reading logs, attempting to find some direction, but nothing has jumped out at me. Here's the beginning of the log...
Code:
?:??: W/?(?): --------- beginning of /dev/log/system
07-19 11:44:02.054: I/Vold(81): Vold 2.1 (the revenge) firing up
07-19 11:44:02.070: D/Vold(81): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
07-19 11:44:02.070: D/Vold(81): --------- beginning of /dev/log/main
07-19 11:44:02.082: I/DEBUG(85): debuggerd: Jul 18 2012 16:25:56
07-19 11:44:02.136: I/Netd(84): Netd 1.0 starting
07-19 11:44:02.191: D/Vold(81): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
07-19 11:44:02.191: D/Vold(81): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)
07-19 11:44:02.191: W/Vold(81): Duplicate state (1)
07-19 11:44:02.191: W/Vold(81): Duplicate state (1)
07-19 11:44:02.191: W/Vold(81): Duplicate state (1)
07-19 11:44:02.195: W/Vold(81): Duplicate state (1)
07-19 11:44:02.808: D/AndroidRuntime(88): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
07-19 11:44:02.808: D/AndroidRuntime(88): CheckJNI is OFF
07-19 11:44:02.812: I/SurfaceFlinger(87): SurfaceFlinger is starting
07-19 11:44:02.820: I/SurfaceFlinger(87): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
07-19 11:44:02.851: E/FramebufferNativeWindow(87): couldn't open framebuffer HAL (Not a typewriter)
07-19 11:44:02.851: E/FramebufferNativeWindow(87): couldn't open gralloc HAL (Not a typewriter)
07-19 11:44:02.851: E/SurfaceFlinger(87): Display subsystem failed to initialize. check logs. exiting...
...but I've not found any help regarding it. I've found several guides for porting roms, but not many for how to build from source for devices or versions not directly supported in AOSP. Does anyone know of a good resource for me? I promise to share anything that I learn or produce from this project! Thank you!
I'm trying to find resources for building Jelly Bean from AOSP for Nexus S 4G. I realize that updated binaries haven't been posted yet, and I've been trying to use the proprietaries from ICS. I've pulled down AOKP, CM and a JB ROM ported to the NS4G for reference. I've tried using the extract-files.sh from AOKP against ICS as well. Right now, my rom, built using make otapackage, doesn't boot. It goes into a loop. I'm excluding the recovery. I guess that I'm looking for a little guidance into how people build ROMs for any device, whether or not binaries are explicitly delivered. I've been comparing sources, makefiles and reading logs, attempting to find some direction, but nothing has jumped out at me. Here's the beginning of the log...
Code:
?:??: W/?(?): --------- beginning of /dev/log/system
07-19 11:44:02.054: I/Vold(81): Vold 2.1 (the revenge) firing up
07-19 11:44:02.070: D/Vold(81): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
07-19 11:44:02.070: D/Vold(81): --------- beginning of /dev/log/main
07-19 11:44:02.082: I/DEBUG(85): debuggerd: Jul 18 2012 16:25:56
07-19 11:44:02.136: I/Netd(84): Netd 1.0 starting
07-19 11:44:02.191: D/Vold(81): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
07-19 11:44:02.191: D/Vold(81): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)
07-19 11:44:02.191: W/Vold(81): Duplicate state (1)
07-19 11:44:02.191: W/Vold(81): Duplicate state (1)
07-19 11:44:02.191: W/Vold(81): Duplicate state (1)
07-19 11:44:02.195: W/Vold(81): Duplicate state (1)
07-19 11:44:02.808: D/AndroidRuntime(88): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
07-19 11:44:02.808: D/AndroidRuntime(88): CheckJNI is OFF
07-19 11:44:02.812: I/SurfaceFlinger(87): SurfaceFlinger is starting
07-19 11:44:02.820: I/SurfaceFlinger(87): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
07-19 11:44:02.851: E/FramebufferNativeWindow(87): couldn't open framebuffer HAL (Not a typewriter)
07-19 11:44:02.851: E/FramebufferNativeWindow(87): couldn't open gralloc HAL (Not a typewriter)
07-19 11:44:02.851: E/SurfaceFlinger(87): Display subsystem failed to initialize. check logs. exiting...
...but I've not found any help regarding it. I've found several guides for porting roms, but not many for how to build from source for devices or versions not directly supported in AOSP. Does anyone know of a good resource for me? I promise to share anything that I learn or produce from this project! Thank you!
I have ported official MIUI V4 for Incredible S to glacier, but WIFI doesn't work, how to fix it ? thanks
FIX,thX
logcat?
You didn't couple a Sense Kernel with an AOSP ROM did you?
log
I/rmt_storage( 4248): rmt_storage user app start
I/rmt_storage( 4248): rmt_storage open success
I/rmt_storage( 4248): rmt_storage shared memory ioctl success
I/rmt_storage( 4248): rmt_storage mmap addr = 400b5000
E/rmt_storage( 4248): rmt_storage wait event ioctl failed
D/WifiService( 224): setWifiEnabledPersist enable=true, persist=true, getCallingPid()=1516
I/WifiHW ( 224): wifi_load_driver load module
I/WifiHW ( 224): is_wifi_driver_loaded
I/WifiHW ( 224): wifi_load_driver end error 2
E/WifiStateMachine( 224): Failed to load driver!
E/WifiStateMachine( 224): DriverFailedState
I/rmt_storage( 4253): rmt_storage user app start
I/rmt_storage( 4253): rmt_storage open success
I/rmt_storage( 4253): rmt_storage shared memory ioctl success
I/rmt_storage( 4253): rmt_storage mmap addr = 40174000
E/rmt_storage( 4253): rmt_storage wait event ioctl failed
A. You shouldn't use a Sense kernel with MIUI.
B. Try porting from a device closer to ours, like Desire S, Desire HD or G2.
MIUI V4 has the 2.8.3 build for the MyTouch, everything works great except for WiFi calling.
trikar21b said:
MIUI V4 has the 2.8.3 build for the MyTouch, everything works great except for WiFi calling.
Click to expand...
Click to collapse
ummm..wifi calling has been working for awhile on miui v4.......
estallings15 said:
A. You shouldn't use a Sense kernel with MIUI.
B. Try porting from a device closer to ours, like Desire S, Desire HD or G2.
Click to expand...
Click to collapse
Totally agree
zeng3545 said:
I have ported official MIUI V4 for Incredible S to glacier, but WIFI doesn't work, how to fix it ? thanks
Click to expand...
Click to collapse
hi.. ive had this problem before on a few different roms.. one thing i usually do is go into settings and disable all of my network and broadcasting options,, then boot the phone into recovery.. after i reboot,, everything is usually ok.. same for my mobile network..
MIUIv4 WIFI ERROR FIXED WITH S-ON
Im too stucked for 2 weeks to get WIFI on MIUIv4... (Worked for my Incredible S, try on your OWN risk)
Incredible S
HBOOT 2.02 S-ON
Bootloader UNLOCKED (htcdev.com)
Cause of error :- MIUI v4 wont works fully on HTC Stock Kernel. MIUIv4.xx.xx.zip contain a BOOT.img that contain the suppported kernel for MIUIv4. When you have S-ON , boot.img can't be updated via Recovery (zip). All errors can be fixed by updating the kernel (boot.img) provided in ROM zip
How to Update Kernel with S-ON : S-OFF-ing is a difficult tasks. So you can update kernel without S-OFF. It is done via 'fastboot'
1.Extract the boot.img from the MIUI-v4-xx-xx.zip. Copy boot.img to C:\Android\
2.Reboot your phone in Bootloader (Power-off -> Vol-Down + Pwr)
3.Goto Fastboot
4.Install HTC Sync (for drivers)
5.Connect USB
6.Open cmd
7.Navigate to 'fastboot.exe' folder
8 Type fastboot flash boot c:\android\boot.img
9.Format system,data,dalvik
10.Reflash MIUI from recovery
Good luck!!
Hit thanks if works, let help others
what is your overall experience on the miui version of android
Some of you may be familiar with my trials with my T699. To make a long story short, (see that story here http://forum.xda-developers.com/showthread.php?t=2528444) (thanks gee one!)
I was attempting to put CM on my Relay and I ended up hard bricking it.
I can now boot but I need a SD card installed to do it.
Recently I was playing around with adb and was running logcat which dumped a whole mess of wonderful information.
The line I thought was important was the following -
I/rmt_storage( 125): No EBR found
It is my guess that I messed up (corrupted) the EBR and that is why I am dependent on the external SD card.
My question is, does anyone know how to restore the EBR to working condition? I have tried to use odin to put the stock
image on but I think it is just over-writing the image on the SD card. If it can be done using adb that would be very great too since
it appears to be working well.
Oh, and the other thing I noticed, if I do not put the SD card, with image, into the slot I just boot into QHSUSB-DLOAD mode.
Which means much but is not useful at this time.
Thanks all,
Lou
I have added the first 25 lines of the logcat -
--------- beginning of /dev/log/main
I/rmt_storage( 125): Target is APQ8064: 1074445686
I/rmt_storage( 125): No EBR found
I/rmt_storage( 125): Error (-1) parsing MBR partitions
I/rmt_storage( 125): Registering modemst1: 0x4a /boot/modem_fs1
I/rmt_storage( 125): Registering modemst2: 0x4b /boot/modem_fs2
I/rmt_storage( 125): Registering fsg: 0x58 /boot/modem_fsg
I/rmt_storage( 125): Registering ssd: 0x5d ssd
I/rmt_storage( 125): 4 GPT partitions found
D/ICD ( 183): icd .02 runs
E/DataRouter( 186): Main entered
E/DataRouter( 186): switchUser
E/DataRouter( 186): monitor_usb_thread
E/DataRouter( 186): server_init
E/DataRouter( 186): Opening of the usb select file failed fd is -1 & errno is 2
E/DataRouter( 186): Opening of the usb select file failed fd is -1 & errno is 2
E/DataRouter( 186): Initialise USB and start the thread
E/DataRouter( 186): dr_usb_init
E/DataRouter( 186): USB Interface is open with 0x9
E/DataRouter( 186): USB interface is now configured for usb_fd = 0x9
E/DataRouter( 186): THREAD LAUNCH
E/DataRouter( 186): monitor_data_of_usb
E/DataRouter( 186): USB monitor thread launched, usb_fd= 0x9
E/DataRouter( 186): init_cur_sock
E/DataRouter( 186): Before the usb select
I/DEBUG ( 182): debuggerd: Mar 16 2013 22:15:51
*** UPDATE ***
I found another interesting line in line in the logcat ...
W/PackageManager( 674): Library not found: /system/framework/com.qualcomm.location.quipslib.jar
More on de-bricking
I have been continuing my hunt on how to permanently de-brick my T699. The following thread does not leave me with
much hope . I know it is for Evita on the HTC One but I see similar behaviour when I hook my T699 to linux.
http://forum.xda-developers.com/showthread.php?t=1966850&page=40
If anyone can comment on this it is greatly appreciated.