Related
Hi, I can't seem to find my way around this issue. Every time I try to open any camera app, it doesn't allow me and says it's unable to connect. Is there no sure solution to this yet? I tried flashing new cameras through recovery. Nothing works at all. I have tried flashing fixes from several threads on a clean start, different camera apps, clearing caches, clean wiping, and other things I can't even remember at this point with all the frustration. What's up with this?
TW based ROMs work. AOSP seems to not. I lost the thread explaining how to dial the codes into a TW based ROM, but another problem with this for me is, I am extremely confused as to how to do some of the steps explained in that thread (hence why I closed it, looks like that should be the way out for me though?).
Same problem
CZory91 said:
Hi, I can't seem to find my way around this issue. Every time I try to open any camera app, it doesn't allow me and says it's unable to connect. Is there no sure solution to this yet? I tried flashing new cameras through recovery. Nothing works at all. I have tried flashing fixes from several threads on a clean start, different camera apps, clearing caches, clean wiping, and other things I can't even remember at this point with all the frustration. What's up with this?
TW based ROMs work. AOSP seems to not. I lost the thread explaining how to dial the codes into a TW based ROM, but another problem with this for me is, I am extremely confused as to how to do some of the steps explained in that thread (hence why I closed it, looks like that should be the way out for me though?).
Click to expand...
Click to collapse
I am having the same problem you are. I am running paranoid android and cant get the camera / gallery to work. I hope somebody can help. I had it working on Beans rom build 13 but that is TW. I am going to have to bail on pa if there isn't a fix
bmanderle said:
I am having the same problem you are. I am running paranoid android and cant get the camera / gallery to work. I hope somebody can help. I had it working on Beans rom build 13 but that is TW. I am going to have to bail on pa if there isn't a fix
Click to expand...
Click to collapse
It's an AOSP problem based on the firmware of your camera when getting the phone from what I've seen.
http://forum.xda-developers.com/showthread.php?p=37072484#post37072484
Here's the thread I was talking about, however I'm confused about how to go about zipping and unzipping these files. Or even how to get to them to place the files in to begin with considering internal SD card is the only thing that comes up for USB storage. Unless you're supposed to move them in and out from within android.
Would really like a confirm on whether or not this works for the Verizon version, and whether or not it's a different process/if this even works at all, rather not break it fully
Why is this not more of a widespread issue? it seems so crucial that many are having but nobody seems to be talking about it or wanting to find a definite fix for it?
CZory91 said:
Would really like a confirm on whether or not this works for the Verizon version, and whether or not it's a different process/if this even works at all, rather not break it fully
Why is this not more of a widespread issue? it seems so crucial that many are having but nobody seems to be talking about it or wanting to find a definite fix for it?
Click to expand...
Click to collapse
I had the camera problem on MIUI...
Before flashing, I made a backup of my system with CW
I extracted the SlimISP_ZH.bin from my backup and
copied it to my /data directory and it worked fine.
Link: d-h.st/dwx
(I can't post links yet)
maybe... someone post the fix in this forum and make it sticky... lol
Ughhhhhhhhh. This is getting irritating. Going to revive the thread.
I flashed the new firmware (MD3) for this phone. I had everything good and working with CM10... Guess what, borken camera, same issues...
I can't post links yet, but it's in the android development thread with this title:
★ [Rom][I535VRBMD3][4.1.2] Stock Root Odex/Deodex [05/29/13]★
Except... this time I cannot do the simple copy/paste of the bin files this time, why is that?
At this point I just want my VRBLK3 (I think?) firmware back.. Where can I get it to reverse what I just downloaded, in essence?
Also.. What the heck kind of hurdles am I going to have to go through when CM10.1 is complete?.. I don't think I'll be updating my phone past 10.1 at this rate if this continues, really irritating.
CZory91 said:
Ughhhhhhhhh. This is getting irritating. Going to revive the thread.
I flashed the new firmware (MD3) for this phone. I had everything good and working with CM10... Guess what, borken camera, same issues...
I can't post links yet, but it's in the android development thread with this title:
★ [Rom][I535VRBMD3][4.1.2] Stock Root Odex/Deodex [05/29/13]★
Except... this time I cannot do the simple copy/paste of the bin files this time, why is that?
At this point I just want my VRBLK3 (I think?) firmware back.. Where can I get it to reverse what I just downloaded, in essence?
Also.. What the heck kind of hurdles am I going to have to go through when CM10.1 is complete?.. I don't think I'll be updating my phone past 10.1 at this rate if this continues, really irritating.
Click to expand...
Click to collapse
did you flash this after flashing the rom?
http://forum.xda-developers.com/showthread.php?t=1788313
---------- Post added at 04:47 AM ---------- Previous post was at 04:41 AM ----------
dandydon414 said:
did you flash this after flashing the rom?
http://forum.xda-developers.com/showthread.php?t=1788313
Click to expand...
Click to collapse
my advice, odin back to stock (4.1.2), root and install this rom
http://forum.xda-developers.com/showthread.php?t=1788313
has been great for me, no issues whatsoever
dandydon414 said:
did you flash this after flashing the rom?
http://forum.xda-developers.com/showthread.php?t=1788313
---------- Post added at 04:47 AM ---------- Previous post was at 04:41 AM ----------
my advice, odin back to stock (4.1.2), root and install this rom
http://forum.xda-developers.com/showthread.php?t=1788313
has been great for me, no issues whatsoever
Click to expand...
Click to collapse
Yes, that is the post. I also tried MB1 out of curiosity, no dice on either of them. I had a perfectly working CM10. I dun goofed :\.
That was my next step (rerooting, installing that firmware AIO, and then installing CM10). However my question is this, what happens when more firmware comes out? I have to re root and start over again?
If you flashed md3 just flash back mb1 and you will fix that problem. I had the issue. Pulled the firmware from invisiblek for mb1 and back to normal on liquid smooth
Sent from my GT-P5113 using xda premium
bbqsfire said:
If you flashed md3 just flash back mb1 and you will fix that problem. I had the issue. Pulled the firmware from invisiblek for mb1 and back to normal on liquid smooth
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
for some reason I haven't good luck running cm roms on the s3........have much better luck with tw based rom. that's why I recommend a restock and basically start all over from scratch
dandydon414 said:
for some reason I haven't good luck running cm roms on the s3........have much better luck with tw based rom. that's why I recommend a restock and basically start all over from scratch
Click to expand...
Click to collapse
Yeah I think a clean slate is definitely needed from time to time. I swap roms frequently but liquid gives me the best battery life right now from my tests so I keep going back. I Get scared telling people to odin because so mant people soft brick while screwing up a flash inodin or hard brick because they flash a non Verizon rom
Sent from my GT-P5113 using xda premium
bbqsfire said:
Yeah I think a clean slate is definitely needed from time to time. I swap roms frequently but liquid gives me the best battery life right now from my tests so I keep going back. I Get scared telling people to odin because so mant people soft brick while screwing up a flash inodin or hard brick because they flash a non Verizon rom
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
good point. saw where someone flashed an i9300 s3 rom on the verizon s3 and brick city. my problem with aokp, cm, liquid, carbon, baked bean, I've tried them all, is constant freezing forcing me to pull the battery. I love the features of those roms but I hate having to pull the battery all the time
Hmm, over the past couple days I've tried out a few different ROMs on my girlfriend's S3 here, and on each one I would get this "Could not connect to the camera" error, every single time upon opening the camera app. One of the Paranoid Android ROMs, Liquid Smooth, and Synergy (even the Touchwiz camera was broken on that!).
I can restore to the original backup I made of the stock ROM, and the camera works fine again. But as soon as I try a different ROM, no camera.
I'd love to get an AOSP ROM running on this phone, but having a working camera is a requirement, and I can't figure out what I'm doing wrong. Searching the individual threads for the ROMs yields little help, and I'm getting exactly the same error on different ROMS, so I feel like I'm doing something wrong on a higher level. Any chance that switching from TWRP to CWM would make a difference? I don't see why it would, but I suppose it's something I could try.
bbqsfire said:
If you flashed md3 just flash back mb1 and you will fix that problem. I had the issue. Pulled the firmware from invisiblek for mb1 and back to normal on liquid smooth
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
Yep, I'm saying I tried that, still nothing :\ I'm going to flash MB1 and get the stock files again to see if it will do anything but I doubt it.
CZory91 said:
Yep, I'm saying I tried that, still nothing :\ I'm going to flash MB1 and get the stock files again to see if it will do anything but I doubt it.
Click to expand...
Click to collapse
Have you tried odin back to MB1 or even LK3 and letting it go through the OTA's? Those OTA's also update rpm, and other partitions, that as far as I know don't get updated when we flash these stock files on xda unless we flash them ourselves. Maybe something screwed up and is being persistent since those partitions aren't getting updated along the way?
Watanuki-Kun said:
Have you tried odin back to MB1 or even LK3 and letting it go through the OTA's? Those OTA's also update rpm, and other partitions, that as far as I know don't get updated when we flash these stock files on xda unless we flash them ourselves. Maybe something screwed up and is being persistent since those partitions aren't getting updated along the way?
Click to expand...
Click to collapse
I'm honestly just going to restart from scratch and re root when CM10.1 is fully done (hopefully soon...) Nothing is working. Flashed to MB1 firmware on CM 10. Tan MB1 CleanROM. Camera worked in CleanROM, copy/pasted onto my CM10 after the restore, still nothing... Seriously mind boggling.
CZory91 said:
I'm honestly just going to restart from scratch and re root when CM10.1 is fully done (hopefully soon...) Nothing is working. Flashed to MB1 firmware on CM 10. Tan MB1 CleanROM. Camera worked in CleanROM, copy/pasted onto my CM10 after the restore, still nothing... Seriously mind boggling.
Click to expand...
Click to collapse
Probably best, that would be my first thing to try if I had that problem, restarting from scratch. If all else fails, restarting from scratch will wipe out everything. If that failed, I would probably suspect hardware issue.
Watanuki-Kun said:
Have you tried odin back to MB1...
Click to expand...
Click to collapse
Flashing the MB1 firmware fixed the camera for me on AOSP. I flashed this zip in recovery after the ROM was installed:
http://invisiblek.org/sch-i535/firmware/
Link was obtained from here (FAQ about it):
http://rootzwiki.com/topic/34053-firmware-vrbmd3-modemrpmtzsbl-verizon-sgs3-sch-i535/
dandydon414 said:
good point. saw where someone flashed an i9300 s3 rom on the verizon s3 and brick city. my problem with aokp, cm, liquid, carbon, baked bean, I've tried them all, is constant freezing forcing me to pull the battery. I love the features of those roms but I hate having to pull the battery all the time
Click to expand...
Click to collapse
Well I would recommend liquid 2.5 with the kernel that comes with it and I never change any of the overclocking settings. I don't have to pull the battery at all on this one.
Sent from my SCH-I535 using xda premium
TunedReference said:
Flashing the MB1 firmware fixed the camera for me on AOSP. I flashed this zip in recovery after the ROM was installed:
http://invisiblek.org/sch-i535/firmware/
Link was obtained from here (FAQ about it):
http://rootzwiki.com/topic/34053-firmware-vrbmd3-modemrpmtzsbl-verizon-sgs3-sch-i535/
Click to expand...
Click to collapse
Yep, that's what I tried. Nothing.
Hi!
I flashed pac-rom but it keeps my phone awake 24hrs even when i am sleeping therefore 70% battery consumption when i am sleeping and everyday i have been posting in that thread for help or update but dev has left,and this was a stable version with never ending problems for me.So i want to remove this and see if the other rom also behaves like this or not.
I want to remove this rom and gapps as well but i am a newbie and never did this before.I will be really grateful if someone guide me step by step in this.
Please reply soon coz i am not able to live a normal life as battery is creating problems for me.Thanks a lot in advance
LG P500 rooted,pac-rom,aokp 4.2.2,stock kernel
Read the sticky thread!
Here it is.. http://forum.xda-developers.com/showthread.php?t=1152306
Sent from my LG-P500 using xda premium
I know that dear
kunnaliskinng said:
Read the sticky thread!
Here it is.. http://forum.xda-developers.com/showthread.php?t=1152306
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
As i said i am newbie things are not clear to me and what i asked in the question is not mentioned clearly and exactly.And since 7 days i am stuck in this esp last three days coz either the rom is a problem or need to be reflashed.And how to remove gapps etc that is not clear dear.Anyone who has a helping nature would write few lines or steps if he wants to help.My head is screwed up with this rom,nothing is working properly and all the time i am busy with my phone.Can't even open my eyes now as i have been continously looking at small screen.
Do not know if i have to reset the phone again or what,how to remove gapps as i do not have google store,gmail and maps in that. I always try to help a newbie coz i know he will not understand things clearly and can screw up,and in my case an experience person can tell if it is some thing else i should do along with that i.e if he would be concerned.
You are the king man so you would not know these small petty things.
Anyway thanks for whatever best you could do.
@kitu34: The procedure for flashing a new ROM is always the same:
1. Download the ROM, put it on your SD card (I recommend creating a folder in your SD card for your ROMs, kernels, etc., so that they're all in one place, but that's just a suggestion, not a requirement. Optional: Download the recommended GAPPS package for the ROM (if the ROM comes with built-in GAPPS, no need to download this).
2. Boot into recovery. You should be able to reboot into recovery simply by pressing power button > reboot > recovery. If not, then shutdown the phone and press & hold power+volume down+home.
3. In recovery, perform a factory reset (wipe data & cache), wipe dalvik-cache, and wipe system.
4. In recovery, flash the zip of the ROM you want to install (the procedure for this depends on your custom recovery; just browse around the menus for the option to flash a zip). If the ROM has a separate GAPPS package, you can also flash it here. Note: Always flash the GAPPS after you flash the ROM, not before.
5. Reboot system.
Flashing a custom kernel uses the same procedure, except you only wipe cache & dalvik-cache in step 3.
____________________
Sent from the moon.
____________________Sent from the moon.[/QUOTE]
Thanks.Ok it is exactly the same.And what if i just have to update the rom,in case i need?
(Two times thanks due to moon from a man just living on earth hhehehe)
Flashing a custom kernel uses the same procedure, except you only wipe cache & dalvik-cache in step 3.
____________________
Sent from the moon.[/QUOTE]
Just confused whether to reflash pac rom or flash either rashed's 10.1 or Jenkin's.Maybe first flashing went wrong coz i am having lots of problems and the phone is awake 24hrs.I want a good rom but battery friendly
kitu34 said:
Thanks.Ok it is exactly the same.And what if i just have to update the rom,in case i need?
(Two times thanks due to moon from a man just living on earth hhehehe)
Click to expand...
Click to collapse
Update the ROM? Do you mean flashing a newer version of the same ROM? Some ROMs can be updated by simply wiping cache, dalvik, & system (no need to wipe data), then flashing the new version. Personally, I advise doing a clean install every time when installing a new ROM, even if it's just an update. That means a full wipe: data, cache, dalvik-cache, & system. A clean install helps you avoid potential errors.
____________________
Sent from the moon.
Syd_M said:
Update the ROM? Do you mean flashing a newer version of the same ROM? Some ROMs can be updated by simply wiping cache, dalvik, & system (no need to wipe data), then flashing the new version. Personally, I advise doing a clean install every time when installing a new ROM, even if it's just an update. That means a full wipe: data, cache, dalvik-cache, & system. A clean install helps you avoid potential errors.
____________________
Sent from the moon.
Click to expand...
Click to collapse
Thanks a lot, but any advise on those three roms? and i need a stable one
kitu34 said:
Thanks a lot, but any advise on those three roms? and i need a stable one
Click to expand...
Click to collapse
If you want good battery life, then I suggest staying away from Jelly Bean ROMs for now -- the battery drain is huge. If you want to try a stable JB ROM, then the latest Jenkins build is good, as long as you don't mind battery drain and a couple of relatively major bugs (those being bluetooth A2DP not working and wifi hotspot reboot).
If you want a relatively more stable, but still high-end, ROM, then stick with ICS. Hephappy's CM9 is good (check the thread in the General LG-P500 forum), or if you want a tweaked & modded ICS, then get neko95's ICySNAP.
That said, the king of battery life still is Gingerbread. I'm personally using the latest unofficial CM7.2 build by FitAmp; it's stable and with good battery life, better than ICS or JB.
____________________
Sent from the moon.
Syd_M said:
If you want good battery life, then I suggest staying away from Jelly Bean ROMs for now -- the battery drain is huge. If you want to try a stable JB ROM, then the latest Jenkins build is good, as long as you don't mind battery drain and a couple of relatively major bugs (those being bluetooth A2DP not working and wifi hotspot reboot).
If you want a relatively more stable, but still high-end, ROM, then stick with ICS. Hephappy's CM9 is good (check the thread in the General LG-P500 forum), or if you want a tweaked & modded ICS, then get neko95's ICySNAP.
That said, the king of battery life still is Gingerbread. I'm personally using the latest unofficial CM7.2 build by FitAmp; it's stable and with good battery life, better than ICS or JB.
____________________
Sent from the moon.
Click to expand...
Click to collapse
ok then for now i will try jenkin's coz that was the first rom i downloaded on my pc but did not flash.actually i have serious battery and other issues that is why i am just getting rid of this now and then read about the roms you mentioned.after fashing i will tell you how it goes and if that also has a battery issue then the next...so kind of you to help as there are very few people here who really want to help.(the other day grgtm from cebu really helped me when my phone went in fastboot,cebu guys are damn good hehe)thanks a lot
4. In recovery, flash the zip of the ROM you want to install (the procedure for this depends on your custom recovery; just browse around the menus for the option to flash a zip). If the ROM has a separate GAPPS package, you can also flash it here. Note: Always flash the GAPPS after you flash the ROM, not before.
I am doing with jenkins as i already have but it does not have gapps as i am not flashing the very last update which has gapps with it.\So is it ok to use rashed's cm10's mini gapps?
kitu34 said:
I am doing with jenkins as i already have but it does not have gapps as i am not flashing the very last update which has gapps with it.\So is it ok to use rashed's cm10's mini gapps?
Click to expand...
Click to collapse
Yes, Rashed's mini gapps is for all cm10.x roms, including the Jenkins builds.
Edit: By the way, grgtm is from Romania, not Cebu (Philippines). You probably got him mixed up with someone else.
____________________
Sent from the moon.
Syd_M said:
Yes, Rashed's mini gapps is for all cm10.x roms, including the Jenkins builds.
Edit: By the way, grgtm is from Romania, not Cebu (Philippines). You probably got him mixed up with someone else.
____________________
Sent from the moon.
Click to expand...
Click to collapse
Hahaha you are right it was you who is from cebu and i was asking him if it is night time in phillipines then he told me he is from Romania.My mistake.
Ok listen i did that and just wanted to check but the home button is not responding,any ideas? Thanks
BUT WHEN SCREEN IS OFF I CAN WAKE UP WITH THE HOME BUTTON AND I DOWNLOADED WHATSAPP BUT THE USUAL NOTIFICATION IN THE NOTIFICATION BAR DID NOT COME.I think have to reflash again
kitu34 said:
Hahaha you are right it was you who is from cebu and i was asking him if it is night time in phillipines then he told me he is from Romania.My mistake.
Ok listen i did that and just wanted to check but the home button is not responding,any ideas? Thanks
BUT WHEN SCREEN IS OFF I CAN WAKE UP WITH THE HOME BUTTON AND I DOWNLOADED WHATSAPP BUT THE USUAL NOTIFICATION IN THE NOTIFICATION BAR DID NOT COME.I think have to reflash again
Click to expand...
Click to collapse
The home button not working is a result of a GAPPS error when the system partition is too full. You'll need to trim the ROM prior to flashing (search the cm10 thread; it's too complicated for me to explain here) or download the version of cm10.1 with built-in GAPPS. The fact of the matter is, our phones has a very small system partition, hence why we have to go to all this trouble when using JB.
____________________
Sent from the moon.
Syd_M said:
The home button not working is a result of a GAPPS error when the system partition is too full. You'll need to trim the ROM prior to flashing (search the cm10 thread; it's too complicated for me to explain here) or download the version of cm10.1 with built-in GAPPS. The fact of the matter is, our phones has a very small system partition, hence why we have to go to all this trouble when using JB.
____________________
Sent from the moon.
Click to expand...
Click to collapse
Thanks,but first i am trying to reflash coz in the first time i wiped even cache partition and now i will try without that coz i did not yet get an answer to how to trim
You're seriously going to need to learn how to help yourself, @kitu34. Instead of asking for step-by-step instructions all the time, try looking for them yourself; simply using the "search this thread" function and running a search for "trim" in Rashed's thread would give you what you need. In fact, here's the link to the program used to trim ROMs: http://forum.xda-developers.com/showpost.php?p=33349661 -- that link was in the first post of Rashed's thread, labeled (and in very big letters) CLICK ME. The instructions for using the program is also in the thread, and the program's interface is so simple that simply browsing around should tell you what to do.
____________________
Sent from the moon.
Syd_M said:
You're seriously going to need to learn how to help yourself, @kitu34. Instead of asking for step-by-step instructions all the time, try looking for them yourself; simply using the "search this thread" function and running a search for "trim" in Rashed's thread would give you what you need. In fact, here's the link to the program used to trim ROMs: http://forum.xda-developers.com/showpost.php?p=33349661 -- that link was in the first post of Rashed's thread, labeled (and in very big letters) CLICK ME. The instructions for using the program is also in the thread, and the program's interface is so simple that simply browsing around should tell you what to do.
____________________
Sent from the moon.
Click to expand...
Click to collapse
Thanks,i did search the thread by the relevant keywords but was not clear that i simply have to remove apps after flashing or before or what and the link you gave did not strike me would be for trimming.Now i know as someone told me to use titanium but the link i have not read fully but it is helpfull and will read now.Thanks again
Just for your info
kitu34 said:
Thanks,i did search the thread by the relevant keywords but was not clear that i simply have to remove apps after flashing or before or what and the link you gave did not strike me would be for trimming.Now i know as someone told me to use titanium but the link i have not read fully but it is helpfull and will read now.Thanks again
Click to expand...
Click to collapse
That link to the website is closed,i mean the website is closed.Bye
I tried Jenkins with rashed's mini gapps and worked perfectly(except battery drain), instead using an tool for rom editing, use an app like root uninstaller to get read of unnecessary apps to free some space on internal memory or use an d2ext script(but it got some strange behavior from my phone, you need a really fast sd card, an class 10 for that, and a reliable brand, mine is class 4, so in the final, sd card will worth half price of the phone)
grigtm said:
I tried Jenkins with rashed's mini gapps and worked perfectly(except battery drain), instead using an tool for rom editing, use an app like root uninstaller to get read of unnecessary apps to free some space on internal memory or use an d2ext script(but it got some strange behavior from my phone, you need a really fast sd card, an class 10 for that, and a reliable brand, mine is class 4, so in the final, sd card will worth half price of the phone)
Click to expand...
Click to collapse
Thanks,i have both titanium and es explorer,can i do with that by simply uninstalling system app? Actually someone told me not to this way and instead trim the rom.Even i am confused what is the difference.Either it creates problems or the amount of space we get by uninstalling with titanium is less compared to trimming the rom.
I will later what i did later.
So after doing a wipe to my phone (was becoming slow) my phone randomly restarts itself for no reason as if it just crashes. I am running the latest version of the beanstalk rom. http://forum.xda-developers.com/showthread.php?t=2091900 I don't have the greatest understanding of flashing, roms, blah blah blah, but managed to get kit kat working for the last year or so, I don't understand why this is happening now, did I choose a bad rom or something? Everything else on the phone works but obviously constant restarts get to be very annoying.
Any help would be appreciated,
thank you!
Infused4life said:
So after doing a wipe to my phone (was becoming slow) my phone randomly restarts itself for no reason as if it just crashes. I am running the latest version of the beanstalk rom. http://forum.xda-developers.com/showthread.php?t=2091900 I don't have the greatest understanding of flashing, roms, blah blah blah, but managed to get kit kat working for the last year or so, I don't understand why this is happening now, did I choose a bad rom or something? Everything else on the phone works but obviously constant restarts get to be very annoying.
Any help would be appreciated,
thank you!
Click to expand...
Click to collapse
Try leaving it turned on in recovery mode (CWM). If it still reboots, then you have a hardware issue. If it stays stable, I would blame the ROM and try a different version or a different distro.
Sent from my MyTouch 4G Slide
joel.maxuel said:
Try leaving it turned on in recovery mode (CWM). If it still reboots, then you have a hardware issue. If it stays stable, I would blame the ROM and try a different version or a different distro.
Sent from my MyTouch 4G Slide
Click to expand...
Click to collapse
Thanks for the reply,
I don't think it is a hardware issue as it never did this when I had Jelly Bean or even the last time I had Kit Kat, never know though! Also, I will try to leave it in recovery and see if it does it but a few questions:
-What is "distro" (does it has to do with the OS of the phone?)
-Is there some ROM you could recommend to me for this phone that is stable.. When I install the beanstalk ROM there are like 10 to choose from, I'm guessing they are all older/newer versions!?
-Finally something I was wondering for the longest time but wasn't sure of is can I go back to say, Jelly Bean? Or is it "irreversible"?
Thanks again, glad there's people out there who can help the noobs like me!
Infused4life said:
Thanks for the reply,
I don't think it is a hardware issue as it never did this when I had Jelly Bean or even the last time I had Kit Kat, never know though! Also, I will try to leave it in recovery and see if it does it but a few questions:
-What is "distro" (does it has to do with the OS of the phone?)
-Is there some ROM you could recommend to me for this phone that is stable.. When I install the beanstalk ROM there are like 10 to choose from, I'm guessing they are all older/newer versions!?
-Finally something I was wondering for the longest time but wasn't sure of is can I go back to say, Jelly Bean? Or is it "irreversible"?
Thanks again, glad there's people out there who can help the noobs like me!
Click to expand...
Click to collapse
Methinks it is the specific ROM. I call the different types of OM out there distributions (or "distros" - in light of what is commonly used in the Linux world), but there may be a better term. It could be the version of Beanstalk you are using, it could be any version of BeanStalk with your phone. Hard to say.
In light of above, I would try CarbonROM. I tried it out briefly, and haven;t had a problem with it (and have heard no issues form the guy I sold the phone to with it installed).
But if you want to go back to JellyBean, there is still a version of 4.2 kicking around (CM 10.1) in the development threads. You can downgrade, at worst you may have to ODIN back to stock. But try to flash in CWM first. I was quite satisfied with that version. My biggest gripe is that the mobile data quick setting didn't work fully (but the long way around did). There is CM 10.2 as well, but I could never get that one installed on my phone (installer would break). Between the two, I would try 10.1 (and if you cannot find a copy, I can dropbox it to you).
5529
joel.maxuel said:
Methinks it is the specific ROM. I call the different types of OM out there distributions (or "distros" - in light of what is commonly used in the Linux world), but there may be a better term. It could be the version of Beanstalk you are using, it could be any version of BeanStalk with your phone. Hard to say.
In light of above, I would try CarbonROM. I tried it out briefly, and haven;t had a problem with it (and have heard no issues form the guy I sold the phone to with it installed).
But if you want to go back to JellyBean, there is still a version of 4.2 kicking around (CM 10.1) in the development threads. You can downgrade, at worst you may have to ODIN back to stock. But try to flash in CWM first. I was quite satisfied with that version. My biggest gripe is that the mobile data quick setting didn't work fully (but the long way around did). There is CM 10.2 as well, but I could never get that one installed on my phone (installer would break). Between the two, I would try 10.1 (and if you cannot find a copy, I can dropbox it to you).
Click to expand...
Click to collapse
YES!
So, after I left the phone in CWM for 25 minutes or so and it being fine I decided to get Carbon as I seen in your "signature" that you had that ROM on your Infuse, it has been good for 2 hours+, looking good! I guess it was the Beanstalk ROM after all.
Thanks for the downgrading information as well, wasn't sure if you could downgrade or what would happen!
Finally, what is flashing? (I could google it but since your here, could you give me a noob friendly definition!?)
Thanks for all your help
Infused4life said:
YES!
So, after I left the phone in CWM for 25 minutes or so and it being fine I decided to get Carbon as I seen in your "signature" that you had that ROM on your Infuse, it has been good for 2 hours+, looking good! I guess it was the Beanstalk ROM after all.
Thanks for the downgrading information as well, wasn't sure if you could downgrade or what would happen!
Finally, what is flashing? (I could google it but since your here, could you give me a noob friendly definition!?)
Thanks for all your help
Click to expand...
Click to collapse
Went to reply about the camera issue and notice it was no longer in the post. Glad you got it sorted.
So flashing, as I understand it, is just another term for installing something via recovery. Not sure of the origin, maybe have something to do with installing to flash memory.
joel.maxuel said:
Went to reply about the camera issue and notice it was no longer in the post. Glad you got it sorted.
So flashing, as I understand it, is just another term for installing something via recovery. Not sure of the origin, maybe have something to do with installing to flash memory.
Click to expand...
Click to collapse
Ah ok, so it's essentially as I thought it was. I thought I was doing something wrong in terms of "flashing" but guess not! Sounds like it should just be called "Installing custom ROM".. !
Yeah, in terms of the camera thing, I'm an idiot and had USB storage turned on *facepalm*, So it wouldn't let me open the camera app!
Infused4life said:
Ah ok, so it's essentially as I thought it was. I thought I was doing something wrong in terms of "flashing" but guess not! Sounds like it should just be called "Installing custom ROM".. !
Yeah, in terms of the camera thing, I'm an idiot and had USB storage turned on *facepalm*, So it wouldn't let me open the camera app!
Click to expand...
Click to collapse
I am not sure if you are still facing the same issue but if you are facing reboots, then considering doing a fresh install after cleaning your internal storage as well since the remnants of the apps from previous installs have caused me problems. Ever since I started doing a fresh install (Factory reset, wiping the cache, wiping the dalvik cache and even the cache partition along with the wiping of the internal storage), there have been no reboot issues.
Hey guys last night I decided to give CM12 a test and while I was liking it I went back to the stock 44S ROM because the phone is critical for business use on a daily basis.
I am using TWRP 2.8.3, Official CM12 Nightly from 1/14, and PA-Gapps from 1/11.
I of course made a full backup and did a clean install when switching from CM11 to 12.
I wiped Cache, Dalvik, Data, and System, and then wiped Cache and Dalvik again between Gapps install and booting. Basically before and after any flashing, I wipe cache.
Before and during trying CM12 everything was was fine, but after restoring my backup my phone will now wake from double tapping or pressing power button, it will ONLY wake if connected to USB, wich turns the screen on and enables me to unlock. Notifs make their noise but since they don't wake the screen, I can't tell whats happening until i plug in.
For now I upgraded again to CM12 nightly, but I would like to go back go 11s 44S until things are more developed. Is there any fixing my TWRP backup or should I just us that guide to return to stock and start over?
It's because your proximity sensor isn't working properly anymore. This is because a new modem was flashed to the device when you flashed CM12, and this modem isn't compatible with older ROMs. This has been discussed very extensively in pretty much every Lollipop thread, plus right here in this q&a section (there's even another thread only a few posts down discussing the exact same problem as this, as well as the solution). You need to go to zephiK's radio/modem thread in our general section and get the last CM11S modem to flash.
timmaaa said:
It's because your proximity sensor isn't working properly anymore. This is because a new modem was flashed to the device when you flashed CM12, and this modem isn't compatible with older ROMs. This has been discussed very extensively in pretty much every Lollipop thread, plus right here in this q&a section (there's even another thread only a few posts down discussing the exact same problem as this, as well as the solution). You need to go to zephiK's radio/modem thread in our general section and get the last CM11S modem to flash.
Click to expand...
Click to collapse
Thank you for the help Timmaaa, I apologize for being "that guy". Truthfully I looked but I guess my search phrasing was terrible because I didn't find anything as helpful as your response. I also have never done this stuff before outside of my old Nexus 4 and that was all on CM11.
Again thank you for answsering, the official OPO forums were not helping much and I was about to use your Back to Stock reflashing tool, but you just saved me a bunch of time.
Issue with cm11 based rom
I3ig Al said:
Thank you for the help Timmaaa, I apologize for being "that guy". Truthfully I looked but I guess my search phrasing was terrible because I didn't find anything as helpful as your response. I also have never done this stuff before outside of my old Nexus 4 and that was all on CM11.
Again thank you for answsering, the official OPO forums were not helping much and I was about to use your Back to Stock reflashing tool, but you just saved me a bunch of time.
Click to expand...
Click to collapse
Hi, I have multirom with cm12 as primary rom. I installed miui rom as secondary rom but proximity sensor does not work. Now I hear many people say to flash cm11s modem. Now do I have to flash cm11s modem on CM12 or on MIUI rom? I am confused.
CM12 to CM11S
timmaaa said:
It's because your proximity sensor isn't working properly anymore. This is because a new modem was flashed to the device when you flashed CM12, and this modem isn't compatible with older ROMs. This has been discussed very extensively in pretty much every Lollipop thread, plus right here in this q&a section (there's even another thread only a few posts down discussing the exact same problem as this, as well as the solution). You need to go to zephiK's radio/modem thread in our general section and get the last CM11S modem to flash.
Click to expand...
Click to collapse
Hi, I am on CM12 and badly wanna go back to CM11S... Really wish to try out the new updates like Maxxaudio and swiftkey integration. So once i have the ROM file how would you suggest me to go back to the CM 11S? I dont want to go wrong therefore please guide me through this or please show me a link where i can find a way to do this. I checked alot of phrases like CM11S from CM12..CM12 to CM11S..believe me i couldnt find any help...May be because I dont spend much time here in xda.
Thanks for your help in advance!
Cheers
Go to my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
Follow the instructions in section 8. Don't flash the userdata image though or it'll wipe your storage.
Hello.
My problem is that sometimes, when I receive a notification, ambient display turns screen on to show it (as it should do normally), but then, when it is supposed to turn screen off again, it only goes black, but the backlight is still on. It's hard to notice, but I don't want the backlight on, using battery, when I think it's off.
The only way to turn it off is by activating ambient display again (moving the phone, waving in front of proximity sensor, pressing power button), and then it would show my normal lock screen and then turn off, until "something" makes it leave the backlight on again.
Anyone have/had/knows this issue? I've used Mokee ROM, now I'm on RR and it happened on both, I don't remember if it happened in CM. Could it be something app related?
Thanks.
Yeah same happened with cm 12.1 latest nightly too.....just checked it now...
The Answer
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
therealduff1 said:
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
Click to expand...
Click to collapse
That's strange! I guess it may be something like the drivers you said, because just one user said that have the same problem, but I'll have to wait until I have some free time to flash stock and root and flash CM and restore all apps and that again... I hate that part of installing another ROM.
therealduff1 said:
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
Click to expand...
Click to collapse
I flashed stock using fastboot and then RR but the problem persists... Any other ideas??
Secuential said:
I flashed stock using fastboot and then RR but the problem persists... Any other ideas??
Click to expand...
Click to collapse
Ok, I have spent some time thinking about this one for you, as I really want you to get this one fixed!
Although I need abit more information.
1) Does the issue occur on stock rom?
2)Are you sure it is not a problem with the build you are running?
3)What exact steps did you use to flash the rom?
To show that you appreciate my help so far, please click thanks
therealduff1 said:
Ok, I have spent some time thinking about this one for you, as I really want you to get this one fixed!
Although I need abit more information.
1) Does the issue occur on stock rom?
2)Are you sure it is not a problem with the build you are running?
3)What exact steps did you use to flash the rom?
To show that you appreciate my help so far, please click thanks
Click to expand...
Click to collapse
Thanks!
1)I can't tell if it occurs on stock, because on stock I use moto display (which doesn't have this issue).
2) I'm almost sure, because I've used 2 ROMs and both do the same. Maybe I'll have to try with CM nightlies?
3)I followed the guide in "general" section to flash stock using fastboot and android sdk. After that, I booted on stock, then rebooted to bootloader, flashed TWRP, entered to recovery, wiped data and then flashed RR ROM with it's gapps and then flashed moto camera and gallery. After that, wipe dalvik and cache and rebooted to system.
Right , ok. I recommend trying one of the cm12 nightly builds, seeing as they worked on my phone fine in terms of ambient display
therealduff1 said:
Right , ok. I recommend trying one of the cm12 nightly builds, seeing as they worked on my phone fine in terms of ambient display
Click to expand...
Click to collapse
Well, the other user that commented on this post was also using latest CM nightly, so I'm not very positive about it, but I may try it when I have time.
Well , looking at all of the information In this post , I think it is safe to say ambient display is not fully working on many roms :/
I installed a new build of cm12 earlier, and I found that sometimes the backlight will stay on , but other times it is fine.
If you want to work on this together, email me at [email protected] , and then we can look into it abit further ?
I will take a thorough look into the forums to see if others are recieving any problems as well .
therealduff1 said:
Well , looking at all of the information In this post , I think it is safe to say ambient display is not fully working on many roms :/
I installed a new build of cm12 earlier, and I found that sometimes the backlight will stay on , but other times it is fine.
If you want to work on this together, email me at [email protected] , and then we can look into it abit further ?
I will take a thorough look into the forums to see if others are recieving any problems as well .
Click to expand...
Click to collapse
Thanks! I have a lot of work right now, so I can't work with this now, but I'll email you when I have more free time!