Database Develop

RAM in Froyo: welcome to Hell

I have been using the latests builds to see if they mitigate a common problem in our devices (mine is a Polaris). The insufficient memory makes it lag until forever when switching amongst applications, not only the heavy ones, but also the supposed light applications like Messaging, Phone, Contacts, etc.
The system has to work under really hard conditions: 20 - 28 MB when starting up. Every application I run is a fire proof. Applications like Navigation makes our devices literally crawl and bite the dust. Not far away, I was driving and tried to play some music at the same time. It was impossible. The waiting was unbearable and it finally hung like a pro.
My question is: is there any chance to free up memory or use it more efficiently in order to avoid these undesirable situations?

Did polaris get back some memory with Froyo kernel like vogue did? From the video buffer or something... what res do you run at?

I'm running at 240x320 - 120 dpi
I made a screenshot of a "free" command in a terminal (see attachment image).
My kernel is this one (converted with Atools):
http://androidhtc.git.sourceforge.n...=2.6.32/VOGUIMG-320-FROYO-10-4-10.NBH;hb=HEAD
Thanks for your interest!

Im not sure.. but is there a way to use the sd as ram?
I think its not fast enough, but i havent seen any "benchmarks" yet how fast the ram on the polaris works.
Maby its slower but fast enough to work as swap etc?

Enabling compcache will help you.
Still, our little devices cannot multitask very well with Android, but I can navigate and play music at the same time, with compcache.
You will need drivers that match your kernel, in /system/lib/modules. I have packaged some in the first post of this thread that should work for each of the two popular kernel versions.

n2rjt said:
Enabling compcache will help you.
Still, our little devices cannot multitask very well with Android, but I can navigate and play music at the same time, with compcache.
You will need drivers that match your kernel, in /system/lib/modules. I have packaged some in the first post of this thread that should work for each of the two popular kernel versions.
Click to expand...
Click to collapse
Alright, I'm downloading the modules for 2.6.32. After applying the update, what should I do to enable compcache? Some time ago, this setting was in Spare Parts.

SuperJMN said:
Alright, I'm downloading the modules for 2.6.32. After applying the update, what should I do to enable compcache? Some time ago, this setting was in Spare Parts.
Click to expand...
Click to collapse
Open terminal
type: Su
and then
compcache.sh enable

-Arturo- said:
Open terminal
type: Su
and then
compcache.sh enable
Click to expand...
Click to collapse
any way to confirm that it worked?

margosmark said:
any way to confirm that it worked?
Click to expand...
Click to collapse
type FREE in terminal and look under swap if it shows zero then it's not active.

-Arturo- said:
type FREE in terminal and look under swap if it shows zero then it's not active.
Click to expand...
Click to collapse
yea, try doing free from a terminal you should have an amount of memory for the swap row

For testing...
Thank you SuperJMN for this thread : I hope this help us for better use of our phone.
Like you, when I try to use my GPS navigation (Navigon or Igo8) I'm bored that's too slow !! Impossible to change anything if I want...
I try now with Compcache enable, I can see 130024 (total and 104156 used) instead of 104024 : swap = 26000
Cheers.

manu33xtro said:
Thank you SuperJMN for this thread : I hope this help us for better use of our phone.
Like you, when I try to use my GPS navigation (Navigon or Igo8) I'm bored that's too slow !! Impossible to change anything if I want...
I try now with Compcache enable, I can see 130024 (total and 104156 used) instead of 104024 : swap = 26000
Cheers.
Click to expand...
Click to collapse
any better luck with comcache on??

Report
I installed this update for my .32 kernel (dated September, the 30th):
http://forum.xda-developers.com/attachment.php?attachmentid=409422&d=1285714954
My build is the latest: http://sourceforge.net/projects/androidhtc/files/system-froyo-01-10-10_16.tgz/download
When I open a terminal and type
su
compcache.sh enable
it states that compcache will be enable in 120 seconds.
After that time, a free command doesn't reveal any change.
I've also tried typing
su
compcache.sh start
When doing this, it processes the command and after 30 seconds or so, some lines are displayed:
Code:
insmod: can't insert '/system/lib/modules/lzo_compress.ko': File exist
insmod: can't insert '/system/lib/modules/lzo_decompress.ko': File exist
insmod: can't insert '/system/lib/modules/ramzswap_compress.ko': File exist
swapon: /dev/block/ramzswap0: Function not implemented
vm.swappiness = 30
After that, a free command doesn't reveal any change, too.

SuperJMN said:
I installed this update for my .32 kernel (dated September, the 30th):
http://forum.xda-developers.com/attachment.php?attachmentid=409422&d=1285714954
My build is the latest: http://sourceforge.net/projects/androidhtc/files/system-froyo-01-10-10_16.tgz/download
When I open a terminal and type
su
compcache.sh enable
it states that compcache will be enable in 120 seconds.
After that time, a free command doesn't reveal any change.
I've also tried typing
su
compcache.sh start
When doing this, it processes the command and after 30 seconds or so, some lines are displayed:
Code:
insmod: can't insert '/system/lib/modules/lzo_compress.ko': File exist
insmod: can't insert '/system/lib/modules/lzo_decompress.ko': File exist
insmod: can't insert '/system/lib/modules/ramzswap_compress.ko': File exist
swapon: /dev/block/ramzswap0: Function not implemented
vm.swappiness = 30
After that, a free command doesn't reveal any change, too.
Click to expand...
Click to collapse
Try this one
http://dl.dropbox.com/u/7688082/androidupdate.tar
Also is terminal added to the white list in super user app.?

Try with this update...

l1q1d said:
Try with this update...
Click to expand...
Click to collapse
It worked! Thanks!
By the way, the touchscreen behaves erratically with 4-oct NBH. Test with calibration app and tap the screen. You will notice abrupt lines.
Edit: if you want to see which behavior I'm referring to, watch this video: http://www.youtube.com/watch?v=DPLu41BUB1Y
It happened sometime in the past, but with this one it happens the same (although the abruptness is not as much as in this video).
Edit 2: Strangely enough, it is fixed on reboot, but after some time running the touchscreen starts to behave crappy again. It happens with the newest .NBHs made in October.

HOWTO: Set Video Recording FPS high again in lowlight (5.6.890)

Hi everybody,
after beeing so glad that Motorola fixed the blue-tint issue they punished us with 12fps video recording in low light. But mostly I shoot videos in low-light-party conditions. So I searched around a bit (I'm not a developer or anything like that) and found a way for getting back to old settings and fps:
Open /system/etc/TICameraProperties.xml
Search for <prop-framerate-range-default>12000,30000</prop-framerate-range-default>
As you can imagine 12000 is 12fps and 30000 is 30fps. So there are two steps of framerates, depending on light situations.
Change 12000 to whatever you think is good, I changed it to 20000 so I have wonderful 20fps in low-light conditions.
Restart and have fun recording good videos
Please report if it works for you. Also someone more expierenced wants to have a look at the whole file, maybe there are other tweaks that can be applied.
Thanks everyone.

Have you tried filming in low light after doing this? Did you have any issues? I'm going to a concert tonight and wanna take video, but if this will mess up the camera at all (or bring back the blue tint) I'd rather not risk it...

Yes, I tried it with almost 20 Clips, since 3 hours, everything is allright! No blue-tint or anything! It's just better low-light-fps Just try it

I will have to compare the OEM file to the Leak file. I bought 2 droid 3's (with the BOGO deal). Maybe there are some obvious differences that I can post up.
---updated----
these are stock settings I found on the OEM software of the D3.
on line 50:
<prop-framerate-range-default>20000,30000</prop-framerate-range-default>
and on line 137:
<prop-framerate-range-default>24000,30000</prop-framerate-range-default>
<prop-framerate-range-values>(24000,30000)</prop-framerate-range-values>

Izeltokatl said:
I will have to compare the OEM file to the Leak file. I bought 2 droid 3's (with the BOGO deal). Maybe there are some obvious differences that I can post up.
Click to expand...
Click to collapse
I have stock still, and I just pulled the file up to see what the default was for this property on stock. It is 20000, so the OP set it to the original default.

Rotkaeqpchen said:
Hey together,
after beeing so glad that Motorola fixed the blue-tint issue they punished us with 12fps video recording in low light. But mostly I shoot videos in low-light-party conditions. So I searched around a bit (I'm not a developer or anything like that) and found a way for getting back to old settings and fps:
Open /system/etc/TICameraProperties.xml
Search for <prop-framerate-range-default>12000,30000</prop-framerate-range-default>
As you can imagine 12000 is 12fps and 30000 is 30fps. So there are two steps of framerates, depending on light situations.
Change 12000 to whatever you think is good, I changed it to 20000 so I have wonderful 20fps in low-light conditions.
Restart and have fun recording good videos
Please report if it works for you. Also someone more expierenced wants to have a look at the whole file, maybe there are other tweaks that can be applied.
Thanks everyone.
Click to expand...
Click to collapse
AWESOME!!
how would i go about doing this? do i need to root???
If someone would kindly walk me through this i woul be more than apprecitave
edit: hell, ill even paypal you five bucks XD

Those instructions are as easy as it can get. If you have no idea on how to follow it, you should turn away and get someone else to do it for you.
Sent from my DROID3 using Tapatalk

Izeltokatl said:
and on line 137:
<prop-framerate-range-default>24000,30000</prop-framerate-range-default>
<prop-framerate-range-values>(24000,30000)</prop-framerate-range-values>
Click to expand...
Click to collapse
The second values are for the frontfacing camera I guess.
Thanks for the values!
@Moderator: Please move this topic to general! Thanks!

eXecuter.bin said:
Those instructions are as easy as it can get. If you have no idea on how to follow it, you should turn away and get someone else to do it for you.
Sent from my DROID3 using Tapatalk
Click to expand...
Click to collapse
Wow, no need to be a tool. Let me explain myself. I have no idea if i have to be rooted or not, im assuming yes. From there i have no idea how to open /system/etc/TICameraProperties.xml or what program i would use to do so.
Thanks for being a proud upstanding member of this community, always ready to stand up and help another user. your mother would be proud.

`Ghost` said:
Wow, no need to be a tool. Let me explain myself. I have no idea if i have to be rooted or not, im assuming yes. From there i have no idea how to open /system/etc/TICameraProperties.xml or what program i would use to do so.
Thanks for being a proud upstanding member of this community, always ready to stand up and help another user. your mother would be proud.
Click to expand...
Click to collapse
Root Explorer is the de facto standard. If you want a free alternative, give File Expert a try (my issue with this one is it is shady when extracting zip files, Root Explorer is better IMO). Yes you need root because /system has to be mounted as r/w to edit the file.

Additionally: To open a file like a xml file you have to longpress on a file in root explorer and choose "open in text editor".

sic4672 said:
Root Explorer is the de facto standard. If you want a free alternative, give File Expert a try (my issue with this one is it is shady when extracting zip files, Root Explorer is better IMO). Yes you need root because /system has to be mounted as r/w to edit the file.
Click to expand...
Click to collapse
Okay cool. I see it in the market for 3.99. ill support the dev and buy it.
now i have no idea how to mount /system as r/w to edit the file. does rootexplorer help with that or let me input commands?
sorry for the questions as i have not done this before. everyone has to learn somewhere.

`Ghost` said:
Okay cool. I see it in the market for 3.99. ill support the dev and buy it.
now i have no idea how to mount /system as r/w to edit the file. does rootexplorer help with that or let me input commands?
sorry for the questions as i have not done this before. everyone has to learn somewhere.
Click to expand...
Click to collapse
In root expolorer, once you get to the directory in question, there is a R/W link in the top right hand corner, click it and it will make it Read/Write. At that point you can make changes to files within that folder (directory).
I would suggest making a backup of the file. I personally saved a copy on my SD card, mounted it, edited in my text editor on my PC and then copied back. Do this because its easier to edit files on a PC than on the phone, and so I dont mess up any other items. That and I have a permanent backup in case I screw something up.
I made the changes last night but haven't bothered to test yet. will do it tonight.

Izeltokatl said:
In root expolorer, once you get to the directory in question, there is a R/W link in the top right hand corner, click it and it will make it Read/Write. At that point you can make changes to files within that folder (directory).
I would suggest making a backup of the file. I personally saved a copy on my SD card, mounted it, edited in my text editor on my PC and then copied back. Do this because its easier to edit files on a PC than on the phone, and so I dont mess up any other items. That and I have a permanent backup in case I screw something up.
I made the changes last night but haven't bothered to test yet. will do it tonight.
Click to expand...
Click to collapse
when I long pressed and opened it in text editor, it automatically created a .bak of the original. Don't know if everyone will experience this, so like the above says, make a backup.

thanks guys. seems pretty simple. ill give it a shot.
im gonna oneclick root and hop to it!

It worked!!! Thank you!!
thankgod i can actually have non bluetint video/pictures and still keep my 20fps low light.
anyone try increasing the lowlight past 20??
btw my guess on why they decreased it to 12000 is maybe the processor has to work harder with the new white balancing and to even it out they lowered the fps.

Glad to hear that, I was so happy like you are now

Rotkaeqpchen said:
Glad to hear that, I was so happy like you are now
Click to expand...
Click to collapse
Thank you very much.
Someone get this man a beer.

Thanks ^^ but this forum has given me so much stuff and modifications, the real developers deserve the beer! But thanks anyway

Hi Guys,
I've fiddled around with the Camera application and found some other tweaks that some of you might like.
This goes hand in hand with Rotkaeqpchen's low light FPS tweaks above.
I've also modified the Camera apk to increase image quality above 100% which has a bug of fc on the Panorama mode so im trying to work that one out, modded application is attached if you wish to try it called MODDED-Cam-installer.zip, once extracted from zip copy to system\app folder on your phone.
Some more digging around found the following:
build.prop - found in System folder
----------
Increased video bitrate past the default 15mbp to over 30mbp is possible and looks really nice at 1080P, no stuttering with frames and in high quality audio.
Enabled slow and fast motion recording in the camera menu.
mp4(extention),h264,30(fps),30000000(bitrate),aac,128000,44100,2(audio channels)
ro.media.camcorder.1080p=mp4,h264,30,30000000,aac,128000,44100,2
ro.media.camcorder.720p=mp4,h264,30,15000000,aac,128000,44100,2
ro.media.camcorder.d1NTSC=mp4,h264,30,6000000,aac,128000,44100,2
ro.media.camcorder.vga=mp4,h264,30,4000000,aac,128000,44100,2
ro.media.camcorder.cif=mp4,h264,30,1500000,aac,128000,44100,2
ro.media.camcorder.qvga=mp4,h264,15,500000,aac,64000,44100,2
ro.media.camcorder.mms=3gp,h264,15,128000,amrnb,12200,8000,1
ro.media.camcorder.mmsres=qvga
ro.camcorder.zoom=true
ro.media.capture.maxres=8m
ro.media.capture.fast.fps=4
ro.media.capture.slow.fps=120
ro.media.capture.flash=led
ro.media.capture.flashMinV=3300000
ro.media.capture.torchIntensity=40
ro.media.capture.flashIntensity=70
ro.media.panorama.defres=3264x1840
ro.media.panorama.frameres=1280x720
ro.camcorder.videoModes=true <- This will enable fast and slow motion recording.
media_profiles.xml - found in Etc folder
-----------------
Increasing the following Max values will enable higher settings for the above to work:
<VideoEncoderCap name="h264" enabled="true"
minBitRate="64000" maxBitRate="30000000"
minFrameWidth="176" maxFrameWidth="1920"
minFrameHeight="144" maxFrameHeight="1080"
minFrameRate="1" maxFrameRate="120" />
TICameraCameraProperties.xml - found in Etc folder
-------------------------------
Still unknown as to what this file does, first appears to be info only on settings for the front and back cameras, as i've not had much luck in changing values like sharpness/brightness/contrast, file format etc.
Only thing I've been trying out is the low light tweaks, mine are currently set to:
<prop-framerate-range-values>(5000,30000),(10000,30000),(12000,30000),(15000,30000),(25000,30000),(25000,120000)</prop-framerate-range-values>
and
<prop-framerate-range-default>25000,30000</prop-framerate-range-default>
I don't know why all this couldn't have just been in the camera app like every other company, Motorola doesn't like to make anything easy.
Have fun.
Edit:
Easy Clockwork installers attached.
- MODDED-Cam-installer.zip - Modded Build.prop, Modded Media_profiles, Modded TiCamera and modded Camera app installer.
- ORIGINAL-Cam-installer.zip - Modded Build.prop, Modded Media_profiles, Modded TiCamera and original (dedexed) Camera app installer.
- DEFAULTS-Cam-installer.zip - Default Build.prop, Default Media_profiles, Default TiCamera and Default Camera app files installer.
Edit2:
Added 5.7.894 camera mod, increase speed, new icons and high image quality, Panorama mode has a bug.
Added huge APN list for GSM using countries, no more manual adding apn's.
Updated for 5.7.894:
-gps.conf
-media_profiles.xml
-TICameraCameraProperties.xml
-build.prop
Edit3:
DarkDroid rom power menu with reboot and screenshot functionality, camera quality mods etc, do not install this file unless you are running the Dark Droid rom 1.01-01/20/12 with framework 5.6.890, infact just download dpwhitty11's rom instead here:
http://forum.xda-developers.com/showpost.php?p=18424016&postcount=1
Instructions for ORIGINAL-Cam-installer.zip, MODDED-Cam-installer.zip and DEFAULTS-Cam-installer.zip:
1.Place the desired zip on your external sd card.
2.Restart phone into clockwork mod.
3.Choose install from zip.
4.Choose zip from sd card.
5.Go back to main menu and select reboot phone, done.
Manual copying to the desired directory must be done with these 5.7.894 files:
-BlurCamera5.7.894mod.apk
-apns-conf.zip
-gps.conf.zip
-media_profiles.zip
-TICameraCameraProperties.zip
-build.prop.zip
-smc

[ROM][Pre-Pre-ALPHA] Droid A855 ICS Build Attempt

new build: http://www.mediafire.com/file/guo6leourklgzgq/cm-9-20120703-UNOFFICIAL-sholes.zip
gapps: http://www.mediafire.com/?ax46kp0yrl85ynn
___________
Don't flash any other kernels. they won't work.
changes:
hexed defy camera libs
HD profile 854x480 green lines in gallery, plays fine on pc
SD profile 640x480, plays fine via gallery
* camera saving null jpegs fixed
* camcorder working
* enabled TLS register user in kernel and userspace
* enabled 1% battery charge display
* lid switch reporting fixed again (haha)
* updated wifi drivers and firmware
* usb storage and adb work
* probably something i forgot
compiled kernel with gcc4.5, userland with linaro gcc 4.7 and -O3
still broken:
camera flash
gps (it was working before. RDS_SOCKET permission issue??)
speakerphone and bluetooth mic routing
HW decode
native tethering
if you like my works, feel free to buy me a beer

Validating file 'device/motorola/sholes/sholes-keypad.kcm'...
No errors.
made a new kcm file according to googles migrating to ICS docs.
also hacked nf_qtaguid from googles ICS kernel into 2.6.32, it probably won't work right though

progress update
MMS is working. alos noticed that red and blue are swapped.
starting pvrsrv via init.sholes.rc causes graphics to be black.
starting after boot via adb doesn't. weird.

You sir, are my hero, even if it's not fully functional you have made it farther than anyone else, so far only one other person has tried over on droid forums and he gave up so far

sdcard works, adb root doesnt. teh process never respawns probably usb related.

so I booted it up and was confused at first by the lack of touch screen and yellow colors

I'm trying to get teh ts working still, using this changeset as a guide
https://github.com/Evervolv-ICS/and...3e2048019764a298ae9e6b6aad02ff52d75453#diff-1

Any progress in ICS should be appreciated!
Looking forward to ICS for milestone.

new build, touchscreen fixed.
bootanimation is disabled for testing.
keyboard is still weird, alt and B keys aren't working
www.mediafire.com/?k4c4mhb8pq37gjj
also, for a good laugh check settings->apps->running->memory
http://www.mediafire.com/?m3yjdp2e329cknb
boot_EGL_broken.img -<only difference is this starts pvrsrvinit in init.sholes.rc
i tried with and without gralloc.omap3.so in /system/lib
boot.img can be flashed easily like this:
[email protected]:~/android/kernel$ ~/Desktop/sbf_flash -f -r --boot ~/Desktop/build/boot.img --recovery ~/Desktop/recovery-clockwork-2.5.0.1-sholes.img ~/Desktop/MC1_A855_1282081087_Recovery-Only_SPRecovery_0.99.3b.sbf
if installing gingerbread gapps do this through adb:
255|[email protected]:/ # mount -oremount,rw /dev/block/mtdblock4 /system
[email protected]:/ # rm /system/app/SetupWizard.apk

You are a monster, you are making great progress I'm going to half to load your latest build up later
Sent from my CushZero using XDA App

is that also for milestone
thx

So I flashed your newest build and stayed on it for 20 minutes exploring everything now that the touch screen was working.

I installed it on my droid. Very nice progress you have going on here. A lot of things work and of course a lot don't. For people who are too afraid to flash, heres a list of what I noticed is working.
Working:
Phone Calls (Speakers don't work)
SMS
3G works great
touchscreen
sms
downloads from browser (installed facebook.apk but couldn't log in because alt key doesn't work on keyboard)
doesn't work:
screen properly, no blue, the yellow looks kinda cool though
screen orientation, to get portrait view you need to slide out the keyboard otherwise its stuck in landscape mode
no onscreen keyboard, only physical works, except like mentioned alt and b dont for some reason
wifi wont turn on
bluetooth wont turn on
gps, couldn't find on googles homepage but browser still works without it
camera
usb doesnt work, mac won't detect it at least when i plug it in
network doesn't display proper network, T-CDMA 64 instead of Verizon
music app doesn't work, its froyo's music app, i think its because the speaker doesn't work not certain
no vibrate mode? only silent mode and ringer doesnt work
neither speakers work, nor does the microphone i believe
anything else i mightve missed probably doesn't work
overall this is amazing progress and it really doesn't run that bad. give it a shot and play around with it for a few minutes, just don't forget to nandroid!

Ammika13 said:
I installed it on my droid. Very nice progress you have going on here. A lot of things work and of course a lot don't. For people who are too afraid to flash, heres a list of what I noticed is working.
Working:
Phone Calls (Speakers don't work)
SMS
3G works great
touchscreen
sms
downloads from browser (installed facebook.apk but couldn't log in because alt key doesn't work on keyboard)
doesn't work:
screen properly, no blue, the yellow looks kinda cool though
screen orientation, to get portrait view you need to slide out the keyboard otherwise its stuck in landscape mode
no onscreen keyboard, only physical works, except like mentioned alt and b dont for some reason
gps, couldn't find on googles homepage but browser still works without it
camera
usb doesnt work, mac won't detect it at least when i plug it in
network doesn't display proper network, T-CDMA 64 instead of Verizon
music app doesn't work, its froyo's music app, i think its because the speaker doesn't work not certain
no vibrate mode? only silent mode and ringer doesnt work
neither speakers work, nor does the microphone i believe
anything else i mightve missed probably doesn't work
overall this is amazing progress and it really doesn't run that bad. give it a shot and play around with it for a few minutes, just don't forget to nandroid!
Click to expand...
Click to collapse
also no hardware acceleration, screenshot force closes the UI. but it is much smoother than I thought this really proves to all those people saying that ICS wouldn't work at all, someone has it booted, I can't wait to see the progress this guy can make. so far he is doing an extremely good job.

durandgir said:
also no hardware acceleration, screenshot force closes the UI. but it is much smoother than I thought this really proves to all those people saying that ICS wouldn't work at all, someone has it booted, I can't wait to see the progress this guy can make. so far he is doing an extremely good job.
Click to expand...
Click to collapse
whats the button combo for screenshot? i tried volume up+power and volume down + power, neither did anything i just couldnt remember what it is for nexus

I'm pretty sure i'ts power button+down

Some of these problems are simple:
Rotation error is /data/system permission error
Adding this to init.sholes.rc fixes it
Chmod 775 /data/system
Alt and b problems are errors in /system/usr/keychars/sholes-keypad.kcm
The patch I used to fix graphics has a define to ovverride EGL config, this might fiz colors
I've seen several patches for legacy audio support floating around, haven't tried any yet.
Virtual keyboard missing is because sholes device makefile inherits from core.mk instead of one of the more complete ones. A complete build will require a larger system partition or other trickery.
Other things will probably be harder

Some of these problems are simple:
Rotation error is /data/system permission error
Adding this to init.sholes.rc fixes it
Chmod 775 /data/system
Alt and b problems are errors in /system/usr/keychars/sholes-keypad.kcm
The patch I used to fix graphics has a define to ovverride EGL config, this might fiz colors
I've seen several patches for legacy audio support floating around, haven't tried any yet.
Virtual keyboard missing is because sholes device makefile inherits from core.mk instead of one of the more complete ones. A complete build will require a larger system partition or other trickery.
Other things will probably be harder

something else I noticed with signal and data, it stayed gray. but other than a few quirks it's still impressive I don't stay on it because I only have one phone but I can't help but to flash just to mess around with it

I Love You

[Q] Camera file name numbering

The XZ camera names the pictures in the usual manner: DSC_0001.jpg, DSC_0002.jpg, etc. So far so good. But as soon as I move the photos to my computer (and delete them from my phone), the camera starts all over again. 0001, 0002, etc.
Is there any way to stop the camera from starting the numbering all over and instead continue from where it left off? My phone is rooted, so I do have access to my system files.
I know it should be somehow possible, because all my previous Android phones do so. I've owned Samsungs and Motorolas. This is my first Sony.

Hi!
You can follow the following tips:
1) Keep the last shot (with the greatest number) in the phone, don't erase it. The next files will be numbered incrementally starting by the number of the left shot +1. At least Xperia Z is doing it this way.
2) Install an alternative camera software, for example lgCamera or CameraZOOM. They have better choices of file naming, for example you can use timestamps, which never repeat .
With regards, Pavel

Don MC said:
... Is there any way to stop the camera from starting the numbering all over and instead continue from where it left off? ...
Click to expand...
Click to collapse
Same problem here with Z3C. Very annoying and time waster. Interested in a good solution!
Have tried keeping the last file but even Sony's own pre-installed app that moves photos to SD card removes *all* files and effectively stuffs this up completely. How stupid idea can this be Sony?

Guys, this app solved my problem in regards to the filename being reset: https://play.google.com/store/apps/details?id=ro.ciubex.dscautorename

It's as easy as this:
Just put a jpg file into the DCIM/100ANDRO folder (where your photos are stored) and name it with the number before the one you wish to start on. For example, if you want your photos to begin at DSC_0501.JPG, name the file DSC_0500.JPG and the camera will begin counting from there. I tested this on a Sony Xperia Z5 Compact.

Video recording not working after root.

I just finished rooting my girlfriend's G4. Everything went well, but for some reason, video recording does not work on any app. On the stock LG camera, I get "An error occurred" as soon as I press the record button.
Doesn't work on snapchat, or on Google Camera either, but can take pictures just fine on everything.
One thing I noticed is that something called "com.tmobile.pr.adapt" was asking for root permission.
If anyone can help, please do. If not, i'll have to just unroot her phone.

There are not many people complaining about this issue, but I a have come across a few posts asking for help with no responses
From what I can determine the issue revolves around the driver/kernel module providing access to the hardware accelerated video encoder/decoder. This could mean something in a configuration file, or the driver is not getting loaded, maybe even some missing .so files, but I haven't figured anything out yet. I do know that all the apps I have that fail rely on the hardware encoder/decoder (LG Camera, Tivo, Plex). Some apps like Youtube, and MLB At Bat play video without error, I believe these applications to use software decoders for thier video.
I spent some time poking around the file system, and looked at a few files / packages of interest.
build.prop - this file had some flags around video and drm, I checked against a copy online and it appears to have no difference.
com.lge.divx.permission, com.lge.divx, com.lge.drm - could be suspect i poked around their files and did a reinstall of them but there was nothing obvious and the reinstall made no change in behaviour.
LG Video, LG Camera - These applications both failed to be reinstalled from their .apks in /system/priv-app/, when the LG Camera app failed to be reinstalled, the application failed to later run until after a reboot. I was hoping that either of these applications would cause a reconfiguration / re-installation of the drivers.
I viewed the dmesg and logcat output in an attempt to see if there were some system errors when the apps were run, however this yielded nothing useful for me.
I wanted to try running ldd on these applications, to see if all the dynamic libs are found, however since I don't know too much about Andrioid I am not sure where the binaries are stored for say the LG Camera app, so I haven't been able to do that yet.
Luckily im on T-Mobile and can flash a rooted MM, but I will try to get to the bottom of the issue if I can.
I would be happy for any one who can give me tips or suggestions.
One thing I noticed is that something called "com.tmobile.pr.adapt" was asking for root permission.
Click to expand...
Click to collapse
I noticed this too, this appears to be a system for tmobile's techsupport to tell if a mobile has been rooted, I blocked it from root in SuperSU, and froze the app using TitaniumBackup. I suspect this has nothing to do with the problems with video recording or playback.

I wonder if it's people flashing the wrong kernel when they root. It would help to know what method was used to root.

lart2150 said:
I wonder if it's people flashing the wrong kernel when they root. It would help to know what method was used to root.
Click to expand...
Click to collapse
Thanks for the reply.
I followed the video tutorial at http://www.xda-developers.com/how-to-root-the-lg-g4-and-install-twrp-recovery-xda-tv/ to root my phone and pulled the images for the tmobile from http://forum.xda-developers.com/g4/...-tmo-vzw-intl-variants-soon-root-lg-t3164765/
At the time I was running the latest lolipop 5.1
I would have thought if I dd'd the wrong image I would have more problems then just the video issues. Though I did have to do a factory reset since many of my apps (System.UI and Google Play Services) were crashing constantly making the phone unusable. Once the factory reset was done it was good except when i later discovered the video issues.