Develop Bugs

[Q] Noticeably more laggy after several different ROM flashes.

I flashed several different ROMs with ROM Manager to see which one I liked. I noticed that my phone was getting more and more sluggish with each flash. Any idea what could be causing this and how I could fix it?

ohtanya said:
I flashed several different ROMs with ROM Manager to see which one I liked. I noticed that my phone was getting more and more sluggish with each flash. Any idea what could be causing this and how I could fix it?
Click to expand...
Click to collapse
Well it might be that you installed one to many Rom on top of other, some roms require and suggest you wipe data and cache before installing their roms.

[Q] What is wrong with my Gnex?

Hey the Problem is the following:
3-5 random reboots every day
restarts during every phonecall after 1-3 Minutes
freezes when in standby, cant turn back on -> need to take battery out
often slow, especially when switching apps. or when typing
I have tried stock 4.3, CM10.2 recently and before that CM10.1 for a while.
I already send it in but they only said my battery is broken.
Is it possible that all my problems come from this?
I rather think my flash memory is broken? What you think?

JonnyZaggi said:
Hey the Problem is the following:
3-5 random reboots every day
restarts during every phonecall after 1-3 Minutes
freezes when in standby, cant turn back on -> need to take battery out
often slow, especially when switching apps. or when typing
I have tried stock 4.3, CM10.2 recently and before that CM10.1 for a while.
I already send it in but they only said my battery is broken.
Is it possible that all my problems come from this?
I rather think my flash memory is broken? What you think?
Click to expand...
Click to collapse
Since yesterday I am facing the same problems you are describing. At first I thought it was a bad flash or something like that. Clean installed various 4.3 costum roms and it's always the same.
Right now I will look deeper into it since the phone is unusable in that condition.
If I find a solution I will comment.
Best regards
Edit: Okay, works again flawlessly. I simply flashed an nightly from carbon-rom and the lags were gone. Hope it helps. What exactly caused the lag I don't know. For now I am staying on 4.2.2 Carbon as it is my favourite rom anyway and I will wait till there are stable 4.3 from carbon.

Are you sure it's the phone and not an app?

chrisinsocalif said:
Are you sure it's the phone and not an app?
Click to expand...
Click to collapse
Not pretty sure, but it still occured after countless factory resets, wipe cache, wipe dalvic cache and wipe system via TWRP.

Have you tried a clean install without installing apps to see if you get a reboot to eliminate an app as a possible cause?
Sent from my Nexus 7 using Tapatalk 4

chrisinsocalif said:
Have you tried a clean install without installing apps to see if you get a reboot to eliminate an app as a possible cause?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Yes I did. I only flashed for example newest PA and their PA Gapps.
So far I resolved it by "downgrading" to a 4.2.2 nightly from carbon. The lags are completly gone. I will stay and wait till carbon has stable 4.3.

why dont people try stock when they are having problems? going from 1 custom rom to the next does not prove it is the phone.
please fastboot flash the stock rom and do not restore any apps/data other than say your google acct

Zepius said:
why dont people try stock when they are having problems? going from 1 custom rom to the next does not prove it is the phone.
please fastboot flash the stock rom and do not restore any apps/data other than say your google acct
Click to expand...
Click to collapse
Already did that.

I am having the same/similar problems with my GNex too. Specifically bullets [1-3] from the original post. I am running unmodified yakjuux and have tried with just my google account with no other apps and the same problem exists.
Mine makes a noticeable "click" sound with a vibration followed by a reboot.
It usually happens during calls and after it boots the phone call log shows no record of the incoming/outgoing call that just happened. Its like a blue screen of death for android!
I have sent the phone back to Samsung's warranty service 4 separate times and each time they reported no trouble found in the completion report. They just factory reset or put an older version of jelly bean back on the phone and send it back to me with some notes of PRL updates and other nonsense to make it seem like they did something to fix it.
Does anyone have any suggestions (logs, adb, etc) how I can help prove to Samsung/service absolute that the phone is a lemon (other than trying to video tape the phone hoping it reboots - because that is the last resort)?
I already escalated to executive customer service and they refused an exchange because the completion reports show no trouble found :crying:
Thx!

well... I also have this problem.
First happened when I flash Cm10.2 nightly (don't remember which one).
Then I flash PA, or whatever... Looks like the random reboot relating to notifications? It's usually happened when whatsapp notification coming in, but not always.
But a few weeks ago I flashed stock ROM rooted (via TWRP, not fastboot).
The problems solved. No random reboots anymore. Then today I tried latest CM10.2, and it happened again... Wonder why... Looks like it's a very rare problems.
Interesting to see someone having the same problem...
Now I want to flash stock ROM via fastboot to check if it'll fix.
Btw, I can flash directly to CM 10.2 from 10.1, can't I? Or I should flash 4.3 via fastboot first?

lonestrider said:
Btw, I can flash directly to CM 10.2 from 10.1, can't I? Or I should flash 4.3 via fastboot first?
Click to expand...
Click to collapse
I believe CM offers an upgrade option somewhere in the system settings. Unless you want to wipe your phone and flash directly to 10.2 in which case I do not think you need to flash stock 4.3 first. Maybe just do a reset within 10.1 before you flash CM10.2 via whatever recovery (clockwork etc) you are using but even that may be unnecessary.
My 1 year warranty expires this month so if I can't manage to get something out of Samsung I am going to play around with flashing stock 4.3 as you suggested. I have tried converting yakjuux to yakju in the past but still saw the problem then which made me revert back to yakjuux so I could send the phone back for service).

[Q] Reboot issue on 4.3 roms

Here is my problem on 4.3 roms, i have no trouble installing them and the load up perfectly but after i do a restart i cant get past the boot screen. It does it on all 4.3 roms, i have the latest twrp recovery latest modem and stuff everything is up to date only have this problem on 4.3 ive formatted the internal storage numerous times and always followed op instructions. i cant find anyone else with this problem any help is appreciated tia

The only time I had this issue was after I changed font in Rom Toolbox. How are you wiping?
sent from my GS3 running Illusion4.3

joeyhdownsouth said:
The only time I had this issue was after I changed font in Rom Toolbox. How are you wiping?
sent from my GS3 running Illusion4.3
Click to expand...
Click to collapse
im using twrp first i tried to factory reset, caches that didnt work i formated internal storage same problem everything works great untill i restart the phone then wont go past boot screen. like its not reading the internal drive even did fix permisions and wiped caches after install. Also i used the updated su to flash after still problems, beyond me no problems with older ones or tw just the 4.3 roms

I, also, am having this very same issue. I'm honestly surprised that noone else seems to have run across this issue.
Installing is never an issue, running is never a problem, but if I ever reboot, if a ROM reboots itself, I'm left stuck at the GalaxyS4 splash screen, and the only way out it to Wipe everything and reinstall.
I see youre posting from an S3, I am using an AT&T S4.
Clearly, the issue is related to 4.3...

I had that problem with an unofficial build. But that was a bad download. Do you have new phones? The mount points are different on the newer sg3's. There's a thread with a fix for that

i had that problem. for some reason it locks your recovery and internal storage. you have to wipe it and install a rom via odin to work again. thats why im staying away from 4.3

i got my phone last december so its not real new, guess Ill just stay away from 4.3 roms. my recovery never got locked it just wont boot back up after restart. thanks for all the ideas

[Q] Can a ROM kill the camera?

I had a perfectly working Galaxy Nexus running CM10.x, which I updated to a CM11 nightly. This worked great for a week or so and then the camera and gallery started FCing. After several resets, restores, newer/older nightly installs, nothing changed. Tried all possible combinations of new/old Gapps, but still no luck. I tried different ROMs - PA, stock 4.3 and some others, but nope. I even tried Ubuntu Touch and even that couldn't access the camera. This is when I was pretty convinced that the camera module itself must have died.
My questions:
What killed the camera? Is it possible that a bad ROM could have done it?
Is it possible to fix this via software?
I can try and get it repaired locally, but I just want to know if anything can be done at home.
Thanks.

aalaap said:
I had a perfectly working Galaxy Nexus running CM10.x, which I updated to a CM11 nightly. This worked great for a week or so and then the camera and gallery started FCing. After several resets, restores, newer/older nightly installs, nothing changed. Tried all possible combinations of new/old Gapps, but still no luck. I tried different ROMs - PA, stock 4.3 and some others, but nope. I even tried Ubuntu Touch and even that couldn't access the camera. This is when I was pretty convinced that the camera module itself must have died.
My questions:
1) What killed the camera? Is it possible that a bad ROM could have done it?
2) Is it possible to fix this via software? I can try and get it repaired locally, but I just want to know if anything can be done at home.
Thanks.
Click to expand...
Click to collapse
A ROM wouldnt just kill the camera over time. It would have not worked right after the ROM was installed. So I doubt it was a ROM. I would do a full reset. Not just a normal factory reset but flash the factory image and see if it fixes it. If it doesn't then most likely it's a hardware issue.

jsgraphicart said:
A ROM wouldnt just kill the camera over time. It would have not worked right after the ROM was installed. So I doubt it was a ROM. I would do a full reset. Not just a normal factory reset but flash the factory image and see if it fixes it. If it doesn't then most likely it's a hardware issue.
Click to expand...
Click to collapse
I've used the phone for over a year without any issues with several kernels and ROMs before and the camera worked just fine.
Yes, I've done a complete clean up - I wiped the whole phone and memory (using the fastboot -w option) and installed different ROMs and even a different OS (Ubuntu Touch), but the camera issue persists.
I believe it's hardware issue, but I just wanted to know if anyone's faced a similar problem.

aalaap said:
I've used the phone for over a year without any issues with several kernels and ROMs before and the camera worked just fine.
Yes, I've done a complete clean up - I wiped the whole phone and memory (using the fastboot -w option) and installed different ROMs and even a different OS (Ubuntu Touch), but the camera issue persists.
I believe it's hardware issue, but I just wanted to know if anyone's faced a similar problem.
Click to expand...
Click to collapse
So you went through this process?
http://forum.xda-developers.com/galaxy-nexus/general/how-to-return-to-stock-galaxy-nexus-t1626895

jsgraphicart said:
So you went through this process?
http://forum.xda-developers.com/galaxy-nexus/general/how-to-return-to-stock-galaxy-nexus-t1626895
Click to expand...
Click to collapse
Yup. I believe that's the exact post I referred to when I did it.
It even lost root during this process (of course) and I had to do it again - something I hadn't done in almost two years.
Since it was a spare phone, there wasn't any useful data on it. I backed up a few pictures and completely wiped it clean. No luck.
I'll add that the issue is only with the camera. Some apps FC, some apps (such as Camera+) give a message saying it was unable to connect to the camera or something. I believe the Gallery also FCs because it uses the camera at some point. All other apps work perfectly fine.

aalaap said:
Yup. I believe that's the exact post I referred to when I did it.
It even lost root during this process (of course) and I had to do it again - something I hadn't done in almost two years.
Since it was a spare phone, there wasn't any useful data on it. I backed up a few pictures and completely wiped it clean. No luck.
I'll add that the issue is only with the camera. Some apps FC, some apps (such as Camera+) give a message saying it was unable to connect to the camera or something. I believe the Gallery also FCs because it uses the camera at some point. All other apps work perfectly fine.
Click to expand...
Click to collapse
Usually if the phone has any issues at all, that process fixes them. And if it doesn't, then there is usually something wrong with the hardware. I wouldn't think the problem was brought on by installing a ROM or kernel though.

I think it's related to the kernel that you're using

......
i think yes but if you change the rom it will work
some roms the camera has some bugs big bugs colors are broken and stuff

Unable to flash AOSP/AOKP without limited functionality.

The title says it all. Not sure why, but I can use Quantum with no issues. I can install apps, backup and restore without issues. I can install tw ROMs with no issues, install apps, restore apps. No issues.
If I install aosp or AOKP, 9 times out of 10 either I've no phone service, no data, or when it does work, I'm unable to restore my apps from tibu backup, or even install them from the play store. I get an error stating "unable to install to SD card or USB storage" I've never seen that before.
I even went as far as moving all data from my device and my SD card to my PC and wiping both. Then pushing it back, still with the same result. Any input is appreciated.
Thanks everyone!
Forgot to mention TWRP 2.8.0.1, boot loader is NE4 and so is the modem

Are you on a stable/release? Kernels with Linux 3.4.103 are known to be problematic. And there have been many cell radio issues lately due to CM commits.
Not sure about the storage problem. Have you tried task650's AOKP and found similar issues?
Samsung Galaxy S3 (AT&T)
i747UCUFNE4 baseband/bootloader

JJohnson1988 said:
Are you on a stable/release? Kernels with Linux 3.4.103 are known to be problematic. And there have been many cell radio issues lately due to CM commits.
Not sure about the storage problem. Have you tried task650's AOKP and found similar issues?
Samsung Galaxy S3 (AT&T)
i747UCUFNE4 baseband/bootloader
Click to expand...
Click to collapse
I have been through numerous ROMs, gummy, candykat, aokp, but not tasks aokp. I'm no stranger to device flashing and recovering from bad flashes etc.. But this is irritating
Update: flashed tasks aokp let it sit while rebooting, it sat at that boot ani for 15 minutes. Reboot again, same thing. No go.

Try factory resetting. Usually solves boot hangs.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

DocHoliday77 said:
Try factory resetting. Usually solves boot hangs.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I'm going to run my phone through the ringer today. Backup, full on wipes internal storage etc... Then go from there and reflash.