I noticed about a week ago that my GPS was not locking my location. I‛m on RootBox 4.0, and I've read that others had this issue with the ROM. I tried all the solutions listed in the thread, but nothing solved the problem. My phone shows no satellites in view or in use, even if I leave it for 20mins. Occasionally I get 1 satellite in view but my phone doesn't use it.
I would appreciate any help.
I had the same problem also on rootbox 4.0. I had success with the third fix in the rootbox thread. What isn't listed there, is that after extracting, pasting/replacing and fixing permissions of the gps driver is that a reboot is needed directly after this. Maybe try fix #3 again from the beginning, but reboot after? I get gps lock within 10 seconds if I do that.
Sent from my GT-I9100: Powered by Dorimanx, running RootBox
Hopper8 said:
I had the same problem also on rootbox 4.0. I had success with the third fix in the rootbox thread. What isn't listed there, is that after extracting, pasting/replacing and fixing permissions of the gps driver is that a reboot is needed directly after this. Maybe try fix #3 again from the beginning, but reboot after? I get gps lock within 10 seconds if I do that.
Click to expand...
Click to collapse
I reboot every time I apply a GPS 'fix'. I'll try again though.
Tried again, still no joy.
vSTATERv said:
Tried again, still no joy.
Click to expand...
Click to collapse
Alright, so the obvious which may not be so obvious. It took me a while to figure out what was going on but now each flash I can get GPS lock after a few minutes fiddling and 10 seconds waiting for a lock. So we're on the same page, this is what you're doing:
Download and extract attachment. Using Root explorer, backup the gps.exynos.so in system/lib/hw to sdcard, then remove it from the system/lib/hw folder. Also using Root explorer, copy the gps.exynos4.so that you extracted or whatever its called to system/lib/hw. Fix permissions to rw-r--r--. Reboot. Open Google maps, grant it the permission to access location. Wait for GPS fix.
Using those steps I get GPS working first go every time on RootBox 4.0. If I miss anything, or do anything different, it won't work. Are those the exact steps you're using?
Hopper8 said:
Fix permissions to rw-r--r--.
Click to expand...
Click to collapse
What do you mean by this? The read write execute permissions? Or something else?
vSTATERv said:
What do you mean by this? The read write execute permissions? Or something else?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1857648
Yes, the file permissions. Stickied at the top of the GSII 'General' Section.
Permissions set properly - still not working.
vSTATERv said:
Permissions set properly - still not working.
Click to expand...
Click to collapse
Another captain obvious comment, you are searching for GPS while you're outside? I would assume so. Have you tried re-downloading the file for the fix from the RB thread? If you haven't, try that. If you have, reflash the ROM after a factory reset, cache & dalvik wipe. Try to fix the GPS before restoring all your data etc.
---------- Post added at 10:25 PM ---------- Previous post was at 10:11 PM ----------
FD1999 said:
Sorry but what attachment?
Gesendet von meinem LG-P880 mit Tapatalk 4
Click to expand...
Click to collapse
The one from the third post of this thread: http://forum.xda-developers.com/showthread.php?t=2117444. In the 3rd post, the third option for the GPS fix.
Does this mean anything? One satellite keeps popping up in the centre of the radar.
vSTATERv said:
Does this mean anything? One satellite keeps popping up in the centre of the radar.
Click to expand...
Click to collapse
Couldn't tell you sorry. Not sure what app that is/what it's meant to do. To test my GPS I use Google maps.
Edit: did you reflash the rom?
Sent from my GT-I9100: Powered by Dorimanx, running RootBox
Hopper8 said:
Couldn't tell you sorry. Not sure what app that is/what it's meant to do. To test my GPS I use Google maps.
Edit: did you reflash the rom?
Sent from my GT-I9100: Powered by Dorimanx, running RootBox
Click to expand...
Click to collapse
I did a full wipe, still persists. I might try and flash another rom.
vSTATERv said:
I did a full wipe, still persists. I might try and flash another rom.
Click to expand...
Click to collapse
Omega AOKP has written in the OP 'instantaneous GPS lock'. I've used it and had no issues with GPS at all, give it a shot.
Sent from my GT-I9100: Powered by Dorimanx, running RootBox
I've restored an old backup of resurrection remix, and I still have the problem.
Is it possible that some system files regarding the GPS were corrupted?
So when you had resurrection remix previously, did you have working GPS? And did you try omega? Next step is to flash stock after a full wipe. Stay away from 4.0.4, but pick yourself an ICS/JB ROM and try it. If the problem still persists, then it's possibly hardware. Either that or something is messing up with each flash, which is doubtful.
Sent from my GT-I9100: Powered by Dorimanx, running RootBox
Hopper8 said:
So when you had resurrection remix previously, did you have working GPS? And did you try omega? Next step is to flash stock after a full wipe. Stay away from 4.0.4, but pick yourself an ICS/JB ROM and try it. If the problem still persists, then it's possibly hardware. Either that or something is messing up with each flash, which is doubtful.
Click to expand...
Click to collapse
I doubt that this is a hardware issue. A week ago I was able to get a GPS lock if I waited for 10 mins or so. I started applying all these patches and fixes in an effort to get a decent lock time. After messing around with all these fixes, I have now ended up with no satellites in view and no lock, no matter how long I wait. Therefore, I believe that I've messed up some sort of file whilst trying to reduce the GPS lock time which has now stopped it from working completely. Oh yeah and btw, I was able to use gps back when I had RR ROM.
vSTATERv said:
I doubt that this is a hardware issue. A week ago I was able to get a GPS lock if I waited for 10 mins or so. I started applying all these patches and fixes in an effort to get a decent lock time. After messing around with all these fixes, I have now ended up with no satellites in view and no lock, no matter how long I wait. Therefore, I believe that I've messed up some sort of file whilst trying to reduce the GPS lock time which has now stopped it from working completely. Oh yeah and btw, I was able to use gps back when I had RR ROM.
Click to expand...
Click to collapse
Two words: Flash Stock.
Flashed stock - problem still persists.
UPDATE - finally got it working. Flashed latest stock firmware; it didn't work at first, however after persistent testing I finally get a lock after 26 seconds or so.
Thanks very much for all the help.
Hardware problem. Service centre (Unless you want to try all the usual fixes you'd try if you were still running a custom rom, which I very much recommend you do first).
Related
Ok, so here's the deal.
After I updated my s3 to Jelly Bean, the following problem started to appear:
Sometimes when WiFi turns off either manually or automatically (I have Tasker which turns off WiFi when screen goes off), WiFi gets stuck at "Turning off..." and doesn't react on any actions.
The switcher gets greyed out and I can do nothing about it. The only way to troubleshot it is to restart the device. Once restarted, everything works fine, but, as you already guessed, it works not for too long. =)
It all depends how lucky I'm. Sometimes the phone can work the whole day without causing the glitch, when I'm not that lucky I have to restart the phone a couple of times during the day. <- really annoying.
The phone is rooted with Galaxy S3 Toolkit by flashing an insecure boot image.
I tried to do factory reset but problem still remained.
I have attached a few screenshots as a proof as well as a screenshot showcasing my phone's firmware specs.
Any ideas or help will be appreciated.
I would blame Tasker try uninstalling and test .
jje
JJEgan said:
I would blame Tasker try uninstalling and test .
jje
Click to expand...
Click to collapse
Thanks for the reply. But it seems like this is not the problem with Tasker. As I stated in my previous post, I did factory reset my phone and the problem still remained, though no third-party apps were installed other than those that came stock.
I can reproduce the bug very easily: all I need to do is to turn my WiFi on using the icon under notifications bar and then, once it gets turned on, quickly tap the icon again to turn WiFi off. At that point WiFi gets stuck.
JJEgan said:
I would blame Tasker try uninstalling and test .
jje
Click to expand...
Click to collapse
What date is your kernel - August ? If you have a late build of JB the stock JB on my S3 had a kernel build from 19th October.
You may need to just flash back a later stock boot image you will retain root.
Fixed things for me - just extract the boot.image from a full stock rom and use the toolkit to create a flashable tar should fix your problem and improve the battery life
starfish_001 said:
What date is your kernel - August ? If you have a late build of JB the stock JB on my S3 had a kernel build from 19th October.
You may need to just flash back a later stock boot image you will retain root.
Fixed things for me - just extract the boot.image from a full stock rom and use the toolkit to create a flashable tar should fix your problem and improve the battery life
Click to expand...
Click to collapse
Did as you suggested, tested it a bit and everything works like a charm. The problem is gone, plus I now see more RAM in the Task Manager (this was another issue I was thinking about), and the whole phone seems a bit smoother (maybe this is a placebo effect, dunno).
So thank you very much and you have my appreciation.
Domovik said:
Did as you suggested, tested it a bit and everything works like a charm. The problem is gone, plus I now see more RAM in the Task Manager (this was another issue I was thinking about), and the whole phone seems a bit smoother (maybe this is a placebo effect, dunno).
So thank you very much and you have my appreciation.
Click to expand...
Click to collapse
excellent - pleasure to help
starfish_001 said:
excellent - pleasure to help
Click to expand...
Click to collapse
What rom are you using, i want also to fix this. Thank you
Could this perhaps be brought to attention again please?
How exactly did you fix it and did it involve losing any data?
NVM: Just download and flash Siyah. Probably the easiest fix.
3dawg said:
Could this perhaps be brought to attention again please?
How exactly did you fix it and did it involve losing any data?
Click to expand...
Click to collapse
Nope, flashing kernel will no impact your data.
3dawg said:
NVM: Just download and flash Siyah. Probably the easiest fix.
Click to expand...
Click to collapse
I don't know about Siyah - I simply took a stock kernel, prepared it with the toolkit and flashed it with Odin. This was pretty easy and it worked.
Hope this post helps.
Could someone with a Jelly Bean ROM, or more specifically Slim Bean on their Vibrant tell me if their voice search works as it should.
Mine listens to what I have to say, loads up the browser, but doesn't actually initiate the search?
FWIW, all other voice actions work, eg: "Send text to xyz" or "Call xyz Home" etc...
Stoked with this ROM (2.9) now that I've sorted out a lot of intricacies, but still finding a few bugs...
Thanks in advance. :cyclops:
Try installing the JB4.2 gapps instead: http://d-h.st/sPL (this patch makes gps stop working on SlimBean rom)
You can also do this manually:
Delete the /system/lib/Velvet.apk and the /system/lib/libgoogle_recognizer_jni.so.
Reboot, then install Google Search from the Play Store.
Sent from my Galaxy Nexus
eksasol said:
Try installing the JB4.2 gapps instead: http://d-h.st/sPL
You can also do this manually:
Delete the /system/lib/Velvet.apk and the /system/lib/libgoogle_recognizer_jni.so.
Reboot, then install Google Search from the Play Store.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Flashed the file and it fully broke search and also broke the clock LOL. Had to Nandroid back.
I'll try the manual method...
EDIT - I actually don't have either of those two files in /system/lib ??
Just flashed the newly released Slim Bean 3.0 and all is fixed. This makes me very happy :laugh:
The Velvet.apk is the actual Google Search app, usually in /system/app if its installed permanently in the system. The lib file is in the /system/lib folder, without it Google Search will not work. When you install Google Search app from the PlayStore, it extract the lib folder to an appropriate folder.
But anyway good that you solved the issue.
eksasol said:
But anyway good that you solved the issue.
Click to expand...
Click to collapse
Thanks!
Yep, Slim 3.0 fixed this issue, but broke my GPS which has been solid on every ROM this phone has run up to this point. Not sure what happened there?
I was thinking of trying out Paranoid, no reason not to now! :laugh:
Install this GPS patch and you're good to go. This and performing the hardware fix made my Vibrant have better signal than my Galaxy Nexus and the XPeria Play which also has GLONASS: http://forum.xda-developers.com/showpost.php?p=33844820
Sent from my Galaxy Nexus
Thanks man. I already have that patch flashed. It does make some difference, without it I now don;t even get the GPS icon come up in the notification bar. With the patch the icon comes up (with the dot flashing) but zero sats in sight/in use
I'm kind of stuck now, this ROM is perfect apart from GPS, I can Nandroid back to 2.9, it had solid GPS but a few other problems, I've also tried flashing Paranoid and CM10 and both come unglued with a status 7 error I can.t get past
I don't have any problem with it on my Vibrant and Galaxy Nexus. Can you try wiping data and cache, then format /system partition, then reflash everything.
To flash other roms you need them to have the compatible version of CWM. So flash the rom once and you will get Status 7, don't reboot but flash it again immediately and it should reboot the phone into a boot loop. Then pull battery and boot back into CWM, you will be in a new version of CWM. Flash the rom the third time and it should work.
Sent from my Galaxy Nexus
Thanks...
I can never get to the bootloop stage, just the status 7 over and over. It's a bit odd.
I've managed to get pretty much this same conversation going in 2 places now, what a spammer
wendleburger said:
Thanks...
I can never get to the bootloop stage, just the status 7 over and over. It's a bit odd.
I've managed to get pretty much this same conversation going in 2 places now, what a spammer
Click to expand...
Click to collapse
If you must, Odin back to stock, update it to CM7, then to ICS Passion rom, then to a JB rom.
Or you can just flash a kernel first, reboot recovery and flash the ROM. I would try semaphore 2.5.0v
???
Good point, that should work.
Sent from my Galaxy Nexus
eksasol said:
Good point, that should work.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Thanks guys, I'll try that when I get a chance. Later today hopefully.
samsgun357 said:
Or you can just flash a kernel first, reboot recovery and flash the ROM. I would try semaphore 2.5.0v
???
Click to expand...
Click to collapse
That did it. Kernel flashed straight in and then the ROM just punched its way straight in :cyclops:
I don't quite understand why flashing the bare kernel first should make a difference but it certainly does.
And hello GPS! Went from dead in the water to locking within 10 seconds indoors?
Safe to say I'll be sticking with this ROM unless I find something really broken in it.
Thanks Guys.
The error was because of recovery mismatch. Some people don't get the error from it, it will just flash a d bootloop. Flashing the kernel first, gives you the proper recovery version.
???
Hi guys, i have this weird problem with touchscreen after i've had a faulty flash in Jelly Bean. My touches cannot hold and drag or drop items, for example i can't hold notification center halfway. Also, there is a problem with overall performance: Videos seem to skip 1-2 seconds every second, music plays the same way, and everything feels heavier, my battery also seems to drain very fast. The weird thing is that phone is perfect when i plug it in a power source, no problems at all. There are some other posts with this problem, but no one seemes to be able to solve this permanently. Some workarounds are flashing blazing v8 with any stock firmware, or flashing CM 10.1-20130121-EXPERIMENTAL-i9100g-M1 ROM, but both has SOD s and random reboots, and the vast battery drain still continues.
The milestone to solving this is this thread : http://forum.xda-developers.com/showthread.php?t=2147306, but it's still NOT solved for months... It seems like this is a problem that only a developer can solve, but i cannot post there, so if anyone finds another workaround/ have the same issue/ can-has solve this/ can post the problem on the developer page is welcome
EDIT: SOLVED!
"Thanks to hawkerpaul for making nuke script, and thanks to jimsilver for reminding me of it! If anyone has this problem, here are the steps i took:
1- Download GS2RomNuke (Read all instructions),
2- Download the rom you want and gapps ofc (Read all instructions),
3- Put them in your phone, i put in the sd card and it worked,
4- Flash GS2RomNuke, don't reboot or anything, flash your rom and gapps,
5- Reboot and done!"
So on that thread they say their phone works fine on stock GB/ICS;but not on JB.
You can either WAIT for a fix,code one yourself,use GB or ICS,or email the CEO of Samsung and complain to him.
Dakura said:
Hi guys, i have this weird problem with touchscreen after i've had a faulty flash in Jelly Bean. My touches cannot hold and drag or drop items, for example i can't hold notification center halfway. Also, there is a problem with overall performance: Videos seem to skip 1-2 seconds every second, music plays the same way, and everything feels heavier, my battery also seems to drain very fast. The weird thing is that phone is perfect when i plug it in a power source, no problems at all. There are some other posts with this problem, but no one seemes to be able to solve this permanently. Some workarounds are flashing blazing v8 with any stock firmware, or flashing CM 10.1-20130121-EXPERIMENTAL-i9100g-M1 ROM, but both has SOD s and random reboots, and the vast battery drain still continues.
The milestone to solving this is this thread : http://forum.xda-developers.com/showthread.php?t=2147306, but it's still NOT solved for months... It seems like this is a problem that only a developer can solve, but i cannot post there, so if anyone finds another workaround/ have the same issue/ can-has solve this/ can post the problem on the developer page is welcome
Click to expand...
Click to collapse
Have you tried using @hawkerpauls GS2RomNuke followed by clean ROM?
theunderling said:
So on that thread they say their phone works fine on stock GB/ICS;but not on JB.
You can either WAIT for a fix,code one yourself,use GB or ICS,or email the CEO of Samsung and complain to him.
Click to expand...
Click to collapse
The thing is, it works on JB stock firmware with blazing kernel v8, but not on the latest versions of this kernel, and this problem occurs to a minority of users so i don't think anyone is aware of this, which is why i started this thread, if the CEO of Samsung gave a hoot about our problems, this forum would not exist...
Jimsilver73 said:
Have you tried using @hawkerpauls GS2RomNuke followed by clean ROM?
Click to expand...
Click to collapse
I didn't, i will try now, thanks :good: Btw, i have tried buying a new original battery, didn't work
Dakura said:
I didn't, i will try now, thanks :good: Btw, i have tried buying a new original battery, didn't work
Click to expand...
Click to collapse
Can't really see how this problem would be related to battery though???
Jimsilver73 said:
Can't really see how this problem would be related to battery though???
Click to expand...
Click to collapse
When i plug in the phone to a power source, it is working perfectly well, which is why i thought there was a problem with my battery, it made sense back then
Hmm, it says that this nuke script is for GT-I9100, will it work for the G variant?
Dakura said:
When i plug in the phone to a power source, it is working perfectly well, which is why i thought there was a problem with my battery, it made sense back then
Hmm, it says that this nuke script is for GT-I9100, will it work for the G variant?
Click to expand...
Click to collapse
I read something from @hawkerpaul saying he couldn't see why not, but as I own an i9100 I obviously can't vouch for that. Suggest you search @hawkerpauls thread and read for yourself.
Flash it (at your own risk) and if that doesn't work you always have odin to go back to :good:
Jimsilver73 said:
I read something from @hawkerpaul saying he couldn't see why not, but as I own an i9100 I obviously can't vouch for that. Suggest you search @hawkerpauls thread and read for yourself.
Flash it (at your own risk) and if that doesn't work you always have odin to go back to :good:
Click to expand...
Click to collapse
I couldn't see why not too, so i went ahead already and nuked and flashed today's CM nightly :laugh: I'll test for some time and get back.
Dakura said:
I couldn't see why not too, so i went ahead already and nuked and flashed today's CM nightly :laugh: I'll test for some time and get back.
Click to expand...
Click to collapse
glad to see you give it a go :good:
Seems like everything is working fine now! Im really surprised this being so easy after 2 months, because i've already made many wipes and flashed brand new stock from odin, but looks like it literally nukes the phone! :laugh: Thanks to hawkerpaul for making nuke script, and thanks to jimsilver for reminding me of it! If anyone has this problem, here are the steps i took:
1- Download GS2RomNuke (Read all instructions),
2- Download the rom you want and gapps ofc (Read all instructions),
3- Put them in your phone, i put in the sd card and it worked,
4- Flash GS2RomNuke, don't reboot or anything, flash your rom and gapps,
5- Reboot and done!
i will try
Dakura said:
Seems like everything is working fine now! Im really surprised this being so easy after 2 months, because i've already made many wipes and flashed brand new stock from odin, but looks like it literally nukes the phone! :laugh: Thanks to hawkerpaul for making nuke script, and thanks to jimsilver for reminding me of it! If anyone has this problem, here are the steps i took:
1- Download GS2RomNuke (Read all instructions),
2- Download the rom you want and gapps ofc (Read all instructions),
3- Put them in your phone, i put in the sd card and it worked,
4- Flash GS2RomNuke, don't reboot or anything, flash your rom and gapps,
5- Reboot and done!
Click to expand...
Click to collapse
thanksssss to you and jimsilver so much
for some reason i cant post anything on developing forums untill i got 10 posts so....
when i try to check for updates it says "check your internet connection", yet i am on wifi and everything else is working.
someone knows whats the problem?
Harellevy said:
for some reason i cant post anything on developing forums untill i got 10 posts so....
when i try to check for updates it says "check your internet connection", yet i am on wifi and everything else is working.
someone knows whats the problem?
Click to expand...
Click to collapse
Well, you are supposed to post stuff like this in the Q&A forum, that's why you have to post 10 times. To learn the structure.
You could try to clear data for play services and the play store app and see if that works. If not, I suggest that you try to flash some other gapps package.
Maybe one of these:
http://forum.xda-developers.com/google-nexus-5/themes-apps/gapps-t2012857
Gnarfsan said:
Well, you are supposed to post stuff like this in the Q&A forum, that's why you have to post 10 times. To learn the structure.
You could try to clear data for play services and the play store app and see if that works. If not, I suggest that you try to flash some other gapps package.
Maybe one of these:
http://forum.xda-developers.com/google-nexus-5/themes-apps/gapps-t2012857
Click to expand...
Click to collapse
Opss...
Well I wasn't taking about apps update. I was talking about cm updates.
Harellevy said:
Opss...
Well I wasn't taking about apps update. I was talking about cm updates.
Click to expand...
Click to collapse
Ah, sorry. I don't know about that.
Harellevy said:
for some reason i cant post anything on developing forums untill i got 10 posts so....
when i try to check for updates it says "check your internet connection", yet i am on wifi and everything else is working.
someone knows whats the problem?
Click to expand...
Click to collapse
Welcome to the family.. Just go and find 10 other things that you are curious about and reply to those.
Kinda hard. Nothing make sense here so many advanced stuff.
Harellevy said:
for some reason i cant post anything on developing forums untill i got 10 posts so....
when i try to check for updates it says "check your internet connection", yet i am on wifi and everything else is working.
someone knows whats the problem?
Click to expand...
Click to collapse
same here, have to download the nightly through browser
the cmupdater has not been working since i started with 403. download through pc or browser
try cyandelta
Just go through the browser. What I did and no problem.
So just download the new nightly and reflash?
Do I need to wipe cache or something?
What if I want to go from nightly to stable or M, then I need to wipe?
Thanks for the help
Harellevy said:
So just download the new nightly and reflash?
Do I need to wipe cache or something?
What if I want to go from nightly to stable or M, then I need to wipe?
Thanks for the help
Click to expand...
Click to collapse
I've always wiped when updating, after a backup of course!
NIke619 said:
I've always wiped when updating, after a backup of course!
Click to expand...
Click to collapse
But then you need to download all the apps all over again no?
Harellevy said:
But then you need to download all the apps all over again no?
Click to expand...
Click to collapse
No, just flash the update zip. (That's called a dirty flash in case you didn't know)
If you use custom kernels, flashed mods or custom system apps, they might have to be reinstalled. You also need to reinstall Xposed Framework from the app if you use that.
But remember to back up your phone in recovery before you update!
Okay thanks. 3 last questions (I hope).
I got cm-11-20140410-NIGHTLY
And yesterday released cm-11-20140411-NIGHTLY
Is this an update? Or a completely new nightly? sorry for all the ignorance, I'm totally new to this and android
2. Should I use old M builds or new nightlys? Which one Is more stable
3. If I want to flash M build and I'm currently using nightly, there is a different way or something special I need to do?
If you're going from an m build to a nightly, or any other variation (stable to m, etc) then wipe data and cache. Every nightly can be flashed on top of itself. There are more specific things to be said but I'll leave it at that so you don't get yourself bootlooped.
Make sure you make a nandroid before you do anything (I.e. a backup in custom recovery) and it would be a good idea to put that on your pc. Also a good idea to have the files and setup ready to flash your phone back to factory with kdz or tot--that way if you do something boneheaded you won't be in as much of a panic. It definitely wouldn't hurt to have some experience with adb ahead of time--just in case.
If none of that makes sense I'd wait a bit before flashing (though you could go for it and probably make out fine).
VS980 - CM11 nightly
marleyinoc said:
If you're going from an m build to a nightly, or any other variation (stable to m, etc) then wipe data and cache. Every nightly can be flashed on top of itself. There are more specific things to be said but I'll leave it at that so you don't get yourself bootlooped.
Make sure you make a nandroid before you do anything (I.e. a backup in custom recovery) and it would be a good idea to put that on your pc. Also a good idea to have the files and setup ready to flash your phone back to factory with kdz or tot--that way if you do something boneheaded you won't be in as much of a panic. It definitely wouldn't hurt to have some experience with adb ahead of time--just in case.
If none of that makes sense I'd wait a bit before flashing (though you could go for it and probably make out fine).
VS980 - CM11 nightly
Click to expand...
Click to collapse
- nandroid BackUP - Check. i learned how importent and how lucky to do a nandroid backup when i flashed yesterday the cm. bricked my phone 2 times, thanks to nandroid backup didnt need to flash stock.
- stock KDZ - Check. including flashing tool and all that.
what do you prefer, nightly or M? the nightly can go rough just like that in the middle of everything?
This is the ONLY thread you guys will talk about the CrDroid ROM.
DONT post questions or whatever at the other leaked AOSP ROM thread else it'll create much confusion
So far annoyances thats been reported are:
• Random reboots (at least for some people)
• Auto-brightness
• Underclocked CPU
• Not working HDR & Panaroma (solved with workaround)
DOWNLOAD LINK FOR CRDROID ROM
http://pan.baidu.com/s/1bnzqPBL
Reserved
Via the Internet
Regarding Random Reboots !
I have been using the ROM since yesterday though i have yet not observed a single reboot . I have tried following things as suggested in AOSP thread however it does not give me a reboot. Auto Brightness is the only lingering issue i faced !
Any pointers to reproduce the reboots ?
M3gAtR0N said:
I have been using the ROM since yesterday though i have yet not observed a single reboot . I have tried following things as suggested in AOSP thread however it does not give me a reboot. Auto Brightness is the only lingering issue i faced !
Any pointers to reproduce the reboots ?
Click to expand...
Click to collapse
LKspro said:
after u have the first reboot, cover the upper sensors and touch the screen while it is off. Then the screen should freeze and rebbot after a while
Click to expand...
Click to collapse
This is from @LKspro
Via the Internet
TiTAN-O-One said:
This is from @LKspro
Via the Internet
Click to expand...
Click to collapse
I have reproduced the same however it did not cause a reboot for me ! Thats why asked !! Is this the encountered random reboot occurrence ?? Or do we have something else too ?
Good rom lots of settings but useless... always reboot..
M3gAtR0N said:
I have reproduced the same however it did not cause a reboot for me ! Thats why asked !! Is this the encountered random reboot occurrence ?? Or do we have something else too ?
Click to expand...
Click to collapse
Yeah, first time it happens random, but if it once happens to you, then you will be able to reproduce it.
Anyone try to use the boot.img from leaked AOSP ROM and put I to this ROM? If yes do the random reboot still happening?
wai10691 said:
Anyone try to use the boot.img from leaked AOSP ROM and put I to this ROM? If yes do the random reboot still happening?
Click to expand...
Click to collapse
I can try this but not sure of the exact steps to follow... I like the CM rom very much.. blazing fast with ART, but random reboots quite often. I am now using wakelock to control the reboots. if you think changing the boot.img can help, i will try it out. lemme know what to do for tht
krispuniq said:
I can try this but not sure of the exact steps to follow... I like the CM rom very much.. blazing fast with ART, but random reboots quite often. I am now using wakelock to control the reboots. if you think changing the boot.img can help, i will try it out. lemme know what to do for tht
Click to expand...
Click to collapse
Before flashing the ROM zip simply replace the boot.img in the crdroid with the one from aosp.
I can try this later but I'm outside now
wai10691 said:
Before flashing the ROM zip simply replace the boot.img in the crdroid with the one from aosp.
I can try this later but I'm outside now
Click to expand...
Click to collapse
Done... Flashing went ok but after booting all my apps are gone (I didnt do a clean wipe while flashing.. only wiped dalvik)
The apps are gone anyway.. so i went back to recovery and did another clean flash.. Reboot the phone, but no mobile network. Unable to latch on to network even manually.. so may be there is something missing in the boot.img ?
Back key
Anyone can confirm back key in this rom didnt behave as it should after deleting pre-install files such as baidu services apps
edit 1 - looks like it has been warned by the dev as do not delete keyboard input method or else back button wont work..
Where is the link to the ROM. I'd update OP. Also, is there any bugs with the ROM? Or is it working like AOSP?
Via the Internet
Download link
http://pan.baidu.com/s/1bnzqPBL