Related
Greetings,,
Many of us are facing some random restarts by launching the camera or slow camera issue
Actually Doc already have a fix, which I found here but I don't know why I can't find a separate thread for it ...
Of course all credits go to Doc for this fix
Link for the fix: http://d-h.st/YYl
Just flash it...
For noobs,, here is a video guide
Regards,,
Great! Thanks
Excellent thanks
Sent from my GT-I9500 using Tapatalk 4 Beta
i'd tried this fix but it didn't work unfortunately and i got reboots on opening the camera again .
after flashing adams kernel 1.3.1 and on Wanam's Rom...so far no reboots ...still testing
i dont really know what this fix does as i have not downloaded. But what i have identified is, if you flash someother kernel from different FW then the problem persist. For example if you flash ME2 stock kernel on ME1 then the camera will be broken and if you flash the ME2 on ME2 then there wont be any problem with the camera
hoezay said:
i'd tried this fix but it didn't work unfortunately and i got reboots on opening the camera again .
after flashing adams kernel 1.3.1 and on Wanam's Rom...so far no reboots ...still testing
Click to expand...
Click to collapse
What has worked for me is limiting the background processes to 4 in the Developers Options. You have to know that every time you reboot the phone the limit for background processes goes back to default, so after every reboot (voluntary) you need to go and change it.
This is not my discovery, somebody suggested it in another thread.
Cheers
it need root right ??? bec i don't have like the recovery in the video
You guys are seriously mistaken. Doc's camera fix merely copies the latest camera firmware rev to the firmware folder, which fixes the "camera failed" message when using an older custom kernel with a newer ROM. It has absolutely NOTHING to do with the random crashing encountered when launching the camera, you WILL still get that until Samsung releases a proper fix for it.
Please either change the thread title or lock the thread, nothing worse than misinformation.
Sent from my GT-I9500 using Tapatalk 4 Beta
cmd512 said:
You guys are seriously mistaken. Doc's camera fix merely copies the latest camera firmware rev to the firmware folder, which fixes the "camera failed" message when using an older custom kernel with a newer ROM. It has absolutely NOTHING to do with the random crashing encountered when launching the camera, you WILL still get that until Samsung releases a proper fix for it.
Please either change the thread title or lock the thread, nothing worse than misinformation.
Sent from my GT-I9500 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I agree with you +1
Sent from my GT-I9500 using Tapatalk 2
what he said
cmd512 said:
You guys are seriously mistaken. Doc's camera fix merely copies the latest camera firmware rev to the firmware folder, which fixes the "camera failed" message when using an older custom kernel with a newer ROM. It has absolutely NOTHING to do with the random crashing encountered when launching the camera, you WILL still get that until Samsung releases a proper fix for it.
Please either change the thread title or lock the thread, nothing worse than misinformation.
Sent from my GT-I9500 using Tapatalk 4 Beta
Click to expand...
Click to collapse
+N
Hello there,
I got a problem with installing Open Pdroid on my Galaxy s I9000. Its rooted and running on CM 10.1.0-RC2 and Android 4.2.2.
The thing is, I can't figure out what exactly I am doing wrong.
I used Kobik77's ApG to create the update.zip and restore.zip and had no further issues with it.
On my phone I entered CWM and installed the .zip without any error.
I installed PDroid Manager via Google Play.
So far so good. But now PDroid Manager says: "The PDroid Core has not been detected on your device."
As of now I am not sure whether the patching Process via ApG has been a failure, something went wrong
when installing it via CWM, the PDroid Manager has been buggy, or none of it and I just missed
some detail, like the version I am using is not supported (though I am pretty sure I read somewhere that 4.2.2 and CM 10.1 are supported).
Any help is greatly appreciated.
Edit: my problem has slightly changed. PDroid manager now always asks me to configure it when i install a new app. But when i attempt to do so, it says: "PDroid Manager has been closed."
When i open PDroid manager via the apps icon it still tells me that open pdroid Installation cannot be detected.
- If there is any additional information u need, I'll gladly provide it.
- I hope this is the right place to post it.. I already tried to post in
the dev forum (permission denied) where an information kindly
directed me here .
- And one last thing .. go easy on me I am new to smartphones
in general and have only aquired some basic knowledge through
reading.
chuSmu
An ideas?
Sent from my GT-I9000
puuush .. please
Is there really no one with an idea? Ort am i just posting in the wrong place?
ANY answer is greatly appreciated!!
Sent from my GT-I9000 using xda app-developers app
chuSmu said:
Is there really no one with an idea? Ort am i just posting in the wrong place?
ANY answer is greatly appreciated!!
Click to expand...
Click to collapse
Hadn't seen these posts before, sorry.
You are only flashing the update.zip file, and not the restore.zip as well?
I use ApG to build openDroid for my LG 4X HD and it works fine.
Hello, first of all thanks for the reply! Yes i only flash the update zip. Flashing the the restore zip would defeat the purpose right?
Sent from my GT-I9000 using xda app-developers app
Any other ideas?
Sent from my GT-I9000 using xda app-developers app
chuSmu said:
Hello, first of all thanks for the reply! Yes i only flash the update zip. Flashing the the restore zip would defeat the purpose right?
Click to expand...
Click to collapse
I can't think of anything obvious that would cause this. Are you running the stock Kernel? I would suggest trying a totally clean install of CM with the .zip file you created by ApG. Don't install anything other than the pDroid Manager and test it again. If it's still not working then try with a newer version of CM, possibly the latest nightly for your device.
SimonTS said:
I can't think of anything obvious that would cause this. Are you running the stock Kernel? I would suggest trying a totally clean install of CM with the .zip file you created by ApG. Don't install anything other than the pDroid Manager and test it again. If it's still not working then try with a newer version of CM, possibly the latest nightly for your device.
Click to expand...
Click to collapse
Actually i have no idea if i run the stock kernal, as I said, I am pretty new to smartphones.
"3.0.76-gc0a8d45
[email protected] #1"
..is what it says in the phone's settings. Doesn't sound like a stock to me.
I will install the latest nightly build first and try it again. If possible i want to avoid to go through the trouble
of reinstalling all my apps. Seems like I have to find a good backup solution earlier than expected if I
want to keep as much of my data as possible >.<
Well thanks again for taking the time to deal with my problem!
chuSmu said:
Actually i have no idea if i run the stock kernal, as I said, I am pretty new to smartphones.
"3.0.76-gc0a8d45
[email protected] #1"
..is what it says in the phone's settings. Doesn't sound like a stock to me.
I will install the latest nightly build first and try it again. If possible i want to avoid to go through the trouble
of reinstalling all my apps. Seems like I have to find a good backup solution earlier than expected if I
want to keep as much of my data as possible >.<
Well thanks again for taking the time to deal with my problem!
Click to expand...
Click to collapse
The kernel sounds stock - if you don't remeber flashing a different kernel then you're fine. If you're that worried about losing your apps then just flash the latest nightly and use ApG on that version to try - but do a NanDroid backup of everything first, just in case.
SimonTS said:
The kernel sounds stock - if you don't remeber flashing a different kernel then you're fine. If you're that worried about losing your apps then just flash the latest nightly and use ApG on that version to try - but do a NanDroid backup of everything first, just in case.
Click to expand...
Click to collapse
OK i screwed and bricked my phone Anyway i managed to try a few things:
I flashed latest CM nightly and tried to get Open PDroid via the update zip from ApG --> failed
I did factory reset and wiped the cache / did a clean install of ONLY (I just tried randome stuff here) the update zip --> failed
I did factory reset and wiped cache / did a clean istall of latest CM nightly, rebooted and installed the ApG update zip --> failed
Each time the PDroid Manager wasn't able to detect a, in my case Open PDroid, installation.
I noticed that it took especially long to initiate the download of PDroid Manager, I mean the bar before the actual download starts. It took a few minutes until sth. happened. Though i doubt it has anything to do with, I just wondered if it may be conflicting with anything in the system. But probably just due to the reset.
I am getting desperate here
Well anyway.. I may have done a mistake,but realized it too late: Did u mean to install without the gapps? .. I did install CM with gapps...
If I was meant to install CM without gapps i will try that tomorrow!
If any different ideas come to mind.. I will try anthing else too.
thanks again..
Hey, my phone's fixed and my problem changed a little, but i dont know if i it is any
progress.
PDroid Manager still displays the same message, that Open PDroid core could not be
detected, but whenever i istall a app now, it asks me to configure it.
When i press the button in the status bar, where it appears, it just says: "PDroid Manager has
been closed".
So basically i can't do anything with it, but it sometimes tells me it's there
any suggestions?
Maybe anyone has the same issue?
I'd be happy if you shared your experience.
Sent from my GT-I9000 using xda app-developers app
Anyone pretty pleaaasseee
I really want to get this working.
Sent from my GT-I9000 using xda app-developers app
No further suggestions?...
Sent from my GT-I9000 using xda app-developers app
chuSmu said:
No further suggestions?...
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
If OpenPdroid isn't working, have you tried Pdroid2.0? It's not the best solution, but it is one.
Thanks for your reply. I might actually try that. I'd really like to get open pdroid working though or at least understand why it doesn' t. So if there are some other solutions i'll be happy to hear about them.
Sent from my GT-I9000 using xda app-developers app
chuSmu said:
Thanks for your reply. I might actually try that. I'd really like to get open pdroid working though or at least understand why it doesn' t. So if there are some other solutions i'll be happy to hear about them.
Click to expand...
Click to collapse
I've been offline for a few days so am only just catching up on stuff. Given the problem you are now having, I'd suggest run ApG and copy the entire text output from the log. Post that along with a description of the problem you're having onto the ApG Dev thread, and also a logcat if you can.
Hi SimonTS thanks for directing me to the dev forum. I got my Problem fixed. The reason it didnt work is pretty embarassing though .
I had a old version of apg and/or the open pdroid Version that comes with it. everything works just fine now. Thanks for your efforts.
Sent from my GT-I9000 using xda app-developers app
chuSmu said:
Hi SimonTS thanks for directing me to the dev forum. I got my Problem fixed. The reason it didnt work is pretty embarassing though .
I had a old version of apg and/or the open pdroid Version that comes with it. everything works just fine now. Thanks for your efforts.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
Why don't you post the solution here? It might help someone else.
Edit: Sorry my bad, I just can't read
I was originally running nutta's pa beta 5 with no issues. I decided to update to beta 6. When I did this I lost text messaging. I tried a different ROM thinking maybe my phone was just picky (wtf). Doesn't matter on slimkat and both beta 5 and beta 6 of pa I can only text during the first couple seconds of a reboot and when I change from global to CDMA for a couple seconds/normally one message.. I'm at a loss at this point I have tried everything I can think of.
Text works fine on TW ROMs.
Things I've tried:
Almost every different combination of network settings I could pick in mobile networks
4 different gapp packages
Checked md5
Reflashed ml1 modem
Odin back to stock 4.1.2
Phillz touch recovery
Twrp recovery
There is more I'm sure but right now I feel like I covered it.
Any ideas??? I don't want have to only use tw.
Thank you in advance!
Sent from my SCH-I535 using Tapatalk
http://forum.xda-developers.com/showthread.php?t=2654822
Sent from my SCH-I535 using Tapatalk
Just bumping to see if anyone else found anything?
Sent from my SCH-I535 using Tapatalk
Dex954 said:
Just bumping to see if anyone else found anything?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
su reboot nvrestore fixed my issue. Thank god no more TW
Sent from my SCH-I535 using Tapatalk
Help
Dex954 said:
su reboot nvrestore fixed my issue. Thank god no more TW
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I'm sorry, a bit of a noob. I am having the 1SMS issue on all ASOP roms...how do I nvrestore? I did a google search but couldn't find the right answer. Thanks for any help....I need my SMS!
pagnardc said:
I'm sorry, a bit of a noob. I am having the 1SMS issue on all ASOP roms...how do I nvrestore? I did a google search but couldn't find the right answer. Thanks for any help....I need my SMS!
Click to expand...
Click to collapse
follow this guide
http://forum.xda-developers.com/showthread.php?t=1852255
I Need help updating my nexus 5 to 4.4.4. I touched the notification notifing me of the update and it switched to the twrp recovery screen and failed. I then switched back to stock recovery. Now it keeps saying my system is up to date. Any suggestions?
it failed because you are not running 100% stock rom/kernel.
gregpyro said:
I Need help updating my nexus 5 to 4.4.4. I touched the notification notifing me of the update and it switched to the twrp recovery screen and failed. I then switched back to stock recovery. Now it keeps saying my system is up to date. Any suggestions?
Click to expand...
Click to collapse
fastboot.
There has to be a better way besides me doing a fastboot or restore to factory. There is an app or script I remember having to cleardata/clear cache . I have too much important data that I can't seem to back up.
gregpyro said:
There has to be a better way besides me doing a fastboot or restore to factory. There is an app or script I remember having to cleardata/clear cache . I have too much important data that I can't seem to back up.
Click to expand...
Click to collapse
Fastboot flash a recovery then use that recovery to flash a rooted stock ROM.zip
Pretty easy really.
Sent from my Nexus 5 using Tapatalk
What system aop controls updates?
rootSU said:
Fastboot flash a recovery then use that recovery to flash a rooted stock ROM.zip
Pretty easy really.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I wanted to reset the app that controlled updates. I had a similar problem with me rooted galaxy s4 and HTC One and it was as simple as an app reset.
gregpyro said:
I wanted to reset the app that controlled updates. I had a similar problem with me rooted galaxy s4 and HTC One and it was as simple as an app reset.
Click to expand...
Click to collapse
Oh right. So to be clear you don't want to be updated / rooted / recovery ?
Because our assumption was that you did want those things and that's the advice we've been giving
App reset? No idea, they changed how it works.
If you use search, there are other threads discussing that. Probably get this one locked
Edit. Oh so you mean the reset that forces OTA updates to be checked again? That was always considered a bad idea and it still won't help your issue of your ROM is modified.
If you want root, what I said is the best way bar none. If you want stock unrooted, fastboot flash system.img to clean up your ROM.
Sent from my Nexus 5 using Tapatalk
rootSU said:
Oh right. So to be clear you don't want to be updated / rooted / recovery ?
Because our assumption was that you did want those things and that's the advice we've been giving
App reset? No idea, they changed how it works.
If you use search, there are other threads discussing that. Probably get this one locked
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah. I'll do all that later. But as for now. I want to update from my device and my device only with out a PC
gregpyro said:
Yeah. I'll do all that later. But as for now. I want to update from my device and my device only with out a PC
Click to expand...
Click to collapse
You can't if your system is modified see above edit
You're not clear about your current status. Are you still rooted?
Sent from my Nexus 5 using Tapatalk
rootSU said:
You can't if your system is modified see above edit
You're not clear about your current status. Are you still rooted?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Maybe I'm not being clear enough. There is a way to actually reset this screen . I just don't know how for this device
yes I worked it out and already told you it is universally acknowledged as a bad idea. Please answer previous questions.!!!
Sent from my Nexus 5 using Tapatalk
rootSU said:
yes I worked it out and already told you it is universally acknowledged as a bad idea. Please answer previous questions.!!!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I just figured out which app I had to clear data. Thanks.
Well thanks for helping me to help you. It's been a dream it really has.
Everyone else don't do what the OP has done. It has been linked to some pretty bad software issues... This was just a case of "OP knows best" unfortunately.
Sent from my Nexus 5 using Tapatalk
finished this one 4am this morning, and fell asleep before I could post, so here you go:
Writeup, details, etc all here:
http://dmitry.gr/index.php?r=06. Thoughts&proj=04. Android M on Grouper
What works: selinux, camera, NFC, GPS, WiFi, Bluetooth
No dirty patches in /platform, no dirty hacks
Lots of cool hacks though. Read up
This is for WiFi devices only (for now)
use latest public bootloader
and i suggest a data wipe - i do not support any conflicts with existing data - selinux policies changed in ways that might affect /data, so having things in /data can affect things like GPS adversely
Awesome! Do we need to update radio/bootloader first?
Sent from my Nexus 5 using Tapatalk
tcat007 said:
Awesome! Do we need to update radio/bootloader first?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
use latest
and i suggest a data wipe - i do not support any conflicts with existing data - sepolicy changed so thing sin /data/can affect thing sliek GPS adversely
Did factory reset. Got error updating binary script in TWRP.
Sent from my Nexus 5 using Tapatalk
tcat007 said:
Did factory reset. Got error updating binary script in TWRP.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
try using fastboot
i did not test TWRP package (fell asleep)
will look into it later today
TWRP package fixed, uploaded
Is the 'Doze' functionality of Marshmallow working?
It is for me
what Gapps did you end up using? I've flashed multiple packages and it all leads to Setup Wizard problems
Yeah, rom flash works, but stuck with no playstore. Also tried flashing supersu and got a bootloop. Also tried to install an apk from Explorer and wouldn't install. I know this is real really so I'm sure things will get added. But what's here feels much faster and smooth! 6 on a 7, wow!
Edit: I downloaded these "mini" and they seem to be installing OK. http://androiding.how/android-6-0-marshmallow-gapps/
Got me to set up screen!
Sent from my Nexus 5 using Tapatalk
After fighting a bit, the ROM started and I'm restoring my apps from playstore, when I chose the restore point in the wizard, this failed, then select "New device" to continue, anyway restoration began. After finishing the wizard i modified play services permissions to stop FCs.
These were my steps:
1 Wipe Data/System/Cache/Dalvik
2 Flash ROM
3 Flash BETA-SuperSU-v2.52
4 Flash benzo-gapps-M-20151011-signed-chroma-r3
5 Wipe Data/Cache/Dalvik
6 Reboot
Seriously, this is quick and brilliant work. Congrats to all of you who put in the hours and stress. This.....is why I only use Nexus devices. Your efforts are truly appreciated. Best of luck as you continue to further this project.
rebel1699 said:
Congrats to all of you who put in the hours and stress..
Click to expand...
Click to collapse
Glad to help
I am not one of them people who make ROMs all the time. I just wanted to do all the actually hard work of the port and offer specific directions to them, so they can support M on this crop of nexus devices
I'm not getting su 2.52 to boot. Everything w/o root is great!
Sent from my Nexus 5 using Tapatalk
See Nexus 4/10 forums where people already figured it out
My Nexus 7 has been revived... 5.1.1 was unbearably slow. I'm very impressed. Great work!
M on N7
Happy to see that people still supports and share their work for the N7 - big thanks :good:
Now it's exciting to see if the N7 will be able to handle Android M for more than a day or two before slowing down :fingers-crossed:
I'll try this out
How does this differ from [WIP][ROM][6.0] Nexus 7 Marshmallow - Android 6.0?
Hello Guys! From where to download the file for grouper.Thank You!
Sent from my Nexus 7 using XDA Free mobile app
When do you think it is possible to have a version for the Nexus 7 3G (tilapia)?
Thanks a lot for your contribution.
hmmm