Related
I'm trying to install Hyperdrive RLS10. The flash instructions say to install an AT&T build prop and I've also seen users mention that you will need to fix the google client database for the rom to function properly on AT&T. I can not locate any AT&T build prop to flash and do not know how to fix the google client database. Would anyone be able to help me so that I can get this rom working properly?
mrpoe222 said:
I'm trying to install Hyperdrive RLS10. The flash instructions say to install an AT&T build prop and I've also seen users mention that you will need to fix the google client database for the rom to function properly on AT&T. I can not locate any AT&T build prop to flash and do not know how to fix the google client database. Would anyone be able to help me so that I can get this rom working properly?
Click to expand...
Click to collapse
If you don't know how to do those, you might wanna look into flashing a AT&T ROM first and learn more about what you're attempting to do. (Google is a good friend)
P.S.: Please, don't double post.
BWolf56 said:
If you don't know how to do those, you might wanna look into flashing a AT&T ROM first and learn more about what you're attempting to do. (Google is a good friend)
P.S.: Please, don't double post.
Click to expand...
Click to collapse
I'm aware of what I'm attempting to do. The build prop on this rom needs to be edited or replaced or reflect AT&T since the rom base is Verizon. I'm not new to flashing roms; I've just never had to edit/replace a build.prop for a rom port from another carrier. I've searched google and the rom thread before posting this question. I'm just trying to see if anyone else from the community would be able to advise me what edits I would need to make to the build.prop or if they could help point me in the right direction for a build.prop zip that I could flash through TWRP. I expected the typical "why don't you just google it" response, but was hoping that someone would be helpful enough to actually assist me.
P.S.: I only started this thread after I realized my original post was in a thread with little to no activity.
mrpoe222 said:
I'm aware of what I'm attempting to do. The build prop on this rom needs to be edited or replaced or reflect AT&T since the rom base is Verizon. I'm not new to flashing roms; I've just never had to edit/replace a build.prop for a rom port from another carrier. I've searched google and the rom thread before posting this question. I'm just trying to see if anyone else from the community would be able to advise me what edits I would need to make to the build.prop or if they could help point me in the right direction for a build.prop zip that I could flash through TWRP. I expected the typical "why don't you just google it" response, but was hoping that someone would be helpful enough to actually assist me.
P.S.: I only started this thread after I realized my original post was in a thread with little to no activity.
Click to expand...
Click to collapse
I didn't mean to sound like ''Why don't you just google it''. You gave really low information on your experience and such, therefor, I made a safe suggestion.
Basically, you have to change the phone model to SGH-I747 in the build.prop file with something like notepad.
As for the other part, I have no idea, and this time, google will actually be helpful as I'm sure people attempted this before.
BWolf56 said:
I didn't mean to sound like ''Why don't you just google it''. You gave really low information on your experience and such, therefor, I made a safe suggestion.
Basically, you have to change the phone model to SGH-I747 in the build.prop file with something like notepad.
As for the other part, I have no idea, and this time, google will actually be helpful as I'm sure people attempted this before.
Click to expand...
Click to collapse
I was able to locate the build.prop edits buried in a thread about google wallet. I'm still not sure about the other part, but I have the rom up and running on at&t LTE with no issues. I appreciate your patience. I try to search as thoroughly as I can, unfortunately, work often gets in the way.
mrpoe222 said:
I was able to locate the build.prop edits buried in a thread about google wallet. I'm still not sure about the other part, but I have the rom up and running on at&t LTE with no issues. I appreciate your patience. I try to search as thoroughly as I can, unfortunately, work often gets in the way.
Click to expand...
Click to collapse
Clearing client database means clearing data and cache in the play store app. That's what worked for me on with that issue...or loading another Google account then deleting it then adding your main one.
Verizon Galaxy S3 running RLS10 - call echo issue
Hey, first of all I wanted to say to the developers of the Hyperdrive RLS ROM, this has become one of my preferred ROMS - great stability, battery life, etc. I just upgraded from RLS9 to RLS10. FYI, I always wipe everything prior to installing a ROM. Anyway, installation went off without a hitch and the ROM runs great, but since I upgraded to this ROM, I am getting an echo with every single call even with bluetooth. Not sure if anyone else is having this issue, and if there's a fix for it? Would appreciate any feedback! Thanks, and thank you to the developers for all the work you do.
jpc477 said:
Hey, first of all I wanted to say to the developers of the Hyperdrive RLS ROM, this has become one of my preferred ROMS - great stability, battery life, etc. I just upgraded from RLS9 to RLS10. FYI, I always wipe everything prior to installing a ROM. Anyway, installation went off without a hitch and the ROM runs great, but since I upgraded to this ROM, I am getting an echo with every single call even with bluetooth. Not sure if anyone else is having this issue, and if there's a fix for it? Would appreciate any feedback! Thanks, and thank you to the developers for all the work you do.
Click to expand...
Click to collapse
the echo is just on your end, correct?
go to settings >accessibility and make sure turn off all sounds is not checked to begin with. now go to settings > sound and make sure your volume levels are correct and sound is turned on.
also, phone > menu > Call settings > additional settings and then uncheck noise reduction. some people have reported less echo and clearer calls with this turned off.
jpc477 said:
Hey, first of all I wanted to say to the developers of the Hyperdrive RLS ROM, this has become one of my preferred ROMS - great stability, battery life, etc. I just upgraded from RLS9 to RLS10. FYI, I always wipe everything prior to installing a ROM. Anyway, installation went off without a hitch and the ROM runs great, but since I upgraded to this ROM, I am getting an echo with every single call even with bluetooth. Not sure if anyone else is having this issue, and if there's a fix for it? Would appreciate any feedback! Thanks, and thank you to the developers for all the work you do.
Click to expand...
Click to collapse
A few have reported the same issue on the thread but no real solution beyond hit speaker on then off and it goes away. Reason that works ? I have no clue.
As many of us have took the recent Kitkat OTA we have a variety of questions. Since there have been many threads asking the same question or related to the same question, I will be making this thread to keep this from continuing.
Question: I have took the Kitkat update, is there any way I can root?
Answer: No, no known exploit works on the RAZR M, unless you have a unlocked bootloader. Then you can flash a custom recovery and flash a superuser.zip and gain root access (Credits - fredsky2)
Question: Can I unlock my bootloader now that I have the kitkat update?
Answer: No, the bootloader has been patched ever since the JB OTA. No exploits will work with the RAZR M.
Question: Will Rootkeeper keep root after the OTA?
Answer: I've yet to see it work so I assume no.
Question: When I take the OTA, will it lock my bootloader?
Answer: No, once the bootloader is unlocked, it cannot be relocked.
Question: Can I downgrade to Jellybean after the Kitkat OTA?
Answer: No, the bootloader is locked, meaning you cannot downgrade or even touch the kernel.
Question: How can I return my phone to stock so I can receive the OTA?
Answer: RSD back to stock.
Question: Where can I get the SBF Files for the DROID RAZR M?
Answer: Here: http://sbf.droid-developers.org/phone.php?device=8
Question: My phone won't let me take the Kitkat ota, what do I do?
Answer: Most likely it's because apps are disabled or root is present. RSD back to stock is typically the solution to the problem. If you want to RSD back to stock but don't want to lose your data, look for the question below.
Question: Can I sim unlock after I take the Kitkat update? (Suggestion Credits - gtmaster303)
Answer: Yes! There is a tutorial with video on how to do it found here: http://forum.xda-developers.com/showthread.php?t=2487863 . MAKE SURE YOU HAVE PROPER DRIVERS INSTALLED!
Question: Can I flash a custom recovery after the Kitkat update?
Answer: No, unless your bootloader is unlocked.
Question: I'm getting a getvar error, how do I fix it?
Answer: In the xml file found in the zip, delete any getvar lines at the beginning of the file.
Question: Can I RSD without clearing data?
Answer: Yes! I asked myself and I'm adding this for others sake. Delete the <step operation="erase" partition="userdata" /> line in the XML file found in the zip. I suggest using it only for when you're on the same version of the update. So 9.30.1 to 9.30.1. Give credits to lem22 for helping me out! http://forum.xda-developers.com/showthread.php?t=2755924
Question: What's are the overall changes/problems with Kitkat? (Suggestion Credits - Strife89)
Answer: There has been a full list provided here: http://forum.xda-developers.com/showpost.php?p=52736453&postcount=1 , click the show button below to see Strife89's list!
Strife89 said:
The Good
The UI is definitely smoother. It doesn't jitter or stall under heavy usage anywhere near as much as it did in Jellybean.
Battery life when the phone is asleep seems to have been improved a little.
USB audio out is now supported.
The occasional "screen jitter" that plagued the Jellybean build is gone.
KitKat's Quick Settings panel is quite handy.
The native lock screen now supports adding, removing, and rearranging widgets.
Although it can't be installed from the Play Store, the Google Experience Launcher can be sideloaded and works just fine.
The Neutral / Very Subjective
The AOSP keyboard has changed; the keys are smaller and, in landscape, very squashed. You may need to adjust to it (I'm trying, but it's a struggle) or find a replacement.
Battery life when the phone is actively in use has not been noticeably improved in my experience; but it hasn't been noticeably worsened, either.
There's now a shortcut to the camera from the lock screen, which can be used even if the phone is locked by a pattern/PIN/etc. (Great if you're a shutterbug; not so great if someone else decides to troll your Dropbox/Drive account.)
The Google Camera app works - but Photosphere can't be used, as the Razr M doesn't have a gyroscope.
The Bad
No more root, for those with locked BLs (me). (Saferoot fails, and many users are reporting losing root even when they try survival methods.)
Wi-Fi tethering via most apps (e.g., FoxFi) has been blocked, so now you must pay your carrier for the feature unless a new workaround is discovered.
All notifications I've seen so far now flash the notification light white, instead of unique colors. This may be frustrating for some who used the colors to decide whether to check the phone immediately or later. (Luckily, there are ways to address this.)
The Blur launcher is same 'ol, same 'ol. It uses a solid black background for the soft keys and notifications bar (rather than taking advantage of KitKat's transparency support), and it still has that Quick Settings menu on the left (which is redundant now). In addition, Holo Launcher (which I was using) doesn't account for the space used by the softkeys at all, making it difficult to use. (I've switched to Nova Launcher, which is working fine.)
I've experienced some weirdness with the application switcher. Sometimes it drops me to the launcher right after displaying the list, and sometimes apps will overwrite another's position on the list, or be dropped from the list entirely without reason (this is always temporary, however - just bring up the switcher again).
Some apps can no longer write to the SD card - or at least not wherever they please. We still have the Files browser, mercifully (but I favor Total Commander anyway, which seems to work perfectly).
The audio quick switch on the lock screen has been removed. Also, the buttons for entering a PIN are smaller.
(Leraeniesh) Under heavy usage, the Razr M may get hotter under KitKat than it did under Jellybean, and may drain the battery more.
(GPIX) Some users have noticed decreased network performance in some apps, such as Chrome or YouTube, while on Wi-Fi and with Wi-Fi power-saving enabled.
(GPIX) Several users have reported popping noises - when a sound begins to play, or in the middle of playback. (I haven't experienced it, however.)
Swype is no longer included. If you used it in Jellybean, you will need to purchase it on the Play Store after taking the OTA.
(ls3c6) Some have encountered problems with sharing the address book to paired devices over Bluetooth.
Click to expand...
Click to collapse
If there are any extra questions needed to be added, let me know and I'd be more then willing to add them!
If there is a user having problems that are listed in this thread, just link him here!
I posted both here and Q&A because questions seem to pop up in both places. I'm doing this to clean up the forums a bit better and keep questions from being asked multiple times. Hope this helps and have a great day!
You should add info about Sim unlocking on KK too. Great write up. I will get this thread stickied
Sent from my Droid RAZR M
megaghostgamer said:
As many of us have took the recent Kitkat OTA we have a variety of questions. Since there have been many threads asking the same question or related to the same question, I will be making this thread to keep this from continuing.
(SNIP)
Click to expand...
Click to collapse
May I suggest merging some of the info from this into the post? Linked post is intended to be helpful for those who haven't taken the update yet and are asking what it's like. (Not as numerous as the threads from those who DID take the OTA, but they're there.)
Since I wrote said post: feel free to chop it to bits as needed, if you use it.
gtmaster303 said:
You should add info about Sim unlocking on KK too. Great write up. I will get this thread stickied
Sent from my Droid RAZR M
Click to expand...
Click to collapse
Sim information has been added and credits have been given!
Thank you for the sticky!
Strife89 said:
May I suggest merging some of the info from this into the post? Linked post is intended to be helpful for those who haven't taken the update yet and are asking what it's like. (Not as numerous as the threads from those who DID take the OTA, but they're there.)
Since I wrote said post: feel free to chop it to bits as needed, if you use it.
Click to expand...
Click to collapse
I added your list to the thread, just click the show button and it shows all of your listings of Kk enhancements / disadvantages . Credits were given to you!
This is the response I got from our lovely mod when I tried to get this stickied: The acting moderator in charge of your case has marked the issue as resolved due to the following reason(s):
Not necessary, thread will stay afloat if used actively.
Click to expand...
Click to collapse
. Like he knows what's best for a device that he doesn't use... Oh well I tried
Sent from my Droid RAZR M
gtmaster303 said:
This is the response I got from our lovely mod when I tried to get this stickied: The acting moderator in charge of your case has marked the issue as resolved due to the following reason(s):
. Like he knows what's best for a device that he doesn't use... Oh well I tried
Sent from my Droid RAZR M
Click to expand...
Click to collapse
Typical. I couldn't expect any less. Let there be more pointless threads then. More for them to "monitor".
Also if anyone has any questions that aren't on the list don't be afraid to ask
Sent from my Dell Venue 8
Less KitKat related but since most of the Q/A are root related: What's the last version that the bootloader is unlockable? My on contract phone met a watery death so I snagged a used Razr M, I know it's a long shot but what should I be looking for when it comes? I'm seeing a few different #'s but it looks like 9.8.1Q-66, 98.15.66.xt907.verizon.en.us is the last one right?
(deleted the quote code by accident)
Question: I have took the Kitkat update, is there any way I can root?
Answer: No, no known exploit works on the RAZR M
---------------------------
Imho i think it would be nice to point out if you can or cannot have root if your bootloader is unlocked
Like, 'question: my bootloader is unlocked, does that means i have a green card?'
=p
Overall awesome thread op, thanks for doing this for the razrm community
seasonone said:
Less KitKat related but since most of the Q/A are root related: What's the last version that the bootloader is unlockable? My on contract phone met a watery death so I snagged a used Razr M, I know it's a long shot but what should I be looking for when it comes? I'm seeing a few different #'s but it looks like 9.8.1Q-66, 98.15.66.xt907.verizon.en.us is the last one right?
Click to expand...
Click to collapse
Yes, you're correct, that's the last one with unlockable BL. If that's what you have, you are LUCKY!
Also, I've just discovered it's not possible to downgrade to JB after flashing KK even with an UNLOCKED bootloader!
GnatGoSplat said:
Yes, you're correct, that's the last one with unlockable BL. If that's what you have, you are LUCKY!
Also, I've just discovered it's not possible to downgrade to JB after flashing KK even with an UNLOCKED bootloader!
Click to expand...
Click to collapse
Thanks, I know the odds aren't great I just want to be sure before I update, could come with kit kat making version pretty irrelevant.
seasonone said:
Thanks, I know the odds aren't great I just want to be sure before I update, could come with kit kat making version pretty irrelevant.
Click to expand...
Click to collapse
Even if you don't update, be sure to unlock that bootloader before you forget!
Thank you all for suggestions and thank you for answering questions while I was gone camping! I'm back and will be updating thread with credits!
GnatGoSplat said:
Yes, you're correct, that's the last one with unlockable BL. If that's what you have, you are LUCKY!
Also, I've just discovered it's not possible to downgrade to JB after flashing KK even with an UNLOCKED bootloader!
Click to expand...
Click to collapse
It is possible. Just tz partition and one other can't be. If you remove command to flash them from xml, you'll be able to downgrade via RSD.
Odesláno z mého ZTE V807 pomocí Tapatalk
KitKat has root and bootloader unlock!
http://www.droid-life.com/2014/06/16/motorola-bootloader-unlock-razr-hd-towelroot/
Happy dance!
Update op please
Sent from my Droid RAZR M
Klen2 said:
It is possible. Just tz partition and one other can't be. If you remove command to flash them from xml, you'll be able to downgrade via RSD.
Click to expand...
Click to collapse
Thanks, someone else pointed that out in another thread and I was able to get it to work by removing gpt and tz from the xml.
Hi guys! I searched everywhere but i can't find a good way to have the aosp lockscreen on stock 4.4. The various apps from play store are always with some kind of different bug, so i was searching for a mode to use the original aosp without bug or problem with double lockscreen.
I even looked for a xposed module, but i didn't find anything...
Anyone who can help me?
Someone?
I don't think it's possible due to the library files.
RoyaLKurTx3 said:
I don't think it's possible due to the library files.
Click to expand...
Click to collapse
Thanks, but a friend of mine has the s4 with a stock based ROM, and i'm sure he can use the aosp lock if he want... (He can choose it with aroma)
Maybe with the right libraries it can work even for us, no?
Alecotro said:
Thanks, but a friend of mine has the s4 with a stock based ROM, and i'm sure he can use the aosp lock if he want... (He can choose it with aroma)
Maybe with the right libraries it can work even for us, no?
Click to expand...
Click to collapse
Ah yeah, it can, but I never used AOSP ROMs so I know pretty much nothing about how they work, so I can't help here.
is current xperia z1c lollipop still have memory leak issue ?
I used lollipop for 2 days already. and it always restart my game (minimized to background) after I open browser to use google (yeah only 2 recent apps displayed. chrome and game apps).
I hate this because my game need long time and heavy bandwidth at loading screen. I never get this problem when I used kitkat. I heard there's xposed module to fix this memory leak issue but my phone isnt rooted.
or is there a way to return to default OS (kitkat) like when I first bought it ? maybe I'll do this way. reset it to kitkat again. but I dont know how.
thanks.
You can flash stock kitkat with flashtool. I should have stock EU . 157 rom somewhere on my pc and can upload it if you want.
Flashing stock rom is pretty easy. Watch a tutorial or something. I can help you a bit more when back home.
Back to your question. I have no idea I'm still running kitkat as L is still not available in my country.
Ephixi4 said:
You can flash stock kitkat with flashtool. I should have stock EU . 157 rom somewhere on my pc and can upload it if you want.
Flashing stock rom is pretty easy. Watch a tutorial or something. I can help you a bit more when back home.
Back to your question. I have no idea I'm still running kitkat as L is still not available in my country.
Click to expand...
Click to collapse
is it working to use your stock rom at my country ? I thought different country have different kind of rom. not sure about this if this is true or not.
flashing stock rom doesnt need root access, right ? and maybe can I also backup current lollipop OS that I have so I can reflash it when it has been fixed ?.
so far what I like from lollipop is when someone call me, I can still use other app because call notification only use small box on top of my current running app. I like this feature very much.
It depends where do you live. If in EU it should be fine. If not I can find a rom good for your location.
No, flashing custom rom does not require rooted device.
I think you don't have to do the backup as you'll be able to just update it again ( at least I think so)
-Vermillion- said:
is it working to use your stock rom at my country ? I thought different country have different kind of rom. not sure about this if this is true or not.
Click to expand...
Click to collapse
Yeah..some features change county wise..
flashing stock rom doesnt need root access, right ? and maybe can I also backup current lollipop OS that I have so I can reflash it when it has been fixed ?
Click to expand...
Click to collapse
Yes. But you dont have to backup the OS. You can download the Firmware using the XperiaFirm Tool >> http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
And here is how to convert the files >> http://www.xperiablog.net/2014/08/1...re-files-using-xperifirm-and-flashtool-guide/
Ephixi4 said:
It depends where do you live. If in EU it should be fine. If not I can find a rom good for your location.
No, flashing custom rom does not require rooted device.
I think you don't have to do the backup as you'll be able to just update it again ( at least I think so)
Click to expand...
Click to collapse
is that mean I can flash pre-rooted rom, shared from Xperia Z1 Compact General subforum without unlock bootloader ?
wow then I better use that. I want lollipop+root+xposed but dont want to unlock my bootloader :victory:
getvaisakh said:
Yeah..some features change county wise..
Yes. But you dont have to backup the OS. You can download the Firmware using the XperiaFirm Tool >> http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
And here is how to convert the files >> http://www.xperiablog.net/2014/08/1...re-files-using-xperifirm-and-flashtool-guide/
Click to expand...
Click to collapse
wow this is nice info. I've just tried using that xperiafirm tool and it shows my country firmware.
Generally you can root your phone without unlocking bootloader. It worked for me, at least on kitkat. I'm not sure what about the Lollipop though.
You should better ask someone else too as I'm not as experienced and don't want to give you false info.
But if there's pre-rooted rom here and it's working for android L you don't have to unlock bootloader to flash it.
-Vermillion- said:
is that mean I can flash pre-rooted rom, shared from Xperia Z1 Compact General subforum without unlock bootloader ?
wow then I better use that. I want lollipop+root+xposed but dont want to unlock my bootloader :victory:
Click to expand...
Click to collapse
Please give a feedback to me as I also want Lp+root+xposed. *cheers*.
btw, if u wish to stay in KK (since xposed in LP wont work perfectly, seen people commenting on that) there is an easy method to root..
http://forum.xda-developers.com/sony-xperia-z1-compact/general/root-fw-14-4-0-157-lb-ubl-t2977774
Ephixi4 said:
Generally you can root your phone without unlocking bootloader. It worked for me, at least on kitkat. I'm not sure what about the Lollipop though.
You should better ask someone else too as I'm not as experienced and don't want to give you false info.
But if there's pre-rooted rom here and it's working for android L you don't have to unlock bootloader to flash it.
Click to expand...
Click to collapse
yeah. I've tried root without unlock bootloader and it worked. as long as I use correct kernel that can be rooted.
getvaisakh said:
Please give a feedback to me as I also want Lp+root+xposed. *cheers*.
btw, if u wish to stay in KK (since xposed in LP wont work perfectly, seen people commenting on that) there is an easy method to root..
http://forum.xda-developers.com/sony-xperia-z1-compact/general/root-fw-14-4-0-157-lb-ubl-t2977774
Click to expand...
Click to collapse
okay I can get lollipop with root+xposed (all day tried this. I read some tutorial how to do it properly because this is my 1st time doing something like this. so tired ). although I dont know if xposed wont work perfectly like you said because I only use 3 modules so far. App Settings (keep screen on for game I'm playing) and Fix Lollipop Memory Leak and gravitybox (LP).
what I've done :
- downloaded kitkat 14.4.A.0.157 from XperiFirm. and flashed it using flashtool.
- I've realized .0157 can't be rooted for now. so I've used your link that you gave (Root FW 14.4.A.0.157 (LB/UBL) ).
- after get root access, then I installed recovery using Z1C-lockeddualrecovery2.8.11-RELEASE.installer.zip from http://nut.xperia-files.com/
- after that I flashed 14.5.A.0.242_CustomizedFR_Pre-Rooted_Dualrecovery 2.8.10 + Fix Xposed for Lollipop using recovery.
- and flashed Massive debloating and Xposed. links and procedure are also from that pre-rooted rom thread.
so far, no bootloop. dont know if I add some xposed modules again. I heard it will get bootloop if too many xposed modules is installed (?)
-Vermillion- said:
yeah. I've tried root without unlock bootloader and it worked. as long as I use correct kernel that can be rooted.
Click to expand...
Click to collapse
:good:
okay I can get lollipop with root+xposed (all day tried this. I read some tutorial how to do it properly because this is my 1st time doing something like this. so tired ).
Click to expand...
Click to collapse
I know that feel :angel:
I have found a way to root stock LP having ULB. http://forum.xda-developers.com/showpost.php?p=60188952
Now going to try xposed. Since you have, tell me how.. Here is the official thread http://forum.xda-developers.com/showthread.php?t=3034811. Is this where you get info?
although I dont know if xposed wont work perfectly like you said because I only use 2 modules so far. App Settings (keep screen on for game I'm playing) and Fix Lollipop Memory Leak (still dont know if this module will work.)
Click to expand...
Click to collapse
Xposed worked perfectly in KK. I tried more than five modules at a time without the bootloop issue. What I fear is the LP. Havent you checked the dev/Q&A thread of the modules?
what I've done :
- downloaded kitkat 14.4.A.0.157 from XperiFirm. and flashed it using flashtool.
- I've realized .0157 can't be rooted for now. so I've used your link that you gave (Root FW 14.4.A.0.157 (LB/UBL) ).
- after get root access, then I installed recovery using Z1C-lockeddualrecovery2.8.11-RELEASE.installer.zip from http://nut.xperia-files.com/
- after that I flashed 14.5.A.0.242_CustomizedFR_Pre-Rooted_Dualrecovery 2.8.10 + Fix Xposed for Lollipop using recovery.
- and flashed Massive debloating and Xposed. links and procedure are also from that pre-rooted rom thread.
Click to expand...
Click to collapse
wow so much struggle... I have a doubt, why not simply flash that pre-rooted ftf file over the KK? [being lazy to search for the thread]
So how is it feels? Dont forget to share your views and link to the thread..
I heard it will get bootloop if too many xposed modules is installed (?)
Click to expand...
Click to collapse
I dont know that. But I heard that activating some module(s) when some other module(s) is(are) active may cause bootloop in KK.
Hey there, the XperiFirm dev here.
No one answered your question so I will. The answer is: No.
Sony made sure to include the memory leak fix built in (the exact fix that the Xposed module offers) for their Lollipop releases. The Xposed module is pointless.
See attached screenshot. Basically the Xposed module replaces the AOSP function with exactly the same function but with this additional "release()" line. As you can see, Xperia already has this line included.
IaguCool said:
Hey there, the XperiFirm dev here.
No one answered your question so I will. The answer is: No.
Sony made sure to include the memory leak fix built in (the exact fix that the Xposed module offers) for their Lollipop releases. The Xposed module is pointless.
See attached screenshot. Basically the Xposed module replaces the AOSP function with exactly the same function but with this additional "release()" line. As you can see, Xperia already has this line included.
Click to expand...
Click to collapse
wow thanks to coming here :victory:
lol. so it's pointless to install that module because they are same thing exactly. time to uninstall.
actually my game is still restarted after I browsing a little. although I still see a lot of free memory in here. before, I thought this is because of that memory leak issue but I'm wrong.
if only there's module that can prevent lollipop refresh/restart/clear my game at memory when I minimized it at background.
I have the same problem, only with audio apps in the background. Pocket Casts, Stitcher and BeyondPod all crash and stop playing when running in the background, after I do something else like load the game Threes. This never used to happen with KitKat. I've also noticed that iplayer radio gets very jerky and skips back and forth by a quarter of a second continuously as soon as I turn off the screen. [edit - I just listened to it for a few minutes with the screen off and it suddenly cut out. I turned the screen on an the app was no longer in my notifications tray]
If Sony fixed this particular memory leak, what's going wrong with my phone? Could it be related to the fact that I've encrypted if for the first time? I'm getting desperate enough to consider factory resetting and losing everything, because listening to podcasts and playing threes is one of my favourite activities. It's not a demanding game for my year old, top of the line phone. My cheap tablet manages it, and so did the phone on KitKat!
I was able to use https://github.com/anestisb/android-prepare-vendor to prepare the vendor images to correctly build AOSP.
I submitted some changes to make it work with Pixel2-XL and they have been merged into main branch.
You have to wipe everything.
I dont know how to make proper zip images for TWRP so use fastboot
I use the fastboot script included in the zip after a full wipe and im all good
Thanks:
anestisb on Github
opengapps
not working:
pixel squeeze
AOSP 8.1 with google apps:
V3:
https://www.androidfilehost.com/?fid=889964283620776051
AOSP 8.1 stock (no gapps):
https://www.androidfilehost.com/?fid=817906626617955840
changelog:
v3:
Jan security update
v2:
updated camera
pixel launcher
updated wallpaper that was causing errors
fixed google setup errors during startup and boot
archive:
v2: https://www.androidfilehost.com/?fid=817906626617955877
V1:
https://www.androidfilehost.com/?fid=745849072291697825
During first boot google setup crashes a bit and I just skip it ...then on reboot I get complaints about stuff. but everything works. so......
deeproot said:
I built AOSP with OpenGapps and all I got was this forum thread
You have to wipe everything.
I dont know how to make proper images so use fastboot
I use the fastboot script included after a full wipe and im all good
Click to expand...
Click to collapse
Link?
Sent from my Pixel 2 XL using Tapatalk
yea, link?
?????
Don't tease us like this, lol. I'll flash anything at this point!
Sent from my Pixel 2 XL using Tapatalk
uplodz complete.
Interesting :good:
I've been doing my best to get my own build running for a few weeks now, and while everything else seems to work perfectly, I can't seem to figure out a way to get it to connect to mobile data. I'd be really interested to hear if there's something in addition to the build instructions provided by Google that you had to do to get it working!
I would just use your build, but my goal is to avoid gapps altogether. Hopefully the trick isn't to have gapps installed
Thanks!
prurigro said:
I've been doing my best to get my own build running for a few weeks now, and while everything else seems to work perfectly, I can't seem to figure out a way to get it to connect to mobile data. I'd be really interested to hear if there's something in addition to the build instructions provided by Google that you had to do to get it working!
I would just use your build, but my goal is to avoid gapps altogether. Hopefully the trick isn't to have gapps installed
Thanks!
Click to expand...
Click to collapse
I thought the whole point of gapps is Google *****es if you build a Rom with google apps installed already...
prurigro said:
I've been doing my best to get my own build running for a few weeks now, and while everything else seems to work perfectly, I can't seem to figure out a way to get it to connect to mobile data. I'd be really interested to hear if there's something in addition to the build instructions provided by Google that you had to do to get it working!
I would just use your build, but my goal is to avoid gapps altogether. Hopefully the trick isn't to have gapps installed
Thanks!
Click to expand...
Click to collapse
u did add in the propietary drivers i assume before u started making ur build?
this build is running smooth! i almost wanna say u couldve left gapps out n let ppl choose which they want to use but of cpurse this is only the beginning.. first thing i did was remove all those google hotword apks that fc, not had any issues yet and u already stated squeeze isnt on here but i nvr used that anyways
I was building from source today but my env has a ways to go before its useable.. it literally took all day to make aosp arm64 eng lol.. started gettin low mem stops towards the end so gonna look at it tom... i actually need to change it up and tweak settings cuz i only got 6gb ram
my set up tho is ur aosp, flash kernel 2.05 and magisk 15.1.. butter.. or shall i say vanilla??
prurigro said:
I've been doing my best to get my own build running for a few weeks now, and while everything else seems to work perfectly, I can't seem to figure out a way to get it to connect to mobile data. I'd be really interested to hear if there's something in addition to the build instructions provided by Google that you had to do to get it working!
I would just use your build, but my goal is to avoid gapps altogether. Hopefully the trick isn't to have gapps installed
Thanks!
Click to expand...
Click to collapse
aosp i dont think includes automatocally.. its runnin android web view n all lol instead of chrome that is
Now, I'm relatively new to the rooting world of Android. Is AOSP essentially custom ROMs? I know this is sort of a "if you don't know, you likely shouldn't be messing with it." I just love tweaking my phone!
So far only the squeeze doesn't work? Should the less advance user hold off until it's been tested a bit? Regardless, thanks for distributing your work to everyone on here! I love this community. Being able to share in the glory that is altering literally almost every aspect of your phone's software.
jgreen077 said:
Now, I'm relatively new to the rooting world of Android. Is AOSP essentially custom ROMs? I know this is sort of a "if you don't know, you likely shouldn't be messing with it." I just love tweaking my phone!
So far only the squeeze doesn't work? Should the less advance user hold off until it's been tested a bit? Regardless, thanks for distributing your work to everyone on here! I love this community. Being able to share in the glory that is altering literally almost every aspect of your phone's software.
Click to expand...
Click to collapse
for u id say hold off.. it works fine for me but it technically is a userdebug build.. AOSP =Android Open Source Project, Its basically Android built from Android source so typically devs can pull the source and make their own roms how they want them. Normally doesnt even have google apps like play store for example.
Its a very clean low lvl android OS and the dev controls every aspect of the build process.. its also been called Vanilla
this technically is "custom" but this initial build doesnt have many tweaks or customizations.. its merely a glimpse as to the possibilities
but hey, try it out if u got the itch, it wont hurt u lol plus the only real way to know the difference is to try it for yourself
jgreen077 said:
Now, I'm relatively new to the rooting world of Android. Is AOSP essentially custom ROMs? I know this is sort of a "if you don't know, you likely shouldn't be messing with it." I just love tweaking my phone!
So far only the squeeze doesn't work? Should the less advance user hold off until it's been tested a bit? Regardless, thanks for distributing your work to everyone on here! I love this community. Being able to share in the glory that is altering literally almost every aspect of your phone's software.
Click to expand...
Click to collapse
for u id say hold off.. it works fine for me but it technically is a userdebug build.. AOSP =Android Open Source Project, Its basically Android built from Android source so typically devs can pull the source and make their own roms how they want them. Normally doesnt even have google apps like play store for example.
Its a very clean low lvl android OS and the dev controls every aspect of the build process.. its also been called Vanilla
this technically is "custom" but this initial build doesnt have many tweaks or customizations.. its merely a glimpse as to the possibilities
but hey, try it out if u got the itch, it wont hurt u lol plus the only real way to know the difference is to try it for yourself
elliwigy said:
for u id say hold off.. it works fine for me but it technically is a userdebug build.. AOSP =Android Open Source Project, Its basically Android built from Android source so typically devs can pull the source and make their own roms how they want them. Normally doesnt even have google apps like play store for example.
Its a very clean low lvl android OS and the dev controls every aspect of the build process.. its also been called Vanilla
this technically is "custom" but this initial build doesnt have many tweaks or customizations.. its merely a glimpse as to the possibilities
but hey, try it out if u got the itch, it wont hurt u lol plus the only real way to know the difference is to try it for yourself
Click to expand...
Click to collapse
Honestly, I'd normally listen and hold off. But since I have a day off I think I'm gonna attempt it just for the sake of learning!
As long as it has the Play Store so I can download the apps I want, I'm good. If I can get all the apps I need to than I'll be a happy camper.
Say later on it's decided I want to go to another AOSP rom, am I going to have to wipe again? If I can get all my apps, won't have to wipe my device every other week, and can get my modules installed I should be good to do some good old fashioned experimentation.
I am not a smart man, at times. I'm gonna try it out. I have a few hours before anyone else is awake. Might as well use that time (un)wisely.
Plus I believe these "vanilla" ROMs, being what they are, can be modded to an even greater extent than the already pretty modifiable "stock" Pixel ones. Please correct me if I'm wrong.
prurigro said:
I've been doing my best to get my own build running for a few weeks now, and while everything else seems to work perfectly, I can't seem to figure out a way to get it to connect to mobile data. I'd be really interested to hear if there's something in addition to the build instructions provided by Google that you had to do to get it working!
I would just use your build, but my goal is to avoid gapps altogether. Hopefully the trick isn't to have gapps installed
Thanks!
Click to expand...
Click to collapse
I found this:
https://github.com/anestisb/android-prepare-vendor
I submitted my changes and they will update in a few days to the add tamien support.
I am going to hold off on this for now, as it's just a shell of what custom Android can be but just wanted to say thank you very much for getting the ball rolling. For giving us hope haha. I check the thread at least 4 times a day and my heart jumped when I saw this post! Good work!
Nice can we flash the Kernels that have been around here for a while on this rom?
patt2k said:
Nice can we flash the Kernels that have been around here for a while on this rom?
Click to expand...
Click to collapse
I flashed Elemental X and finger print stopped working.
deeproot said:
I found this:
https://github.com/anestisb/android-prepare-vendor
I submitted my changes and they will update in a few days to the add tamien support.
Click to expand...
Click to collapse
@deeproot
have you uploaded your WIP android_prepare_vendor anywhere? I would like to clone your changed repo and run this script if possible.
I attempted to manually add your changes in the pull request, but the script is breaking with a debugfs error
Thanks,
Edit: Found it, still getting same debugfs error.
Code:
[*] Extracting '/tmp/android_prepare_vendor.jlQiR6/taimen/opm1.171019.011/taimen-opm1.171019.011-factory-2df1c1cb.zip'
[*] Unzipping 'image-taimen-opm1.171019.011.zip'
[-] Symlinks have not been properly processed from /tmp/android_img_extract.FRWAOM/taimen-opm1.171019.011-factory-2df1c1cb/images/vendor.img.raw
[!] If you don't have a compatible debugfs version, modify 'execute-all.sh' to disable 'USE_DEBUGFS' flag
[-] Factory images data extract failed
[email protected] ~/Desktop/android-prepare-vendor $