Hyperdrive RLS10 Issue - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

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.

Related

[ROM]|Icee-Modz_1.0.6|05-13-12|Simple, Stock, and Bugless, with native tethering.

This is very simple the ROM is intended to serve as a ROM for people who are like me who likes the stock ROM but with a little customization, and enjoys the ICS OS without some of the customizations found in the AOSP choices that we have so far. The goal for this is simple, stock, and bugless as a ROM can be and there is no donate button in the ROM. It uses mods and battery saving techniques that I found to work for me, but like I said since this is more of a modded stock ROM I'll keep this intro brief.
Features:
De-odexed
Build.prop tweaks for performance and to perserve battery life
Dalvik Cache moved to cache
Super User (root) and Busy Box
Native Tethering
I also have customized some settings for better user experience (well at least for me). I am keeping this simple so I'll tell you now I like how the stock ROM works so I have not added any of the CM Mods or Kang Mods and probably won't as of now. Also I am not gonna post any screen shots since this is a re-vamp of what you got out of the box and there is no visual customizations added since all of my tweaks are to the apps and settings. ....... anyway take a chance try this out let me know what ya think ...........
Download for today
http://www.mediafire.com/?ws5d7hbdpkjvk3d
or
http://www.4shared.com/zip/DIdXuE7p/Icee_Modz_1_0_6_051312.html
As always make sure you know how to flash a ROM before using this or you may encounter problems or even brick your device please follow these instructions:
1: Factory reset data and system wipe
2: Wipe cache
3: Install ROM .zip file
4: Reboot
To ensure that you get the best out of my preset customizations don't sign into google services when you setup the ROM you can always do this later, try the rom out as is to put it to the test before you add your customizations and settings to it.
ENJOY
JD
NOTE: The Google Apps provided in this ROM is to be only used with the Sprint branded variant of the Galaxy Nexus and not to be redistributed to any other device not licensed to Sprint or not a Sprint variant Galaxy Nexus, the Google Apps are the property of GOOGLE and should be respected as such and if need be I will demolish all links to Google property should I be asked to.
Change Log
050412:
Initial release for Jakd-Modz 3
rom 3.0.8
Changed the name to Icee_Modz
ROM allows native tethering (at least thru USB thats all I tested)
Updated:
Maps
GoogleEarth
Street
GooglePlus
GoogleVoice
wallet
Lock Screen rotation is enabled
I'll try it when I get home.
Sent from my Galaxy Nexus
Does the compass work properly with this?
peabody42 said:
Does the compass work properly with this?
Click to expand...
Click to collapse
I don't see why it wouldn't
Not sure what you do with these ROMS but they are fast smooth and bugless like you state. Only issue I have on this version is MMS won't send. Had this problem on another earlier build also can't do a PRL or Profile update. Not sure why not though I have flashed wiped and reflashed like always but jo go.
GN Sent
ifly4vamerica said:
Not sure what you do with these ROMS but they are fast smooth and bugless like you state. Only issue I have on this version is MMS won't send. Had this problem on another earlier build also can't do a PRL or Profile update. Not sure why not though I have flashed wiped and reflashed like always but jo go.
GN Sent
Click to expand...
Click to collapse
I'll check on that for you and thanks
OK gotta fix mms
Hey sorry was on a plane but I got it fixed. You just need to get the SDM.apk which apparently has the sprint prl and profile update in it. Put that in system, set permissions then reboot update profile and prl and you are golden. If you need the SDM.ak pm me and ill get it to you. Just getting off the plane but can do it when I get home.
Thanks again for this kick a$$ rom, I have tried AOKP and team eos but my phone likes this one the best with franco kernel. I do t use all the fancy stuff the others have so this is erfect.
GN Sent
ifly4vamerica said:
Hey sorry was on a plane but I got it fixed. You just need to get the SDM.apk which apparently has the sprint prl and profile update in it. Put that in system, set permissions then reboot update profile and prl and you are golden. If you need the SDM.ak pm me and ill get it to you. Just getting off the plane but can do it when I get home.
Thanks again for this kick a$$ rom, I have tried AOKP and team eos but my phone likes this one the best with franco kernel. I do t use all the fancy stuff the others have so this is erfect.
GN Sent
Click to expand...
Click to collapse
Yeah I just removed the sdm package because I got tired of the phone wanting to activate every time I flash lol but I'm on my way to Chicago for the weekend and won't get back until Sunday so I will fix this then and thanks for the positive words
No worries man. I got tired of that too. Once I reinstalled it I updated and then froze it with TB. Have a good trip.
GN Sent
Any screenshots?
would try...
jakdillard said:
Build.prop tweaks to perserve battery life
Dalvik Cache moved to cache
Super User (root) and Busy Box
Build.prop tweaks to force better GPU rendering
Zipaligning on boot
Click to expand...
Click to collapse
Thanks for sharing your work. Just to clarify, this is based on the Sprint's as-shipped GN ROM, with the customizations listed above, and Google Apps removed (which can be installed via the separate package you provided).
Is there anything else I'm missing?
What is the MMS issue?
Lastly, what are your customizations?
Cheers.
snovvman said:
Thanks for sharing your work. Just to clarify, this is based on the Sprint's as-shipped GN ROM, with the customizations listed above, and Google Apps removed (which can be installed via the separate package you provided).
Is there anything else I'm missing?
What is the MMS issue?
Lastly, what are your customizations?
Cheers.
Click to expand...
Click to collapse
yep based off sprint shipped and all of googles apps removed and every thing I've done to it is not anything that you will see like a theme or extra options for whatever its all under-the-hood type tweaks, and the mms thing is a fluke on my part because I removed the package that updates your profile to sprint to allow you to send mms.
broad_st_bully said:
Any screenshots?
Click to expand...
Click to collapse
Its just like stock except cleaner so I dont think screens are needed for that ?
jakdillard said:
yep based off sprint shipped and all of googles apps removed and every thing I've done to it is not anything that you will see like a theme or extra options for whatever its all under-the-hood type tweaks, and the mms thing is a fluke on my part because I removed the package that updates your profile to sprint to allow you to send mms.
Click to expand...
Click to collapse
Just to verify--the package is now put back into the ROM? Also, does the separate GApps package put everything back that you took out?
Thanks.
snovvman said:
Just to verify--the package is now put back into the ROM? Also, does the separate GApps package put everything back that you took out?
Thanks.
Click to expand...
Click to collapse
No I'm in the process of rebuilding from scratch and haven't fix that yet. so I'd wait to try this out
Ok did a complete rebuild, the ROM is just like what you get out the box now (I actually like the stock ROM) everything is there just like what you get out of the box I have just did a lot of "under-the-hood" engine tuning, mms works and so does the compass .
Awesome! I am checking this out now but like it simple.

Working pdroid patches [currently AOKP(toro+maguro), stock AOSP, cm9]

I'm using this thread to share working pdroid patches I've got for various Galaxy Nexus roms. This was made using the patcher being developed here (patcher is in the 4th post). The patcher is currently linux-only, but will also work with cygwin in windows. I'm posting the finished flashable zip here as a convenience to anyone who can't use it themselves. Please note that I am not one of the people actively developing this patcher, just a willing tester who happens to own a toro Gnex.
If you don't know what Pdroid is, this is the thread for it on xda. Basically, it lets you deny permissions to apps on a per-permission basis, without risking apps crashing. Same basic idea as LBE privacy guard, but in my opinion executed better. Plus, open source is always a plus. Even though the official patcher there won't work for us yet, check the official thread. You'll need to download the app from the market and follow the same instructions, just using the zips I'll post here (or make your own).
I'll include a revert.zip for anything I post here, but please note that I take no responsibility for anything that happens to your phone. Make backups before flashing things. Try TWRP if you haven't, it's faster at backup/restore than CWR and does a bunch of other neat stuff like compressed backups and queued zip flashing. Also, in case of things breaking, please note that these revert zips are (1) only going to work if you are running the same rom used to create the zip and (2) just a slimmed down version of the rom's zip. What this means is that if you flash a pdroid zip and you need to revert, the surest thing to do is just re-flash your rom without wiping anything.
I'll try to update this thread as I get more patches working. Here's where my own experiments stand:
Link to my dropbox folder with files, notes below
Working patches:
-AOKP b39 (toro):
-AOKP b39 (maguro):
-CM9 Nightly: Patched build: 2012/06/19
--Note: Not sure if these will automatically fail with later nightlies or only when something relevant is updated in the rom. Feel free to try, just reflash your rom if it bootloops.
-Stock AOSP(+root, busybox): Patched build: 2012/06/02
-Paranoid Android v1.4a
Not Working (Yet):
-Liquidsmooth 1.5RC4:
-Slim ICS 4.0:
Unless otherwise noted, these are all for the toro (verizon) Galaxy Nexus. It's pretty quick and easy for me to make new patches so feel free to request something. But please be aware that sometimes it's a few days between when I can devote any time to this and don't be offended if I don't reply to you right away.
Just to reiterate, all you need to do for this is download the "Pdroid Patch Zip" file for your rom, flash it in recovery, and download Pdroid from Google Play.
Finally, be aware that the first boot after flashing can take a very long time, without any indication like the "Android is Upgrading..." screen. Don't assume it's bootlooping! Seriously, put the phone down and do something else for a bit. Anything in the tested section I've either personally flashed on my phone or someone else reported as working. If you're sure you're getting a bootloop on a clean install, my only advice is to do a full revert to stock and re-unlock/root/etc and see if it works then. Though rare, it is possible for something to be corrupt that persists across the usual "clean install" routine.
Isn't that what Permissions Denied does?
https://play.google.com/store/apps/details?id=com.stericson.permissions
Wow, I didn't realise you could patch AOKP on ICS yet. Have been waiting for this for so long. How would I go about applying your patch for AOKP gsm?
xternal said:
Wow, I didn't realise you could patch AOKP on ICS yet. Have been waiting for this for so long. How would I go about applying your patch for AOKP gsm?
Click to expand...
Click to collapse
For gsm you'd need a new patch. There are instructions in the first thread I linked to if you'd like to try it out. I might make one in a bit since I expect that to be a popular request and I expect it to work.
danger-rat said:
Isn't that what Permissions Denied does?
https://play.google.com/store/apps/details?id=com.stericson.permissions
Click to expand...
Click to collapse
Same idea, different approach. Permissions denied generally causes apps to crash if they need info that they are denied. I also had a major issue with it a while back that I ended up doing a factory reset for, but I think that's been fixed since then.
Not sure how pdroid gets around apps fc'ing (maybe it spoofs data so apps go on running normally? It has an option to set your own values I haven't played with much), but it works very smoothly.
xternal said:
Wow, I didn't realise you could patch AOKP on ICS yet. Have been waiting for this for so long. How would I go about applying your patch for AOKP gsm?
Click to expand...
Click to collapse
Quick update, I put up a maguro for AOKP, and I also updated the OP quite a bit since I last posted. Finally got around to testing the patches I made; getting better at reading the patching process as well to tell when a patch will work before flashing it, too.
At far as updates go, I don't really intend to follow the cm9 nightlies as I don't run them myself. I'll probably continue to try new versions of AOKP and paranoid android as they come out. I'll continue to try the roms that don't patch yet with new versions of the patcher as they are released.
Thank you. The maguro patch works for me.
Edit: not sure, but this likely breaks 2 apps: Listen, Drive.
I've been using LBE Privacy to control permissions and this app doesn't crash apps that have permissions blocked. It's one of their selling points, doesn't crash apps.
deaffob said:
I've been using LBE Privacy to control permissions and this app doesn't crash apps that have permissions blocked. It's one of their selling points, doesn't crash apps.
Click to expand...
Click to collapse
PDroid source has been released, whilst LBE created by a 'suspect' chinese company. I put the suspect in inverted comma's because nothing has actually been proven.
The patch works a treat on GSM aokp, many thanks
edit: looking at it though, it seems it doesn't find all the permissions correctly. I am assuming this is a limitation of the current pdroid as it is not designed for ics.
For instance it does not find hardware controls. Google Drive has access to hardware controls to take photos/videos.
Thanks for the confirmations on the maguro zip, I edited the post to reflect that it's definitely working.
I hadn't heard of LBE before making these threads but from what I've read it seems like people generally prefer pdroid. I'll check it out at some point but it looks like it does a bit more than I'd want it to, and pdroid being open source is definitely a plus.
IIRC, there's certain instances where apps can bypass LBE but not PDroid. I think reboot is one of those times due to when LBE loads.
I've been running LBE but lately the service keeps stopping because it doesn't get root soon enough after boot. Trying this now on Paranoid. Thanks!
i have used this patch for CM9 but after the Bootscreen have i a Blackscreen -.- what can i do?
SGDynamite said:
i have used this patch for CM9 but after the Bootscreen have i a Blackscreen -.- what can i do?
Click to expand...
Click to collapse
I'm guessing you are running a different build/more recent nightly? I might take that link down as it was meant as more of a proof of concept if the cm9 patcher was working and it's unlikely anyone is going to be flashing that particular build just to test pdroid.
The most effective thing would be to just re-flash the original rom's zip, you don't need to wipe anything. The revert zip file is basically just four files copied from a given rom's original zip, services.jar, core.jar and framework.jar in /system/framework, and build.prop in /system.
xternal said:
LBE created by a 'suspect' chinese company. I put the suspect in inverted comma's because nothing has actually been proven.
Click to expand...
Click to collapse
I hadn't heard of pdroid until I was on the Nexus, so I'm not familiar with it to compare, but I'm currently using LBE and blocking its data connections with Droidwall. Perhaps a bit overkill... but works great as far as I can tell.
Sent from my Galaxy Nexus using xda premium
JoeSyr said:
I'm guessing you are running a different build/more recent nightly? I might take that link down as it was meant as more of a proof of concept if the cm9 patcher was working and it's unlikely anyone is going to be flashing that particular build just to test pdroid.
The most effective thing would be to just re-flash the original rom's zip, you don't need to wipe anything. The revert zip file is basically just four files copied from a given rom's original zip, services.jar, core.jar and framework.jar in /system/framework, and build.prop in /system.
Click to expand...
Click to collapse
I think I flashed it to a nightly a day or two after 5-18 and it worked, but it definitely did not work on 5-27 or 5-29.
If the patch doesn't work for you, pull the battery, then hold volume up and down while you hold power, then use volume up and down to get to recovery option--press power to select. Either flash the revert or the old from there on top of the non-working one. Don't clear data partition and you won't lose anything.
@Joesyr, I think there is some interest in CM9 nightly patches...would you mind making a CM9 patch maybe once a week? I haven't had any luck making the patch on my own.
robjective said:
I think I flashed it to a nightly a day or two after 5-18 and it worked, but it definitely did not work on 5-27 or 5-29.
If the patch doesn't work for you, pull the battery, then hold volume up and down while you hold power, then use volume up and down to get to recovery option--press power to select. Either flash the revert or the old from there on top of the non-working one. Don't clear data partition and you won't lose anything.
@Joesyr, I think there is some interest in CM9 nightly patches...would you mind making a CM9 patch maybe once a week? I haven't had any luck making the patch on my own.
Click to expand...
Click to collapse
Well the last cm9 nightly I tried didn't patch at all (I believe it was a 5/29 build). I will try tinkering with things as I get the time but I'm not really at the level of fully understanding these kinds of failures yet.
Next time there's an updated cm9 patch I will try to get a working pdroid zip and I'll consider weekly updates. I'm also generally willing to make these on request as it's a pretty quick process. Fiddling with dropbox links is probably the longest part of any of this.
Any particular issue you're having with the patcher? I've been thinking I could write a little tutorial for getting cygwin up and running since I imagine that for most people the limiting factor is just that they don't have a linux environment to work in. But until I get the time to do that I can help troubleshoot.
Can you make a patch for stock root.
Thx
Has anybody experienced random rebooting? All was fine until I opened a non system app. Then it just started rebooting randomly after opening any app. I ran it on Maguro with AOKP b37.
soloxp said:
Can you make a patch for stock root.
Thx
Click to expand...
Click to collapse
Yup, not sure if the rom I just put up is the same you were looking for but it's the first one I've been able to get to patch correctly with the aosp patch.
Just flashed the Toro AOKP b37 patch, tested and working great here. Thank so much! Awesome work!!

How to get 5GHz Wi-Fi on AOSP ROMs working.

Hello everyone,
I didn't see a thread for this and I am just sick and tiered of not being able to post in dev threads, I figured I would attempt to make something useful for newer users of using AOSP ROMs.
I noticed that when using AOSP ROMs, the 5GHz band won't work, I can see the network but can not connect to it, and in some ROMs I can get it to take the Key but then says something like disabled and still doesn't work. Crazy thing is this is something that is not unique to this Device (the i317), I had a i777 (Galaxy S2) before that and it did the same exact thing. What is even more crazy is the fix is exactly the same for both phones.
While making this post I am going through a wip and re-install of my ROM (PAC-Man in this case, but does it with all other AOSP ROMS)
Some information befor I start, 5GHz is important to me as I use it at home, the 2.4GHz range in my area is quite crowded and I am the only 5GHz network in the area so it works better for me.
Anyways here we go;
Step 1, Install your ROM like normal, once you're signed in to your Google Account download Root Explorer (or something of equivalence) Once that is done proceed to step 2.
(NOTE: If you already have your ROM installed you can skip Step 1)
Step 2, In Root Explorer go to System --> etc --> wifi, once here you're going to see various files. Were looking for "nvram_net.txt" and "nvram_net.txt-murata".
These are the two files were going to modify.
Step 3, Hold your finger on "nvram_net.txt" until the popup window for Options comes up, hit Open With and then select Text Editor. From here you're going to look for a line of code thats "ccode=GB" this is needing to be changed to "ccode=US". Once that has been changed then hit the back button and hit Yes on the save box. This will automatically make a backup of the original file.
Step 4, Were going to do the same thing to the "nvram_net.txt_murata" so open it with the Text Editor and look for the same line of code "ccode=GB" and change it to "ccode=US", save the file.
Step 5, Reboot your phone and once back up go into settings and you are now able to use your 5GHz network.
I hope this helps someone and I hope that one day we won't have to keep changing these settings to get 5GHz working on AOSP ROMs, have fun Everyone!!!!
PS. If you all want screenshots I can do them but bare in mind I would have to wipe my phone again and take them during the process. The instructions should be clear and easy to follow without them.
Excellent....
Many thanks....this will help several people out I'm sure.
Thank you...g
gregsarg said:
Excellent....
Many thanks....this will help several people out I'm sure.
Thank you...g
Click to expand...
Click to collapse
Thank You!!
I need to add something to it, if you ever update your ROM you need to do it again just start from step two.
Thanks for the post. I'm sure those who need 5ghz support appriciate it.
I just saw this post and checked. The latest CM10.1 for today (20130701 build) has the correct US settings. Not sure about other AOSP. However you should mention it to the devs of each one you find it in so they can fix it.
Holy ****balls. I just have to say that.
I'm using Galaxy S3 i9300, been running Slimbean 4.2.2 build 8 flawlessly when I came across that situation where I can't connect to 5G wifi. since then I tried searching for a fix but failed. So i opted to cm13, with utter disappointment with its lag and bugs. And still, hoping for a miracle, i flashed my old recovery back, trying to give it one more chance. Lo and behold, you've given me the fix that I've been searching for all these while. But instead of just that two files, I've changed all nvram_net files ccode with US instead GB. Reboot. And now I'm replying this on my workplace 5ghz wifi. Thanks dude. Very much thanks.
I don't have wifi folder
I don't have the WiFi folder in system/etc
Unknown300 said:
I don't have wifi folder
I don't have the WiFi folder in system/etc
Click to expand...
Click to collapse
Have you found any solutions yet?
Mushfiq Khan said:
Have you found any solutions yet?
Click to expand...
Click to collapse
No what phone do you use?I got a new phone and it seems to work
Unknown300 said:
No what phone do you use?I got a new phone and it seems to work
Click to expand...
Click to collapse
I use pocofone f1.I'm on Aosp extended rom.
.
Mushfiq Khan said:
I use pocofone f1.I'm on Aosp extended rom.
Click to expand...
Click to collapse
Are you from Bangladesh?
Mushfiq Khan said:
I use pocofone f1.I'm on Aosp extended rom.
Click to expand...
Click to collapse
Dont think there is a way to change region in aosp extended roms but some region don't support 5ghz for some reason but it's only in miui I think try joining the pocophone f1 telegram

Location services - Google message - how to avoid

I could not find it searching.
When I switch GPS on - Google wants to collect data about my position. I dont want it.
On 4.3 there was marker - remember my choice.
On 4.4 - I need cancel it every single time. Soon it becomes pain.
Any known trick ?
Or I just miss something ...?
F308 said:
I could not find it searching.
When I switch GPS on - Google wants to collect data about my position. I dont want it.
On 4.3 there was marker - remember my choice.
On 4.4 - I need cancel it every single time. Soon it becomes pain.
Any known trick ?
Or I just miss something ...?
Click to expand...
Click to collapse
Hi, did you resolve this problem?
If your z1c is rooted, try this http://forum.xda-developers.com/xposed/modules/mod-disable-google-location-consent-t2449926
merrymenvn said:
Hi, did you resolve this problem?
If your z1c is rooted, try this http://forum.xda-developers.com/xposed/modules/mod-disable-google-location-consent-t2449926
Click to expand...
Click to collapse
I didn't.
My phone is rooted, yes.
As I've read - Xpose requires lot of work, deodex ROM and more ...
For now I don't have time to play this way with my Z1C, it must work almost all the time.
Neither I want deodex ROM, opinions are that odexed is faster.
I opened other question of this sort, curious if something comes up.
When I disabled some Google services - GPS went to defaults = use everything.
I am afraid it may be hardcoded in library, gps-something.so.
Recompiling from sources is even worse considering time spent on it.
I can live with it as is if I have no other options.
Thanx for info.
F308 said:
I didn't.
My phone is rooted, yes.
As I've read - Xpose requires lot of work, deodex ROM and more ...
For now I don't have time to play this way with my Z1C, it must work almost all the time.
Neither I want deodex ROM, opinions are that odexed is faster.
I opened other question of this sort, curious if something comes up.
When I disabled some Google services - GPS went to defaults = use everything.
I am afraid it may be hardcoded in library, gps-something.so.
Recompiling from sources is even worse considering time spent on it.
I can live with it as is if I have no other options.
Thanx for info.
Click to expand...
Click to collapse
Oh, my Z1C run stock KK 4.4.4.
After rooting, just download and install xposed as other apps. It does not require anymore of work (deodex or something else).
merrymenvn said:
Oh, my Z1C run stock KK 4.4.4.
After rooting, just download and install xposed as other apps. It does not require anymore of work (deodex or something else).
Click to expand...
Click to collapse
Thank you for info.
Only that much is worth of effort.
I am rooted, locked BL, 4,4,4-108-RU ROM version.

[AOSP Tamien 8.1 with OpenGapps]

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 $

Categories

Resources