Database Users

-FIX- camera and wifi tether on CM 6.1 Builds

Camera fix copy to Android/system/app - http://www.multiupload.com/NUM91NJRVK
Wifi tether fix - install like any other app (make sure you uncheck ''Disable Wake-lock'' in the settings of the app) http://www.multiupload.com/VX0DELSCT0
Default froyo theme for CM 6.1 builds -for those who like default froyo look. Unzip framework.zip to Android/root/system, your folders must look like this on your SDCARD "Android/root/system/framework", or use any other root explorer to copy the files to the system - http://www.multiupload.com/HA0I19WPTM
PS. Sometimes when changing from camera to video doesn't work, for this just restart the app.

Thanks for camera fix =)

What does this fix in the camera?
Thanks

Thanks
Will it work in Sense builds like Desire HD or is it Cyanogen Mod version only ?

aread22 said:
What does this fix in the camera?
Thanks
Click to expand...
Click to collapse
+1 ???????????

I believe it fixes the issue where flash gets stuck after a quick set of photos or some minutes of video... atleast thats what it fixed for me

v-b-n said:
I believe it fixes the issue where flash gets stuck after a quick set of photos or some minutes of video... atleast thats what it fixed for me
Click to expand...
Click to collapse
Indeed. It fixes the flash issue

camera fix not work??
i copied the camera fix to android/system/app....... now what?? how do i install it? I reboot the phone and everything... the flash is still stuck after 5 shots?
help please.. thanks.

lucian777 said:
Camera fix copy to Android/system/app - http://www.multiupload.com/NUM91NJRVK
Wifi tether fix - install like any other app (make sure you uncheck ''Disable Wake-lock'' in the settings of the app) http://www.multiupload.com/VX0DELSCT0
Default froyo theme for CM 6.1 builds -for those who like default froyo look. Unzip framework.zip to Android/root/system, your folders must look like this on your SDCARD "Android/root/system/framework", or use any other root explorer to copy the files to the system - http://www.multiupload.com/HA0I19WPTM
PS. Sometimes when changing from camera to video doesn't work, for this just restart the app.
Click to expand...
Click to collapse
anyway to get this without the wood panel?

ajm2387 said:
anyway to get this without the wood panel?
Click to expand...
Click to collapse
What wood panel are you taking about

now the camera no longer hangs, thanks for the work.

So I tried to put in the camera APK, the folders you listed did not exist so I made them and put the APK I downloaded into the folder but it will not install, it fails
Any advise?

mattfmartin said:
What wood panel are you taking about
Click to expand...
Click to collapse
The camera fix changes the theme of the camera app. It has a fancy woodpanel-like frame now.
Is there a way to change it back to the stock theme/frame?

I have also noticed continuous auto focus is gone in the camcorder and the camera only focuses after you have pressed the shutter button.

lemar123 said:
Thanks
Will it work in Sense builds like Desire HD or is it Cyanogen Mod version only ?
Click to expand...
Click to collapse
did it work on desire hd Sense builds

Camera fix doesn't work by me...
i make pictures, go into preview and back to camera, than camera makes problems:-(
(Sorry for my englisch)

Camera Mod works for me, although sometimes I can't exit by pressing back, if this happens I need to press Home then select camera again, then back to exit. But all in all a huge improvement many thanks, running on BiffMod HD2 1.2

Can someone please share the steps to putting this into place? I am unable to it seems. When I try and run the APK it fails to install and if I just have it in the folder specified then I still have the problem. I am using BiffMod 1.2

k3nmill3r said:
Can someone please share the steps to putting this into place? I am unable to it seems. When I try and run the APK it fails to install and if I just have it in the folder specified then I still have the problem. I am using BiffMod 1.2
Click to expand...
Click to collapse
You should use Root explorer or SUFBS or another program that has root acces to system, then you can manually copy the camera app to system/app.

This works for fixing the flash issue but I noticed I can no longer click the thumbnail in the bottom corner of the screen and look at the pictures I take in the gallery. It is a minor issue but just wondering if anyone else is experiencing the same.

[Q] Menu Text

Can anyone tell me what xml i edit to change the text color? Been trying to follow a few tutorials with no joy.
Thank you

Well it is very easy to change the text colour.There are two ways.One is easy and other is a bit tricky.if you dont have root access try adw launcher ex it makes changing text colour and size very easy and fun and it offers a lot of customizations.if you dont have adw launcher ex(paid app)inform me I will post a link for the same.Hope this helps.

Thank you for your help. I have been trying to mod it in the styles.xml, after i recompiled it, i just get stuck in boot screen.

starof said:
Thank you for your help. I have been trying to mod it in the styles.xml, after i recompiled it, i just get stuck in boot screen.
Click to expand...
Click to collapse
Can you go into download/recovery mod

starof said:
Thank you for your help. I have been trying to mod it in the styles.xml, after i recompiled it, i just get stuck in boot
Click to expand...
Click to collapse
well I will surely try it today and see what goes wrong

Still no luck. I'm doing eveything it says in this link: http://forum.xda-developers.com/showpost.php?p=8316984&postcount=2297
Wonder if the problem is with APK manager

DPI conflicts in LMY47E

Today I found something really strange about builds LMY47E and LMY47D. I had been running 47D since last week with a DPI of 520, which was adjusted using Root Explorer in the build.prop. After trying to do the same in 47E, rebooting my device would display the "Android is upgrading... Optimizing app 1 of XXX" screen, and make it bootloop after optimizing the last app, displaying the same screen and optimizing my apps again and again.
After many hours trying to isolate the culprit, I found that to properly change DPI In 47E, one has to edit the build.prop lcd density AND use "adb shell wm density XXX". That's the only way I've made sure my device reboots properly.
I think this is really weird, since 47D and 47E are supposed to be identical. Does anybody have any clue about this?

redsmith said:
Today I found something really strange about builds LMY47E and LMY47D. I had been running 47D since last week with a DPI of 520, which was adjusted using Root Explorer in the build.prop. After trying to do the same in 47E, rebooting my device would display the "Android is upgrading... Optimizing app 1 of XXX" screen, and make it bootloop after optimizing the last app, displaying the same screen and optimizing my apps again and again.
After many hours trying to isolate the culprit, I found that to properly change DPI In 47E, one has to edit the build.prop lcd density AND use "adb shell wm density XXX". That's the only way I've made sure my device reboots properly.
I think this is really weird, since 47D and 47E are supposed to be identical. Does anybody have any clue about this?
Click to expand...
Click to collapse
I just changed it with root explorer. I didn't have any issues.
Then again I stayed within the default density's from my past devices.
Nexus 6 is 560, I went to 480.

antiochasylum said:
I just changed it with root explorer. I didn't have any issues.
Then again I stayed within the default density's from my past devices.
Nexus 6 is 560, I went to 480.
Click to expand...
Click to collapse
That's weird. Mine would survive a couple of reboots but after that, bootloop fest.
I'll keep an eye on this issue anyway.

I just went through this on 47E. It was bad but it turns out that you only need to do "adb shell wm density XXX" and not edit the build prop. Editing the build prop sent me through the bootloop

krazekid007 said:
I just went through this on 47E. It was bad but it turns out that you only need to do "adb shell wm density XXX" and not edit the build prop. Editing the build prop sent me through the bootloop
Click to expand...
Click to collapse
The thing is, if you only do "adb shell wm..." you will get weird graphical glitches, especially in the keyboard. So far, I've managed to avoid them by editing build.prop too.

redsmith said:
The thing is, if you only do "adb shell wm..." you will get weird graphical glitches, especially in the keyboard. So far, I've managed to avoid them by editing build.prop too.
Click to expand...
Click to collapse
Still get glitches even after rebooting?

Lol, I'm so glad someone brought this up. Thought I or my phone was going nuts!

All I've ever done is change the build.prop, no adb stuff, never had issues...for all builds
Sent from my Nexus 6 using XDA Free mobile app

A2CKilla said:
All I've ever done is change the build.prop, no adb stuff, never had issues...for all builds
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
It lasts for a few days sometimes.... Usually after a reboot or 2 its gameover.. It'll usually let me reboot 2x before looping .. If I don't reboot it'll just randomly turn off and then..well.. Loop

Not the only ones with this issue... here's what I have found even with "D" & "E" working with the group trying to port the Blinkfeed Launcher from Sense 7 which requires a DPI change to work correctly on the Nexus 6.
532DPI use to work with 5.0.1 & 5.0.2... No longer the case for any 5.1 build (haven't tried "M" build yet) which is the perfect setting for Blinkfeed Sense 7 Launcher....
I am using 520 right now... other experience issues with the bootloop at 520... I have found a way to test:
1. TWRP backup current good DPI setting... Backup up everything cache, efs, system, data, etc.
2. After TWRP backup, boot up and apply the new settings you wish to test. Apply then completely power off.
3. Power on and boot up. If no optimizing apps issues, you have passed step one.
4. Now TWRP backup your new settings, backup everything, reboot system. If no bootloop, then you should be golden
I think it is something in the code to streamline how it handles graphics... however it seems that what is acceptable varies from phone to phone. Most see good results staying with factors of 40 & 80 while others can do even factors of 20....
Don't think anyone has figured out root cause entirely..... I really like to know why I could 532 before and can't now???

Yea 532 was my buttah

redsmith said:
The thing is, if you only do "adb shell wm..." you will get weird graphical glitches, especially in the keyboard. So far, I've managed to avoid them by editing build.prop too.
Click to expand...
Click to collapse
So were you able to successfully change your DPI by editing the build.prop?

I had to do adb shell trick too, otherwise, bootloops.

Build.prop edit LCD_density
redsmith said:
. . . . . I think this is really weird, since 47D and 47E are supposed to be identical. Does anybody have any clue about this?
Click to expand...
Click to collapse
Started with rooting 5.0.1. Then edited build.prop with 'build.prop.editor and changed the LCD-density to 493.
Because the native resolution is of the N6 screen is 493.
After upgrading to LMY47D the DPI value was 520 (0r 560?) again. I edited this value 'ro.sf.lcd_density' and set the value to 384.
With that value the N6 is in tablet mode.
After rebooting the value of 'ro.sf.lcd_density was 384, but the display was not different.
In the Build.Prop editor there is a menu item called Build.Prop Tweaks. In the Tweaks-list the entry 'LCD Density' was missing.
I did not have a backup of the build.prop file so a full restore in recovery was needed to correct this.
The Build.Prop editor has an option to create a backup. Use this option first before editing.
Now for about a week with 47D and DPI 384 and font size to huge, the N6 works fine. (Stock, rooted, encrypted).
Remark.
Because the N6 has a amoled display it's a bit strange that the name 'ro.sf.lcd_density' is used.

NLBeev said:
Started with rooting 5.0.1. Then edited build.prop with 'build.prop.editor and changed the LCD-density to 493.
Because the native resolution is of the N6 screen is 493.
After upgrading to LMY47D the DPI value was 520 (0r 560?) again. I edited this value 'ro.sf.lcd_density' and set the value to 384.
With that value the N6 is in tablet mode.
After rebooting the value of 'ro.sf.lcd_density was 384, but the display was not different.
In the Build.Prop editor there is a menu item called Build.Prop Tweaks. In the Tweaks-list the entry 'LCD Density' was missing.
I did not have a backup of the build.prop file so a full restore in recovery was needed to correct this.
The Build.Prop editor has an option to create a backup. Use this option first before editing.
Now for about a week with 47D and DPI 384 and font size to huge, the N6 works fine. (Stock, rooted, encrypted).
Remark.
Because the N6 has a amoled display it's a bit strange that the name 'ro.sf.lcd_density' is used.
Click to expand...
Click to collapse
whojabacod said:
Yea 532 was my buttah
Click to expand...
Click to collapse
krazekid007 said:
So were you able to successfully change your DPI by editing the build.prop?
Click to expand...
Click to collapse
redsmith said:
I had to do adb shell trick too, otherwise, bootloops.
Click to expand...
Click to collapse
I don't believe there is any rhyme or reason to it bootlooping... something is definitely different in the programming in 5.1... tried everything last night to get 532DPI to stick.... build.prop.... adb command... tried them all... would reboot 1 time ok, second time "op apps" bootloop. this was not the case with 5.0.1 or 5.0.2... I remember tweaking the dpi by 2 up and down to find a perfect dpi for a Blinkfeed launcher port on 5.0.2 and never had this issue. It is either something Google did on purpose for this build or on accident. Either way, we are kind of screwed until someone smarter than I can put a finger on as to what is causing this... I just think 5.1 was rushed to get VoLTE out there for the Verizon release...

When your N6 is bootlooping in 5.1. And you can't find the cause and/or a solution then you could decide to go back to the factory settings including unroot. This can be done easily with the toolkit of Wugfresh.
I did that and I am using now 5.1 (47D) and edited buil.prop. DPI set to 384.

NLBeev said:
When your N6 is bootlooping in 5.1. And you can't find the cause and/or a solution then you could decide to go back to the factory settings including unroot. This can be done easily with the toolkit of Wugfresh.
I did that and I am using now 5.1 (47D) and edited buil.prop. DPI set to 384.
Click to expand...
Click to collapse
Or you can just fastboot flash system.img and save time and your data. It's what I did on a DPI bootloop.

SilkyJohnson said:
Or you can just fastboot flash system.img and save time and your data. It's what I did on a DPI bootloop.
Click to expand...
Click to collapse
Let's hope for him.

NLBeev said:
Let's hope for him.
Click to expand...
Click to collapse
No need to hope - it works. I did it.

[Q] Screenshot blocked by security policies and camera problem DPI

Friend!
I have a problem.
When I take a screenshot, the device tells me that it is blocked by security policies.
How can I remove the message and take screenshots?
Another problem is that when opening the camera, the image has changed the DPI, just like when opening the multitasking. I'm sorry but I can not go upstairs.
Thanks!
PS: Excuse my English, it is not my native language.
PS: SOLVED!

nicko-win said:
Friend!
I have a problem.
When I take a screenshot, the device tells me that it is blocked by security policies.
How can I remove the message and take screenshots?
Another problem is that when opening the camera, the image has changed the DPI, just like when opening the multitasking. I'm sorry but I can not go upstairs.
Thanks!
PS: Excuse my English, it is not my native language.
Click to expand...
Click to collapse
Hi,for resolve your problem,install from Playstore terminal emulator.Open and write:
su
wm size reset
wm dpi reset
Now you can make a screenshot

Solution!
Piombo71 said:
Hi,for resolve your problem,install from Playstore terminal emulator.Open and write:
su
wm size reset
wm dpi reset
Now you can make a screenshot
Click to expand...
Click to collapse
Excelent! Now it works perfect!
Thanks my friend

Piombo71 said:
Hi,for resolve your problem,install from Playstore terminal emulator.Open and write:
su
wm size reset
wm dpi reset
Now you can make a screenshot
Click to expand...
Click to collapse
and for those without root?

Sorry,i don't know any procedure for this problem whitout root,why any custom rom for N9005 (Note 3)have root inside.

Pixel UI Sounds

Hey folks,
Coming from a pixel, I really missed the nice sound it played when you touch anything on the screen (sounds similar to google keyboard touch sounds). So here's what I did:
1. Had a friend with a rooted pixel send me his UI sounds (https://drive.google.com/file/d/10bI8faSnKBSwT0LRS2stk7g1Q9rrIRSf/view?usp=drivesdk)
2. Located the file that controls touch sounds (/system/product/media/audio/ui/Effect_Tick.ogg)
3. Using a root browser (mixplorer is my favorite), I tried copying and pasting over the current Effect_Tick.ogg, no luck. Tried deleting the current Effect_Tick.ogg, no luck. Tried changing permissions on the live file, no luck. I checked file size and the pixel one is smaller than the oneplus file, so I'd think partition size wouldn't be a problem.
I'm running android 11 with magisk. I'm wondering if android no longer lets you change live system files? Maybe this is something I need to change while phone is in fastboot? Think this breaks safetynet?
Thanks for the input folks!

xxBrun0xx said:
Hey folks,
Coming from a pixel, I really missed the nice sound it played when you touch anything on the screen (sounds similar to google keyboard touch sounds). So here's what I did:
1. Had a friend with a rooted pixel send me his UI sounds (https://drive.google.com/file/d/10bI8faSnKBSwT0LRS2stk7g1Q9rrIRSf/view?usp=drivesdk)
2. Located the file that controls touch sounds (/system/product/media/audio/ui/Effect_Tick.ogg)
3. Using a root browser (mixplorer is my favorite), I tried copying and pasting over the current Effect_Tick.ogg, no luck. Tried deleting the current Effect_Tick.ogg, no luck. Tried changing permissions on the live file, no luck. I checked file size and the pixel one is smaller than the oneplus file, so I'd think partition size wouldn't be a problem.
I'm running android 11 with magisk. I'm wondering if android no longer lets you change live system files? Maybe this is something I need to change while phone is in fastboot? Think this breaks safetynet?
Thanks for the input folks!
Click to expand...
Click to collapse
did you know how to do?

Morloc2 said:
did you know how to do?
Click to expand...
Click to collapse
Nope, never got it to work. I don't think it's possible

xxBrun0xx said:
Nope, never got it to work. I don't think it's possible
Click to expand...
Click to collapse
thx for reply me
maybe is possible with pc
how can we surf in android folders when we connect the phone to the pc?