[Q] Jelly Bean camera bug -- swipes to wrong photo - Samsung Galaxy Nexus

Hi, I'm seeing an odd bug in the Jelly Bean camera (running stock jelly bean on a GSM Galaxy Nexus) that I haven't seen reported elsewhere:
When I snap a photo, that photo appears in the little window on the top right of the screen (as it should), but when I then swipe left to see the photo I just took, I instead see photos I took days ago. I have to swipe through a bunch of photos in order to get to the one that I just took. Is anyone else seeing this behavior? And is there a way to fix it so that swiping in the camera actually takes me to the most-recently-taken photograph?
Thanks, Alan

carrot34 said:
Hi, I'm seeing an odd bug in the Jelly Bean camera (running stock jelly bean on a GSM Galaxy Nexus) that I haven't seen reported elsewhere:
When I snap a photo, that photo appears in the little window on the top right of the screen (as it should), but when I then swipe left to see the photo I just took, I instead see photos I took days ago. I have to swipe through a bunch of photos in order to get to the one that I just took. Is anyone else seeing this behavior? And is there a way to fix it so that swiping in the camera actually takes me to the most-recently-taken photograph?
Thanks, Alan
Click to expand...
Click to collapse
Having the same problem here. Im using stock jelly bean. I have been looking for a fix too but no luck yet. Looks like it is not a common problem...

Glad it wasn't just me! I actually switched to another Galaxy Nexus (for unrelated reasons), and this isn't an issue. So it must have been something odd about the way something was set up on your phone and my old one. Though I think I've got things set up the same way on this new phone as that one, so I'm not sure what the difference might be.

fernandoarafat said:
Having the same problem here. Im using stock jelly bean. I have been looking for a fix too but no luck yet. Looks like it is not a common problem...
Click to expand...
Click to collapse
It might be a date issue on your phones, are they set to correct date/time ? It might be as simple as the date on the photos you are taking is older then the ones already there.

No, it's not a date issue -- the date was set right on the phone and was showing up right on the pictures. For some reason, the phone would just think that the last picture taken was in fact one taken days earlier.

This Is A Known Issue
carrot34 said:
No, it's not a date issue -- the date was set right on the phone and was showing up right on the pictures. For some reason, the phone would just think that the last picture taken was in fact one taken days earlier.
Click to expand...
Click to collapse
This is symtomatic of this bug, which Google are already aware of. I would love to post the actual link here, but the stupid restrictions that this forum places on me forbids me prom posting external links and helping people.... go figure... Thanks XDA team...
You can try Googling "jelly bean gallery pictures wrong date order" and you can navigate to the actual Google bug report describing this problem.
As the photos are not always displaying in the actual order they were taken, you see the bug described above.
There is a workaround, namely turning off GPS data for your photos. Once again, I would love to help you further and post the URL for the relevant info, but this stupid web site won't let me until I have posted at least 10 responses... DUMB!!!
The above Google search should also steer you in the direction of rootzwiki dot com, where you can search for "jelly bean nexus pics out of order date taken" and you should hit gold.
I am running a ROM based on the current JRO03L build, so it isn't fixed yet. Hopefully soon...
Martin.

Thanks, Martin! Indeed, the thread is here:
http://code.google.com/p/android/is...D Type Status Owner Summary Stars#makechanges

Related

[DEV][CDMA/GSM] Group Effort to Optimize Existing HoneyComb Ports

Full credit goes to Ssserpentine, SpaceMoose, and OldMacnut for their work on their united efforts to port Honeycomb to our tablets! It seems they are no longer working on it so I decided to create this thread and see what we all could to do together to improve what they have given us!
The point of this thread is to find ways to gather anyone with knowledge on developing, even if its just the "lowly 7-Zippers" like me, to see how we can remove minor bugs and small issues from the ROM. I know Oldmacnut was going to pick it up, but he has a lot on his plate right now and he has been in pain and is more interested in finishing the CM7 Port instead. I respect his decision, but so many people want honeycomb working on our tabs. So I am turning to the dev community here to see if we can group together and fix things in this rom together. If we cant solve the major bugs, lets address all the little things, cuz the little things add up.
Spacemoose made a list of suggestions from users earlier on how to solve minor issues, and little workarounds, but I would like to see if there is a way to roll up those fixes into one full updated ROM flashable through a zip/odin/heimdall file, and see if we can come up with more. You can see this post here, but I have added them to the second post as well in a more organized form.
Some Useful Links as Well:
SpaceMoose's Github
6-19-11 Apps Confirmed Working on [CDMA] / [GSM] Honeycomb Alpha 2.5
Currently Known Bugs:
CDMA
A) Red Border Around Screen at Random Times
B) Constant Gallery Force Close
C) Stock Launcher hangs for many seconds at a time randomly
D) SD Card Does Not Mount
E) Youtube app does not work
F) Orientation Sensor is not functional
G) Honeycomb thinks Device Keyboard is enabled by default
H) When pressing Quick Settings, an image that is semi transparent that is supposed to cover the entire screen isnt scaled properly
I) HQ Youtube does not work (LQ does on the mobile site)
J) Quick Settings Shortcut on Bottom Right Side (Wi-Fi Toggle, Brightness Slider, etc) appears for a second but disappears afterwards.
K) Flash Player is not Fully Functional
GSM - Please Submit or confirm if the above bugs are the same and/or you have different ones!
Red - Signifies an issue that is unaddressed or has not been solved yet.
Orange - Signifies a Temporary Fix or Workaround is mentioned in the post I linked to.
Blue - Will signify a temporary fix or a work around that we have been able to include in a flashable file
Green - Will signify a bug that has been completely fixed in a flashable file.
------------------------------------------
Lets put our minds together and see what we can do guys! Btw this was inspired by Rodderik's thread [SPRINT][CDMA]Galaxy Tab (SPH-P100) Mega Development Starter Thread (CWM, EF17 TAR), so if youre interested in this, you might like his thread too!
Current Workarounds/Temporary Fixes:
Letters correspond to the bugs listed in the OP.
A)
Ssserpentine:
1) Open up Dev Tools
2) Go to Development Settings
3) StrictMode Visual Indicator - turn it off
4) back out of app and now open it again.
5) If this doesn't get rid of MOST of the red borders, REBOOT and open app again.
Click to expand...
Click to collapse
B)
anfalas:
"Get Gallery3D to play nice by going into settings, applications then 'Clear Data' - works great, can change wallpaper etc. Only downside is it has to be done each reboot....."
Click to expand...
Click to collapse
C)
Ssserpentine:
“WANT IMPROVED UI, LESS RED BORDERS, LESS FC'S AND SCROLLING AND SOFT KEYS THAT PLAY NICER? Try adw launcher. for some reason just having it installed helps just as much as using it.”
Click to expand...
Click to collapse
D)
mattman83:
"to mount UMS if you have no external SD then use the below line. Same changes as above... echo /dev/block/mmcblk0p1 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file"
Click to expand...
Click to collapse
or
corodius:
"if you have an external sd, by extending the commands to: su mount -t vfat /dev/block/mmcblk0p1 /mnt/sdcard/ mount -t vfat /dev/block/mmcblk1p1 /mnt/sdcard/external_sd/ This will mount the cards the way they are originally mounted in the samsung/overcome roms."
Click to expand...
Click to collapse
E)
Use m.youtube.com to play LQ videos
Click to expand...
Click to collapse
F)
ztag100:
"If you download barcontrol from the market, you can set it so that a notification links to the rotation app, thus when the notification is clicked it will change the orientation."
Click to expand...
Click to collapse
G)
"one way to load keyboards On the language/keyboard settings page, turn physical keyboard to "no" or "off" or something like that. Now when on a text field, you should see a small keyboard tray in bottom right corner.."
Click to expand...
Click to collapse
H) ---
I) ---
J) ---
K) ---
----------------------------
Submit a New Bug or Fix:
Please submit bugs using the color coded system I explained in the OP. If you are submitting information on solving a bug please address the bug by the corresponding letter so that we can stay organized and know what youre talking about. If you have a new bug please check the OP to make sure I havent listed it, then post it on here and dont worry about the letter, I will alphabetize them. Of course I will credit you in the OP for any fixes or workarounds you may find! Good luck to us all!
Reserved as well!
Yes, please
I would really love a Honeycomb ROM for the Galaxy Tab. There are many reasons why I want to put Honeycomb onto the original Galaxy Tab.
Just see the difference for yourself: Blank space, single pane, one-category-at-a-time menus in Gingerbread
VS.
Less blank space, concise, dual pane interfaces in Honeycomb.
Gingerbread apps are just designed for smaller smartphone screens, so they look too big and spaced-out on the 7-inch Galaxy Tab for my taste. I would really love to see some tablet-optimized apps on the Galaxy Tab!
-------------------------
And yes, I respect the developers and appreciate them so much for the time they put into making custom roms a reality for us!
Please make the thread for GSM also.
TheATHEiST said:
Please make the thread for GSM also.
Click to expand...
Click to collapse
Are the bugs the same? Or are there others that I havent mentioned? I will try to make a section for both tabs if theres different bugs in each one.
Why no mention of ssserpentine?
In op or thread tittle?
He worked on the GSM version.
Moose did the major part of the port and the cdma version.
That other person stumbled, or so he claims, on a audio fix. Never saw a release of this apparent audio fix.
Wonder how many donations he got on open thread with no release posted.
Hmm.
Makes ya wonder why that thread is even there.
Dole out the credits properly.
Just know it needed to be said, and go ahead and get mad. Truth hurts.
alot of angry responces coming, maybe, but dare ya to point out a single lie in this post. Even an exaggeration.
Moose did hc for MONTHS and noone offered any valid help, except ssserpentine, why do you think anyone is gonna get off their but now?
Why don't you, punkrock?
Cause I know how utterly hopeless this task is.
Why don't you all just wait for the leak of the next os?
That so much closer than some random Joe, or Joe's on xda getting hc ported at this point .
is the dead horse braised yet?
Still, hope is eternal, I suppose
PunkRock said:
Why no mention of ssserpentine?
In op or thread tittle?
He worked on the GSM version.
Moose did the major part of the port and the cdma version.
That other person stumbled, or so he claims, on a audio fix. Never saw a release of this apparent audio fix.
Wonder how many donations he got on open thread with no release posted.
Hmm.
Makes ya wonder why that thread is even there.
Dole out the credits properly.
Just know it needed to be said, and go ahead and get mad. Truth hurts.
alot of angry responces coming, maybe, but dare ya to point out a single lie in this post. Even an exaggeration.
Moose did hc for MONTHS and noone offered any valid help, except ssserpentine, why do you think anyone is gonna get off their but now?
Why don't you, punkrock?
Cause I know how utterly hopeless this task is.
Why don't you all just wait for the leak of the next os?
That so much closer than some random Joe, or Joe's on xda getting hc ported at this point .
is the dead horse braised yet?
Click to expand...
Click to collapse
Easy man, in my frenzy of trying to organize the thread, I forgot to credit Ssserpentine in the OP, youre right he did contribute a lot, no need to be rash, I will update it right now.
EDIT: btw oldmacnut did make an audio fix, im running his rom right now, I downloaded it when he had it posted before he took it down, and Im sure some of the bugs I mentioned are fixable on the rom level rather than through adb. My goal wasnt to debug the rom completely, it was to incorporate all the existing bug fixes and workarounds into one rom, while possibly solving others. Also the GSM devs are aplenty here, while we barely have any CDMA, Im sure we have enough talent to make it better than what it is. It might not be flawless, but Im sure we can squeeze more functionality out of it.
Its weird,
Honeycomb is more or less froyo based, obviously as we had hc long before gb, so at the time when I started getting into this whole dev thing hc/froyo seemed just different to me.
But after working on the abortion called gingerbread, and working onbthe kernel stuff, froyo to me, is starting to look like a much more viable and dev friendly option.
Alot if the work Dan did in hc was from scratch, or from the sdk, etc. The audio fix I did was from both.
The big issue on getting hc up and going into a usuable rom is source, we really really need that source for hc. Otherwise, its going to be a long drawn out road of trial and error building with alot of these issues never really getting fixed.
Truth is,
No device with our hardware exists with hc, so no drivers that we need.
We need Google to release the hc source.
I liked hc on my tab just like y'all, but.......I know its just a novel weekend fun toy till we get better resources.
Sent from my SCH-I800 using xda premium
oldmacnut said:
Its weird,
Honeycomb is more or less froyo based, obviously as we had hc long before gb, so at the time when I started getting into this whole dev thing hc/froyo seemed just different to me.
But after working on the abortion called gingerbread, and working onbthe kernel stuff, froyo to me, is starting to look like a much more viable and dev friendly option.
Alot if the work Dan did in hc was from scratch, or from the sdk, etc. The audio fix I did was from both.
The big issue on getting hc up and going into a usuable rom is source, we really really need that source for hc. Otherwise, its going to be a long drawn out road of trial and error building with alot of these issues never really getting fixed.
Truth is,
No device with our hardware exists with hc, so no drivers that we need.
We need Google to release the hc source.
I liked hc on my tab just like y'all, but.......I know its just a novel weekend fun toy till we get better resources.
Sent from my SCH-I800 using xda premium
Click to expand...
Click to collapse
Yeah I know, the lack of source sucks along with the fact we dont have drivers. I dont think we'll have everything working anytime soon at all, if ever even, but I think some of the minor annoyances like the disappearing quick settings toggle, sdcard mounting issues, and graphical errors can be solved without that kind of stuff. Me personally, Id just like HQ Video Playback and 3D Graphics working a hundred percent along with orientation, but as you said no drivers so idk how easy that'd be. Still, Im sure we could solve some of these minor issues. I keep browsing over the Nook Color Forums trying to find hints to solving some of these things
GSM Tab here I'll flash the old 2.5 alpha release and confirm these bugs, see what else I can do.
Sent from my GT-P1000 using xda premium
BulletproofIdeal said:
GSM Tab here I'll flash the old 2.5 alpha release and confirm these bugs, see what else I can do.
Sent from my GT-P1000 using xda premium
Click to expand...
Click to collapse
Nice to see something happening here. I love my Tab but would like some advancements in OS to address specific issues. I am very new to the dev side of the Android OS but would like to get involved.
--Mike
What blows my mind is that they have created an almost perfect HC port for the $150.00 walmart sold viewsonic g-tablet by means of the flashback roms so why is it so hard to get HC working on our tabs? And why can't someone just dump the Rom from the gtab10.1 and use that as a starting point?
On a different note, the alpha 2.5 HC Rom for gsm, the sd cards will not mount no matter what, I've tried The terminal and the mount instructions many times all I am able to do is get the tab to recognize my external sd as the internal sd, and if you try to go to settings applications and clear data for the gallery you get a force close as soon as you tap manage applications
Sent From Githrog's Tab
Ok done some immediate testing on my GSM Tab for some of the known issues
A) Red Border Around Screen at Random Times
Confirmed
Solution: is the same as the CDMA
B) Constant Gallery Force Close
Confirmed
Solution: Cannot be fixed through Setting, crashes as soon as you try to Manage Applications
C) Stock Launcher hangs for many seconds at a time randomly
Not really was slow on boot but no major problems
D) SD Card Does Not Mount
Confirmed
Solution: Haven't tested fix yet
E) Youtube app does not work
Confirmed
Solution: Confirmed
F) Orientation Sensor is not functional
Confirmed
Solution: "Rotating Screen" flips screen incorrectly so that capacitive buttons are on the top of the device
G) Honeycomb thinks Device Keyboard is enabled by default
Confirmed
Solution: Must be set on each boot
H) When pressing Quick Settings, an image that is semi transparent that is supposed to cover the entire screen isnt scaled properly
Confirmed
I) HQ Youtube does not work (LQ does on the mobile site)
Confirmed
J) Quick Settings Shortcut on Bottom Right Side (Wi-Fi Toggle, Brightness Slider, etc) appears for a second but disappears afterwards.
The widget that display battery level, time, etc stays active however no settings are located underneath it. While this menu is expanded a press on the bottom bar will cause the settings to briefly appear but then the whole menu will close
K) Flash Player is not Fully Functional
Not tested
"New" GSM bugs
1. Wi-fi settings are not saved on restart
2. Manage Applications and Running Services menu causes force close of settings
3. Small thing but Tab's first start had language set to Spanish (Not sure if it was spanish but it certainly was not English)
And as always 3G does not work (tried APN settings but it wouldn't let me save)
Alright I'm back to MIUI until I can find some more time on my hands
---------- Post added at 02:51 PM ---------- Previous post was at 02:31 PM ----------
Githrog said:
What blows my mind is that they have created an almost perfect HC port for the $150.00 walmart sold viewsonic g-tablet by means of the flashback roms so why is it so hard to get HC working on our tabs? And why can't someone just dump the Rom from the gtab10.1 and use that as a starting point?
Click to expand...
Click to collapse
If it were that simple I'm sure someone would have thought of that To be honest I think the problem is that the Tab is an extremely fractured device; it was really the first Android tablet to directly compete with the iPad, so it was spread as wide as possible. That's great for Samsung who got a pretty large base of customer but sucks for devs because the GSM and CDMA are 2 very different devices not to mention the P-1000N. When I got my Tab last month the first thing I noticed in this forum was the fragmentation between the different versions of Tabs. More profoundly this means that the developers are split apart, usually when one dev makes a break through everyone else can take advantage of it (i.e. the amazing Voodoo Sound/Color hacks) but not here. I feel like everyone is by themselves and I truly feel bad for the developers because they must make their own breakthroughs on top of dealing with complaints from Tab users with other versions that they want this awesome thing on their Tab. As if its no big deal to go and buy a $450 device to develop something as a hobby and then release it for free for people on the internet after already buying nearly the exact same device.
Sadly I think the Tab is a perfect storm working against modifying it in any ground breaking ways. Don't get me wrong I love my Tab and will try to help getting Honeycomb running but I almost feel like it would just be easier to wait for Ice Cream Sandwhich. /rant
Guys, there is no reason to develop honeycomb, it is inposible to make fully functional honeycomb rom, wait a month or less for ICS, read this (quote from android police posted today):
Honeycomb is closed source. Nobody can make a tablet without Google's blessing. The reason given is that Honeycomb was rushed out the door, and the code isn't good enough for an open source release. They're right you know, setting the emulator to anything smaller than a tablet will result in about a million force closes. Honeycomb just isn't as supportive of hardware as Gingerbread was. To save developers the headache of supporting a platform that wasn't ready, Android's openness got shelved.
Luckily this is going to change. The big cheese said so himself on the Official Android Developers blog, "This temporary delay does not represent a change in strategy. We remain firmly committed to providing Android as an open source platform across many device types." Source code is coming back. This will make the modding community's life much easier. Cyanogenmod 8 (I got excited just typing that) and Ice Cream Sandwich will be able to get hacked onto just about anything.
Click to expand...
Click to collapse
CROrION said:
Guys, there is no reason to develop honeycomb, it is inposible to make fully functional honeycomb rom, wait a month or less for ICS, read this (quote from android police posted today):
Click to expand...
Click to collapse
I just wanted an excuse to try out Honeycomb
BulletproofIdeal said:
Ok done some immediate testing on my GSM Tab for some of the known issues
A) Red Border Around Screen at Random Times
Confirmed
Solution: is the same as the CDMA
B) Constant Gallery Force Close
Confirmed
Solution: Cannot be fixed through Setting, crashes as soon as you try to Manage Applications
C) Stock Launcher hangs for many seconds at a time randomly
Not really was slow on boot but no major problems
D) SD Card Does Not Mount
Confirmed
Solution: Haven't tested fix yet
E) Youtube app does not work
Confirmed
Solution: Confirmed
F) Orientation Sensor is not functional
Confirmed
Solution: "Rotating Screen" flips screen incorrectly so that capacitive buttons are on the top of the device
G) Honeycomb thinks Device Keyboard is enabled by default
Confirmed
Solution: Must be set on each boot
H) When pressing Quick Settings, an image that is semi transparent that is supposed to cover the entire screen isnt scaled properly
Confirmed
I) HQ Youtube does not work (LQ does on the mobile site)
Confirmed
J) Quick Settings Shortcut on Bottom Right Side (Wi-Fi Toggle, Brightness Slider, etc) appears for a second but disappears afterwards.
The widget that display battery level, time, etc stays active however no settings are located underneath it. While this menu is expanded a press on the bottom bar will cause the settings to briefly appear but then the whole menu will close
K) Flash Player is not Fully Functional
Not tested
"New" GSM bugs
1. Wi-fi settings are not saved on restart
2. Manage Applications and Running Services menu causes force close of settings
3. Small thing but Tab's first start had language set to Spanish (Not sure if it was spanish but it certainly was not English)
And as always 3G does not work (tried APN settings but it wouldn't let me save)
Alright I'm back to MIUI until I can find some more time on my hands
---------- Post added at 02:51 PM ---------- Previous post was at 02:31 PM ----------
If it were that simple I'm sure someone would have thought of that To be honest I think the problem is that the Tab is an extremely fractured device; it was really the first Android tablet to directly compete with the iPad, so it was spread as wide as possible. That's great for Samsung who got a pretty large base of customer but sucks for devs because the GSM and CDMA are 2 very different devices not to mention the P-1000N. When I got my Tab last month the first thing I noticed in this forum was the fragmentation between the different versions of Tabs. More profoundly this means that the developers are split apart, usually when one dev makes a break through everyone else can take advantage of it (i.e. the amazing Voodoo Sound/Color hacks) but not here. I feel like everyone is by themselves and I truly feel bad for the developers because they must make their own breakthroughs on top of dealing with complaints from Tab users with other versions that they want this awesome thing on their Tab. As if its no big deal to go and buy a $450 device to develop something as a hobby and then release it for free for people on the internet after already buying nearly the exact same device.
Sadly I think the Tab is a perfect storm working against modifying it in any ground breaking ways. Don't get me wrong I love my Tab and will try to help getting Honeycomb running but I almost feel like it would just be easier to wait for Ice Cream Sandwhich. /rant
Click to expand...
Click to collapse
Wow now that is the kinda posts i like seeing on here! I will try to update the OP tonight with this info! Thanks so much! Definitely echo your sentiments about the fractured and fragmented development we have going on here, it really sucks =/
Ive found out that replacing the existing Gallery with Gallery3D should fix the FC that keeps popping up.
I think Ive found a working Youtube App (in LQ).
Ive also found a hint towards solving the sdcard mounting issue. Its not the vold.fstab its something either in the framework or ramdisk within the kernel, according to the Nook Color Forums.
This thread is interesting: http://forum.xda-developers.com/showthread.php?t=1062626 , actually the entire nook color forum is interesting for finding fixes.
Also changing the dalvik_heapsize to a certain value is supposed to increase app compatibility. Before I update the OP with some of these things, I wanna do a little more testing and see what I can come up with.
Sorry to bother for help,
Sorry to bother you guys for help, but I've been trying to install Oldmacnut's updated of Spacemoose's CDMA Honeycomb (2.5.1) for hours now, with no success.
I used Rodderick's awesome stock rom/kernel and got into clockworkmod (using 4.0.1.5 or 3.0.0.0), installed the zip from there, then rebooted the phone, but I would either 1) be stuck at logo for 10+ minutes 2) see the Sprint startup video loop over and over again, or 3) get stuck on a turned on, but black screen.
How did you guys install Honeycomb on your CDMA tab? Am I doing something wrong? Should I use Spacemoose's 2.5 rom instead of Oldmacnut's?
EDIT: NEVER MIND, IT BOOTED INTO HONEYCOMB. I am in a foreign language, haha, I'm guessing Portuguese?
EDIT EDIT: Google Translate detects the language as Catalan. Haha!
iliveinabucket said:
EDIT EDIT: Google Translate detects the language as Catalan. Haha!
Click to expand...
Click to collapse
Hehe that happened to me as well
First Impressions and problems encountered
HOLY SHOOT THIS IS QUITE FAST!
Considering there is no graphics acceleration support, Honeycomb runs much faster than I anticipated. SD card support is fantastic, and so is hearing sound! (I love you OMC) The UI is awetastic and the standard web browser is blazing fast. Scrolling in web pages is faster on Honeycomb than on Gingerbread stock.
The jittery touch screen bug I have is still there, unfortunately. Damn bug drives me crazy sometimes. I'm sure somebody has this problem that many of us have but have not found a fix to: http://forum.xda-developers.com/showthread.php?t=970965
Basically, when I hold down my finger to scroll on white or light-color backgrounds, the screen shakes back and forth in a spastic, noticeable way, especially when I hold it in place. This happens on every single rom I've been on, froyo, GB, CM7, and now Honeycomb. Has anyone found a fix for that yet?
Anyways, I think all the known Honeycomb bugs are true to me too. Youtube force closes on me, GPS doesn't work, auto-orientation doesn't work. Strangely enough, Quick Settings doesn't work for me. Anyone encounter that?

What have you noticed better in 4.0.4!!!

I have not received an update but wanted to see what i have to look forward to!!!
I just hope the reboot issue is fixed...
T-Mobile USA
4.0.2
Use search and find out
Sent from my Galaxy Nexus using xda premium
I did not but couldn't find a comprehensive list, just bits of info in many posts.
http://forum.xda-developers.com/showthread.php?t=1481044
Sent from my Galaxy Nexus using xda premium
Thank you!!!
The guy is trying to stimulate discussion on a hot subject. Stop posting links to 2months old and irrelevant (its not the the same update...). Besides, he didnt ask for a changelog... as far as i know..
Personally, the camera is a huge improvement in many ways, browser query delay is faster (definitely, not placebo). I cant say the device is "snappier" since it was already pretty much instant. Also, i used to have a kind of lag while typing text in browser (such as this post), that is also gone now. I did experience a few app crashes though, but i am certajn that its because the custom rom needs work (B29 aokp).
Edit: also, the android OS battery using is significantly less. Of course sampke is smalll but it went from 25% to 4-5%
MatAuc12 said:
The guy is trying to stimulate discussion on a hot subject. Stop posting links to 2months old and irrelevant (its not the the same update...). Besides, he didnt ask for a changelog... as far as i know..
Personally, the camera is a huge improvement in many ways, browser query delay is faster (definitely, not placebo). I cant say the device is "snappier" since it was already pretty much instant. Also, i used to have a kind of lag while typing text in browser (such as this post), that is also gone now. I did experience a few app crashes though, but i am certajn that its because the custom rom needs work (B29 aokp).
Click to expand...
Click to collapse
Honestly, even though it is a 2 month old thread. I read a few bullets on the OP post and most of those changes are relatively accurate on the OTA update released yesterday.
So I don't see what your point is? Even the points you made about 4.0.4 is listed,
Noticeably Faster
Browser performance noticeably improved
Miscellaneous camera UI changes
Click to expand...
Click to collapse
zephiK said:
Honestly, even though it is a 2 month old thread. I read a few bullets on the OP post and most of those changes are relatively accurate on the OTA update released yesterday.
So I don't see what your point is? Even the points you made about 4.0.4 is listed,
Click to expand...
Click to collapse
my point is relatively clear. It is old and this is a new update, you dont know how accurate it is. Besides, his post was more oriented towards a discussion than "please post change logs!!!!!". If you dont like those kind of discussions, fine, but i think its appropriate instead of being an ass about a new thread.
I find nothing wrong with this thread. Who knows what else Google coulda added to 4.0.4 for GSM over the leaked 4.0.4 for CDMA.
Not only are the phones different which can affect things such as reception and radios, but this is much newer and could have additional improvements. No point attaching GSM stuff to an already quite long CDMA change log thread as no one is going to see it.
-Picture quality is definitely improved; likely related to better operation
-Dialer is slightly bigger (?); layout a little different, e.g. settings button at bottom of dialer
-Haven't noted a difference in rotation,
-Backing out of some apps is faster, Play for instance, hit back-back-back and there is no lag migrating back and out of the app,
-The majority of my other observations are likely placebo (i.e. smoother, etc...)
Did google double the storage? Haha.
Iphone. Helping computer illiteracy get popular since 2007.
MatAuc12 said:
my point is relatively clear. It is old and this is a new update, you dont know how accurate it is. Besides, his post was more oriented towards a discussion than "please post change logs!!!!!". If you dont like those kind of discussions, fine, but i think its appropriate instead of being an ass about a new thread.
Click to expand...
Click to collapse
It actually is very accurate. Yes there are some new changes but not many. A lot of the most obvious changes have been pointed out in OP and we can quickly recognize them as we use 4.0.4.
That thread could of been continued on since OP actually had a lot of the points down. Many of the points that people are posting in this thread have been already made in that thread listing changes from a "leaked" build. The same bootloader from that leak made it into the OTA.
Scrolling seems odd in the browser and Facebook at times. Little slow... anyone else notice it?
Sdobron said:
Scrolling seems odd in the browser and Facebook at times. Little slow... anyone else notice it?
Click to expand...
Click to collapse
After 1 or 2 battery pulls that behavior went away for me.
First off, thought I'd let you know I updated with the CWM method. I was 100% stock but unlocked bootloader. Worked fine took 2min to do. One small quip was after my first reboot, I didn't have cellular network connection. Took 2-3 more reboots and lots of toggling to make it work. Now its working just fine.
Here's what I've observed:
1) Power menu sound toggles are nice (50x better if mute actually meant full system mute)
2) Screen shot sound changed to the same as the camera shutter sound
3) Feels snappy!
4) Color fade and transitions (like in menus) are now smooth instead of jittery.
5) Multitasking button has less lag. Definitely not perfect still though.
6) GTalk icon updated to look like Messaging and Google Voice.
7) When you turn the screen on, it fades in a much more pronounced way (imo).
8) Auto-rotate is fast and smooth, although I never found it particularly sluggish before.
9) Other, likely "placebo", effects of smoothness, etc.
developing...

Camera app - old vs ics new

Hi guys
I originally asked this in the Q&A section a week ago, but I wasn't sure if it belong here in the apps section instead. Since I didn't get any replies, I'm thinking maybe I should have posted it here to begin with. I hope someone in this section might be able to help.
If I'm not supposed to put this in two areas, I apologize. I'm not too forum saavy; just looking for help for my issue.
Thanks a lot guys
--- Original post ---
Hi everyone! This is my first post here so I hope I'm doing this right. I'm not sure if this should be here in Q&A or in the App section but here goes.
I really love my Epic 4G. Up until a couple of weeks ago, I was still running Dk28 with midNIGHT rom 3.1. Then I finally switched over to the wonderful CM9 Beta1. I am loving it so far, but there's one thing that bothers me. The camera.
One of the things I used to use on the camera very frequently was the panorama/wide shot function. I really hate the sweep panorama of the ICS camera because with the crafts I make, it's just horrible and it's always distorted because sweeping and me don't get along. The camera that was on my leaked Froyo had the feature where I would click the first picture, and while moving to the side a green box would guide me and then automatically take the next shot when it lined up, then I'd move again and it would take the next shot. It would then put the images together for me.
I really need that feature back. Is there a way that I can install that camera app back onto my phone in addition to the updated ICS camera? I really like the smoothness and speed of the ICS camera for normal picture taking.
I can pull the camera.apk from my original install, but as I said, I don't want to overwrite the ICS one, which I fear because they have the same name and I don't know if renaming it will make the difference. I want both. If someone could guide me in getting both on my phone, that would be great. I'm sure there must be a way, but I don't know how to do it. I've read a lot on these boards so I figure if anyone knows how to help, the great minds here do!
I hope I've explained this ok. If I'm not clear, please let me know. Thanks much!
p.s. I've tried a number of camera apps from Play. I don't like the wide shot ones where it has a ghost image for you to line it up manually either, so please don't suggest that.
I'd love to see the old TW camera on CM9. The ported TW apps thread a couple posts down mentions this, but i haven't seen anyone post a successfully working version yet.
Hopefully someone who knows what they're doing can figure it out for us. *crosses fingers*
Wishlist? Anyone?
Lol....I was running the peoples rom last week and was wondering the opposite. If there was a way to put the ics camera on that tw rom. That's an awesome rom and has the tw camera (obviously), but maybe just flash that and try it for a while?
On a side note.....Not sure if its just me, or does does the ics camera take much better (normal) pictures, even when zooming in quite a bit? I've been wondering if something was done in ics to better utilize the camera hardware.
Sent from my SPH-D700 using XDA
djjroc007 said:
Lol....I was running the peoples rom last week and was wondering the opposite. If there was a way to put the ics camera on that tw rom. That's an awesome rom and has the tw camera (obviously), but maybe just flash that and try it for a while?
On a side note.....Not sure if its just me, or does does the ics camera take much better (normal) pictures, even when zooming in quite a bit? I've been wondering if something was done in ics to better utilize the camera hardware.
Sent from my SPH-D700 using XDA
Click to expand...
Click to collapse
I find the ICS camera to be really nice for just normal pics. Definitely faster and does seem to be on the clearer side. But I'm really needing that old auto panorama/wide shot feature. (non sweeping motion or ghost line up).

MMS bug - opening thread doesn't bring to the bottom

Hello.
I was wondering if anyone has a fix or an apk for stock messaging with split threads...the ones I've came across have a bug where you open the thread and it brings you some place in the middle of the thread instead of the bottom. It's really annoying. Any ideas? I'm on AOKP.
I think 4.2.2 has that scrolling bug.. I might have seen something about a 'scrolling cache' fix...
Ahhh. Ok. That makes sense cause I extracted a couple apks from different roms and it was the same on all of them. Darn. That's annoying
Yea, i've experienced it a bit with mms. I believe it happened somewhere else too, but i can't quite recall now. And i read the changelogs from 4.2.1 to 4.2.2 and it was noted and supposedly fixed?! Anyway the rom i think i saw that had the fix might have been vanir.
EDIT: Scratch that, it's mmuzzy's rom with scrolling cache disabled. http://forum.xda-developers.com/showthread.php?t=2096538

[Q] Pictures don't show- SEARCHED AND SEARCHED

Hello to all,
Im new to the forums and rooting, so I am still learning, please bear with me.
I have SEARCHED this for days and days, and still have no answer. Please don't flame, if you know where to find the answer please direct me to a link
With that said:
My dad has a SGH- T989 (Tmobile Galaxy S2).
His issues:
1) phone didn't receive calls all the time
2) when factory camera app opens all images were fuzzy or staticy
3) images of static when taken didn't save.... random icon app shows up in gallery
4) If you used Skype - camera was fine
SO I knew it couldn't be the camera itself.... so i decided to root the phone and update firmware/software and see what happens
I used CWM, then Jedi Mind tricks V6
phone seems fixed, camera screen seems fixed (no more fuzzy), but..... when you take a pic the image is a generic icon still. See pic I took with my GS4 attached.
any idea whats going on?
I have read that 4.2.x may have this issue.... should I try a different ROM?
Thanks for any direction
95gsrturbo said:
Hello to all,
Im new to the forums and rooting, so I am still learning, please bear with me.
I have SEARCHED this for days and days, and still have no answer. Please don't flame, if you know where to find the answer please direct me to a link
With that said:
My dad has a SGH- T989 (Tmobile Galaxy S2).
His issues:
1) phone didn't receive calls all the time
2) when factory camera app opens all images were fuzzy or staticy
3) images of static when taken didn't save.... random icon app shows up in gallery
4) If you used Skype - camera was fine
SO I knew it couldn't be the camera itself.... so i decided to root the phone and update firmware/software and see what happens
I used CWM, then Jedi Mind tricks V6
phone seems fixed, camera screen seems fixed (no more fuzzy), but..... when you take a pic the image is a generic icon still. See pic I took with my GS4 attached.
any idea whats going on?
I have read that 4.2.x may have this issue.... should I try a different ROM?
Thanks for any direction
Click to expand...
Click to collapse
Try a ROM that is 4.1.x. I had a similar problem where a lot of my pictures didn't show up, so I switched to a different ROM and it seemed to have worked. I'm on Infamous right now, and it works fine. Or you can try JediJelly, which is similar to JMT, but is updated and works rather well.
lovesxserenity said:
Try a ROM that is 4.1.x. I had a similar problem where a lot of my pictures didn't show up, so I switched to a different ROM and it seemed to have worked. I'm on Infamous right now, and it works fine. Or you can try JediJelly, which is similar to JMT, but is updated and works rather well.
Click to expand...
Click to collapse
By the way, Jedi Mind tricks is android 4.1.2 (jedi Mind trick JB6)
any idea where to download a good one (that you know will work without viruses or crash etc)?
any other suggestions?
still having the same issue
Have you tried a gallery app from play store? Probably same thing....but to see?
Sent from my cell phone telephone using some sort of app...
Thanks
kj2112 said:
Have you tried a gallery app from play store? Probably same thing....but to see?
Sent from my cell phone telephone using some sort of app...
Click to expand...
Click to collapse
No I haven't but ill try that now

Categories

Resources