Related
Hello, some of you might recognize me as the one who was having trouble installing PA last night.
Now I've got it installed, and it runs very smoothly.
Specs off the bat...
TF700T Infinity
VoltageControl Overclock system set at 370-1800
Very latest gaps, installed last night from g+
MaxKernel V4 Reloaded RC2
Installed and flashed through TWRP
ParanoidAndroid 3.15
Likely enough for myself, all of a sudden, a few hours into having the ROM, kernel and gapps freshly flashed, the screen starts giving random graphical flashes and blips here and there, and it's grown to a point where I can't use my tablet without a flash every three seconds.
To explain exactly what is happening, when I switch from app to app or UI section to another UI section or any of the mix, it will brightly flash what I am switching to/from while I do it. For example, I will be opening up PIE and it will flash the app screen in full for a split second if PIE is over it.
Anything that I am doing wrong? I have a restore from a few hours ago set up, will I have to use that?
If anyone has any advice/assistance, please let me know.
Thanks,
Neb
EDIT: I tried resetting the overclocking system to stock clock. No change whatsoever.
Also did a restore. No luck
Turn off the corresponding setting in the developer options.
Also Max's kernel is a stock based kernel. I'm surprised PA even boots off it. I'd switch to a PA compatible kernel of I were you.
Thank you for helping me out on this. I saw some posts stating that Max was a PA based kernel. My bad. Got it taken care of by reverting to PA stock kernel
Hi all,
Did anyone able to use gps with custom rom ( I would say CM base). I research and try everything that's I could find here but not success.
Every time I do clean wipe everything including a internal storage. So that will nothing left behind.
I know that stock is work fine with gps. some said that install and replace stock but I have no idea that what file will left in our device when we delete all.
Always had the same problem when running Paranoid Android (not tried other ROMs). Had to return to stock, where GPS runs fine. Would also love to kknow how people have got it functioning.
I am trying too. I modified gps.conf files, tried some workarounds mentioned in cm11 thread like restoring GPS Status backup from stock with titanium so far with no success. Some people say that it works but it doesn't on mine whatever I do.
I run on CM and I don't have any problem. Everything works fine with gps and I didn't use any fix or something similar.
I'm on CM 11-20140627 and I have 1032 phone.
Interesting, why does it work on some while it doesn't on others? Maybe some variants are having problems...
I have xt1033 asia version.
spajdo said:
I run on CM and I don't have any problem. Everything works fine with gps and I didn't use any fix or something similar.
I'm on CM 11-20140627 and I have 1032 phone.
Click to expand...
Click to collapse
Which recovery did you use?
CWM
As I wonder is about library missing or some partition need from stock ?
I've also been using the micro gapps package, would this matter?
I had problems with Paranoid Android and GPS too... If anyone know something about that, please comment!
TMaxtor said:
I had problems with Paranoid Android and GPS too... If anyone know something about that, please comment!
Click to expand...
Click to collapse
Hey i found a solution, you have do this flash following in this order.
- flash stock 4.4.4 (depend on your current)
- flash cm
- flash gapp
I try this twice and work like a charm.
Sent from my Moto G using XDA Free mobile app
thestory101 said:
Hey i found a solution, you have do this flash following in this order.
- flash stock 4.4.4 (depend on your current)
- flash cm
- flash gapp
I try this twice and work like a charm.
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
I am having he same problem on XT1032 running Carbon ROM. GPS worked fine on stock, no signal with Carbon.
I found many answers saying to flash stock and then reflash custom ROM. I will try it, but I wonder, how does this help? Isn't the phone restoring the whole system? Do I have to keep the gps.conf from stock?
I've read in some CM thread on here you need to flash stock ROM then enable GPS and get a lock. Once you've done that then flash your custom rom. Sounds STUPID and dosent make sense I know, but a lot of people say this is how they got it to work.
EDIT: I can confirm. I've just flashed stock 4.4.4 and played around with google maps. Flashed CM11 nightly and my GPS is now working ok
am05 said:
I've read in some CM thread on here you need to flash stock ROM then enable GPS and get a lock. Once you've done that then flash your custom rom. Sounds STUPID and dosent make sense I know, but a lot of people say this is how they got it to work.
EDIT: I can confirm. I've just flashed stock 4.4.4 and played around with google maps. Flashed CM11 nightly and my GPS is now working ok
Click to expand...
Click to collapse
Did you wipe anything, like Dalvik, Cache and Data, or you just flashed it over?
am05 said:
I've read in some CM thread on here you need to flash stock ROM then enable GPS and get a lock. Once you've done that then flash your custom rom. Sounds STUPID and dosent make sense I know, but a lot of people say this is how they got it to work.
EDIT: I can confirm. I've just flashed stock 4.4.4 and played around with google maps. Flashed CM11 nightly and my GPS is now working ok
Click to expand...
Click to collapse
Sorry people, I was so happy to have my phone back working, I forgot to write it back here.
Yes it worked indeed, all I did was flashing back the stock, going outside to have a gps lock with gmaps, then re-flashing back the Carbon. I also kept a copy of the gps.conf, but I never needed it, the GPS got a fix quickly. Working fine so far, it only takes some tens of seconds to fix, from time to time.
I can't remember if I also did all the wiping, I think I didn't, but I made so many trials in a couple days, I am not sure.
Thanks a lot guys!
am05 said:
I've read in some CM thread on here you need to flash stock ROM then enable GPS and get a lock. Once you've done that then flash your custom rom. Sounds STUPID and dosent make sense I know, but a lot of people say this is how they got it to work.
EDIT: I can confirm. I've just flashed stock 4.4.4 and played around with google maps. Flashed CM11 nightly and my GPS is now working ok
Click to expand...
Click to collapse
Yes, this worked for me too on PA.
I couldn't even see a single sat (it wasn't just a lock problem). No matter with gps patch, gpx fix app, or gps.conf I used.
What I did?: Back to stock, lock GPS, flash again the custom ROM (but don't wipe /system!).
Good luck on that guys, it should work for you too.
thestory101 said:
Hi all,
Did anyone able to use gps with custom rom ( I would say CM base). I research and try everything that's I could find here but not success.
Every time I do clean wipe everything including a internal storage. So that will nothing left behind.
I know that stock is work fine with gps. some said that install and replace stock but I have no idea that what file will left in our device when we delete all.
Click to expand...
Click to collapse
GPS works fine on this unofficial CM11 rom for me. Stable daily driver rom for me, YMMV.
General advice is to:
- make sure you get a GPS lock on stock rom first
- flash CM11 (or other custom rom)
There may not be a file left on the device. it may just be that stock contains the code to initialize the GPS functionality on the SoC or chipset firmware. Whatever, it works...
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!
So, this happened to me for the first time last night...My phone had charged 100% and so I removed the charger..Idk for some reason the battery drained overnight in about 4 and a half hours..when I woke up and went to check some notifications, I also found out some very very serious ghosting, not instant ghosting, the long lasting one...I don't really remember much about last night (was high) but I'll post some screen shots.
Look near the CPU in the top center of the screen..there's a small whitish circle which is a Snap from CNN on snapchat..and its not going away..not visible on white surfaces though.
Oh and BTW I'm on Sultan's ROM on 5.1.1 latest update (was stable until November, now some FCs and random reboots and whatnot, will migrate to Oxygen OS 2.2.0 by PMehra) with AK kernel.
go to mashmallo instead
#sychrome# said:
go to mashmallo instead
Click to expand...
Click to collapse
I did try Sultan's Marsh..But too buggy for me..suggest me a good ROM (with support for custom kernels please )
Xno3 said:
I did try Sultan's Marsh..But too buggy for me..suggest me a good ROM (with support for custom kernels please )
Click to expand...
Click to collapse
i have very stable check for correct twrp version and firmware and no su
Xno3 said:
So, this happened to me for the first time last night...My phone had charged 100% and so I removed the charger..Idk for some reason the battery drained overnight in about 4 and a half hours..when I woke up and went to check some notifications, I also found out some very very serious ghosting, not instant ghosting, the long lasting one...I don't really remember much about last night (was high) but I'll post some screen shots.
Look near the CPU in the top center of the screen..there's a small whitish circle which is a Snap from CNN on snapchat..and its not going away..not visible on white surfaces though.
Oh and BTW I'm on Sultan's ROM on 5.1.1 latest update (was stable until November, now some FCs and random reboots and whatnot, will migrate to Oxygen OS 2.2.0 by PMehra) with AK kernel.
Click to expand...
Click to collapse
You do realize AK kernel despite using anykernel isn't in line with Sultans latest changes to the ROM & kernel? Either way your camera seemed to have held a wakelock and drained your battery
Sent from my A0001 using Tapatalk
Renosh said:
You do realize AK kernel despite using anykernel isn't in line with Sultans latest changes to the ROM & kernel? Either way your camera seemed to have held a wakelock and drained your battery
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
That's what I thought after seeing the qcamera process in battery stats. Thanks for the confirmation! going to flash Sultan's Latest Marsh...last time I flashed it, the DPI settings were causing reboots and also random freezes plus I like stability so I flashed back to 5.1.1...hope the Feb update has got rid of it.
Plus did you notice the ghosting image? It's gone now but I was really worried!
#sychrome# said:
i have very stable check for correct twrp version and firmware and no su
Click to expand...
Click to collapse
Yea I am going to flash 6.0.1 now using 2.8.6.0 TWRP. Hope it isn't as buggy now because IMHO Sultan's Roms are the best!
I have the same 4hr battery life on my OPO. upgraded to latest CM12 but wanna go back to old Android Kitkat CM11 if i can.
Xno3 said:
Yea I am going to flash 6.0.1 now using 2.8.6.0 TWRP. Hope it isn't as buggy now because IMHO Sultan's Roms are the best!
Click to expand...
Click to collapse
upgrade ur unofficial twrp to 3.0 unofficial it solved many problems with me
Xno3 said:
So, this happened to me for the first time last night...My phone had charged 100% and so I removed the charger..Idk for some reason the battery drained overnight in about 4 and a half hours..when I woke up and went to check some notifications, I also found out some very very serious ghosting, not instant ghosting, the long lasting one...I don't really remember much about last night (was high) but I'll post some screen shots.
Look near the CPU in the top center of the screen..there's a small whitish circle which is a Snap from CNN on snapchat..and its not going away..not visible on white surfaces though.
Oh and BTW I'm on Sultan's ROM on 5.1.1 latest update (was stable until November, now some FCs and random reboots and whatnot, will migrate to Oxygen OS 2.2.0 by PMehra) with AK kernel.
Click to expand...
Click to collapse
Think there may have been an issue with his latest builds. I have moved away from both of his roms and went to all stock cm-12.1-20151117-SNAPSHOT and had 5 days on a charge, with a 0.6% drain/hr. I also don't use my phone much during the week, wifi on and switched to 3g. Might want to install better battery stats (you can find here on xda) and/or wakelock detector (playstore) and see what actually is killing your battery. Or just revert to an earlier build where these issues weren't present.
#sychrome# said:
upgrade ur unofficial twrp to 3.0 unofficial it solved many problems with me
Click to expand...
Click to collapse
version of twrp makes no difference, I've been using 2.8.6.0 for over a year now with no issues at all.
kenboyles72 said:
Think there may have been an issue with his latest builds. I have moved away from both of his roms and went to all stock cm-12.1-20151117-SNAPSHOT and had 5 days on a charge, with a 0.6% drain/hr. I also don't use my phone much during the week, wifi on and switched to 3g. Might want to install better battery stats (you can find here on xda) and/or wakelock detector (playstore) and see what actually is killing your battery. Or just revert to an earlier build where these issues weren't present.
version of twrp makes no difference, I've been using 2.8.6.0 for over a year now with no issues at all.
Click to expand...
Click to collapse
but yesterday I lost everything still didn't achieve my goal and After flashing .u know ?
Sent from my A0001 using Tapatalk
#sychrome# said:
but yesterday I lost everything still didn't achieve my goal and After flashing .u know
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I hear ya, been there, done that. Lost some of my files, but most were already saved on pc. I do a backup of my sdcard once a week, just in case. A month or so ago, I did a clean update to a new build of Sultan's CM13 caf rom and I was caught in a bootloop. I tried everything to solve this and had no luck. I could however flash cm13 nighlies and RR rom no issues, but as soon as I flashed cm13 caf rom, went to bootloop. Finally fastboot flashed official cm11s factory image and started fresh. Since then I have had no problems. There were a lot of other people with this issue, so there was something in his rom that was jacked somewhere. I did go back to Sultan's cm13 rom for a bit, but didn't run as good as his earlier builds, so went to his cm12 rom. After the latest upstreams from CM, phone performance started to go down hill. So, I just said the hell with it and went to stock cm-12.1-20151117-SNAPSHOT and everything is stable and running like it should. May flash a dif kernel in a day or so, but right now, everything is running fine. Like I said, I got 5 days on a charge with minimal usage as I don't use phone during the week. I don't have time to use phone when working and to damn tired after work. Think I had around 2hr SOT.
kenboyles72 said:
I hear ya, been there, done that. Lost some of my files, but most were already saved on pc. I do a backup of my sdcard once a week, just in case. A month or so ago, I did a clean update to a new build of Sultan's CM13 caf rom and I was caught in a bootloop. I tried everything to solve this and had no luck. I could however flash cm13 nighlies and RR rom no issues, but as soon as I flashed cm13 caf rom, went to bootloop. Finally fastboot flashed official cm11s factory image and started fresh. Since then I have had no problems. There were a lot of other people with this issue, so there was something in his rom that was jacked somewhere. I did go back to Sultan's cm13 rom for a bit, but didn't run as good as his earlier builds, so went to his cm12 rom. After the latest upstreams from CM, phone performance started to go down hill. So, I just said the hell with it and went to stock cm-12.1-20151117-SNAPSHOT and everything is stable and running like it should. May flash a dif kernel in a day or so, but right now, everything is running fine. Like I said, I got 5 days on a charge with minimal usage as I don't use phone during the week. I don't have time to use phone when working and to damn tired after work. Think I had around 2hr SOT.
Click to expand...
Click to collapse
good luck and I am real sad for the potential of phone.it could serving u Right but it is torturing u.its funny that though 2 same things in nature yet so much diff[emoji3]
Sent from my A0001 using Tapatalk
Okay so i have TWRP 3.0.2.0 modded for multirom and multirom installed on my phone and it was working okay for a long time now all of a sudden my phone randomly reboots and ALL 7 roms in mutli rom boot loop when you try to boot them. so i erased all of them and reflashed the rom, the second i flash anything other than the rom, kernel,mods, stupid files, literally ANYTHING but the rom it bootloops again and it never did this before all of these files worked together before, so i rewrote the twrp and mutlirom and all, figuring maybe that would help, it did not. so i thought okay, fine i will do an RUU and go to stock. it says the firmware is mismatched? so because of S-ON i cant restore to stock now. ( same one ive been using to RUU it for over a year anytime necessary )
literally everything i try i just end up with Bootloops. if i flash ONLY the rom it boots fine but the kernels tend to kill the battery really bad so i usually flashed a custom one and i just dont understand how the same kernel and files ive been using for like the last 8 month now are bootlooping every time. i tried looking for new roms too, nothing works. i also tried plain stock TWRP and no mutlirom, same results, bootloops if anything more than the plain rom is flashed.
also my battery seems to be dying like a rock now, unplugged it and within like 10 min i had lost 18%
universelove said:
Okay so i have TWRP 3.0.2.0 modded for multirom and multirom installed on my phone and it was working okay for a long time now all of a sudden my phone randomly reboots and ALL 7 roms in mutli rom boot loop when you try to boot them. so i erased all of them and reflashed the rom, the second i flash anything other than the rom, kernel,mods, stupid files, literally ANYTHING but the rom it bootloops again and it never did this before all of these files worked together before, so i rewrote the twrp and mutlirom and all, figuring maybe that would help, it did not. so i thought okay, fine i will do an RUU and go to stock. it says the firmware is mismatched? so because of S-ON i cant restore to stock now. ( same one ive been using to RUU it for over a year anytime necessary )
literally everything i try i just end up with Bootloops. if i flash ONLY the rom it boots fine but the kernels tend to kill the battery really bad so i usually flashed a custom one and i just dont understand how the same kernel and files ive been using for like the last 8 month now are bootlooping every time. i tried looking for new roms too, nothing works. i also tried plain stock TWRP and no mutlirom, same results, bootloops if anything more than the plain rom is flashed.
also my battery seems to be dying like a rock now, unplugged it and within like 10 min i had lost 18%
Click to expand...
Click to collapse
Try a different twrp version worked for me awhile ago when I had it
Thank you for the suggestion but as it says above i have tried that. this phone will not let me restore or use anything without google play now so im probably just going to get rid of it or smash it because ive been trying for weeks and NOTHING works.
only android 7+ roms boot, cant RUU, no home button menus, notifications or anything work without google installed so my phone has some weird new firmware on it and is forcing me to use the most up to date android/google play or it just wont work at all.
Update: charger port just quit working, probably burned up from getting so hot with all the battery over use, phone is officially dead now.