maemo.org - Talk
Page 22 of 29 « First 122021 22 2324 Last »
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Multimedia (https://talk.maemo.org/forumdisplay.php?f=32)
-   -   camera-ui2 (now a part of CSSU) (updated 09. May) (https://talk.maemo.org/showthread.php?t=70870)

woody14619 2012-01-21 03:50
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
Quote:
Originally Posted by RichardN900 (Post 1153551)
If i have to go too far on OC i'd rather lose 720p recording capablity than my phone.
Wise statement. Realistically, you don't have to overclock much at all to get 720p. I seem to recall several testers of it were running 800Mhz. I personally run 500-900Mhz, but locking is a rather silly concept. Btw: even locking in general still leaves two levels, one of which is 0, or the resting state. But locking at a high rate means one rogue widget could suck your battery and turn your phone into a pocket warmer.

As for overclocking, the simplest way to do so is use the kernel-config command. Look at the documentation page for it for options, set it up the way you want to... test it out, and if it all seems happy, save it as a profile and set that profile to be the default one. You can do all that via command line just using kernel-config. Or, you can load one that's already done for you, like the dsp config.

The only "speed up app" I trust is swapolube, for the simple reason that it has a button marked "default" that restores the kernel's default settings. It also shows you what it's doing, and gives you all the proper internal names so you can look-up what the value tweaks and why you may or may not want to touch it. Any app that lets you reset what it's done in a clear and transparent method is generally good IMHO.

Keep in mind though, any time you install anything, you're taking a risk that it can cause instability. The less you know about it, the more likely it can screw things up. If you don't know what it does, or how it does it, best to stay away from it all together, because you probably don't need it anyway. :p

karam 2012-01-21 05:11
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
this is your opinion guys
but just a small correction

speedpatch doesn't do permanent changes as woody stated
i have no idea why are you saying this
but my best guess is :

when a user have a problem and he has speedpatch or batterypatch installed
you tell him to remove it
then when he does
the problem is not gone
--->it made you think that speedpatch does unreversed changes
but the problem was not caused by speedpatch in the first place

and for batterypatch conflict with HD rec
it has no conflict as i use it and record/watch HD almost every day
becuase it has the same dsp values as dsp profile
correct me if am wrong

and oh
i moved speedpatch/batterypatch to the repo according to users requests and their feedbacks
such as

Quote:
Originally Posted by Garcel (Post 1013163)
I can now confirm it. That multi tasking is much, MUCH better now. I will recommend this in our filipino based forum. Thanks a million Karam. And keep sharing

PS this is the only patch I used. I don't use swappolube.
PS this is the only patch I used. I don't use swappolube. Once again HUGE thanks. :)
or this
Quote:
Originally Posted by Dark_Angel85 (Post 1012472)
well, hopefully it's not placebo but i did try opening many browser windows... launched all my bookmarked sites... about 7-8 of them... with 3 accounts online using the default IM application (this is normally the killer in all thing lagging)... but the multitasking seems to be pretty smooth so far... which is good cause normally after opening 4+ browser windows it'll start to slow down... so we'll see how consistently this happens...

then i'll have MORE BROWSING POWER!! imagine having seamless 8++(right now btw) windows open all the time... what a sight
and would you think i would have left speedpatch/battterypatch in repos if they kill you device ?
the answer is no

so my question is
what is the bloody hell way to proove to you that speedpatch speeds up and batterypatch saves up ?

and please if you want to continue disscution
then do it in the dedicated thread

Estel 2012-01-21 07:35
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
... And this way, another thread is in danger of becoming never-ending, useless /speedpatch discussion.

*unleash voodoo powers to cleanse this topic from evil presence*

marmistrz 2012-01-21 11:28
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
Quote:
Originally Posted by karam (Post 1153566)
i moved speedpatch/batterypatch to the repo according to users requests and their feedbacks
So why don't you make an serious warning in the description?

RichardN900 2012-01-21 16:31
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
Quote:
Originally Posted by woody14619 (Post 1153554)
Wise statement. Realistically, you don't have to overclock much at all to get 720p. I seem to recall several testers of it were running 800Mhz. I personally run 500-900Mhz, but locking is a rather silly concept. Btw: even locking in general still leaves two levels, one of which is 0, or the resting state. But locking at a high rate means one rogue widget could suck your battery and turn your phone into a pocket warmer.
OK, i have now toped it at 850 would this be enough? I think that if it's dynamic i could let it get up to 900.
Why low limit at 500? Any issue with using 250 or 125?

Quote:
Originally Posted by woody14619 (Post 1153554)
Keep in mind though, any time you install anything, you're taking a risk that it can cause instability. The less you know about it, the more likely it can screw things up. If you don't know what it does, or how it does it, best to stay away from it all together, because you probably don't need it anyway. :p
I ussually try to avoid anything that has any serious warning or does not makes me feel sure enough.
As i know my limitations i usually dont go too far on unknow terrain. (when i want to go far i start asking a lot of questions :))


Code:
Now, about my black screen when changing res?
Could that be a sign of underclocked cpu?
Or may i miss any [ step | lib | thing ]?
Never mind this... i found i have preview now... It's ALIVE, It's ALIVE!!!:D:D

tecs 2012-01-22 01:17
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
IIRC freemangordon suggested locking of the CPU while recording in HD for a better performance... if I'm not mistaken. And I personally think it is reasonable as it leaves more cycles for crunching rather than scaling. Yet again, I could be wrong ;)

Estel 2012-01-23 04:14
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
AFAIK, You're wrong. Such suggestion was made looong time ago, and, IIRC, for testing purposes.

Using actual KP and 720p video recording "stuff", it's not needed to lock frequency.

/Estel

woody14619 2012-01-23 22:06
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
Quote:
Originally Posted by RichardN900 (Post 1153691)
OK, i have now toped it at 850 would this be enough? I think that if it's dynamic i could let it get up to 900.
Why low limit at 500? Any issue with using 250 or 125?
850 should be fine. I (and many others) use 500 as the low point for a few reasons. One is the "race to idle" theory, where in if you have short jobs that happen on occasion (a CPU wakeup to check on a file or what not) if that happens at 500Mhz vs slower, it completes faster and thus goes back to sleep sooner, saving power. There's also a tested and proven fact that the power vs cpu use efficiency is maxed out very close to 500Mhz. It's what the chip was designed to work at, and where most of the power-saving comes into play.

Also, FYI: 125 is in many cases unstable. Enough so that Nokia dropped it from their scaled listing, starting at 250 instead.

Quote:
Originally Posted by RichardN900 (Post 1153691)
I ussually try to avoid anything that has any serious warning or does not makes me feel sure enough.
As i know my limitations i usually dont go too far on unknow terrain. (when i want to go far i start asking a lot of questions :))
Same thing I do. Nothing wrong with asking questions when you're not sure what's going on. The three most useful and honest words in English are "I don't know". You should never be afraid to admit that, or to question what you know.

RichardN900 2012-01-23 23:35
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
Thanks to everyone who answered, this is working like a charm on every way.

At the beginning.i left 250 as lower and 850 as max, then i raised it to 900, but it went bananas and rebooted. As my settings weren't saved as default it then remained 500 and 850, a couple of days now and nothing strange nor killing battery so i'm very happy with this.

Thanks a lot to everyone, specially the masterminds behind this awesome project.

Now i'll be roaming around to seek how many other ways could i squeeze my phone. :D

woody14619 2012-01-23 23:54
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
Quote:
Originally Posted by karam (Post 1153566)
speedpatch doesn't do permanent changes as woody stated
i have no idea why are you saying this
The current version does, in fact, do permanent changes. On install it replaces your .profile and .bashrc files, but fails to restore them when uninstalling. (See prerm and postinst for the deb if you don't believe me.) It also sets your kernel config to "default" which on most systems is (250-600), without mentioning it anywhere.

So, since I bothered to grab the latest versions to see what it actually does, lets take a look-see shall we?

All "speedpatch 2.0" seems to do is add a separate cgroup for CLI commands and adds shell-scripts to that cgroup as they run. Nowhere do I see it adding groups for desktop and applications, as stated in it's description. Which means it's not really doing anything but lumping shell scripts and xterms together into a shared cgroup. How does that help speed? Since most apps are not shell scripts, I don't see how that helps anything. Further, it depends on KP without specifying it as a pre-req. Everything I'm seeing would indicate that speedpatch has a better chance of slowing things down by setting the kernel back to default than it does speed things up.

As for Batterypatch 4.0: The current version also sets your config to default kernel config, on install and on uninstall. All it seems to do is set the nice levels on a few apps and loads a kernel config if your close the keyboard and it goes into sleep mode. Namely, it renices modest, browserd, image-viewer to a value of 1 and ignores nice loads. It loads a separate config for when you open it, and when a call is going on. I note that it tries to renice "background apps" via a call into /dev/cgroups, but unless you have speedpatch installed (not a pre-req!) it will find nothing there, as cgroups aren't mounted by default.

The "speed" from battery patch comes from the fact that you're heavily overclocking the system (705-850!) when the system is awake. For calls, you're using a (250-805) config that's closer to stock, but still overclocking. (Are you telling people that your scripts overclock their devices?) And for the sleeping system a (125-600) config that ignores nice loads.

This means when an app in the nice list (modest, browserd, etc) wake the system up to do something, when it's closed, it will run at 125Mhz until done. Weather this is even saving battery or not is questionable, since it's against the "race to finish" idea in multiple ways. Also, it's enabling 125Mhz, which just about everyone including Nokia, Titan, and Lehto believe is unstable.

So what does the combo of these two do? From what I'm seeing, next to nothing, except that it screws with your configuration, enables a kernel speed that Nokia and others avoid because it's unstable, and adds a user cgroup to lump scripts and shells together for sharing resources. Not something I'd care to inflict on anyone.

Quote:
Originally Posted by karam (Post 1153566)
so my question is
what is the bloody hell way to proove to you that speedpatch speeds up and batterypatch saves up ?

and please if you want to continue disscution
then do it in the dedicated thread
You've been asked, on several occasions (even on your dedicated thread) to explain what these patches are doing, and why it's helpful. You've declined to give much information at all, and what information you have given (the package description, for example) is patently false. So maybe that's where you should start in your "proof" of what either package does.

The fact that the entire install is nothing but scripts that tinker with kernel settings in a way you're incorrectly describing doesn't lend any confidence that anything you're saying about this is correct.

Estel 2012-01-24 00:06
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
This latest post, honestly, deserves own thread, for further discussion, that I'm damn sure will happen. Also, it would be nice to bookmark it, for every new person asking "why I should avoid installing (...)patch?". I really got enough of writing it all over and over again.

So, please, please, start another thread with direct copy of this post as 1st post, and just drop a link here ;)

/Estel

ed_boner 2012-01-24 14:10
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
So...is there any way for someone to restore default files after speed and battery patch installed and purged, without reflash?

woody14619 2012-01-24 18:47
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
Turns out the damage is less than it was in previous versions. So yes. There are backups made in your /home/user/ directory when speedpatch "updates" your .bashrc and .profile (and ls -a will find them). As for the kernel settings, running a kernel-config command to default to the right config for yourself will repair that as well.

Repairing the fact that this forces overclocking when people think they're not overclocking though... And this assumes that all cgroup stuff already in the kernel resets every reboot, and isn't stored somewhere (like in gconf).

woody14619 2012-01-24 21:24
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
Quote:
Originally Posted by Estel (Post 1154702)
This latest post, honestly, deserves own thread, for further discussion, that I'm damn sure will happen. Also, it would be nice to bookmark it, for every new person asking "why I should avoid installing (...)patch?". I really got enough of writing it all over and over again.

So, please, please, start another thread with direct copy of this post as 1st post, and just drop a link here ;)

/Estel
As suggested by Karam, I instead reposted the entry to the patch announce thread. To my surprise, he responded, leading to another article where I break down exactly what his scripts are doing.

Of course several of his followers (including his alternate ego Mohammad) quickly chimed in with their "it worked for me!" Without reading anything I said.

Realistically, the only good thing either patch does is pull in KP. That, and the overzealous use of overclocking and enabling SR (dangerously in most cases) makes things faster and/or saves battery, in spite it the shenanigans being done by Karam's scripts. :P

Anyway.. feel free to drop in and read/like/add to the discussion, as it won't be taking any more of this thread over. ;)

(PS: Sorry about the minor highjack of the thread Nicolai! Thanks for all the great work on N900 and the several apps you've made. I use many of them daily.)

don_falcone 2012-01-24 22:11
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
...not to mentioned i still wonder why the dependency on bash. IIRC he stated that if you use bash as your default shell, the cgroups are then set up correctly because the whole desktop experience is started from a login shell.

woody14619 2012-01-24 22:32
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
Quote:
Originally Posted by don_falcone (Post 1155213)
...not to mentioned i still wonder why the dependency on bash.
Another dependency not listed in the install debs? :(

Quote:
Originally Posted by don_falcone (Post 1155213)
IIRC he stated that if you use bash as your default shell, the cgroups are then set up correctly because the whole desktop experience is started from a login shell.
Which may be all fine and dandy... but then desktop and shell and all scripts are in one cgroup. That also assumes cgroups are inherited across a fork/exec, which I'm not sure is always the case.

One more thing to chat about in the other thread. :)

don_falcone 2012-01-24 22:46
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
Quote:
Originally Posted by woody14619 (Post 1155224)
One more thing to chat about in the other thread. :)
...and remember: If you continue to discuss about speedpatch, people think you are though. If people think you are tough, they want to see how tough. When people wanna see how tough, you wake up in a roadside ditch. Don't wake up in a roadside ditch. Get rid of ... ;)

impeham 2012-01-24 22:52
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
What would be the best way to run a script before the camera-ui application loads and run another after it is closed?

I was trying to do that by using dbus (tracking the event of the camera shutter) but with no success - it seems that the only possible event to hook to was:

:1.10 null org.freedesktop.Hal.Device Condition ButtonPressed cover

but this event is also fired during application usage - i think when i press the camera button but not sure...

i would like to run a script that activates the dsp profile and disconnects 3G network, wifi and bluetooth to avoid interference with the video recordings.

nicolai 2012-01-24 23:49
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
@impeham
take a look at /usr/bin/camera-ui-set-priortiy
(should be in freemangordons latest camera-ui, maybe
in the cssu-testing version as well)
it is a shell script by freemangordon which starts with camera-ui
(or when recording starts) and renices some
processes and stops the thumbnailer and tracker daemon.
You could try to include your own commands there.

impeham 2012-01-25 07:25
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
Quote:
Originally Posted by nicolai (Post 1155255)
@impeham
take a look at /usr/bin/camera-ui-set-priortiy
(should be in freemangordons latest camera-ui, maybe
in the cssu-testing version as well)
it is a shell script by freemangordon which starts with camera-ui
(or when recording starts) and renices some
processes and stops the thumbnailer and tracker daemon.
You could try to include your own commands there.
I tried doing so and it works, but not so well since it takes a long time to start/stop the recording...

is there a way to make camera-ui-set-priortiy run when the camera-ui application starts/closes? i prefer the wait time to happen on application launch. this will make a super fast recording start

freemangordon 2012-01-25 07:31
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
Quote:
Originally Posted by impeham (Post 1155336)
I tried doing so and it works, but not so well since it takes a long time to start/stop the recording...

is there a way to make camera-ui-set-priortiy run when the camera-ui application starts/closes? i prefer the wait time to happen on application launch. this will make a super fast recording start
The thing that slows down start of recording is stopping the tracker. And it must be done on every start because tracker could be restarted between two recordings.

impeham 2012-01-25 08:33
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
Quote:
Originally Posted by freemangordon (Post 1155339)
The thing that slows down start of recording is stopping the tracker. And it must be done on every start because tracker could be restarted between two recordings.
Ok - thanks.
Is there a way then to start other things like my script for Wifi,BT,etc. on application launch and call another script on application closure?

freemangordon 2012-01-25 09:59
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
Quote:
Originally Posted by impeham (Post 1155359)
Ok - thanks.
Is there a way then to start other things like my script for Wifi,BT,etc. on application launch and call another script on application closure?
Maybe you can listen to dbus, though you should find by yourself to which service/signals to attach, I simply don't know.

impeham 2012-01-25 10:38
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
Hmm... tried that already but no good...

is there a way to run a script which will start my script, then run the camera-ui application (and wait for it to close) and then run another script?

i tried to do that running camera-ui using standalone.sh but it runs it as a background process which is not good (the second script runs immediately and doesn't wait for the application to close)

i also tried to create a while loop to wait for the camera-ui process to close and when it does - to run the second script but it is not good since the camera-ui process does not close when i quit the application...

Any other ideas will be great...

freemangordon 2012-01-25 14:46
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
Quote:
Originally Posted by impeham (Post 1155405)
Hmm... tried that already but no good...

is there a way to run a script which will start my script, then run the camera-ui application (and wait for it to close) and then run another script?

i tried to do that running camera-ui using standalone.sh but it runs it as a background process which is not good (the second script runs immediately and doesn't wait for the application to close)

i also tried to create a while loop to wait for the camera-ui process to close and when it does - to run the second script but it is not good since the camera-ui process does not close when i quit the application...

Any other ideas will be great...
camera-ui is always running in background, that is by design. So your dbus script should listen when it becomes visible and/or top application. And I think that is OT here.

impeham 2012-01-26 15:36
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
I tried but no such events logged from dbus log.

Why is this OT? i believe it might improve video recording experience for many people since when you are doing that, you don't want to get any phone calls or emails/other notifications to interfere with the recordings.

blackjack4it 2012-02-02 21:41
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
Could it be possible to add the possibility to switch to Front Camera (like in Samsung Galaxy S2) for recording and take pictures? I know that Front Camera has only 640x480px but it could be nice if someone:
1 - add a button to switch from back/front camera
2 - improve the front camera with all the applicable-realtime-improvement functions (like ISO for example) of the back camera

I remember that I could capture images and videos even with a N95 :( why not with a N900?

EDIT: We could take the code needed from "Mirror" application in Extras-Devel, it already shows in realtime from the front camera but there is no possibility to capture images ecc ecc.

Thanks a lot

Estel 2012-02-03 11:12
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
Read first post.

Estel 2012-02-04 12:44
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
Quote:
Originally Posted by nicolai (Post 1147463)
@geohsia @Estel

Can you test this version. I removed the black-level values in
the dng file. This isn't right, but it seems to be responsible for
the bad raw data for lower light images.
Nicolai, any chances on applying this fix for CSSU-testing camera-ui version? It seems, that photos with this tweak are better in every condition.

/Estel

// Edit

Or was it added already, as exiftool reports:
Code:
Black Level    : 0 0 0 0
... for RAW images, shot by camera-ui 10 (latest CSSU-Testing)?

// Edit

Nicolai, I've also tested image from sunny day (yet, it was almost sunset), and it had Black Level: 25 29 12 25.

I've tested how it looks with Black Level: 0 0 0 0, and, obviously, it's much worse. So, enabling 0 black levels for all images may be not-so-good idea.

ArnimS 2012-02-05 19:14
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
Estel: It is a fact of the universe that poking at a box with a stick rarely improves its function. :)

nicolai: thanks for the interesting package. I hope to use it for reference.

Estel 2012-02-05 19:52
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
Quote:
Originally Posted by ArnimS (Post 1160953)
Estel: It is a fact of the universe that poking at a box with a stick rarely improves its function. :)
.
If You scrollback a little into this thread history, you will see, that for many images, poking this box with a stick - in fact - improved it. Nicolai knew that something is wrong here, so he requested sunny day tests.

It's still a mystery, why moderate/low light photos looks amazingly better with black levels set to 0 0 0 0, yet, Your post with "universal wisdom" wasn't helping to solve this.

/Estel

int_ua 2012-02-25 08:34
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
There was an interesting question about keeping last N minutes of video capture:
http://talk.maemo.org/showthread.php?t=82561
But we need help with gstreamer.
I've tried to use queue sink with leaky=upstream and min-threshold-time:
Code:
gst-launch v4l2src device=/dev/video0 ! queue leaky=upstream min-threshold-time=10000000000 ! autovideosink
But don't have enough experience to correctly select any non-raw recording sink combination. And currently it becomes unresponsive even with 10 seconds of threshold, not to say about more time. Maybe encoding video will allow more delay? And, finally, maybe it can be camera-ui2 feature someday? :)

tecs 2012-02-25 11:27
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
Found two bugs in camera-ui2:

Open camera
Open 'General settings' (rectangle icon on the lower left on main screen)
Change 'Show captured image' setting to something else
Click save
Image count (number on the left) now is 0 and 'General settings' icon has become a striked out microphone (mute?)
Take an image/record video -> "Memory full. Unable to save image."

Restoring the original settings for 'Show captured image' does not fix that. Cannot choose internal storage for saving images (drop down is disabled).

Only way to fix the problem was to insert a microSD card and restart camera application, then go to 'General settings' and choose 'Internal Storage'.

Bug is reproducible every time.

Second one:

While 'No' is selected for 'Show captured image' setting camera-ui does not save captured images.

ticktock666 2012-02-25 11:55
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
I can confirm this bug too

I used this solution and it worked for me, and now I can edit the time out option in the camera app :
http://talk.maemo.org/showpost.php?p...39&postcount=2

nicolai 2012-02-25 16:56
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
1 Attachment(s)
Thank you tecs and ticktock666
for your bug reports. I pushed a new commit
to camera-ui gitorious that fixed the
"not enough memory" bug.
Please test this fix (deb file attached).

Quote:
Originally Posted by tecs (Post 1169538)

Second one:

While 'No' is selected for 'Show captured image' setting camera-ui does not save captured images.
Are you sure about this? For me, images are always saved.
Regardless of the show captured image setting.

ticktock666 2012-02-26 12:05
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
I've downloaded the file but I'm unable to install it (usually I just click the file and HAM does the rest) but I'm getting an error message :
incompatible package , can't install (I believe this is a problem in my device rather than the .deb file)

I installed it via terminal using dpkg command and it installed correctly, I can't see the problem anymore, but I think tecs need to report about this since my problem was fixed yesterday using terminal command you mentioned in the other thread

Thanks again for your great work on the camera-ui app, this really improved my experience in taking pictures

tecs 2012-02-26 13:15
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
Real-time test :) -

Changed the setting - memory full shows up
Installed package and rebooted
Opened camera-ui - image number fixed, changing settings does not recreate bug

Bugfix 1 confirmed :)

Taking shot - no image in gallery, reopening gallery after 30s - nothing, reopening after 30s -nothing, ... , and so on.

Every time I reopen the gallery a notification saying "Retrieving information on new media files. Estimated time remaining: xx:xx" shows up where xx:xx is for example 05:xx, goes down, jumps to 06:xx, goes down, jumps to 07:xx, and so on - constantly taking more time.

After about ~10 minutes image shows up...

Bug 2 does not exist, it actually takes a lot of time for image to show up.

Images with 2s preview or more show up immediately.

aakash_scsa_hellyeah 2012-02-26 16:08
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
No one bothered to tell How TO install these .deb files..
whenever I try to open them, I recieve an error sayin "Unable to update, Incompatible application package"
Anyone please help!!

mr_pingu 2012-02-26 17:32
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
sudo gainroot
dpkg -i /path/to/package.deb

don_falcone 2012-02-26 18:23
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
 
Quote:
Originally Posted by aakash_scsa_hellyeah (Post 1169999)
No one bothered to tell How TO install these .deb files..
whenever I try to open them, I recieve an error sayin "Unable to update, Incompatible application package"
Anyone please help!!
If you would have searched for this exact error message string, you would have found at least one post where the solution is exactly what my pre-poster wrote.


All times are GMT. The time now is 23:25.
Page 22 of 29 « First 122021 22 2324 Last »
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8