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.
Major credits again to @zachariahpope for the Lollipop build earlier tonight. Unfortunately getting it rooted from stock won't work. Which is why I proceeded to try the same method from my rooting guide to attempt root. And I am proud to say...I HAVE THE ROOTED LOLLIPOP SONY XPERIA Z3V!!!
And also, I have recovery as well.
If you're going to follow in the same footsteps, please PLEASE remember when you get the supersu file, grab the v2.49 as that is for LOLLIPOP.
@GigaSPX Make one of these in the development section too!!
well, looks like its time to flash
I thought this day would never come!!
Sent from my D6708 using Tapatalk
where is it? can I just root the phone when I Flash it back to stock root from there and not take the OTA and go straight to the pre-root for Lolipop?
GhostTrunks said:
where is it? can I just root the phone when I Flash it back to stock root from there and not take the OTA and go straight to the pre-root for Lolipop?
Click to expand...
Click to collapse
If you want root, you need to preroot. Otherwise, you won't have it at all.
Also this is an update: it seems it's still Verizon holding all of us by the edge about VoLTE. I tried activating it but it won't work. Still can't browse and call at the same time dammit.
Is this patched for Stagefright?
rooted lollipop for z3v ,,,,,,,,,, congrats
1linuxfreak said:
Is this patched for Stagefright?
Click to expand...
Click to collapse
Unfortunately... no.
GigaSPX said:
Unfortunately... no.
Click to expand...
Click to collapse
Giga, any success in actually using Advanced Calling? I can't seem to get it to work, even after "activating" it on the phone
srsaloom said:
Giga, any success in actually using Advanced Calling? I can't seem to get it to work, even after "activating" it on the phone
Click to expand...
Click to collapse
No, that's what I've been trying to tell a lot of people now. It's still all in the hands of the big red...
srsaloom said:
Giga, any success in actually using Advanced Calling? I can't seem to get it to work, even after "activating" it on the phone
Click to expand...
Click to collapse
You must also activate it from your vzw account.
GigaSPX said:
No, that's what I've been trying to tell a lot of people now. It's still all in the hands of the big red...
Click to expand...
Click to collapse
Figured so, just wasn't sure if I'd missed a memo somewhere along the way. Appreciate it!
Delebird said:
You must also activate it from your vzw account.
Click to expand...
Click to collapse
srsaloom said:
Figured so, just wasn't sure if I'd missed a memo somewhere along the way. Appreciate it!
Click to expand...
Click to collapse
Yeah, and can't activate it on the Verizon account when it won't let you to.
Has anyone tried installing Xposed? I can't flash to install.
GigaSPX said:
Has anyone tried installing Xposed? I can't flash to install.
Click to expand...
Click to collapse
Just installed it. v74-sdk21-arm . Gave me a little scare, as it hung on the Sony logo after rebooting. Also, upon that initial reboot, the lockscreen was vacant and couldn't get beyond what should've been there. Had to long-press power to bring up power menu and select reboot.
Following that, things seem to be working fine. Xposed Installer crashes if you click on xda support links in module pages, and the installation of xposed modules from within the Xposed installer can take significantly longer than it did on KK.
GigaSPX said:
No, that's what I've been trying to tell a lot of people now. It's still all in the hands of the big red...
Click to expand...
Click to collapse
Not sure if this helps, but, I jumped from this phone to the LG G4. We don't have much development but, some rooted users don't have advanced calling because they are rooted. I am a non-rooted user with advance calling. To add another variable to the equation, you have to have the My Verizon Mobile app installed and not disabled to at least initiate advanced calling. Some of the rooted users I think figured that out.
srsaloom said:
Just installed it. v74-sdk21-arm . Gave me a little scare, as it hung on the Sony logo after rebooting. Also, upon that initial reboot, the lockscreen was vacant and couldn't get beyond what should've been there. Had to long-press power to bring up power menu and select reboot.
Following that, things seem to be working fine. Xposed Installer crashes if you click on xda support links in module pages, and the installation of xposed modules from within the Xposed installer can take significantly longer than it did on KK.
Click to expand...
Click to collapse
Big thanks here. Fully updated now, and with this tip I'm running xposed as well.
Uninstalled old xposed first (may not have been necessary)
TWRP dirty flashed pre-rooted 5.0.2 zip from post 44 of that lollipop dev thread
After boot TWRP isntalled v74-sdk21-arm module
Installed xposed_installer.apk and added back my most used modules
-chromepie
-xtether (still working )
Didn't bother with xperiaxposed, not even sure if it's updated. Never really used it
Also, I like this boot animation, not that it's of any importance http://forum.xda-developers.com/z3/themes-apps/bootanimation-xperia-z3-t3079263
darker_slayer said:
Big thanks here. Fully updated now, and with this tip I'm running xposed as well.
Uninstalled old xposed first (may not have been necessary)
TWRP dirty flashed pre-rooted 5.0.2 zip from post 44 of that lollipop dev thread
After boot TWRP isntalled v74-sdk21-arm module
Installed xposed_installer.apk and added back my most used modules
-chromepie
-xtether (still working )
Didn't bother with xperiaxposed, not even sure if it's updated. Never really used it
Also, I like this boot animation, not that it's of any importance http://forum.xda-developers.com/z3/themes-apps/bootanimation-xperia-z3-t3079263
Click to expand...
Click to collapse
I did much the same but I did not uninstall xposed before I flashed and it wouldnt let me uninstall it after I upgraded to lollipop. But I flashed and installed the files above and it works great. Xperia Xposed works use v1.7 cause it's the only one that works.
Just wish there was a foolproof way to get rid of those useless small apps
darker_slayer said:
Just wish there was a foolproof way to get rid of those useless small apps
Click to expand...
Click to collapse
They're super useful to me, being all multitasking useful and all. loll
running h901-10c sirsltus
Phone is fricken amazing but got carried away flashing themes and mods. I have the right Xposed installed but lost the signature line. I had it working but between playing with Lg theme tool and g4 tweak box I cant get anything to show up on that top line.
I have uninstalled Xposed and all mods, still wont work. I re-flashed dirty.. nothing.. So before a reflash the right way I figured I would ask if anybody know of a way. If not.. a wiping I will go
budeone said:
running h901-10c sirsltus
Phone is fricken amazing but got carried away flashing themes and mods. I have the right Xposed installed but lost the signature line. I had it working but between playing with Lg theme tool and g4 tweak box I cant get anything to show up on that top line.
I have uninstalled Xposed and all mods, still wont work. I re-flashed dirty.. nothing.. So before a reflash the right way I figured I would ask if anybody know of a way. If not.. a wiping I will go
Click to expand...
Click to collapse
Try using titanium to clear second screen data and sb signature data.. My mod isn't deodexed so it will def have issues on a deodexed rom.
Swizzle82 said:
Try using titanium to clear second screen data and sb signature data.. My mod isn't deodexed so it will def have issues on a deodexed rom.
Click to expand...
Click to collapse
It did not work, but thanks for the idea. It was a good one.
Xposed mod works on the lg v10 h901 20j ?
budeone said:
It did not work, but thanks for the idea. It was a good one.
Click to expand...
Click to collapse
Off hand I don't know the exact files that relate to the secondscreen ui. So personally I would find one of the old xposed second screen fix files or use surrounding info to determine what files relate to the second screen. I would extract those from my current Rom zip, or as near as I can, and write a flushable zip using the needed files. You might be able to use the file explorer in twrp, but I have barely used it and don't know it can replace files like that.
Its LGSignBoard
I wish I knew exactly what caused this to happen. I was using a Malaysk ROM and starting having the issues. I thought maybe it was the ROM so I downgraded back to the original ROM that came with my unit and I'm still having the same issues. I downgraded through system updates in settings.
I can get it to boot into recovery, but it's just a black screen with pulsating light blue lights on the side of my unit. I have a Joying RK3188 1024x600 with the touch buttons on the left side.
Also when the unit boots up I don't get the Android splash screen anymore, it's also black. The first sign of life is when the car logo screen pops up.
There have also been multiple cases where when I am using the unit the screen has turned black ( if the radio is playing it will continue to play though ) and I can't do anything on the screen. This has to be a related issue.
Does anyone have any idea whats going on here?
I appreciate any help I can get!
Anyone have any ideas?
ahfunaki said:
Anyone have any ideas?
Click to expand...
Click to collapse
Try reflashing both MCU and ROM.
Use USB method for recovery of brick unit.
Or try reflashing from GPS card by mimicking procedure as it should be done on screen working even if you don't see it (look for screenshots of recovery and try to perform needed actions - somewhere here was such hint for someone whose screen brightness was completely darked out and has to perform factory reset from recovery on the blind).
pa.ko said:
Try reflashing both MCU and ROM.
Use USB method for recovery of brick unit.
Or try reflashing from GPS card by mimicking procedure as it should be done on screen working even if you don't see it (look for screenshots of recovery and try to perform needed actions - somewhere here was such hint for someone whose screen brightness was completely darked out and has to perform factory reset from recovery on the blind).
Click to expand...
Click to collapse
What is USB method? Just load the files on to a flash drive?
And I've found a picture of the recovery menu and I've tried that multiple times with no success.
Thank you for your help!
pa.ko said:
Try reflashing both MCU and ROM.
Use USB method for recovery of brick unit.
Or try reflashing from GPS card by mimicking procedure as it should be done on screen working even if you don't see it (look for screenshots of recovery and try to perform needed actions - somewhere here was such hint for someone whose screen brightness was completely darked out and has to perform factory reset from recovery on the blind).
Click to expand...
Click to collapse
Putting the stock MCU and ROM on the GPS card fixed it! I did the update from the settings menu and it worked! I have recovery again! Thank you so much for the help!
I really want to install the custom ROM again, but I really don't want to keep having this issue though. Does anyone have any idea what is causing this to happen?
ahfunaki said:
Putting the stock MCU and ROM on the GPS card fixed it! I did the update from the settings menu and it worked! I have recovery again! Thank you so much for the help!
I really want to install the custom ROM again, but I really don't want to keep having this issue though. Does anyone have any idea what is causing this to happen?
Click to expand...
Click to collapse
I had bad experience with MCU v2.83
After some time it started to make touch screen not working, factory settings pass not recognising standard 126 etc.
After restart - all normal. Then for no reasons next day problems rrapear...
Reverting to stock v2.80 resolves issue. And Nalaysk ROM works with no prob.
So, if you upgraded MCU - that may be a reason.
If not, then maybe your ROM file was corrupted. Or your internal memory got corrupted somehow.
My prob with newer MCU, not working on cold morning first start but working after reset, points out that there is some HW related issue. With new version only though! Figure it out...
pa.ko said:
I had bad experience with MCU v2.83
After some time it started to make touch screen not working, factory settings pass not recognising standard 126 etc.
After restart - all normal. Then for no reasons next day problems rrapear...
Reverting to stock v2.80 resolves issue. And Nalaysk ROM works with no prob.
So, if you upgraded MCU - that may be a reason.
If not, then maybe your ROM file was corrupted. Or your internal memory got corrupted somehow.
My prob with newer MCU, not working on cold morning first start but working after reset, points out that there is some HW related issue. With new version only though! Figure it out...
Click to expand...
Click to collapse
I never updated the MCU so I'm really not sure what happened.
I'm actually don't mind using the stock ROM minus the fact I've already ran out of storage, is there anything I can do about that? So many things are working better for me now. Before I wasn't able to get an OBDII adapter to connect to torque and now it works perfect.
I'd love to go back to the Malaysk ROM but I just had so many issues...
Use link2sd to store your apps on an external sd card.
Sent from my SM-G920F using Tapatalk
ahfunaki said:
I never updated the MCU so I'm really not sure what happened.
I'm actually don't mind using the stock ROM minus the fact I've already ran out of storage, is there anything I can do about that? So many things are working better for me now. Before I wasn't able to get an OBDII adapter to connect to torque and now it works perfect.
I'd love to go back to the Malaysk ROM but I just had so many issues...
Click to expand...
Click to collapse
There is also another ROM, look for thread named Interesting ROM with FUSE support.
It is almost stock but with FUSE partitioning so you have all space for both sys app and data.
BTW your prob with OBD2 is known issue in Malaysk ROM if you enabled xposed BT module.
gk66 said:
Use link2sd to store your apps on an external sd card.
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
I actually tried that, but I couldn't get it to run on boot. It didn't seem like it was working too well for me but maybe I was just doing something wrong.
pa.ko said:
There is also another ROM, look for thread named Interesting ROM with FUSE support.
It is almost stock but with FUSE partitioning so you have all space for both sys app and data.
BTW your prob with OBD2 is known issue in Malaysk ROM if you enabled xposed BT module.
Click to expand...
Click to collapse
I will look into this, thanks again!
ahfunaki said:
I actually tried that, but I couldn't get it to run on boot. It didn't seem like it was working too well for me but maybe I was just doing something wrong.!
Click to expand...
Click to collapse
You need to root your head unit. Use the root code from the wiki. Then install super su and give permissions to link2sd. Remember to properly partition sd card ss well
Sent from my SM-G920F using Tapatalk
gk66 said:
You need to root your head unit. Use the root code from the wiki. Then install super su and give permissions to link2sd. Remember to properly partition sd card ss well
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
Thank you for the help, I ended up just installing that other rom with FUSE so everything is good now.
Really enjoying this thing...
ahfunaki said:
Putting the stock MCU and ROM on the GPS card fixed it! I did the update from the settings menu and it worked! I have recovery again! Thank you so much for the help!
I really want to install the custom ROM again, but I really don't want to keep having this issue though. Does anyone have any idea what is causing this to happen?
Click to expand...
Click to collapse
How did you doing this, did you do this from the system update menu? I have same problem but if I try your way, I only get a black screen.
MueKo said:
How did you doing this, did you do this from the system update menu? I have same problem but if I try your way, I only get a black screen.
Click to expand...
Click to collapse
Please check the solution here:
http://forum.xda-developers.com/showpost.php?p=66415327&postcount=3139
oscyp said:
Please check the solution here:
http://forum.xda-developers.com/showpost.php?p=66415327&postcount=3139
Click to expand...
Click to collapse
Thank you for your support. My problem was that my recovery image was damaged. I fixed it by reflashing the recovery image.
thx
I have the same problem now. I just went into recovery mode and installed update_4_4_4_FUSE_1024X600_RK3188_17_MAL_23_04_2016.
All was well until the Android loader image just sat there pulsing. The unit still had not started up after 40 mins of this logo being on screen.
Going into recovery mode just shows a black screen now. So my unit is effectively dead, or can it be rescued?
RS-TLS said:
I have the same problem now. I just went into recovery mode and installed update_4_4_4_FUSE_1024X600_RK3188_17_MAL_23_04_2016.
All was well until the Android loader image just sat there pulsing. The unit still had not started up after 40 mins of this logo being on screen.
Going into recovery mode just shows a black screen now. So my unit is effectively dead, or can it be rescued?
Click to expand...
Click to collapse
Anybody able to help me out here?
RS-TLS said:
Anybody able to help me out here?
Click to expand...
Click to collapse
Is it possible to start your device normal?
No. It just sits at the bootloader.
Sent from my SM-G928F using Tapatalk
Try in recovery mode to enter back in normal boot mode. It's difficult to explain in englisch. I had to pin a small needle into my radio and ca. 0,5 seconds before the LED are flashing, stop with pushing. When you stop pushing you must wait 5-10 second and see if you device boot up normal.
You have to try this often to find the correct moment. Thats how I entered back to normal boot mode.
I am not on Android P dp1 but made some mods based on the Android P apks.
Clock mods
Navbar height adjustment 30-48 dip
Internet Speed indicators
Battery icon remover
3 Minit Battery Mod (install MinitBatteryResources.apk first)
Enabled stock WiFi-Data in-out arrows
Custom one percent batteries
Colored statusbar icons
Colored Notification Backgrounds
Colored Notification Text
Colored QS backgrounds
Colored QS text
3,4,5,6,7 column QS tiles
Navbar swap of back and recents
Invisible power menu button in far right hand corner of statusbar. Tap closes the screen, long press brings up the power button menu.
Remove carrier text
Remove NavBar completely, choices of 3,4,5,6,7 column QS.
Invisible home button on far left of status bar option in case LMT or other mods don't start on reboot.
Flash the base first. It is in the first menu. After that you can flash away. No need to boot between flashing. There is a stock restore option as well.
Edit: AOD version clocks show up on lockscreen instead of the system icons. Can't seem to get all off together.
Aroma dp1
https://www.androidfilehost.com/?fid=818070582850506348
Tulsadiver said:
I am not on Android P dp1 but made some mods based on the Android P apks.
Aroma dp1
https://www.androidfilehost.com/?fid=818070582850506157
Click to expand...
Click to collapse
Thank you for this. I'm not on P right now or I would just flash and find out, but can you give any insight as to what is included?
Thanks again for sharing. :good:
Namolas said:
Thank you for this. I'm not on P right now or I would just flash and find out, but can you give any insight as to what is included?
Thanks again for sharing. :good:
Click to expand...
Click to collapse
My bad. Updated op. Same as my other aroma thread.
Thanks for this. Find a little bug.
Whatever option I choose for center clock (day /am/pm) I always got 2 clocks on status bar when I boot up.
See the screenshot.
I m on P Of course.
If u need any log let me know.
Tulsadiver said:
My bad. Updated op. Same as my other aroma thread.
Click to expand...
Click to collapse
I was really interested in trying this so I flashed the Android P preview to both slots, boot and set up as new device. But then after installing the mod installer I am getting "Your device is corrupt" prompt several times and then it doesn't boot.
Any idea how to avoid this or what caused it?
EDIT: Thought I could just boot back into recovery and flash the stock restore option but I can't get into recovery at all. Even fastboot TWRP image just gets me to the "Your device is corrupt." screen and I cannot proceed. No big deal as I have everything backed up properly, but just wondering how to avoid this next time?
Namolas said:
I was really interested in trying this so I flashed the Android P preview to both slots, boot and set up as new device. But then after installing the mod installer I am getting "Your device is corrupt" prompt several times and then it doesn't boot.
Any idea how to avoid this or what caused it?
EDIT: Thought I could just boot back into recovery and flash the stock restore option but I can't get into recovery at all. Even fastboot TWRP image just gets me to the "Your device is corrupt." screen and I cannot proceed. No big deal as I have everything backed up properly, but just wondering how to avoid this next time?
Click to expand...
Click to collapse
Did you flash 3minit battery? Did you flash a base first?
dukat0s said:
Thanks for this. Find a little bug.
Whatever option I choose for center clock (day /am/pm) I always got 2 clocks on status bar when I boot up.
See the screenshot.
I m on P Of course.
If u need any log let me know.
Click to expand...
Click to collapse
The clock is in a different place. Forgot about that. I'll try and fix that and rerun my aroma.
What happens if you choose a right side clock?
Tulsadiver said:
The clock is in a different place. Forgot about that. I'll try and fix that and rerun my aroma.
What happens if you choose a right side clock?
Click to expand...
Click to collapse
Gimme a sec I try it
Tulsadiver said:
Did you flash 3minit battery? Did you flash a base first?
Click to expand...
Click to collapse
Didn't flash any 3 minute battery stuff. Yes flashed the base first unless I misunderstood how that works. You said flashing base would be at the end but it's the very first thing you have to do before it will continue.
I chose,
WiFi data arrows
30 point navbar
Swap navbar buttons
Remove battery icon
7 column QS tile
Tulsadiver said:
The clock is in a different place. Forgot about that. I'll try and fix that and rerun my aroma.
What happens if you choose a right side clock?
Click to expand...
Click to collapse
Here my friend. If I choose right side clock its work fine
Namolas said:
Didn't flash any 3 minute battery stuff. Yes flashed the base first unless I misunderstood how that works. You said flashing base would be at the end but it's the very first thing you have to do before it will continue.
I chose,
WiFi data arrows
30 point navbar
Swap navbar buttons
Remove battery icon
7 column QS tile
Click to expand...
Click to collapse
It is possible to skip selecting a base so you don't have to start from scratch each time to add or change a mod. Which base did you pick?
Tulsadiver said:
It is possible to skip selecting a base so you don't have to start from scratch each time to add or change a mod. Which base did you pick?
Click to expand...
Click to collapse
So I started again from fresh factory image again just now,
Flash "SystemUIbase Signal"
Next, Next, Install.
Then Install in TWRP again, this time choosing,
"Traffic Speed Single" Traffic Right,
"Navbar Height" Dynam30,
"Navbar" Swap Navbar Swap 30,
"Remove Battery Icon" Remove Battery Icon7 Col QS WiFi up-down,
"QS Column Options" SystemUI7QS Column
Next, Install, Reboot
Your Device is corrupt!
Namolas said:
So I started again from fresh factory image again just now,
Flash "SystemUIbase Signal"
Next, Next, Install.
Then Install in TWRP again, this time choosing,
"Traffic Speed Single" Traffic Right,
"Navbar Height" Dynam30,
"Navbar" Swap Navbar Swap 30,
"Remove Battery Icon" Remove Battery Icon7 Col QS WiFi up-down,
"QS Column Options" SystemUI7QS Column
Next, Install, Reboot
Your Device is corrupt!
Click to expand...
Click to collapse
Flash again and flash stock. Try those again minus traffic speed.
Tulsadiver said:
Flash again and flash stock. Try those again minus traffic speed.
Click to expand...
Click to collapse
Ok. I tried again without the traffiic indicators.. Same result. Sorry to muddy up your thread.... I'm just gonna let it go. Log is attached if it gives you any helpful info.
Thanks for all your help.
EDIT: So its driving me nuts that this isn't working for me so I tried again. Flashed P to both slots WITH wipe ( I NEVER flash without the -w), setup, boot TWRP and installed just the base and reboot and I get the corrupt device error. Got that log too but its too big to upload.
So I can't even get past flashing the base. Seeing as how nobody else is having the problem it must be something I am doing specifically. (although I can't see any fault in my flashing methods). I'm happy to try anything anybody suggests but as things sit now, I give up.
dukat0s said:
Thanks for this. Find a little bug.
Whatever option I choose for center clock (day /am/pm) I always got 2 clocks on status bar when I boot up.
See the screenshot.
I m on P Of course.
If u need any log let me know.
Click to expand...
Click to collapse
Can you try this one? Just trying some things.
https://www.androidfilehost.com/?fid=818070582850506348
Tulsadiver said:
Can you try this one? Just trying some things.
https://www.androidfilehost.com/?fid=818070582850506348
Click to expand...
Click to collapse
Thanks this work great.
Namolas said:
Ok. I tried again without the traffiic indicators.. Same result. Sorry to muddy up your thread.... I'm just gonna let it go. Log is attached if it gives you any helpful info.
Thanks for all your help.
EDIT: So its driving me nuts that this isn't working for me so I tried again. Flashed P to both slots WITH wipe ( I NEVER flash without the -w), setup, boot TWRP and installed just the base and reboot and I get the corrupt device error. Got that log too but its too big to upload.
So I can't even get past flashing the base. Seeing as how nobody else is having the problem it must be something I am doing specifically. (although I can't see any fault in my flashing methods). I'm happy to try anything anybody suggests but as things sit now, I give up.
Click to expand...
Click to collapse
If you flash 7 column remove battery, do not flash the SystemUI 7 column qs at the bottom. I probably should move that option up to the top. That is really for people that are only interested in a 7 col mod and nothing else. Also, you can only select one option per section. It appears you are trying to select more than one in some. Only the last one selected will install.
Hi Tudaviser,
Is there any way to apply different color to different QS toggles only for the round background (e.g wifi and mobile data are blue, battery is green...)?