Related
R there any new kernel for Mondrian wifi sm-t320
i tried several time to upgrade to lollipop and marshmallow device work fine for 5 days or less, after that it become dead
i have to wait 3or 4 days it restart again and i go back to stock rom .
What's wrong with the Kernel as it is! I mean as a T325 (LTE), owner I'm kinda jealous of the fact that the T320 (WiFi), has all the support it has. Having compiled my own build of CM-12.1 (i.e. Lollipop), by using the same mondrianwifi Kernel (from CyanogenMod). Everything that needs to work just does. The same could be said for Marshmallow (CM-13.0), but I'm not quite able to get the Phone bits working, and the unofficial nightlies that are being created crpalmer. Are all outta date by a good month now.
So I'm a bit confuse as to what your problem is since you should just be able to flat out install pre-built images though TWRP Recovery. And, should CyanogenMod not be your 'thing' there are a few more options to you, that again as a T325 user I do not have.
sorry i cannot understand what do u main
I can not upgrade
Device stops working completely
After the upgrade to 5 or 6 days
But it does not stop working after many days
Some of them advised me to upgrade the kernel
Now that I have a root
And also TWRP Recovery.
The version used 13 cm but the machine stopped working.
Now promised to KIT KAT
Hey Guys how's it going ... I'm having a little trouble getting twrp touch screen to work , running latest update 8.1 dec patch ...read many , many forum discussions here so i wouldn't make any mistakes but for some reason twrp touch is not responsive. Started from absolute stock brand new device , unlocked boot loader and critical and fastbooted pixel 2 xl twrp.img 3.2.1 and while in temporary twrp i flashed the twrp 3.2.1 zip and then the magisk 15.1 zip and absolutely nothing else and rebooted ....everything's fine except when i reboot in to twrp from my device, the touch screen does not work downloaded file from official twrp site and tried a couple times from scratch but never seems to change .... if there's something i've done wrong or if anyone might be able to help it would be very much appreciated and i apologize in advance if there is a solution on here that i haven't located yet
Mr. Blanco said:
Hey Guys how's it going ... I'm having a little trouble getting twrp touch screen to work , running latest update 8.1 dec patch ...read many , many forum discussions here so i wouldn't make any mistakes but for some reason twrp touch is not responsive. Started from absolute stock brand new device , unlocked boot loader and critical and fastbooted pixel 2 xl twrp.img 3.2.1 and while in temporary twrp i flashed the twrp 3.2.1 zip and then the magisk 15.1 zip and absolutely nothing else and rebooted ....everything's fine except when i reboot in to twrp from my device, the touch screen does not work downloaded file from official twrp site and tried a couple times from scratch but never seems to change .... if there's something i've done wrong or if anyone might be able to help it would be very much appreciated and i apologize in advance if there is a solution on here that i haven't located yet
Click to expand...
Click to collapse
Your issue has been well documented. From what I've read, it seems to be much more prevalent when using the stock kernel (boot.img) I would try flashing a custom kernel..ie..Flash, Elemental X, or electron to name a few. Hopefully that will solve your problem :good:
Yep, custom kernel seems to resolve it... I'm using Flash's latest.
Badger50 said:
Your issue has been well documented. From what I've read, it seems to be much more prevalent when using the stock kernel (boot.img) I would try flashing a custom kernel..ie..Flash, Elemental X, or electron to name a few. Hopefully that will solve your problem :good:
Click to expand...
Click to collapse
Thanks Badger , i really appreciate your help and suggestions ...i'm gonna give it a shot after work tonight
was on stock and having the touch issue... switched to flash kernel and all is well
dadoc04 said:
was on stock and having the touch issue... switched to flash kernel and all is well
Click to expand...
Click to collapse
thank you dadoc and also galaxyS for your guys support , really appreciate it !!! Do you notice any improvements using the Flash Kernal compared to stock ?
Mr. Blanco said:
thank you dadoc and also galaxyS for your guys support , really appreciate it !!! Do you notice any improvements using the Flash Kernal compared to stock ?
Click to expand...
Click to collapse
You'll have much more control over your kernel, such as, color control, gestures, memory, governors, schedulers, vibration, and wakelocks :good:
Badger50 said:
You'll have much more control over your kernel, such as, color control, gestures, memory, governors, schedulers, vibration, and wakelocks :good:
Click to expand...
Click to collapse
Thanks Badger .....between the Flash , Electron and ElementalX kernals , do you have a preference ?
Mr. Blanco said:
Thanks Badger .....between the Flash , Electron and ElementalX kernals , do you have a preference ?
Click to expand...
Click to collapse
Flash and Ex have been my 2 favorites for a long time. Flash does a great job keeping it up to date with upstream changes, and Ex has been a solid performer for many years. Can't go wrong with either :good::good:
Badger50 said:
Flash and Ex have been my 2 favorites for a long time. Flash does a great job keeping it up to date with upstream changes, and Ex has been a solid performer for many years. Can't go wrong with either :good::good:
Click to expand...
Click to collapse
agree 100% with what he said... been using flash since the 6p
using adb reboot recovery also works
Badger50 said:
Flash and Ex have been my 2 favorites for a long time. Flash does a great job keeping it up to date with upstream changes, and Ex has been a solid performer for many years. Can't go wrong with either :good::good:
Click to expand...
Click to collapse
Hey Badger i have a question , i'm on stock 8.1 dec patch . and wanted to flash Ex kernal but i've noticed that it and a couple other kernals are on jan patch ... if i flash kernal with new jan patch , will i still be able to revert back to factory image with dec patch ....as that is all that is available for my device presently
Mr. Blanco said:
Hey Badger i have a question , i'm on stock 8.1 dec patch . and wanted to flash Ex kernal but i've noticed that it and a couple other kernals are on jan patch ... if i flash kernal with new jan patch , will i still be able to revert back to factory image with dec patch ....as that is all that is available for my device presently
Click to expand...
Click to collapse
Yeah, no problem. When you flash your factory images, it will overwrite your system and return to stock kernel. Question, what do you mean by "that is all that's available for my device"? There are factory images for the P2XL on Google's site. Why not just upgrade to the January build?
Badger50 said:
Yeah, no problem. When you flash your factory images, it will overwrite your system and return to stock kernel. Question, what do you mean by "that is all that's available for my device"? There are factory images for the P2XL on Google's site. Why not just upgrade to the January build?
Click to expand...
Click to collapse
Thanks Badger . that's what i figured , but wanted to be safe as ive read you can't revert back but i'm assuming that's to the 8.0 os builds. Yeah i was all over it looking for my device build to flash the jan build but it's only showing the dec build for mine on the developers google site 8.1.0 (OPM2.171019.012, Dec 2017, Telus Only)
Mr. Blanco said:
Thanks Badger . that's what i figured , but wanted to be safe as ive read you can't revert back but i'm assuming that's to the 8.0 os builds. Yeah i was all over it looking for my device build to flash the jan build but it's only showing the dec build for mine on the developers google site 8.1.0 (OPM2.171019.012, Dec 2017, Telus Only)
Click to expand...
Click to collapse
im pretty sure you can use the version (OPM1.171019.013, Jan 2018)
as you see, there isn't a Telus only build for every single release.
Hopefully someone who is more familiar will chime in and give you some assurance
dadoc04 said:
im pretty sure you can use the version (OPM1.171019.013, Jan 2018)
as you see, there isn't a Telus only build for every single release.
Hopefully someone who is more familiar with chime in and give you some assurance
Click to expand...
Click to collapse
I was kind of wondering that myself as i've noticed that too about the available builds , never the less i really appreciate your help bro
Hi,
I am using Pixel2 and had same touch issue with TWRP and got a fix from other forum (Thanks to Google)
Before rebooting into recovery disable Ambient display in settings screen.
Settings -> Battery -> Ambient display >> Switch off Always On
Now try to reboot into TWRP and it should work.
If its still not working try with disabling all options under Ambient display option.
Thank You
tiniwings said:
Hi,
I am using Pixel2 and had same touch issue with TWRP and got a fix from other forum (Thanks to Google)
Before rebooting into recovery disable Ambient display in settings screen.
Settings -> Battery -> Ambient display >> Switch off Always On
Now try to reboot into TWRP and it should work.
If its still not working try with disabling all options under Ambient display option.
Thank You
Click to expand...
Click to collapse
Tried this solution doesnt work on my pixel 2
6alaal said:
Tried this solution doesnt work on my pixel 2
Click to expand...
Click to collapse
I know the P2 is a little different than the P2XL, but, have you tried disabling screen lock security and then fastbooting into twrp?
Badger50 said:
I know the P2 is a little different than the P2XL, but, have you tried disabling screen lock security and then fastbooting into twrp?
Click to expand...
Click to collapse
Yeah it's really weird all this happened lost my root after installing the screen fix module in magisk sorry I'm using the P2XL
My 5T will be arriving today (coming from the Moto X Pure Edition...just under 2 years old. Yucky!) and I'm reading about rooting. ADB/oem unlocking/fastboot/etc. are familiar territory for me. I just wanted to make sure of something quick: I saw the guide saying to get Codeworkx TWRP, but I also see TWRP has a dumpling recovery image. I'm kind of thinking regular TWRP is fine, but I'm always careful when unlocking bootloader/custom recovery/rooting. I figured I'd ask just to be sure.
The official TWRP has always had issues with encryption on this device. Basically it's been behind the curve on updates. Last I heard it's gotten better, but it's generally still recommended to use Codeworkx or Blu's version. Personally I'm using Codeworkx.
[RECOVERY][dumpling] TWRP 3.2.3 by codeworkx
Blu seems to be more updated at the moment and has Amoled, and Treble support for 5.1.5.
Not sure if codeworkx has amoled and treble...
https://forum.xda-developers.com/oneplus-5t/development/kernel-t3706295
DOWNLOAD KERNEL ZIP and RECOVERY
https://forum.xda-developers.com/devdb/project/?id=21949#downloads
twrp-3.2.3-x_blu_spark_v9.85_treble-op5_op5t.img works really nice for me on 5.1.5
Thanks for the replies! :highfive: I went with blu's version and have had no problems. I think I read somewhere (I can't find it agian, obviously...) that for a nandroid backup all screen lock safety has to be removed or encryption will prevent a restore. Would this be accurate? There's a lot of new stuff I'm trying to get used to with my 5T, coming from a closer to stock Android MXPE, especially the world of encryption. I wanted to try out some custom ROMs and wanted to make sure if I didn't like it I could restore to OOS easy. Apologies if there's a guide somewhere on the 5T forums...I've had this for 2 days now. Love it.
Another question about custom ROMs; are they as snappy as OOS? Every other Android phone I've had sacrificed speed for customization with custom ROMs. I miss the closer to stock Android look, but it's no deal breaker. I also really miss the option to make the volume buttons only control media. I tried Gravitybox for Oreo (Magisk + Systemless Xposed), but it wouldn't work.
@Moppusan with experience anything is just as snappy as anything else...
I deblot OOS and run microG on it, then if you know your way around Kernels, you can stick in EX Kernel Manager, or Kernel Adiutor and tweak up the stock kernel and get it smoother, or faster, overclock, get real crazy... RenderZenith seems like a nice kernel for OOS, it's a newer kernel version with newer features that seem to perform over stock.
It seems like, if OnePlus gave us a newer kernel version then we could have some nice newer kernel features in a stock kernel. OOS 5.1.5 is on 4.4.78 So maybe the next release of OOS will see a nicer more up to date version... Maybe some one running the latest beta can tell us what version it's on?
I'm getting ready to put up a guide, hopefully in a few weeks about doing the debloating and microG on OOS.
Remember OOS is a Custom Rom, from OnePlus...
@DoR3M3, well...yeah that is another way to look at it. OOS being a custom ROM.
I'm probably in the intermediate level of Kernel knowledge. I bought the pro/premium/donate/whatever-he-calls-it version of Kernel Adiutor and have read plenty of guides on cpu/gpu governors, hot plugs, over/underclocking, input boost, voltage, storage...governors?, net congestion and blah blah blah. I think the only thing that's really over my head is the tunables for the cpu governors. I've just found settings other people have tested and try it myself.
It would be great seeing such a guide ! Was thinking about a journey into the mirco land but my laziness holds me back :/
Moppusan said:
@DoR3M3, well...yeah that is another way to look at it. OOS being a custom ROM.
I'm probably in the intermediate level of Kernel knowledge. I bought the pro/premium/donate/whatever-he-calls-it version of Kernel Adiutor and have read plenty of guides on cpu/gpu governors, hot plugs, over/underclocking, input boost, voltage, storage...governors?, net congestion and blah blah blah. I think the only thing that's really over my head is the tunables for the cpu governors. I've just found settings other people have tested and try it myself.
Click to expand...
Click to collapse
OOS is a Custom ROM, the only difference is that OnePlus is a manufacture, and because of Google's licensing, has to include the Gapps. But, I wonder if OnePlus can put up OOS for download on their site, that is GappsFree, now that would be nice!
If you're not running Linux and you are into Android, I highly recommend it. Of course there are things specific to Android, but it comes from Linux and running Linux makes the journey easier.
AlMustansir said:
It would be great seeing such a guide ! Was thinking about a journey into the mirco land but my laziness holds me back :/
Click to expand...
Click to collapse
I'm still working on it, been typing away on it today. Also added in an extra section for the Privacy Geeks, I figured out how to do the Play Store anonymously for getting paid apps...
DoR3M3 said:
OOS is a Custom ROM, the only difference is that OnePlus is a manufacture, and because of Google's licensing, has to include the Gapps. But, I wonder if OnePlus can put up OOS for download on their site, that is GappsFree, now that would be nice!
If you're not running Linux and you are into Android, I highly recommend it. Of course there are things specific to Android, but it comes from Linux and running Linux makes the journey easier.
Click to expand...
Click to collapse
I've tried Linux many times and I just can't get into it. The biggest drawback is the lack of serious DAWs (Digital Audio Workstations, if you didn't know) and gaming support (I don't think my PC could handle running anything smoothly through Wine).
Moppusan said:
I've tried Linux many times and I just can't get into it. The biggest drawback is the lack of serious DAWs (Digital Audio Workstations, if you didn't know) and gaming support (I don't think my PC could handle running anything smoothly through Wine).
Click to expand...
Click to collapse
If you need to be on Windows all the time, then run a VM like VirtualBox and run Linux on it, or dual boot Linux/Windows...
Moppusan said:
I've tried Linux many times and I just can't get into it. The biggest drawback is the lack of serious DAWs (Digital Audio Workstations, if you didn't know) and gaming support (I don't think my PC could handle running anything smoothly through Wine).
Click to expand...
Click to collapse
Well, Steam play can run many games with almost same performance than on windows.
----------------------------------------------------------------------------
Download link here: https://www.androidfilehost.com/?fid=7161016148664789606 (2021-08-05)
** CROSSHATCH (PIXEL 3 XL) FILE MISSING FOR 2021-08-05!! ALL OTHERS ARE GOOD.
Older Releases (not sure why I'm bothering, since newer releases will install fine on older A11 system versions, but whatever):
https://www.androidfilehost.com/?fid=14943124697586362458 (2021-07-05)
https://www.androidfilehost.com/?fid=14943124697586348210 (2021-06-05)
https://www.androidfilehost.com/?fid=2188818919693794137 (2021-05-05)
https://www.androidfilehost.com/?fid=2188818919693776406 (2021-04-05)
https://www.androidfilehost.com/?fid=17248734326145747020 (2021-03-05)
https://www.androidfilehost.com/?fid=17248734326145727328 (2021-02-05)
https://www.androidfilehost.com/?fid=17248734326145726589 (2021-01-05)
Edge Sense Plus has been hidden from the Play Store by the original dev, and I believe it won't show up unless you've previously added it to your account before it was officially discontinued. As far as most of us can tell, everything seems to still work fine (for now), but I've also seen a few people ask about the app scattered across these threads across the different Pixel devices. So here is a download link to the latest version of the APK.
Edge Sense Plus v1.32.0 APK: https://www.androidfilehost.com/?fid=7161016148664805712
Again, please don't expect any support from the dev since the mod has been discontinued by the original dev. Also, I'm not sure if you'll be able to unlock the pro features, nor what will happen if you attempt to pay for the pro license. Basic functionality, however, should work fine, at least for now. Also, it seems the app no longer properly recognizes whether the Magisk / Xposed mod is correctly installed, so it will likely always give you an error when you open it. Just hit ignore.
EDIT MARCH 2, 2021: THE ACTIVE EDGE MOD / EDGE SENSE PLUS PROJECT HAS OFFICIALLY BEEN RE-CONTINUED BY JAN'S DUDE, THE LEGENDARY TEAM VIPER MEMBER, MIKHAIL (@mikalovtch)!! NO NEED FOR ME TO CONTINUE MAKING THESE - PLEASE REFER TO THE MAGISK MANAGER REPO FOR FUTURE UPDATES. IT WAS FUN WHILE IT LASTED!!
SINCE IT HASN'T YET BEEN UPDATED AS OF TODAY THOUGH, I RAN MY SCRIPT AND BUILT FOR ALL PIXEL 3 / 3A / 4 VARIANTS AND UPDATED MY MODULE. PLEASE REFER TO DOWNLOAD LINK BELOW.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
(now updated to also install for 3 / 3 XL / 3a / 3a XL as well)
ONLY WORKS FOR PIXEL 4 XL "CORAL" AND PIXEL 4 "FLAME"!!!!
(WON'T EVEN INSTALL ON OTHER DEVICES, SO DON'T BOTHER)
tl;DR - A continuation of the "[Discontinued]Active Edge Mod for Pixel devices" Magisk module on the Magisk Module Repository, discontinued and last released for 2020-12-05 patch level. This is simply the same exact mod applied to the 2021-01-05 patch level. PLEASE DO NOT BOTHER THE ORIGINAL DEV FOR ANY SUPPORT - THIS IS AN UNOFFICIAL MOD.
As my wife and I love and can't live without, and basically purchased Pixel 4's, for the ability to retain the (advanced, custom) squeeze function that we've become so accustomed to over our years with the HTC U11 and U12+, I've modded the current month's SystemUIGoogle.apk file with the Active Edge Mod with the developer's permission. Please DO NOT bother him with any support requests and/or questions. Edge Sense Plus (the app itself) continues to work perfectly fine as far as I'm aware, and I only aim to continue keeping the Active Edge Magisk mod up to date for as long as I have the ability to do so. Also note that the Xposed Active Edge mod will continue to work in its capacity to remap short squeeze functions, though unfortunately since 01-2021 update we lose the long squeeze functionality without an updated Magisk module.
Since I've already done the work for our phone models, I decided to share it with you all. We really love this mod, and it brings back those sweet memories of the good ol' HTC days.
Again, PLEASE DO NOT ask the official developer for any support for this mod - this is an UNOFFICIAL continuation of his work!
Cheers, and long live Edge Sense Plus!
----------------------------------------------------
* Like I said, the original Edge Sense Plus dev gave me permission to modify and share this with you guys. This is just the base Active Edge / Edge Sense Plus magisk mod with no extras. This targets SystemUIGoogle.apk, and so will not play nicely with many of Tulsadiver's mods. Though if you're a regular user of his mods, you'll probably notice he often slipstreams the Active Edge mod option into his mods and offers separate packages - you'll need to refer to them if you use his mods.
All I wanted to do was bring Edge Sense Plus's advanced functionality back to our devices, updated to play nicely with the newest security patch levels. This is literally just an unofficial continuation of the Active Edge Mod that used to be offered on the Magisk Download Repository (now marked as [Discontinued]). AGAIN, PLEASE DON'T BOTHER J TO THE 4N (OR TULSADIVER FOR THAT MATTER) FOR ANY SUPPORT - THIS IS AN UNOFFICIAL MOD!
NOTE: Download link in the OP will install mod for the current patch level down to January 2021. It will detect your current patch level and install the correct file. For earlier system builds from 2020 and prior, please use the official discontinued module on the Magisk Manager repo. I did not clone the entire Active Edge Mod repository; my unofficial repository only hosts January 2021 and later builds.
Changes:
I know, I know... I said I was done with releasing my Unofficial Active Edge Mod installer, yet here's another month's update. I might keep doing it for those that update immediately and want it a bit sooner, so long as it's fortunate enough to happen on a day when I'm able to do it relatively quickly. Since I'm building these anyway and sending them over to the dev, for now, to upload to the official Magisk repo, for now I don't mind also updating it here a bit sooner. Anyway, more on this below and some of the headache involved moving forward...
04-05-2021: Soooo... the script I wrote to churn these out as quickly as possible as Google releases the updates, relied on system image dumps on GitRip... unfortunately the domain was seized by the FBI (lol) and so it looks like the old dumper is no longer updating his Android dumps repo on GitRip. Fortunately, mikalovtch pointed me over to a new source that hosts such system dumps, and I was able to get these done relatively quickly afterwards. OP is updated with the 04-05-2021 installer now!
03-02-2021: Meant to post an update a week or two ago. Noticed the magisk module on the official Magisk repo now says [RE-CONTINUED], so there really isn't much need for me to continue updating this anymore! As a final gift, I ran my batch builder script and built the modded apk's for all variants for the 2021-03-05 patch level, and download link for the module installer is in the OP.
02-02-2021: February 2021 mod is now uploaded. Updated installer is in the link in the OP.
02-01-2021: Modified and uploaded modded SystemUIGoogle.apk files for 3 / 3 XL / 3a / 3a XL to GitHub repository. Updated Magisk installer slightly to accommodate this, and removed a few unnecessary lines. Won't make any difference if you already installed the first release.
is there a chance for the unlocked active edge app? would also pay for it but is unfortunately no longer possible
IchiroKatsu said:
is there a chance for the unlocked active edge app? would also pay for it but is unfortunately no longer possible
Click to expand...
Click to collapse
Sorry, but I can't help you with that. Like I mentioned, I'm not at all affiliated with the original developers. However, I would encourage you to check out the dev's telegram - maybe they can help you there.
sorry, but i can't use it with edge sense plus. after flash modul via magisk, edge sense plus
announced 'magisk module required'.
fRuzzy said:
sorry, but i can't use it with edge sense plus. after flash modul via magisk, edge sense plus
announced 'magisk module required'.
Click to expand...
Click to collapse
using
Can you make sure the module is activated in Magisk Manager? If you updated to February patch level, depending on the order you did everything, the module might be disabled and greyed out. Also, you're using a Pixel 4 XL (or 3 or 3a) right? Also did you reboot after flashing?
fRuzzy said:
sorry, but i can't use it with edge sense plus. after flash modul via magisk, edge sense plus
announced 'magisk module required'.
Click to expand...
Click to collapse
Click on ignore
i5lee8bit said:
using
Can you make sure the module is activated in Magisk Manager? If you updated to February patch level, depending on the order you did everything, the module might be disabled and greyed out. Also, you're using a Pixel 4 XL (or 3 or 3a) right? Also did you reboot after flashing?
Click to expand...
Click to collapse
i'm using pixel 4xl, rooted, January patch level. thanks for create share this mod
IchiroKatsu said:
Click on ignore
Click to expand...
Click to collapse
i did it, thanks you
I ended up releasing for April 2021 firmware as well... I was going to stop, but this month was a bit complicated due to the closure of GitRip, requiring some tweaks to my build script. More details in 2nd post. Anyway, I figured I'll keep releasing my unofficial version anyway, at least for the time being. I'm basically using my script to build these really quickly in an automated fashion and sending them to the dev, who then updates the Magisk repo. So the official version on the Magisk repo won't take very long to get updated anyway, but maybe for those that like to update as soon as it drops may find this thread useful.
Gah! Everything was working fine on my Pixel 3, but I just installed the updated official Active Edge module that was released today, and I'm borked. Phone either bootloops or goes to the "corrupted" screen. Am I really going to have to factory reset and start over?
Edit...Whew! What a pain. It wouldn't even get through the stock firmware flashing process successfully until I manually flashed the stock boot image to both slots first. After that I was able to boot to stock, then reboot to safe mode, re-flashing the Magisk patched image along the way, then reboot with modules disabled and get everything working again.
Has anybody successfully flashed the new Active Edge module? I'm afraid to try again, but I do miss my squeeze for flashlight.
Hey guys, sorry about this month. I'm actually not sure because I didn't generate the files this month. Been so busy with fixing up the new house I haven't communicated with the dev yet this month; heck I haven't even updated my wife's Pixel either. Anyway, I'll take a look as soon as I can (probably won't be til at earliest tomorrow) and compare the hash checksums to see if maybe there was a silly mistake somewhere. Sorry for those that ran into problems, but I'm glad you got it all sorted out! Stay tuned for hopefully some good news and an update....
CSX321 said:
Gah! Everything was working fine on my Pixel 3, but I just installed the updated official Active Edge module that was released today, and I'm borked. Phone either bootloops or goes to the "corrupted" screen. Am I really going to have to factory reset and start over?
Edit...Whew! What a pain. It wouldn't even get through the stock firmware flashing process successfully until I manually flashed the stock boot image to both slots first. After that I was able to boot to stock, then reboot to safe mode, re-flashing the Magisk patched image along the way, then reboot with modules disabled and get everything working again.
Has anybody successfully flashed the new Active Edge module? I'm afraid to try again, but I do miss my squeeze for flashlight.
Click to expand...
Click to collapse
I had the same issue after @mikalovtch updated the repo module.
I was able to adb shell in while at the white spinning G screen before the phone rebooted to corrupted message. Once in went into /data/adb/modules and rm -rf the ESP mod.
Went through this twice then notified him in the Telegram channel.
I've mostly reverted to just using ESP in non root mode (hide it from Magisk) since usually by the time we get a working mod it is time for monthly update again. It sucks to not have long squeeze, but double works (kind of a pain to pull off reliably though).
I appreciate the time that the devs put in to keeping this going, and sometimes when I'm too busy to update monthly I can still get a month or two of use from it.
Anybody try V.82 module yet?
OP updated... though Pixel 3 XL is missing. All others should work fine. If I noticed sooner that mikalovtch had already updated the official repo, I probably would have skipped, but whatever... Feel free to use the unofficial one or the official one.
newkydawg said:
Anybody try V.82 module yet?
Click to expand...
Click to collapse
Apologies again to everyone. I literally didn't get a chance to start building the files until tonight... only to realize it looks like Mikhail already updated the official repo with fixed files. Have you (or has anybody) tried the updated module yet? The comment on GitHub says that blueline and crosshatch were fixed.
Btw, unfortunately the dumps I usually source the SystemUIGoogle.apk files from didn't dump crosshatch (3 XL), or blueline (3) this month, so I manually pulled the file from the Pixel 3. But I still don't have the Pixel 3 XL file. Again, this was all before I noticed he had updated the official repo again and luckily it looks like he already took care of them. I know we're heading towards the end of the month already, but late is better than never I suppose... Can't wait til these bigger, more urgent new house projects are over with! This last week was basically dealing with 3 brand new toilets, but poorly placed water supply lines... and not realizing the new ones wouldn't fit til after one of the old ones was already taken out and thrown in the garbage. Among a million other projects... FUN!! I can't wait til I can get more than 3-4 hours of sleep in a row again, D:
i5lee8bit said:
Mikhail already updated the official repo with fixed files. Have you (or has anybody) tried the updated module yet? The comment on GitHub says that blueline and crosshatch were fixed.
Click to expand...
Click to collapse
Yes, the official v82 works on blueline. I appreciate the work you and Mikhail put into this!
I can relate on your house renovation work. I just went through one on our master bedroom and bath last year. It wasn't planned, but made necessary after the bath flooded when the tub drain seal failed. :-/ Since so much work had to be done anyway, we did some more things, including replacing faucets and the toilet.
So should we just grab the Edge Sense Plus apk online? Because it's no longer on the Play Store.
blksith0 said:
So should we just grab the Edge Sense Plus apk online? Because it's no longer on the Play Store.
Click to expand...
Click to collapse
It didn't show up for me when I searched either, but when I go here I can at least see this page with an "Installed" button:
https://play.google.com/store/apps/details?id=eu.duong.edgesenseplus
CSX321 said:
It didn't show up for me when I searched either, but when I go here I can at least see this page with an "Installed" button:
https://play.google.com/store/apps/details?id=eu.duong.edgesenseplus
Click to expand...
Click to collapse
Oh interesting. For me it's just a 404 page.
blksith0 said:
Oh interesting. For me it's just a 404 page.
Click to expand...
Click to collapse
Strange. I cleared my browser cache, and it still shows up. Are you signed into your Google account in your browser? I noticed that I get a 404 if I open it in incognito mode.
How is it possible pixel 6 pro to be faster and smoother on a beta version than stable android 12???
Fingerprint sensor is very good, brightness is higher than android 12 specially under sun and camera is far way more derailed than android 12 stable... Why is this happening? Are they trolling us?
Presumably because this is a beta build release that is much further ahead in the current development schedule. Keep in mind that stable Android 13 releases in about two months and a week or so (August is currently the scheduled release).
It wouldn't really be a great idea in development to only start optimizing your product for stability and performance after it releases. So, that is what they are working on now; optimizing the stability, speed and performance so that they can spend the last few months of development ensuring that the new system functionality works well and is a pleasant update for us Pixel 6 users.
Also, it's important to make sure that you are releasing a great OS build - especially when that OS version's effectiveness will aid in the sales of your upcoming smartphone product that is going to launch with it (the Pixel 7 series)!
So overall, there are *Noexcusses* for being crummy with your software development and management =). Google had suffered enough with their Pixel 6 series release as they were still lacking funds in their phone development department due to a crummy lawsuit. But as a result of that issue, I'm assuming that they are shaping themselves up for that upcoming Pixel series.
NippleSauce said:
Presumably because this is a beta build release that is much further ahead in the current development schedule. Keep in mind that stable Android 13 releases in about two months and a week or so (August is currently the scheduled release).
It wouldn't really be a great idea in development to only start optimizing your product for stability and performance after it releases. So, that is what they are working on now; optimizing the stability, speed and performance so that they can spend the last few months of development ensuring that the new system functionality works well and is a pleasant update for us Pixel 6 users.
Also, it's important to make sure that you are releasing a great OS build - especially when that OS version's effectiveness will aid in the sales of your upcoming smartphone product that is going to launch with it (the Pixel 7 series)!
So overall, there are *Noexcusses* for being crummy with your software development and management =). Google had suffered enough with their Pixel 6 series release as they were still lacking funds in their phone development department due to a crummy lawsuit. But as a result of that issue, I'm assuming that they are shaping themselves up for that upcoming Pixel series.
Click to expand...
Click to collapse
I want my phone better than pixel 3xl at least on camera and still it is not. Im using pixel phones from Nexus 6p..
There is no Beta 3 yet. The latest release is Beta 2.1 which has some bug fixes for Beta 2.
More info here
biohaz55 said:
There is no Beta 3 yet. The latest release is Beta 2.1 which has some bug fixes for Beta 2.
More info here
Click to expand...
Click to collapse
Ok then Beta 2,1!
Noexcusses said:
I want my phone better than pixel 3xl at least on camera and still it is not. Im using pixel phones from Nexus 6p..
Click to expand...
Click to collapse
And it will be. Beta 2.1 (on a newly wiped 6 pro) is excellent. Battery life has settled and is more consistent, image processing is getting better and so is the overall experience.
I also have the 3 XL and I remember that it took 6 months for the device to improve. When it was upgraded to A10, it was a different phone. This happens on all Pixels/Nexus devices. Software optimization takes time and is probably more visible on Google devices just due to the way they develop and improve their software over time (just different than apple or other oems, not necessarily better or worse)
Alekos said:
And it will be. Beta 2.1 (on a newly wiped 6 pro) is excellent. Battery life has settled and is more consistent, image processing is getting better and so is the overall experience.
I also have the 3 XL and I remember that it took 6 months for the device to improve. When it was upgraded to A10, it was a different phone. This happens on all Pixels/Nexus devices. Software optimization takes time and is probably more visible on Google devices just due to the way they develop and improve their software over time (just different than apple or other oems, not necessarily better or worse)
Click to expand...
Click to collapse
Hope so... Im on beta 2.1 also and i have realised brightness improvements and charging improvements too... Battery duration on 2.1 isn't so good as Android 12 but is fine as soon as is so early Beta.
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
NippleSauce said:
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
Click to expand...
Click to collapse
Patching the boot image works for me on A13B2.1. Direct install may cause bootloops though. If you encounter a bootloop using direct install you can just boot into the bootloader and flash your patched Canary 24313 (or whatever you were on) and it will boot and then patch the boot image rather than using direct install with 24314. No need to wipe the device, in my experience.
I also have verity and verification disabled.
Lughnasadh said:
Patching the boot image works for me on A13B2.1. Direct install may cause bootloops though. If you encounter a bootloop using direct install you can just boot into the bootloader and flash your patched Canary 24313 (or whatever you were on) and it will boot and then patch the boot image rather than using direct install with 24314. No need to wipe the device, in my experience.
I also have verity and verification disabled.
Click to expand...
Click to collapse
You're correct here. I forgot a few words in my original comment there, haha. It should have said "if the patched boot image was installed via Magisk". Sometimes I make comments too soon after rolling out of bed LOL.
Regardless, I did a full wipe and reinstall as I hadn't done my typical device setup when I had first upgraded to 13B2.1. I usually install all updates onto both slots (a and b), however, I hadn't done that initially. So a full wipe and installation onto both slots was required by my standard practices - as I wasn't even sure which one I was currently using, haha. Anyway, I've been trying to resolve some problem with Google Phone as the Visual Voicemail hasn't been working for me. So, I had figured a full wipe and reinstallation across both slots would have definitely resolved the boot loop as well as that visual voicemail problem....but it hasn't fixed the latter... =(
NippleSauce said:
You're correct here. I forgot a few words in my original comment there, haha. It should have said "if the patched boot image was installed via Magisk". Sometimes I make comments too soon after rolling out of bed LOL.
Regardless, I did a full wipe and reinstall as I hadn't done my typical device setup when I had first upgraded to 13B2.1. I usually install all updates onto both slots (a and b), however, I hadn't done that initially. So a full wipe and installation onto both slots was required by my standard practices - as I wasn't even sure which one I was currently using, haha. Anyway, I've been trying to resolve some problem with Google Phone as the Visual Voicemail hasn't been working for me. So, I had figured a full wipe and reinstallation across both slots would have definitely resolved the boot loop as well as that visual voicemail problem....but it hasn't fixed the latter... =(
Click to expand...
Click to collapse
Here's Google's workaround for visual voicemail bug on Android 13 betas
Rolling back to a v81 release of the Phone by Google app can fix the issue
www.androidpolice.com
uicnren said:
Here's Google's workaround for visual voicemail bug on Android 13 betas
Rolling back to a v81 release of the Phone by Google app can fix the issue
www.androidpolice.com
Click to expand...
Click to collapse
Thank you for this! Unfortunately, downgrading the phone app to V81 didn't resolve the issue. I have also tried some of the other methods that were being discussed in that Reddit post but haven't had any luck with those tricks either.
I'm going to try removing myself from the Google Phone Beta next though. Worst comes to worst (if removing myself from the phone beta list doesn't work), I'll have to wait a few weeks for the next Android 13 beta update.
Woah! This is offtopic but the pictures are so good! You're lucky that you have a pixel 6 pro
NippleSauce said:
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
Click to expand...
Click to collapse
Im not rooted sir
notnoelchannel said:
Woah! This is offtopic but the pictures are so good! You're lucky that you have a pixel 6 pro
Click to expand...
Click to collapse
On android 13 beta 2,1 photos are much better than android 12...
NippleSauce said:
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
Click to expand...
Click to collapse
I updated to A13 beta 2.1 without a full wipe, using canary 24314 just fine. I did of course disable all modules before installing the A13 update.I also removed the -w command in the flash all bat file.
Amd4life said:
I updated to A13 beta 2.1 without a full wipe, using canary 24314 just fine. I did of course disable all modules before installing the A13 update.I also removed the -w command in the flash all bat file.
Click to expand...
Click to collapse
It seems to be a known error after clean wipe updates to the latest A13 beta build based on @uicnren 's post. According to users on the Reddit thread, the issue has to do with the beta and a current OS build miscommunication with the phone carriers in the United States. So, if this is truly the case, users experiencing this issue won't have it resolved until the next beta build release (or later). Time will tell =)
I'm abut ready to jump in and load the 13 beta on my P6 and wanted to know it there are any hotspot issues since that would be the one deal breaker for me.
Does anyone know When would be next Beta update?
Thanks...