In all of the current AOSP builds, the forward facing camera video fails because the information is pulled from msm8960-common. We share almost everything in common with the other devices, but our forward facing camera is of lower resolution so the base settings do not work with ff video on the xt907.
This is a relatively simple xml edit that I have played around with. I have tested on CM10.1 rc and CM10.2 nightly with the stock camera and hangouts video (it starts ok with hangouts, but I'm not where I can have a conversation with anyone right now so ymmv). It should work on all of the aosp based builds.
To apply use a root enabled file explorer, in directory...... delete your existing media_profiles.xml (or add .bak extension). copy this file, remove the .txt extension, and set permissions to rw-r-r then reboot.
I will try and get a flashable zip up later if anyone wants it. That way, you can simply flash it after flashing your rom of choice if you are running nightlies or like to try new builds often.
Let me know if it works or if anything looks like it needs tweaking.
********Update********
it may be necessary to clear data on camera/gallery app after updating the media_profiles.xml file
also adding flashable zip file
ej1911 said:
In all of the current AOSP builds, the forward facing camera video fails because the information is pulled from msm8960-common. We share almost everything in common with the other devices, but our forward facing camera is of lower resolution so the base settings do not work with ff video on the xt907.
This is a relatively simple xml edit that I have played around with. I have tested on CM10.1 rc and CM10.2 nightly with the stock camera and hangouts video (it starts ok with hangouts, but I'm not where I can have a conversation with anyone right now so ymmv). It should work on all of the aosp based builds.
To apply use a root enabled file explorer, in directory...... delete your existing media_profiles.xml (or add .bak extension). copy this file, remove the .txt extension, and set permissions to rw-r-r then reboot.
I will try and get a flashable zip up later if anyone wants it. That way, you can simply flash it after flashing your rom of choice if you are running nightlies or like to try new builds often.
Let me know if it works or if anything looks like it needs tweaking.
Click to expand...
Click to collapse
hmm, having some troubles getting the file to download - just showing up as a text in my browser....
edit: just copied to a notepad, saved it, and e-mail it to myself. downloaded it, placed it in the "system/etc" folder, changed permissions, rebooted.... but no dice for me, still get a force close. wondering if it has to do with me being on AOKP, since you said this is for AOSP ROMs....
jco23 said:
hmm, having some troubles getting the file to download - just showing up as a text in my browser....
edit: just copied to a notepad, saved it, and e-mail it to myself. downloaded it, placed it in the "system/etc" folder, changed permissions, rebooted.... but no dice for me, still get a force close. wondering if it has to do with me being on AOKP, since you said this is for AOSP ROMs....
Click to expand...
Click to collapse
Easiest way is to right click the file and save as.
Couple of questions. Which app is force closing, is it the camera? and Which AOKP are you on? I have most of them downloaded. I will try to flash it and see if I can figure it out.
ej1911 said:
Easiest way is to right click the file and save as.
Couple of questions. Which app is force closing, is it the camera? and Which AOKP are you on? I have most of them downloaded. I will try to flash it and see if I can figure it out.
Click to expand...
Click to collapse
well, the official message is that the gallery has stop responding (same as before) - but this happens when I attempt to launch camcorder in front-facing mode - so yes, it is camera, but I think android refers to it as "gallery".
i believe that video calls for hangouts works fine though (but I'll test again tonight).
I'm on the "unofficial" AOKP ROM
jco23 said:
well, the official message is that the gallery has stop responding (same as before) - but this happens when I attempt to launch camcorder in front-facing mode - so yes, it is camera, but I think android refers to it as "gallery".
i believe that video calls for hangouts works fine though (but I'll test again tonight).
I'm on the "unofficial" AOKP ROM
Click to expand...
Click to collapse
OK, thanks. You might have to clear the data in the gallery app, I'm not sure. I got the video camera to work on the AOKP 4.3 9/11 nightly, but I flashed the update zip that I made to test it and it was a fresh install. I couldn't do much testing though because I got the AOSP keyboard is force closing problem.
I will update the OP in a little bit with the flashable zip file.
ej1911 said:
OK, thanks. You might have to clear the data in the gallery app, I'm not sure. I got the video camera to work on the AOKP 4.3 9/11 nightly, but I flashed the update zip that I made to test it and it was a fresh install. I couldn't do much testing though because I got the AOSP keyboard is force closing problem.
I will update the OP in a little bit with the flashable zip file.
Click to expand...
Click to collapse
got it working now.
i downloaded the file this time, e-mailed it to myself, copied it to the "system/etc" folder, changed permissions, renamed the org as .bak, renamed the new file as .xml, then rebooted. after reboot, I went into the camera app and once again got a force close. however, I tried playing around with the settings "record mode" from 1020 to 480, and then went back to FF camcorder, and it recorded! I then changed the "record mode" back to 1080, and FF camcorder worked just fine.
so I think you are correct, perhaps one needs to clear cache/data in the gallery prior to use.
thanks for the tip and the mod! nice work!
to resolve your AOSP keyboard force closing problem, try wiping system before installing the update. this worked for me.
Bit of thread necro, I know... But it's for a good cause.
Have you pushed this fix to CM? I am looking into what exactly needs to change in the source, I suppose we can fix this somehow from CM, and then all of the ROM's will be fixed (assuming they all update with the fix )
The flashable zip worked perfect for me. Thank you so much!
---
Sent using my Droid Razor M- THE BEST SMARTPHONE ON THE PLANET!
Heard about Kettlebells... learn more: http://synergykettlebell.com
arrrghhh said:
Bit of thread necro, I know... But it's for a good cause.
Have you pushed this fix to CM? I am looking into what exactly needs to change in the source, I suppose we can fix this somehow from CM, and then all of the ROM's will be fixed (assuming they all update with the fix )
Click to expand...
Click to collapse
Argggh merged it into cm code. All it should flow to all ROMs as they sync and build.
Sent from my XT907 using xda app-developers app
Related
Link: http://forum.xda-developers.com/showpost.php?p=9172522&postcount=2058
Many thanks to supagforce, for this find!!
I personally tested this on TnT Lite 1.02, with no issues in the default browser (other than high memory use, but I guess that's to be expected).
11/29/10 EDIT: Newer Flash version out, GLES optimized. See this post for details: http://forum.xda-developers.com/showpost.php?p=9476506&postcount=26
Doesn't work on cm6
akodoreign said:
Doesn't work on cm6
Click to expand...
Click to collapse
Good point. For cm6.1 beta2, just alter the build.prop as follows:
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
and reboot.
This was not my fix, and I take no credit for it - it was in the big thread. I believe that the forthcoming beta 3 is going to have this change built-in.
roebeet said:
Good point. For cm6.1 beta2, just alter the build.prop as follows:
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
and reboot.
This was not my fix, and I take no credit for it - it was in the big thread. I believe that the forthcoming beta 3 is going to have this change built-in.
Click to expand...
Click to collapse
yup that was it. TY !
I can confirm it works on CM6 with the above added to the build.prop. I've done it myself.
Wants to join the party
I have been trying to days now to get this one last piece working. I have copied the flash apk to everywhere I can think of but still can't get it to install. I have tried using ADB (INSTALL_FAILED_INVALID_APK), Droid Explorer (crashes while trying to install), made sure SYSTEM was R/W, and still I am stumped.
Any ideas what else I can try? I am running CM v6.1b2.
Gbmedusa said:
I have been trying to days now to get this one last piece working. I have copied the flash apk to everywhere I can think of but still can't get it to install. I have tried using ADB (INSTALL_FAILED_INVALID_APK), Droid Explorer (crashes while trying to install), made sure SYSTEM was R/W, and still I am stumped.
Any ideas what else I can try? I am running CM v6.1b2.
Click to expand...
Click to collapse
look at the post above about the build.prop change. Btw, there's a beta3 now that does not have this issue, tmk.
Hulu
Can this be hacked to include the mod in the hulu enabled flash apk? Can they be diffed?
http://forum.xda-developers.com/showthread.php?t=688054
Thanks for all your hard work roe...
The Dude
It worked for me in stock system
roebeet
Please thank supag for me. I am not a programmer, I purchased this item so I could show my patients video and anatomy intructional pics. There is no way I would have been able to use it with out the combined team effort from all you folks.
P.S. The only change I made to the system was loading Launcher Pro.
Thanks again
Wyngnut
Gbmedusa said:
I have been trying to days now to get this one last piece working. I have copied the flash apk to everywhere I can think of but still can't get it to install. I have tried using ADB (INSTALL_FAILED_INVALID_APK), Droid Explorer (crashes while trying to install), made sure SYSTEM was R/W, and still I am stumped.
Any ideas what else I can try? I am running CM v6.1b2.
Click to expand...
Click to collapse
I am having the same problem trying to install on full vanilla. In fact, my device will not even download the rar...it fails. I had to copy it from another device....so dumb question, i assume i just need to rename the file to apk, not unrar it?
Flash 10.1 fix
I used a RAR extractor on my windows machine then side loaded the APK into SD on system. I then used ES file explorer to find the file On the internal SD and when I opened it it gave me the option to install. Install went off without a hitch.
I have stock system with no ROM changes and I loaded launcher pro which I use instead onf TapNTap. I have now viewed many Utube video's as well as movie trailers with no problems.
Hope that helps
Wyngnut
roebeet said:
look at the post above about the build.prop change. Btw, there's a beta3 now that does not have this issue, tmk.
Click to expand...
Click to collapse
My apologies for not explaining more fully. I actually have the build.prop edit in place. I tried copying the flash apk to /system as well as /system/app. My problem is that I can't get it to install. Either I get an error, the program attempting the install crashes, or nothing happens.
By the way, you mention a beta 3 of CM. Any idea where I can find it? I did a quick 'net search but came up with nothing specific for the gtablet. Guess I need to plow through the megathread again.
Any help would be greatly appreciated.
Edit: Could it be I need to fix flash prior to installing CM? I had to do that with the wifi hack before it would work. Guess I need to get another backup going just in case.
Edit (again): Never mind about Beta 3. I see in the megathread that it is in the works.
For the APK error, not sure about vanilla (never tried it). TnT Lite is 90% vanilla so I figured it should work on full stock.
I usually install with "adb install", which is how I tested it. I assumed a sideload would also work. I haven't put it in /system yet although I probably will do that when I build out TnT Lite 2.00 - that's coming next week btw, as soon as VS sends out their new firmware update and I can get my hands on it.
roebeet said:
For the APK error, not sure about vanilla (never tried it). TnT Lite is 90% vanilla so I figured it should work on full stock.
I usually install with "adb install", which is how I tested it. I assumed a sideload would also work. I haven't put it in /system yet although I probably will do that when I build out TnT Lite 2.00 - that's coming next week btw, as soon as VS sends out their new firmware update and I can get my hands on it.
Click to expand...
Click to collapse
Yeah, the ADB install just gave me an invalid APK error so I gave up there.
I may try flashing back to stock(ish) and installing from there.
Wyngnut said:
I used a RAR extractor on my windows machine then side loaded the APK into SD on system. I then used ES file explorer to find the file On the internal SD and when I opened it it gave me the option to install. Install went off without a hitch.
I have stock system with no ROM changes and I loaded launcher pro which I use instead onf TapNTap. I have now viewed many Utube video's as well as movie trailers with no problems.
Hope that helps
Wyngnut
Click to expand...
Click to collapse
+1 on that. Same setup and very easy fix. Thanks for this!
still no luck..
roebeet said:
Good point. For cm6.1 beta2, just alter the build.prop as follows:
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
and reboot.
This was not my fix, and I take no credit for it - it was in the big thread. I believe that the forthcoming beta 3 is going to have this change built-in.
Click to expand...
Click to collapse
this doesn't work for me.. in fact i opened the build.prop file and the properties were already set to the same values.. i'm running tnt lite 2.0. any suggestions?
i'm willing to even use CM if it'll mean running flash player, but so far this rom has been the most stable.
Works on the stock "out of the box" G Tablet!!
S_C_B said:
Works on the stock "out of the box" G Tablet!!
Click to expand...
Click to collapse
I am having the same problem as iksnae. I changed the Rom to TNT Lite 2.0.2 prior to loading the 10.1 Flash Player. I get Youtube videos and even Angry Birds but I can't get flash video from CNN or Hulu? Should I flash back to stock and then add flash. If so can someone point me to that thread? Every other hack has worked perfectly.
cbrownesq said:
I am having the same problem as iksnae. I changed the Rom to TNT Lite 2.0.2 prior to loading the 10.1 Flash Player. I get Youtube videos and even Angry Birds but I can't get flash video from CNN or Hulu? Should I flash back to stock and then add flash. If so can someone point me to that thread? Every other hack has worked perfectly.
Click to expand...
Click to collapse
My GTab was configured like yours. I unintalled Flash 10.1 and loaded the vanilla "out-of-the-box" Rom version. This version also had the clockwork menu so when you Flash don't panic if you see this pop up, just follow the instructions for loading the update.zip file from the /sdcard (I think it was option 2). I then side loaded Flash 10.1.apk from the PC to /sdcard and using ES File Explorer to access /sdcard, I doubled clicked on the Flash 10.1.abk to install.
Then I reinstalled TnT_Lite 2.0, flashed and then TnT_Lite 2.02 & Flashed this update.
ESPN3 works great. Also get Flash_TV from the Android Market and you now have IPTV. I am anxious to get the docking module so I can stream HDMI 1080P to my 46" LCD. No more cable, no more monthly cable bills (I do get internet 28MB/sec service).
Still looking for an optimized Nvidia Tegra 2 video media player that will take advantage of the processors embedded video encoder functions. I expect this will play HDMI 1080P movies quite nicely. Rock Player is rumored to be working on a dual core Cortex 9 version. Right now it plays using the software control option and is slow and clunky.
I believe that Flash 10.1 is optimized for the Nvidia Tegra 2 processor and it is quite nice. The streaming videos play smoothly. Not sure how they will play in HD when using the docking module and the HGMI connection to the large screen.
Best of luck. It's easy once you figured out how to do the original Flash load(s).
EKS
roebeet said:
Link: http://forum.xda-developers.com/showpost.php?p=9172522&postcount=2058
Many thanks to supagforce, for this find!!
I personally tested this on TnT Lite 1.02, with no issues in the default browser (other than high memory use, but I guess that's to be expected).
11/29/10 EDIT: Newer Flash version out, GLES optimized. See this post for details: http://forum.xda-developers.com/showpost.php?p=9476506&postcount=26
Click to expand...
Click to collapse
Thank you for this 11/29 edit pointer to the flash apk file (rename txt to API), all I have done is rooted thus far with z4root, stock TnT, and now YouTube videos work!
I was really getting tired of my carrier name showing up twice on the lockscreen and taking up extra real estate on my notification drop-down so I figured out how to disable the SPN from showing and how to customize the PLMN to say whatever I want.
KEY FILES TO EDIT
/data/data/com.android.providers.telephony/optable.db
/system/etc/apns-conf.xml
/system/etc/spn-conf.xml
In the apns-conf.xml make sure your provider is listed with a numeric value.
Here's an example: numeric="311370" mcc="311" mnc="370"
* As you can see the numeric is the MCC plus the MNC.
In the spn-conf.xml make sure your provider is listed with an spnOverride.
Here's an example: <spnOverride numeric="311370" spn_display_rule="SPN_RULE_SHOW_PLMN" spn_override_only_on="310,311"/>
The optable.db needs to be edited with SQLite Database Browser to add your numeric and the text to display.
Here are a few pre-configured downloads:
PLMN: CyanogenMod
http://www.4shared.com/file/BawWWTpv/cm7_plmn_gsm_crespo.html
PLMN: The Ultimate Droid
http://www.4shared.com/file/jo0455rx/tud_plmn_gsm_crespo.html
PLMN: GCI Wireless
http://www.4shared.com/file/l3fZUzGu/gci-apns-plmn.html
PLMN: B*** I Got An Android (with no asterisks)
http://www.4shared.com/file/Vkz6poYC/*****_plmn_gsm_crespo.html
NSFW YouTube Video - B*** I Got An Android
Flash these files AFTER you have flashed a ROM and booted up at least once! I tested all four files on TUD 3.0.0 Beta, CM7 A3, and various CM7 Crackflasher builds.
*Screenshots are from CM7 Crackflasher build #54 with the Jungle Waterfall livewallpaper
Very cool mod. I will try this out when I have the time!
thank you
Love this, it worked great on Bionix with 1.3 kernel. For some reason running the same rom with the new 1.4b kernel it no longer works and yes I tried reflashing and wiping a few times. Any ideas?
Hey could you make me one and either PM me or post it up?
I'm on CM7 on a Nexus S, and I don't see a '/system/etc/spn-conf.xml' file. It doesn't seem to exist on mine. I'm on the latest nightly (#8) and have updated everything. Am I missing something?
How exactly did you get these files? I'm having all sorts of trouble with this. First off, the optable.db file is zero K, even when I extract it through ASTRO or Root Explorer with R/W permissions. Secondly, as I mentioned in the last post, the 3rd file is missing from the stated directory.
I'm really confused, as it seems that none of these instructions add up for a Nexus S. I'd like my T-Mobile message to instead display "Nexus S: Pure Android, Pure Google"
Did not work on Modaco R9, CM7 or The Cracker builds...
nickmv said:
I'm on CM7 on a Nexus S, and I don't see a '/system/etc/spn-conf.xml' file. It doesn't seem to exist on mine. I'm on the latest nightly (#8) and have updated everything. Am I missing something?
Click to expand...
Click to collapse
spns-conf.xml does not exist on the Nexus S originally, but if you place it in /system/etc/ the OS knows to use it.
nickmv said:
How exactly did you get these files? I'm having all sorts of trouble with this. First off, the optable.db file is zero K, even when I extract it through ASTRO or Root Explorer with R/W permissions. Secondly, as I mentioned in the last post, the 3rd file is missing from the stated directory.
Use the optable.db from my zip and just edit it as you see fit.
I'm really confused, as it seems that none of these instructions add up for a Nexus S. I'd like my T-Mobile message to instead display "Nexus S: Pure Android, Pure Google"
Click to expand...
Click to collapse
I'm not sure what the character limit is but that might be too long.
I have all the files in the proper folders but it still doesn't work. Modaco R9
for those having problems getting this to work try using clockwork and press mount/storage then mount/system. hope this works.
tsalate said:
for those having problems getting this to work try using clockwork and press mount/storage then mount/system. hope this works.
Click to expand...
Click to collapse
You might be on to something, it worked for about 3 seconds then went right back to T-Mobile.
Still doesn't work. Mounted /system and /data. Does it only work for certain carriers? I'm using a&t
Is there a way to apply this to ALL carriers, rather than selecting one manually.
thanks
deleted .
Finally ! That bug was very annoying to me.
I'll try the fix asap, thanks a lot!
e: works like a charm!
Yeah, it was a so annoying issue...
I wonder why so less people visited this thread .
I copied this ZIP onto my SD card,rebooted, went into clockwork mod, install zip, choose zip and flashed this,rebooted but am stuck on the HTC screen now for over 7 minutes am i doing something wrong?
It's as well i made a backup or id lose everthing
jonny68 said:
I copied this ZIP onto my SD card,rebooted, went into clockwork mod, install zip, choose zip and flashed this,rebooted but am stuck on the HTC screen now for over 7 minutes am i doing something wrong?
It's as well i made a backup or id lose everthing
Click to expand...
Click to collapse
Try adding the libaudio.so to your ROM.zip (with 7-zip or WinRAR) at the right directory and flash the ROM.zip again. That's what I am doing everytime I change something
j4n87 said:
Yeah, it was a so annoying issue...
I wonder why so less people visited this thread .
Click to expand...
Click to collapse
Because you posted it in the "Themes and Apps" section
thanks a lot for post here
great job
kackburt said:
Try adding the libaudio.so to your ROM.zip (with 7-zip or WinRAR) at the right directory and flash the ROM.zip again. That's what I am doing everytime I change something
Click to expand...
Click to collapse
you mean copy the actual zip file into the ROM zip and then flash?
jonny68 said:
you mean copy the actual zip file into the ROM zip and then flash?
Click to expand...
Click to collapse
Unzip the cwm with the fix and navigate to "system/lib" and copy the "libaudio.so".
then open the rom zip navigate to "system/lib" and paste the "libaudio.so" there.
Didn't understand your previous post..did you make a backup or not?
If not...just flash your current rom again, you won't lose your data if you do this.
Only the files that you edited in /system like gps.conf or other tweaks you have to edit again.
Tried on UD3.3.0 wont boot... :s
People dont understand that this work the best on CM7 nexus roms.
That by installing this fix on CM7 or AOSP you will probaly lose the robo and high volume on first call fix. That most roms have custom libs including this lib. Minimum requirements I would say CM7 2.34 and AOSP 2.34 since cm7 and AOSP are the most equal roms to each other.
To say it simple you cant just simply flash this on every rom also make sure your permission is right.
Is this fix able to work on an HTC Desire running 2.3.4 Oxygen ROM?
jonny68 said:
I copied this ZIP onto my SD card,rebooted, went into clockwork mod, install zip, choose zip and flashed this,rebooted but am stuck on the HTC screen now for over 7 minutes am i doing something wrong?
It's as well i made a backup or id lose everthing
Click to expand...
Click to collapse
If you have a nandroid backup, you should be on the safe side!
Try to wipe cache partition first, then the dalvik cache and then flash the zip-file.
All of these actions take place in the CWM.
Hope it works!
The libaudio.so fix was submitted to gerrit (Change I24a4a11b: Fix for a1026 suspend)by Jordon aka Jyxent. It was mergered with the latest nightlies, and should be merged with CM 7.0.4
jens1288 said:
The libaudio.so fix was submitted to gerrit (Change I24a4a11b: Fix for a1026 suspend)by Jordon aka Jyxent. It was mergered with the latest nightlies, and should be merged with CM 7.0.4
Click to expand...
Click to collapse
Yes, that fix works fine. I'm not sure it fixes the few seconds delay that affects all Gingerbread phones though but there was another potential workaround submitted for that too.
http://review.cyanogenmod.com/#change,5420
I have yet to include it in my build and try it though.
The story on the front page links to the wrong fix. The libaudio fix was for the wonk on the Nexus One. The libaudio library is hardware specific and may cause issues on other devices that don't share the same processor.
I've submitted a patch to gerrit that helps with the call delay here:
http://review.cyanogenmod.com/#change,5420
Thank you for clearing that up jyxent. To go into a bit more detail...
The fix that was posted, as jyxent mentioned, is for the Nexus One. That is for the infamous "wonk" that has been plaguing N1 users since the Gingerbread nightlies started (who woulda thunk it was just a single line that needed to be added).
The 2-3 second delay is something that affects most (if not all) Gingerbread installs. Currently there isn't a simple "fix" for this. It requires recompiling portions of Gingerbread. jyxent's fix is submitted to CM, but I don't see any reason why this can't be applied to AOSP as well. It has yet to be reviewed by the CM dev team (at least it doesn't have any comments on it yet). It might be something that can be made into some device-independent flashable zip, but it has yet to be created.
j4n87 said:
Unzip the cwm with the fix and navigate to "system/lib" and copy the "libaudio.so".
then open the rom zip navigate to "system/lib" and paste the "libaudio.so" there.
Didn't understand your previous post..did you make a backup or not?
If not...just flash your current rom again, you won't lose your data if you do this.
Only the files that you edited in /system like gps.conf or other tweaks you have to edit again.
Click to expand...
Click to collapse
done thanks
Can this be done manually with root explorer, by copying the libaudio.so to/system/lib and a reboot?
LG O4X UnoX SENSE4 ALPHA RELEASEYou thought you never see a HTC SENSE with BeatsAudio interface on O4X? This is the ALPHA release of SENSE 4.0 (version 2.17.401.2) and using STOCK LG kernel for your LG Optimus 4X HD
Latest update 10.Jan.2013
Changed build to avoid conflict with team venoms mods, this should be more stock now.
It is now a ClockWorkMod Update.zip using AROMA installer.
alot changed and yet, no GSM is working but i am getting closer.
***STATUS***
Click to expand...
Click to collapse
This is very early developer release, more a proof of concept, to help others start porting or even developing roms, without thinking the locked bootloader will limit the distribution. so regular users, will probably not use this for anything since mobile connectivity is not working.
but if you wish to check performance and maybe test some performance here, this is a way to do it and compare.
Any contribution to fixing the RIL driver in this one or other fixes are appreciated, feel free to make patches if you can help improve this.
***WHY***
Click to expand...
Click to collapse
So the O4X community have been almost dead and not a single custom rom has been released, primarily because many believe a unlocked bootloader is needed.
WHAT WORKS
Click to expand...
Click to collapse
GSM Mobile Radio - NO
AUDIO - YES (+ BEATS AUDIO works fine with headset)
PHOTO CAMERA - YES (FRONT is very,very dark, BACK camera is ok)
VIDEO CAMERA - YES (for now only 1080p recording, 1280x720 closes camera, change in settings)
VIDEO PLAYBACK - YES
MICROPHONE - YES
WIFI - YES
GPS - YES
BLUETOOTH - YES (Wifi seems affected by enabling bluetooth at bootup, and no wifi connectivity exists, so disable BT at bootup)
ROTATION - YES
YOUTUBE - YES
MOST SENSORS - YES
VIBRATION - NO
NFC - YES (No icon when activated, but works fine with included NFCtag+)
PC CONNECTION - NO (not worked on it)
INT / EXT SDCARD - YES (without sdcard, camera cannot save to internal storage)
NOTES ON FIRST USE
Click to expand...
Click to collapse
- First start can take 5-6 minutes due to a process waiting for media scanner.
- in /system folder, you can rename "local.prop1" to "local.prop" , and you can enable adb root.
- its based on v10d, i do not know if the boot.img is required, but remove it if you wish to try it without. (remember to edit md5 checksum file if you do)
- do not try and install recovery from the CWM app, just use it to reboot into cwm, do NOT install recovery, its already in place and modified to work with sense.
DOWNLOAD
Click to expand...
Click to collapse
Download full as CWM update.zip ALPHA 1.0 here
Firefox users: Ignore warning, this is just a zip with a backup included, no executables here
great! i will flash i tmr morning and have a taste on sense
Its online now!
2.17.401.2, so it's Android 4.0.4?
reas0n said:
2.17.401.2, so it's Android 4.0.4?
Click to expand...
Click to collapse
yes i believe so, it was based on a onex rom i found, nothing special, but a testrom.
Dexter you are GREAT !!! :good: :good:
THANK YOU !!
Looks amazing!
thank you very much... sense 4 on 4x
can someone make a backup for TWRP recovery??
---------- Post added at 06:51 AM ---------- Previous post was at 06:48 AM ----------
Dexter_nlb said:
Its online now!
Click to expand...
Click to collapse
finally first custom rom for LG4X..how about CM10 on LG4X?? btw, thanks for making first custom rom on our device :good:
razerblade17 said:
can someone make a backup for TWRP recovery??
Click to expand...
Click to collapse
you can modify the existing backup, by editing the nandroid.md5 checksum file, remove the "system.ext4.tar" line in the md5 file
and rename the "system.ext4.tar.a" to "system.ext4.tar" . and of course do the same with the real tar file.
then it should look pretty much like old backups
-------------------------------------------------------------------------------
Update:
after the upload,
i have checked GPS and NFC.
GPS is confirmed working
NFC needed fixing but it works now , althoug icon is gone, and the NFCplus app works too, so you can modify tags
wow NICE!! almost had a mini heart attack when i saw this post!:fingers-crossed:
looking forward to working CALL XDD
THX a lot for ur work!!!
Dexter_nlb said:
you can modify the existing backup, by editing the nandroid.md5 checksum file, remove the "system.ext4.tar" line in the md5 file
and rename the "system.ext4.tar.a" to "system.ext4.tar" . and of course do the same with the real tar file.
then it should look pretty much like old backups
-------------------------------------------------------------------------------
Update:
after the upload,
i have checked GPS and NFC.
GPS is confirmed working
NFC needed fixing but it works now , althoug icon is gone, and the NFCplus app works too, so you can modify tags
Click to expand...
Click to collapse
no luck...btw any other method to install via TWRP recovery?? my sd card has a problem, and no money to buy new one...so any solution to restore this backup??
i've been stuck in the setup wizard for so long now, i managed to get past the language/locale selection screen but I'm stuck in the next screen where venom setup is.
Anyone managed to get past this screen? can i delete setupwizard to bypass this process?
EDIT: finally get past the setup wizard!!! ultra smooth rom!!!
i know this is ALPHA but thought i should post a list of things i found not working so maybe someone can fix it =)
- Vibration not working
- Google Voice Search not working
- mount ext-sdcard not working
- Flashlight not working
- Whatsapp doesn't work (it says "Tablet is not supported" so i guess there's sth wrong with the IMEI or build.prop)
- pressing "settings" in camera app crash the app itself
- "Share" option is unusable (tested both by email and by Google+)
BUT
- Camera app works GREAT with rear camera!!!!!
- most if not all widgets work (though i didn't test all of them, most of them work!!! without a lag)
- Speaker works
tomanlam said:
i've been stuck in the setup wizard for so long now, i managed to get past the language/locale selection screen but I'm stuck in the next screen where venom setup is.
Anyone managed to get past this screen? can i delete setupwizard to bypass this process?
EDIT: finally get past the setup wizard!!! ultra smooth rom!!!
i know this is ALPHA but thought i should post a list of things i found not working so maybe someone can fix it =)
- Vibration not working
- Google Voice Search not working
- mount ext-sdcard not working
- Flashlight not working
- Whatsapp doesn't work (it says "Tablet is not supported" so i guess there's sth wrong with the IMEI or build.prop)
- pressing "settings" in camera app crash the app itself
- "Share" option is unusable (tested both by email and by Google+)
BUT
- Camera app works GREAT with rear camera!!!!!
- most if not all widgets work (though i didn't test all of them, most of them work!!! without a lag)
- Speaker works
Click to expand...
Click to collapse
thanks for the report back, and yes, i am aware of the setup screen bug, it also seems to relate to the customization process hanging in the background, so it will hang for some time too, sorry. porting is not always easy
edit: i believe the problem rely in the SIMcard not being detected as you might note, the simcard screen normally shown is not being shown, which asks to insert sim. it also seems the the firmware seems to tell the htc software it is a CDMA phone, so this might also be the problem why gsm is not working. this is seen in the radio log.
- i noted the other things, and flashlight is the only one i am not looking at, as our flashlight is different and can be damaged if i try to make it like a lightbulb i think. (do not know and do not want to find out)
- we got no IMEI yet, since phone is not working, so the whatsapp might have a different issue or as you say, it does not exist. build.prop is pretty much OneX original here.
- external sdcard works fine here, i wonder why you cannot see it in storage settings?
- i do not know why googlevoice do not work, ill check up on it, probably relate to recording format, which i noted only works with AAC and not AMR format.
Dexter_nlb said:
thanks for the report back, and yes, i am aware of the setup screen bug, it also seems to relate to the customization process hanging in the background, so it will hang for some time too, sorry. porting is not always easy
edit: i believe the problem rely in the SIMcard not being detected as you might note, the simcard screen normally shown is not being shown, which asks to insert sim. it also seems the the firmware seems to tell the htc software it is a CDMA phone, so this might also be the problem why gsm is not working. this is seen in the radio log.
- i noted the other things, and flashlight is the only one i am not looking at, as our flashlight is different and can be damaged if i try to make it like a lightbulb i think. (do not know and do not want to find out)
- we got no IMEI yet, since phone is not working, so the whatsapp might have a different issue or as you say, it does not exist. build.prop is pretty much OneX original here.
- external sdcard works fine here, i wonder why you cannot see it in storage settings?
- i do not know why googlevoice do not work, ill check up on it, probably relate to recording format, which i noted only works with AAC and not AMR format.
Click to expand...
Click to collapse
external sd is not accessible in the default file manager? but if i use another file manager (FX Explorer), i can access the extSD
but in storage settings, everytime i try to unmount the sd, settings.apk crashes
but as an alpha "port" (sort of), the rom is ULTRA-SMOOTH, wish at least GSM call work soon:silly:
tomanlam said:
external sd is not accessible in the default file manager? but if i use another file manager (FX Explorer), i can access the extSD
Click to expand...
Click to collapse
ok i see now.
this the the HTC way of having external sdcard, the semi way, since they officially do no longer make many top models with sdcard.
the location of external sdcard is at /mnt/sdcard2 and internal is /mnt/sdcard
let me check up on the unmounting, i already got some fixes, but not GSM, sorry, that require alot more it seems to fix.
about the GSM part, it is strange that both OneX and O4X uses a radio chipset with QUO 6260 radio, but they flash firmware different ways, so that makes it incompatible somehow.
Great job man!
I will join your development as soon as I finish my exams (2-3 weeks) so the LG 4X community gets alive. Will read your thread in the meantime.
Making a backup now while downloading this rom.
Thank you so much for your time and effort Dexter!
Sense 4.1 is actually pretty smooth on our O4X. Too bad radio is somehow turned off. I would rock this rom as my daily once radio gets solved. But for now, everything else seems to be working. Beats works great too. Camera is good, but video FCs.
babymatteo said:
Sense 4.1 is actually pretty smooth on our O4X. Too bad radio is somehow turned off. I would rock this rom as my daily once radio gets solved. But for now, everything else seems to be working. Beats works great too. Camera is good, but video FCs.
Click to expand...
Click to collapse
getting DRM working little better here, i simply copied the generated RSA keys from /data to a tar file and extract it at every boot, but not sure how i get the lgeril to load it now, since its htc based.
for the camera, i simply use a camera from another htc 4.0.4 release and it works fine. probably related to resolution of camera and it works now recording in 1080p as well.
This is a repost from the Moto X Pure section. LINK
Follow the instructions to backup and then flash the AOSP dialer and contacts in TWRP. This worked perfectly for me on my Turbo.
Works great. Thanks!
I'm considering flashing this. Then I got to looking at these apps in the play store. Of course it shows that they're incompatible with all my devices, but my question is to ask if after flashing this, has anyone tried updating to the updated apps that are in the Play Store? Of course if I don't get a response in the next few minutes, I'll probably give it a shot anyway. After a nandroid, naturally.
I was able to get the contacts to install and initiated, and the dialer installed, according to Aroma, but for some reason, it wouldn't initiate. I suspect it's something to do with it being CM. I recall that CM somehow broke the dialer compatibility, back in either 10 or 11...
Sent from my DROID Turbo via Tapatalk. Now with that cyanogenmod goodness.
The original write up didn't pan out for me. I renamed the stock dialer and contacts, extracted the ones from the .zip and put them in the folder where dialer and contacts were. System>priv-apps>Dialer/Contacts. I then rebooted and they seem to be working, time will tell. There doesn't appear to be the oft desired Call Blocking. I think that's only on the newer versions, Marshmallow only. The newest versions of these apps that are on the Play Store won't work either, as they're MM only.
Wynnded said:
The original write up didn't pan out for me. I renamed the stock dialer and contacts, extracted the ones from the .zip and put them in the folder where dialer and contacts were. System>priv-apps>Dialer/Contacts. I then rebooted and they seem to be working, time will tell. There doesn't appear to be the oft desired Call Blocking. I think that's only on the newer versions, Marshmallow only. The newest versions of these apps that are on the Play Store won't work either, as they're MM only.
Click to expand...
Click to collapse
I did the same thing. On CF's 1.2.5 odex ROM, renamed the existing dialer.apk and contacts.apk, flashed the zip, and it worked.
GeoFX said:
I did the same thing. On CF's 1.2.5 odex ROM, renamed the existing dialer.apk and contacts.apk, flashed the zip, and it worked.
Click to expand...
Click to collapse
Flashing the .zip wasn't panning out for me. When I did it that way, I didn't have a dialing app. I could go to contacts and initiate a call from there, and it would ring through, but there wasn't an interface for the ongoing call. I couldn't close the line. I removed the .apks from the .zip and placed them in the appropriate folders then rebooted. Really only had one incoming call, yesterday, and it was fine. I don't think that we have video call though, not that I've ever used it, but I didn't notice the icon for it.
Can somebody help me out? I'm trying to figure out the difference between the 5.1 stock contacts and the Google contacts zipped with the Google dialer in the OP. I'm comparing the 2 side by side on my phone and I swear I cant find a difference. I know the Google dialer has differences I am specifically asking about the contacts app. Thanks.
koftheworld said:
This is a repost from the Moto X Pure section. LINK
Follow the instructions to backup and then flash the AOSP dialer and contacts in TWRP. This worked perfectly for me on my Turbo.
Click to expand...
Click to collapse
couldn't get this to work on my droid. i tried the OP way by deleting the folders and letting the flash repopulate them, but the problem is that the zip's folders aren't 'contacts' and 'dialer', but rather 'googlecontacts' and 'googledialer'. i tried to flash and then to rename the contacts and dialer apks, and replace them with the new ones, but i still didn't have a dialer to speak of on my phone after reboot.
anyone find another way that works? i would really love to have this dialer...
I renamed the .apks inside of the Contact and Dialer folders to .bak, then flashed this file.
By the way, I believe that these Google .apks have been updated, but I don't have a clue how to make a flashable .zip. Anyone want to have a go at it?
Wynnded said:
I renamed the .apks inside of the Contact and Dialer folders to .bak, then flashed this file.
Click to expand...
Click to collapse
this is where my hangup is. the folder structure in my system is priv-apps>dialer>dialer.apk; in the flashable zip it's priv-apps>googledialer>dialer.apk
whether or not i rename the original file or delete it entirely, the new dialer apk just isn't routing to the same directory. guess i'll have to be patient and keep on with what i have...
midnitemass said:
this is where my hangup is. the folder structure in my system is priv-apps>dialer>dialer.apk; in the flashable zip it's priv-apps>googledialer>dialer.apk
whether or not i rename the original file or delete it entirely, the new dialer apk just isn't routing to the same directory. guess i'll have to be patient and keep on with what i have...
Click to expand...
Click to collapse
Odd, in the flashable .zip, and as installed, mine drills down as: priv-app>GoogleDialer>GoogleDialer.apk. The structure is the same when I drill down into the .zip file that I keep because I have to rename and flash it again after ROM updates. I can't help you beyond that. Beyond my abilities.
If you are running CM 13, download the latest version of gapps stock from open gapps project. You will have Google Dialer. They have white listed our device"quark" as compatible.
Once flashed make sure that you set the app as default in your app settings.
Sent from my DROID Turbo using XDA-Developers mobile app