SebasHacks
Newbie
Still no recording and CM11 green camera fix applied? Is there no way to repair it completely to where you don't have to have certain lighting for the green to disspear?
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Still no recording and CM11 green camera fix applied? Is there no way to repair it completely to where you don't have to have certain lighting for the green to disspear?
Hmm, oddly enough, after flashing your most recent zip, the recording still does not work. Not in third party apps like Snapchat or default camera app.. Though I know I did flash it correctly because vibration and home button light is workingvideo recording should be working, green tint is a work in progress that i have theory about
Hmm, oddly enough, after flashing your most recent zip, the recording still does not work. Not in third party apps like Snapchat or default camera app.. Though I know I did flash it correctly because vibration and home button light is working
Sprint, and yes at first I performed a dirty flash but later tried a clean flash, but to no avail, same result came out.Did you dirty flash? What carrier do you have? Make sure you clean flash with these early builds.
Bluetooth is working for me (although I compiled from the most recent commits). @che_edgar to create a logcat, open a terminal (or Command Prompt if you've got Windows) and run "adb logcat > C:\path\to\log.txt" right before testing something. It will create a text file wherever you specified when running the command, and will dump log information into it until you cancel the command.Hello guys, I found out that at least in my device when I try and turn on Bluetooth it asks me to stop it or something like that? Do you guys know what it could be? **I don't know how to create logcats![]()
Bluetooth is working for me (although I compiled from the most recent commits). @che_edgar to create a logcat, open a terminal (or Command Prompt if you've got Windows) and run "adb logcat > C:\path\to\log.txt" right before testing something. It will create a text file wherever you specified when running the command, and will dump log information into it until you cancel the command.
Are u on the most current build http://androidforums.com/index.php?posts/7281400![]()
This is what I get.
Yes I am, actually in both of my voltsAre u on the most current build http://androidforums.com/index.php?posts/7281400
I didn't fix anything really. I didn't download the latest ROM file, I compiled it from the latest commits by the devs on Github.Out of curiosity and for science, what fixed your build?
Did you dirty flash over a previous CM13 build? If you did, try wiping your cache and Dalvik/ART caches in TWRP and reboot.![]()
This is what I get.
This works beautifully. Thank you for sharing.Just got the boot loop again so I know it wasn't a issue of whatever bad kernel I flashed like I thought it was before. Interestingly I found you can still use adb during the boot loop of TWRP v3.0.0 so I used that to downgrade to TWRP v2.8.7.0 which seems alright for now.
I'm not sure if this has been posted anywhere but if anyone bootloops on TWRP v3.0.0 the below instructions should downgrade TWRP without erasing the OS or /data. This worked for me, however use extreme caution when entering these commands below, I'm not responsible for bricked devices.
Code:# First download a copy of TWRP v2.8.7.0 from bad_mofo https://www.androidfilehost.com/?fid=24052804347771339 # Connect your boot looping LG VOLT and adb push the resulting downloaded img file to somewhere in the LG Volt like so. /sdcard/Download should be a safe place. adb push twrp_2.8.7.0_volt.img /sdcard/Download # Then open a shell and dd copy the img to the correct recovery partition. adb shell # Verify the correct recovery partition by listing all possible partitions. ls -l /dev/block/platform/msm_sdcc.1/by-name/ # Should be recovery -> /dev/block/mmcblk0p17 # Then dd clone the TWRP img in place dd if=/sdcard/Download/twrp_2.8.7.0_volt-LOLLIPOP.img of=/dev/block/mmcblk0p 17 # Wait for completion and then type the command. reboot # It should reboot into the older TWRP v2.8.7.0 from here you can ask it to continue booting to the system or flash something else if you want.
This works beautifully. Thank you for sharing.
So using TWRP v2.8.7.0 is the culprit behind my SD card showing up as a USB (in Total Commander)??Glad it worked, one other thing I found though. TWRP v2.8.7.0 does not work if you choose to use "Adopted Storage" (SD + Internal) in CM 13/MM 6. TWRP v3.0.0 needs to be fixed so it doesn't boot loop, only thing that would work with "Adopted Storage”.
Format as internal means that your device will format the SD card to be seen as part of the phone's internal storage. However, it also encrypts it in a way that mean it can only be used on the device that formatted it. Formatting it as portable storage lets you swap SD card between phones. Regardless of what you do, make sure you backup your SD card's contents somewhere, such as on your computer's hard drive or a USB disk, because whichever formatting option you choose will wipe your SD card.So using TWRP v2.8.7.0 is the culprit behind my SD card showing up as a USB (in Total Commander)??View attachment 104346
But when I look at Storage & USB in settings it shows as portable storage. View attachment 104348 After selecting portable storage, I press the 3 dot overflow menu to access settings. This is what shows. View attachment 104349What does format as internal exactly mean? Does that straighten the SD card issue out or is that still reliant on the version of TWRP?
Everything works for storage, even the Xposed module Download2SD. Why would it show as a USB? Is there a way to correct that? Is there anything foreseeable that would cause issues by not correcting it?
Only other thing is data gets borked when I turn it off and back on, to keep WiFi from handing off during weak signal. APN fix(es) didn't work. Quick fix is to toggle airplane mode and LTE works again.
Format as internal means that your device will format the SD card to be seen as part of the phone's internal storage. However, it also encrypts it in a way that mean it can only be used on the device that formatted it. Formatting it as portable storage lets you swap SD card between phones. Regardless of what you do, make sure you backup your SD card's contents somewhere, such as on your computer's hard drive or a USB disk, because whichever formatting option you choose will wipe your SD card.
So using TWRP v2.8.7.0 is the culprit behind my SD card showing up as a USB (in Total Commander)??View attachment 104346
But when I look at Storage & USB in settings it shows as portable storage. View attachment 104348 After selecting portable storage, I press the 3 dot overflow menu to access settings. This is what shows. View attachment 104349What does format as internal exactly mean? Does that straighten the SD card issue out or is that still reliant on the version of TWRP?
Everything works for storage, even the Xposed module Download2SD. Why would it show as a USB? Is there a way to correct that? Is there anything foreseeable that would cause issues by not correcting it?
Only other thing is data gets borked when I turn it off and back on, to keep WiFi from handing off during weak signal. APN fix(es) didn't work. Quick fix is to toggle airplane mode and LTE works again.
I made a kernel change to try to combat the green camera, but it seems to prevent the phone from booting. I merged the w7's camera dts into ours. I'm guessing the slight differences matter to the libraries. I'm going to try the w7 libraries again...
I'm running latest @whoshotjr2006 build, but this bug happened on all CM13 builds. I just ran into my first issue with SD card bring recognized as USB. The torrent downloader FLUD force closes settings when trying to set storage to the real SD card.I'm not seeing that bug here, are you running @Bad_MOFO_33's build or @whoshotjr2006's build? @whoshotjr2006's latest build from http://androidforums.com/threads/cyanogenmod-13-beta-1.1023879/ works pretty great for me, even the stock CM camera app does pictures and video recording.