• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Just throwing this out there: Cm13 for g2 mini sources

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?
 
SebasHacks said:
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?
Click to expand...

video recording should be working, green tint is a work in progress that i have theory about
 
whoshotjr2006 said:
video recording should be working, green tint is a work in progress that i have theory about
Click to expand...
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
 
SebasHacks said:
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
Click to expand...

Did you dirty flash? What carrier do you have? Make sure you clean flash with these early builds.
 
I've been in a boxing match with my trees the last few days but I'll focus on the kernel for now. You know, where I can actually be useful. :-P

I pushed a few commits yesterday, and will at least fix OTG tonight. I'll also compare our camera dts against the other phones in case there's anything to fix there.
 
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 :(
 
che_edgar said:
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 :(
Click to expand...
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.
 
73e6687dfb78b540556465ae3ff7bd38.jpg


This is what I get.
 
Ph0enix_216 said:
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.
Click to expand...

Out of curiosity and for science, what fixed your build?
 
I would double check reason being is the last build I was running I had no Bluetooth I just did a clean flash to the new build and everything is running great
 
Last edited:
Okay this is weird. I've got two Volts - a crackpot one I use for dev work, and my daily driver. I compiled CM13 today and flashed it to both. The crackpot Volt runs it perfectly, but my daily driver doesn't let me swipe down on the notification shade to access my quick settings :c

EDIT: After funking around with it until 3 AM this morning, I've concluded that the notification shade issue only happens when you flash the ROM and the Gapps package at the same time, whereas installing the ROM and doing a basic setup and then rebooting into TWRP and flashing the Gapps package works (wish just the "Setup Wizzard has stopped" error of course).
 
Last edited:
ShapeShifter499 said:
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.
Click to expand...
This works beautifully. Thank you for sharing.
 
ShapeShifter499 said:
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”.
Click to expand...
So using TWRP v2.8.7.0 is the culprit behind my SD card showing up as a USB (in Total Commander)??
_20160429_115019.JPG

But when I look at Storage & USB in settings it shows as portable storage.
_20160429_115315.JPG
After selecting portable storage, I press the 3 dot overflow menu to access settings. This is what shows.
_20160429_115001.JPG
What 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.
 
HasH_BrowN said:
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.
Click to expand...
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.
 
Ph0enix_216 said:
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.
Click to expand...

Be careful though... I can't get my phone to work now... Removed SD card(it FUBAR'd my SD card) then reflashed modded stock and now I loop in twrp 3.0
 
HasH_BrowN said:
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.
Click to expand...

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.
 
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...
 
spock1104 said:
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...
Click to expand...

Spock, try enabling the ov8858 or ov8588 config in defconfig. (Can't remember off the top of my head the exact name but I'm close.) I've been meaning to upload a test build with that enabled to see what happens for the green tint folks. Just haven't had time yet. That was my theory, it's a sensor for the camera that isn't enabled in our cm defconfig yet but was used for another msm8226 variant, I think the jagnm.
 
ShapeShifter499 said:
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.
Click to expand...
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.
Screenshot_20160429-205255.png
Screenshot_20160429-205136.png
 
You must log in or register to reply here.
Back
Top Bottom