Hello everyone,
I have tried looking around the XDA forums regarding my issue but my case seems a bit unique and so I haven't really seen any threads that solved my problem.
I have always stuck with AOSP and AOKP roms solely for their customisation capabilities and quick updates. Only gripe I have with these is just the poor battery life, which is why I went back to using a sammy rom.
Specifically, when I use a 4.3 stock sammy rom (i.e. I was using Indie's Omega Rom when this first happened), after I record a video in instagram and try to upload it, the app crashes. I can get to the page just before the caption page and the app crashes. This isn't just specific to the Omega Rom but all 4.3 stock roms I have tried, so I'm thinking that this isn't a rom-specific issue maybe..? But it might be something to do with the camera itself?
I have tried wiping the dalvik cache, fixing permissions, and even formatting my whole phone - both internal and external storages, so I'm not sure what might be the problem. Which is why I hope someone can help me out
I have seen some threads which have said it might be an issue with changing some camera settings but I haven't touched these so that shouldn't be an issue.
On a side note, another issue I've noticed with the 4.3 stock roms is that apps such as LMT don't work even though they are running in the background and I receive toast notifications about them having root access and all. Not sure if this is related, or something else completely.
I thank you for taking the time to read this, and really hope I can get some help regarding this isue.
Regards.
having the same issue here on s3...... on mk6 4.3 rom. has also happened to me across CM11 and cm10.2 and s4 revolution rom.
anyone know what i can try?
Related
I've been experiencing this problem ever since I've had the phone. More often than not, accessing the Gallery will cause the system to freeze and I have to take out the battery to reboot. I applied the OCLF and it seemed to help for a little while, now this phone is back to it's old tricks. Has anyone else experienced this? Is there something I can do to fix it? I'm running stock btw.
I personally have not seen anyone else post that issue. I had an issue before when pics would not show because Media Scanner was not running... the roms I am on lately seem to resolve that though (back then when I had the issue I used an app in the market to scan my media and then the pics would show).
You say stock, do you mean stock JI6... as in you have done nothing to the phone?
Maybe not an option, but why not try a custom rom and see if that fixes the issue... if it does not, unroot and tell Samsung what's wrong and get a replacement.
I usually hate when people mention getting replacements, but you sound like you have a legit problem and not trying to work the system.
digitaltoddy said:
I've been experiencing this problem ever since I've had the phone. More often than not, accessing the Gallery will cause the system to freeze and I have to take out the battery to reboot. I applied the OCLF and it seemed to help for a little while, now this phone is back to it's old tricks. Has anyone else experienced this? Is there something I can do to fix it? I'm running stock btw.
Click to expand...
Click to collapse
yes, this is a common issue on stock 2.1.1 firmware right now, happened to me constantly, when it does this someone told me that when you open gallery, theres a memory leak bug which opens and then phone can't handle so it freezes.
Flash a custom ROM, i use axura 2.1, so far its been the fastest, most stable for me.
idk if this will work but ask for a gallery.apk from different roms where the leak has been fixed, and then try that, or just flash a new rOM.
digitaltoddy said:
I've been experiencing this problem ever since I've had the phone. More often than not, accessing the Gallery will cause the system to freeze and I have to take out the battery to reboot. I applied the OCLF and it seemed to help for a little while, now this phone is back to it's old tricks. Has anyone else experienced this? Is there something I can do to fix it? I'm running stock btw.
Click to expand...
Click to collapse
i had this problem when i just wantes to use stock with root. this is actually common problem with ji6 roms that still use the stock gallery apk.for some reason the stock gallery in ji6 always tends to lock up.there's a fixed version of the apk floating around somewhere.
I had this same problem with JI6, but it went away when I updated to the leaked JK6. This or any recent custom rom should fix the problem for you.
Sent from my SGH-T959 using XDA App
As i said its a memory leak bug, which has been fixed, you should either get a different gallery.apk from newer roms, or get a new rom.
I suggest a newer rom, but its up to you.
If you are running JI6, then this is a common problem for many people.
i had the same problem with my first and second vibrant, i updated to jk6 on number 2 and it went away.
can anyone post the apk to fix this????
Also interested in a the new Gallery .apk.... probably would have to push it using adb? I'm probably just gonna jump right on JL5 tonight.
I'm having an issue with every rom except the stock rom with the phone automatically rebooting itself while doing simple tasks and showing a green screen. I tried enabling force gpu rendering etc but still getting this. Though with any stock roms (default rogers rom + the jb 4.1.2 for att etc) i dont occur this issue. What could be the problem?
Yeah this happens wayyy to often on 4.2.2 roms a little bit less on 4.1.x roms.
arberthebarber said:
I'm having an issue with every rom except the stock rom with the phone automatically rebooting itself while doing simple tasks and showing a green screen. I tried enabling force gpu rendering etc but still getting this. Though with any stock roms (default rogers rom + the jb 4.1.2 for att etc) i dont occur this issue. What could be the problem?
Yeah this happens wayyy to often on 4.2.2 roms a little bit less on 4.1.x roms.
Click to expand...
Click to collapse
This is usual since we do not have the kernel source to make ROMS stable and not reboot. 4.2.2 ROMs are more stable then 4.1.2 so idk what you did there.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Rebooting on 4.2 ROMS
I'm having the same problem as OP with my i717 It happens bad on all of the 4.2 ROM's I've tried, and I know it's not the ROM. So far I've tried: Slim, Supernexus, CM10.1,ReVolt all of which I love! I really want to fix this. I start a game or other app and get a wildly flashing green, blue or sometimes black screen and then she reboots. Usually when opening a game or instagram, but not limited to those apps. It's hard for me to replicate the symptoms. Anyone else struggling with these symptoms on 4.2 roms? It seems less often on 4.1.2 ROM. When I restore a Blackstar ICS setup from twrp the phone runs beautifully. I've used darkside super-wipe hoping that would help. I've also tried changing recovery. Now I'm running out of things to try. I feel like somethings not being cleaned properly before install but I'm new so I don't really know.
Should I try using ODIN to flash a stock jelly bean firmware in order to sort of "start over fresh"?
I wish I could explain to everyone better my problem.
DollarStrawz said:
I'm having the same problem as OP with my i717 It happens bad on all of the 4.2 ROM's I've tried, and I know it's not the ROM. So far I've tried: Slim, Supernexus, CM10.1,ReVolt all of which I love! I really want to fix this. I start a game or other app and get a wildly flashing green, blue or sometimes black screen and then she reboots. Usually when opening a game or instagram, but not limited to those apps. It's hard for me to replicate the symptoms. Anyone else struggling with these symptoms on 4.2 roms? It seems less often on 4.1.2 ROM. When I restore a Blackstar ICS setup from twrp the phone runs beautifully. I've used darkside super-wipe hoping that would help. I've also tried changing recovery. Now I'm running out of things to try. I feel like somethings not being cleaned properly before install but I'm new so I don't really know.
Should I try using ODIN to flash a stock jelly bean firmware in order to sort of "start over fresh"?
I wish I could explain to everyone better my problem.
Click to expand...
Click to collapse
1) AOSP is unofficial so these is going to happen. 2) Is your screen flickering? 3) if so check HW overlays in dev options.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
It happens to PACman ROMs too, try listening to music while attempting to cause the crash.. .There will be a loud beeping sound, followed by the greenish-blue screen, then the device will shut off, and reboot
I got the crash on trying to wake the device to unlock, and grabbed a logcat using Catlog.
When I first tried the Hyperdrive ROM, it was RLS4. I was experiencing touchwiz crashes periodically, so I switched back to Synergy ROM in the hopes that this wouldn't occur once Hyperdrive had been updated. I've recently flashed Hyperdrive RLS5.7 and I'm experiencing the exact same touchwiz crashes. I'm not sure how to fix them, but it's making the ROM all but unusable for me. I really like all of the features, but it's back to Synergy until I can figure this out. Can anyone help me out with these crashes? If I can't get this resolved, does anyone know of any alternative ROMs with similar customization and functionality? Thanks for any and all help.
Djustinf said:
When I first tried the Hyperdrive ROM, it was RLS4. I was experiencing touchwiz crashes periodically, so I switched back to Synergy ROM in the hopes that this wouldn't occur once Hyperdrive had been updated. I've recently flashed Hyperdrive RLS5.7 and I'm experiencing the exact same touchwiz crashes. I'm not sure how to fix them, but it's making the ROM all but unusable for me. I really like all of the features, but it's back to Synergy until I can figure this out. Can anyone help me out with these crashes? If I can't get this resolved, does anyone know of any alternative ROMs with similar customization and functionality? Thanks for any and all help.
Click to expand...
Click to collapse
What exactly is crashing on you and when is it crashing ie what are you doing?
First off, I'd just like to thank you for trying to help as I realize that after all of the work you've already done on this ROM you're in no way obligated to help me out, and I appreciate that.
I'm having Touchwiz crash on me (it becomes unresponsive and then pops up with a message before resetting itself) whenever I try to move an application or remove one from a page. I've considered that this may be a conflict with my previous ROM, Synergy, as it has an extra row of apps on each page. I wipe everything multiple times before flashing, but I use Titanium Backup which may store app layout data. I have nothing to support that guess, its just a theory of mine.
Sorry if this thread already exists.
You have no idea how happy I am this ROM exists!! But I cannot get SMS working. I get FC's on every SMS app I try including Hangouts. Anybody else getting this and/or have a remedy? Thanks
I was about to post the same error here, I have an Amaze with Videotron, S-Off, Super CID, HBOOT-1.93.2222 (JuopunutBear), TWRP as a recovery.
I tried everything, I tried different Gapps, I also tried without installing Gapps, I tried sms apps from the Play Store and Hangouts too. The only thing I haven't tried is formatting my internal SD card. (it was a clean install, all formatted and cache cleared). I also tried switching to ART but I had the same problems.
Everytime I try to just open the sms apps, the app crashes. I managed to see the error once and it was something about SQL but it might be a misinterpretation from my part.
Calls, 4G and WiFi were all working perfectly too.
After some research on Google, I tried installing busybox, xposed framework and uninstalling Voice+, but nothing works. The basic messaging app just closes without any kind of message and other apps show that it stopped working.
(I tried the Evervolv rom 4.4 and SMS were working on that one, maybe it's a setting with my network type as I am on Videotron in Canada and it is using AWS, maybe a setting under *#*#4636*#*# ??)
I want to contribute and sen some log of that error, how can I do that? I am familiar with roms, kernels, etc but not that much with logs... I tried many roms before and never got that specific problem...
Thanks to anyone who can help with this issue!
It's not just you SMS simply doesn't work on this rom and I was surprised to see that no one else pointed this out in the original thread. The default Messaging app closes immediately when you try and open it. Other SMS apps also crash either immediately upon opening them, or when you try to send a message (hangouts & SMS Pro for example). This is the only thing keeping me from using this amazing rom as my DD.
I have the same exact problem with SMS- will try the evervolv 4.4 though was really looking forward to CM11
Edit: also didnt have any other problems with the rom except for the black boxes and the camera
Let's hope there is a way to fix it!
I would post the question in the official thread but I do not have enough posts to do so unfortunately
Heck I couldn't even try SMS due to the black box issue, that's why I didn't mention it in the original thread.
For those with the black box issue--are you using the correct gapps?
In olden days there were some issues with some google things not working, and people uninstalling the ones that came in gapps and downloading them fresh from the play store.
Have you gone into recovery and fixed permissions?
Again, in days of yore, this might straighten some things out.
Is it possible that black-boxing has something to do with CPU frequency, and is it possible to tweak up the speed through developer options and lose the boxes?
I haven't tried this rom yet, as I'm currently sticking with the stable(r) cm10.
Good luck.
anybody get the SMS working on this ROM so far?
pbergonzi said:
For those with the black box issue--are you using the correct gapps?
In olden days there were some issues with some google things not working, and people uninstalling the ones that came in gapps and downloading them fresh from the play store.
Have you gone into recovery and fixed permissions?
Again, in days of yore, this might straighten some things out.
Is it possible that black-boxing has something to do with CPU frequency, and is it possible to tweak up the speed through developer options and lose the boxes?
I haven't tried this rom yet, as I'm currently sticking with the stable(r) cm10.
Good luck.
Click to expand...
Click to collapse
The black box issue has nothing to do with GPU or CPU speeds. There are discussions on the dev threads. The issue affects other legacy devices on various KK based source builds, not just Amaze and CM. The consensus is this seems to be related to the default browser which has changed in KK. This would also explain why it effects other gapps too.
MS92 said:
anybody get the SMS working on this ROM so far?
Click to expand...
Click to collapse
Not that I'm aware of.
Media Issues
The ROM is pretty good for the most part.
I just have this problem where Play Music gives this error, "Cannot play the music track you requested"
I clear my media storage and try to rescan my SD card but none of the apps work. They all crash.
Is there anyway to fix this?
ranwal said:
The ROM is pretty good for the most part.
I just have this problem where Play Music gives this error, "Cannot play the music track you requested"
I clear my media storage and try to rescan my SD card but none of the apps work. They all crash.
Is there anyway to fix this?
Click to expand...
Click to collapse
Maybe app settings for the app and Erase App Data?
can i get a link for the updated adreno drivers? thanks!
865DETH said:
can i get a link for the updated adreno drivers? thanks!
Click to expand...
Click to collapse
Yes you can its on last three pages of orignal thread you also have to sign up for that
Sent from my HTC_Amaze_4G using Tapatalk
as the OP says and i quote that only non working things are
1. camera exposure
2. tethering
but as the thread goes ahead we read more prolems/bugs
May i ask what is the current status for bugs/not working and other issues and what has been fixed and any other stuff we should flash over the ROM like driver, may it be upoaded to the OP for ease as its reall hard to search for those things on mobile app. thank you and good luck.
Anyone else have issue disabling their microphone while in a call? I tried with both the speaker phone and regular handset mode, the "no mic" icon enables but my caller can still hear me. The Hold button seems to work fine though.
FYI, it took a while for the battery to figure itself out. I wiped the battery stats before flashing everything and the first few days I got a lot of jumping battery levels. I let it charge all the way down as much as I could then rebooted and did a full charge and rebooted again and then full charge again. That seemed to reset the battery level to the correct state.
I also , enabled Device/GPS only for the location detection other wise the google services at 50% or more battery.
I'm running the 2014-02-16 build, with the updated video drivers.
Camera is not working
I have also installed this pacman rom 4.4.2. all is well instead of camera.
Any updates for the camera isssue??
Shahxz said:
I have also installed this pacman rom 4.4.2. all is well instead of camera.
Click to expand...
Click to collapse
Since PAC uses the CM device tree for its source any issues with CM will also be evident in PAC. Until the CM devs are able to resolve the camera exposure issue it will exist in both ROMs.
Librastar said:
Any updates for the camera isssue??
Click to expand...
Click to collapse
Think about your question for a minute. Have you seen any recent posts in the CM dev thread indicating an update which solves this issue? If you had just taken a moment to look at the dev thread instead of posting this you would have answered your own question. It's not like the CM-11 thread is incredibly long, it's only 28 pages total. This post is just laziness on your part and an unnecessary waste of bandwidth.
is there any alternate app in the market, i tried couple of apps but nothing useful
@Odysseus1962
If I were to compile AOSP, which variant would you suggest for me to build?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
On any stock ROM I try I can turn the phone on and use it until I turn the screen off. For whatever reason I can never get it to go back on I've tried raising the minimum processor speed and changing the governor. But when I flash aosp the problem disappears entirely. I would really like to know what's going on there's a couple stock based ROMs I would like to try
I had the same issue when I was on stock. So you aren't alone there
optimusv45 said:
I had the same issue when I was on stock. So you aren't alone there
Click to expand...
Click to collapse
did you ever find a fix? I want to try some of those qslide apps. and slightly unrelated but which ROMs have the qslide browser working?
Nope, I just flashed other roms. haven't been on stock in a while, don't know what qslide browser is
Last shot for help fixing this ive included a logcat as well not sure why i didnt do it first. ive lgnpst every bin for this phone there is and ive even tried a couple ls970 roms. the only thing that seems to boot and work correctly is kit kat (which i find horribly boring)
http://pastebin.com/hrh2MA98
I think you may want to post it in a specific stock based rom thread so that the developer of that particular rom can look at it and attempt a fix
it persists across all stock based including lgnpst flashes. I tried the nexus 4 fix just in case but that didn't help. it must be a software problem because every aosp ROM I've tried works flawlessly. its quite frustrating