Related
Hey everyone. between my brothers and I, we have five Evo's. two of us are running full roots and nand unlocks, the other three are using unrevoked. those that unrevoked can use the wifi router without issue, but for my brother and myself, using the wifi router results in the app crashing and having to force close.
has anyone seen anything similar? can anyone offer me some solution?
and btw, this is my third rom. they all have the same results(full wipe, data and davik cache clear each time)
Delete wi fi tether from the phone and re-download it. This has worked for me everytime i change roms =)
Hope it helps.
Do you mean the wireless tether app? I am running my own rom but it seems that it worked for me when I was using fresh. But that is the only other rom I have tried. Have you tried re-installing the tether app?
I'm not sure i can remove the base wifi tether app. it's always cooked into the rom. and i have tried reinstalling the app. i've gone from the original version, to the newer version and finally the beta version with no luck
I was having this issue for awhile. I'm not sure exactly what fixed it, but my work around was:
1. Re-install from the market place (Do not launch)
2. Reboot
3. Install this version http://code.google.com/p/android-wifi-tether/downloads/detail?name=wireless_tether_2_0_5-pre2.apk&can=2&q=NexusOne
(Don't lanch)
4. Reboot
5. Should work now
Hmmmmmm. I am sure someone else can offer better advice, but does the super user app come up to ask for permission or it fc's before that?
topdawgn8 said:
I was having this issue for awhile. I'm not sure exactly what fixed it, but my work around was:
1. Re-install from the market place (Do not launch)
2. Reboot
3. Install this version http://code.google.com/p/android-wifi-tether/downloads/detail?name=wireless_tether_2_0_5-pre2.apk&can=2&q=NexusOne
(Don't lanch)
4. Reboot
5. Should work now
Click to expand...
Click to collapse
okay, i did exactly as you said. now the app will start, but as soon as i click on the wifi symbol, it thinks for a second and says "Unable to start tethering. Please try again!"
Edit: and on first run, it asked me for super user permissions. i click grant and checked the box to allow future requests
I am not sure if your signature is correct but have you tried flashing the newest radio? I am not sure if that would fix it or not. And the same thing happens to the other phone? Puzzling indeed. I'm sure someone will drop in and tell you how to fix it soon. Worst case, start over. Even though I know you said you tried various roms, maybe you are accidentally skipping a step, I do that sometimes
SilverStone641 said:
okay, i did exactly as you said. now the app will start, but as soon as i click on the wifi symbol, it thinks for a second and says "Unable to start tethering. Please try again!"
Edit: and on first run, it asked me for super user permissions. i click grant and checked the box to allow future requests
Click to expand...
Click to collapse
Ok, go back through the same process and try this one instead of what was in step 3.
http://code.google.com/p/android-wi...me=wireless_tether_2_0_2.apk&can=2&q=NexusOne
If that doesn't work, I've got nothing else. The first one was the beta you probably tried earlier. This is the stable one; however, I never tried it with this one. I always got it working using the 2_0_5 version.
Also, for ****s and giggles, have you tried updating you profile and prl?
- you didn't flash the wireless n patch over a 1.47 base Rom correct? Can you connect to a WiFi router or is it just the tether app?
elegantai said:
Also, for ****s and giggles, have you tried updating you profile and prl?
Click to expand...
Click to collapse
uh....what?? you got me there! i thought i knew what those were, but it escapes me now.
the only thing i can think of is that the rooting process screwed up somehow. but for it to screw up in the same way for two separate phones is odd, but it's the only thing that has remained constant since the very beginning.
Menu - settings - system updates. The profile and prl won't mess with root or anything but its something I have heard to do in this case. Don't know if it will help.
Also did you see the note about the wifi n patch on the other page? I added it after I posted... like this
elegantai said:
Menu - settings - system updates. The profile and prl won't mess with root or anything but its something I have heard to do in this case. Don't know if it will help.
Also did you see the note about the wifi n patch on the other page? I added it after I posted... like this
Click to expand...
Click to collapse
done. same results. "Unable to start tethering. Please try again!"
Well crapola. I think I'm outta ideas man. if you didn't patch the wireless n over a 1.47 Rom then I have no clue what it could be. maybe Sprint is spying on you and has your phones on lock down! but if you can't find the answer just try starting fresh. it might be a pain but who knows what little quirk could have gotten messed up.
elegantai said:
Well crapola. I think I'm outta ideas man. if you didn't patch the wireless n over a 1.47 Rom then I have no clue what it could be. maybe Sprint is spying on you and has your phones on lock down! but if you can't find the answer just try starting fresh. it might be a pain but who knows what little quirk could have gotten messed up.
Click to expand...
Click to collapse
i do have the wireless N enabled, but i do not have the new 1.47 yet. i'm waiting on OMJ to release an update
Hey I have a desire Z and my logcat says that the Wifi driver isnt loading. I want to replace it with one that works so my wifi actually turns on.
If you have a bcm4329.ko for the desire z could you please let me know?
Thanks
Isn't that file subject to the kernel you're running? Or are you stock and just looking for the stock bcm file also?
KCRic said:
Isn't that file subject to the kernel you're running? Or are you stock and just looking for the stock bcm file also?
Click to expand...
Click to collapse
Yeah I think it is normally part of a kernel but I cant seem to get this damn wifi to work no matter what I do, so I was thinking if anyone had one of the files kicking around I would just ADB overwrite the old one and see if it works.
Try flashing one of the kernels in my signature -- they both include a corresponding WiFi driver.
theSpam said:
Try flashing one of the kernels in my signature -- they both include a corresponding WiFi driver.
Click to expand...
Click to collapse
Still doesn't work
Really have no more ideas to fix my wifi.
you can always jus download a rom and go to the folder where its located and take it out and push it in your phone instead of waiting for some one
ilostchild said:
you can always jus download a rom and go to the folder where its located and take it out and push it in your phone instead of waiting for some one
Click to expand...
Click to collapse
I tried that too and it didn't do anything. Im really pulling at straws. Is there a program to test to make sure the hardware is actually good?
Im sure you done this already but some one is bound to ask, so ask now.
have you tried to wipe
and reflash the rom your using and try it again,
ilostchild said:
Im sure you done this already but some one is bound to ask, so ask now.
have you tried to wipe
and reflash the rom your using and try it again,
Click to expand...
Click to collapse
Yep, tried that twice. I even went back to stock between the reload.
One time I flashed it using the PC10IMG method and the other I used Clockwork (rom manager).
I really have no idea where to go at this point. I think I've exhausted all my ideas. Ive tried reflashing roms, kernels, and radios.
Was hoping someone had some diagnostic software that would test the hardware of the phone or something so at least then I would know if my actual hardware for the WiFi and Bluetooth was shot or not.
Thanks anyways.
Wow, I forgot about this thread over the weekend
Anyway, have you tried changing the permissions for the file? You can use 'fix permissions' in ROM Manager or clockwork or use Root Explorer to change the permissions. Of course if you're a terminal kind of guy you can chmod it.
Sometimes the permissions don't set correctly or, on some systems running linux, the permissions get changed for some reason. Maybe that's what's going no here, sounds like it anyway. Btw, make sure to reboot after changing the permissions because it won't work until you do.
has anyone fixed this issue where wifi stops working?
wifi not turning ON
Hello Everyone,
During the process of getting IP address from WiFi network, I received a "Error Massage" on my Alcatel OT-990. After this massage, WiFi started behaving abnormally. Sometimes it turned ON another time it did not. Now after a few weeks later, WiFi is not turning ON at all.
I have Tried following Solutions but nothing worked:
1. Did factory reset, erased system, cache etc and Flashed different ROMs (JB ot 990, ICS QME, QLTsar, 2.3.4, Telenor One touch 4.0.04) using Recovery many a times(From different Sources).>>Problem not solved
2. Updated my phone using alcatel update manager to 2.3.4>>> Problem not solved
3. Tried by changing permissions of BCM4329.KO, wpa_supplicant.confg etc every file related to wifi/wlan>>Problem not solved
4. Used WiFix Manager>>>Problem not solved.
Bluetooth and FM radio working all right.
If anybody knows about its solution ..please help me out.
Since about January, all the CM7 based roms have had flaky GPS for me. Basically it loses the signal after about 5 minutes. A quick GPS on/off cycle usually fixes the problem. However, I really don't like the distraction
(and the danger) of messing with the gps when driving 70 mph.
I spent quite a bit of time searching for a solution on this and other forums, but found nothing helpful. Yesterday, I got the idea to try out one of the Sense GPS drivers in the AOSP roms. I extracted the attached file from one of the Stock roms and replaced the AOSP driver.
The good news is it appears to work. In the 4 times I've driven I didn't have to do any GPS cycling.
Steps:
1) Extract the attached gps.glacier.so.zip file.
2) Using Root Explorer or ES File Explorer (with the root option checked) copy the attached gps.glacier.so file into your system/lib/hw directory replacing the current file.
3) Reboot.
4) You may want to clear out the A-GPS state using the GPS status app, but I don't know if this is necessary or not.
or
1)Use clockworkmod to install the GPS_Fix.zip file.
Anyway, I hope this helps someone else. I am thinking of developing zip you can flash if there is interest in it. But in the meantime I wanted to post the fix, since I know there have been other people with the same problems I had.
I hope this helps!
EDIT-
I have also added the gps_update.zip that has the gps.conf file, the supl.root.cert and the gps.glacier.so all put together by tnpapadakos
testing now
have you tried the gps.conf by crypted? the gps lock is way quicker/better than the stock/aosp gps.conf file
just wondering if you tried it
tnpapadakos said:
testing now
have you tried the gps.conf by crypted? the gps lock is way quicker/better than the stock/aosp gps.conf file
just wondering if you tried it
Click to expand...
Click to collapse
No, I haven't tried it. My lock time hasn't been bad... I usually have a lock in the time it takes me to pull out of my garage. That being said, I am always tweaking things so I will definitely give it a try.
Gadianton said:
No, I haven't tried it. My lock time hasn't been bad... I usually have a lock in the time it takes me to pull out of my garage. That being said, I am always tweaking things so I will definitely give it a try.
Click to expand...
Click to collapse
use this one
these work for glacier but are in other threads, you'll notice
in any case, this is the one to use if you wanna save yourself some reading
also, the guy's a fricking genius or something, open up the file in that zip and see what he's doing...he's hosting his own gps servers
tnpapadakos said:
use this one
these work for glacier but are in other threads, you'll notice
in any case, this is the one to use if you wanna save yourself some reading
also, the guy's a fricking genius or something, open up the file in that zip and see what he's doing...he's hosting his own gps servers
Click to expand...
Click to collapse
Thanks. I just finished reading through his notes.
tnpapadakos said:
use this one
these work for glacier but are in other threads, you'll notice
in any case, this is the one to use if you wanna save yourself some reading
also, the guy's a fricking genius or something, open up the file in that zip and see what he's doing...he's hosting his own gps servers
Click to expand...
Click to collapse
Do you flash this in recovery?
Sent from my HTC Glacier using XDA
Supamike88 said:
Do you flash this in recovery?
Sent from my HTC Glacier using XDA
Click to expand...
Click to collapse
The gps.conf by crypted file can be flashed in recovery. You can also just open up the zip and copy it using root explorer, etc.
Gadianton said:
The gps.conf by crypted file can be flashed in recovery. You can also just open up the zip and copy it using root explorer, etc.
Click to expand...
Click to collapse
somtimes I just add it to the rom before flashing, and you have to also add the SuplRootCert to system/etc, but if he comes up with an update in between roms, i just flash from recovery....
Gadianton said:
Since about January, all the CM7 based roms have had flaky GPS for me. Basically it loses the signal after about 5 minutes. A quick GPS on/off cycle usually fixes the problem. However, I really don't like the distraction
(and the danger) of messing with the gps when driving 70 mph.
I spent quite a bit of time searching for a solution on this and other forums, but found nothing helpful. Yesterday, I got the idea to try out one of the Sense GPS drivers in the AOSP roms. I extracted the attached file from one of the Stock roms and replaced the AOSP driver.
The good news is it appears to work. In the 4 times I've driven I didn't have to do any GPS cycling.
Steps:
1) Extract the attached zip file.
2) Using Root Explorer or ES File Explorer (with the root option checked) copy the attached gps.glacier.so file into your system/lib/hw directory replacing the current file.
3) Reboot.
4) You may want to clear out the A-GPS state using the GPS status app, but I don't know if this is necessary or not.
Anyway, I hope this helps someone else. I am thinking of developing zip you can flash if there is interest in it. But in the meantime I wanted to post the fix, since I know there have been other people with the same problems I had.
I hope this helps!
Click to expand...
Click to collapse
Don't forget to check the permissions on the file. I am not sure if it was because I backed up the old one first and copied in the new one after, but I had to change the permissions to rw-r--r--.
This, I learned the hard way. I always forget something...
G8351427 said:
Don't forget to .....change the permissions to rw-r--r--.
Click to expand...
Click to collapse
definitely....i always check the permissions of the file i'm replacing and match that on a new file, or, if i'm inserting one thats not there, i look at the permissions of the surrounding similar files, and match it to those
otherwise, rw-r--r-- is usually the fallback
Yea I have noticed that the best GPS experience I have had was when the phone was completely stock the GPS worked great, locked on quickly, and never lost signal. After I flashed it and such the GPS has been a pain to get lock when I needed it the most.
I've found that any of the radios after the official Froyo version causes the GPS to fail after a few minutes as described by the OP. However, with some of the newer ROMS I've found that the newest radio doesn't completely lose the GPS signal but it does still seem to temporarily lose it but it then it comes back by itself (causes navigation to get stuck at a location for a minute or two every now and then).
I tried the driver and agps mod from this thread. At first it completely killed my GPS then someone posted about the required permission changes which fixed that. I haven't tried navigation so I can't say whether it prevents the temporary position loses, but it does seem to still be pretty slow to lock on and after it does lock on may take several minutes before the accuracy gets to a useful level.
I think I'm going to go back to the Froyo radio as that one seems to work the best for GPS and I'm not convinced it makes much of a difference for voice/data. Perhaps the Froyo radio with these mods would be the best?
tmagritte said:
I've found that any of the radios after the official Froyo version causes the GPS to fail after a few minutes as described by the OP. However, with some of the newer ROMS I've found that the newest radio doesn't completely lose the GPS signal but it does still seem to temporarily lose it but it then it comes back by itself (causes navigation to get stuck at a location for a minute or two every now and then).
I tried the driver and agps mod from this thread. At first it completely killed my GPS then someone posted about the required permission changes which fixed that. I haven't tried navigation so I can't say whether it prevents the temporary position loses, but it does seem to still be pretty slow to lock on and after it does lock on may take several minutes before the accuracy gets to a useful level.
I think I'm going to go back to the Froyo radio as that one seems to work the best for GPS and I'm not convinced it makes much of a difference for voice/data. Perhaps the Froyo radio with these mods would be the best?
Click to expand...
Click to collapse
I have noticed the "stuck position" before. I haven't paid attention to that with this mod before. I'll have to keep an eye out for it.
I have updated the OP to include a CWM flashable GPS_Fix.zip file. It worked for me, but if anyone wants to test it, I'd appreciate it.
The thing I am most curious about is if the file is copied with the correct permissions.
thanks.
Gadianton said:
I have updated the OP to include a CWM flashable GPS_Fix.zip file. It worked for me, but if anyone wants to test it, I'd appreciate it.
The thing I am most curious about is if the file is copied with the correct permissions.
thanks.
Click to expand...
Click to collapse
I flashed the update and after that the GPS locked on pretty quick. I haven't tested for navigation yet.
here's one with the gps.conf file, the supl.root.cert and the gps.glacier.so all put together if anyone would like to test it
quick satellite fixes and continuous GPS lock
(hopefully)
It worked on MIUI... Thanks...Its been losing signal for the longest time and now it locked in and never lost it again...
THANK YOU!!!!!!!!!!
spyderman33 said:
It worked on MIUI... Thanks...Its been losing signal for the longest time and now it locked in and never lost it again...
THANK YOU!!!!!!!!!!
Click to expand...
Click to collapse
I'm glad it helped you out!
Thanks best thing we needed yet. Works perfect wit miui.us.
Sent from my HTC Glacier using xda premium
I updated the OP to include the gps_update.zip put together by tnpapadakos and updated the thread title to include MIUI.
When installing FXP113 to my phone, I found that on bootup I would get an error on the phone process and I had no service. After trying a few different things, I finally found the solution: Install FXP112 first, then install FXP113 over it without wiping data. Here is a step by step tutorial on installing FXP113 on the R800x. It probably would work the same for all Xperia Plays.
Required: Rooted Xperia Play and unlocked bootloader.
Needed Files: FXP112 as modified by Chevyowner
FXP113 as modified by Chevyowner
Replacement build.prop file for R800x
Fastboot - Fastboot+ADB+Fastboot_Drivers.zip
Sony Drivers
Recommended: Boot into recovery and make a Nandroid backup before continuing.
1. Copy the files for FXP112 and FXP113 to your sdcard. You will need to access these from recovery.
2. Install Fastboot. Unzip the file into C:\fastboot.
5. 2. Extract the boot.img of your choice to the fastboot directory. You may use the one in FXP113, or DarkForest3.img or DarkForest4.img (available here.)
5. Enter into Fastboot Mode. - Turn off phone. Hold search button down. Plug in USB cable. The power light should be blue The first time you do this, you will be prompted for the fastboot drivers. They will be in C:\fastboot\fastboot drivers.
6. To flash the new boot image, go to a command prompt and change to the c:\fastboot directory. Then use the following command:
fastboot -i 0x0fce flash boot boot.img <----- the name of your boot image.
7. When finished, remove the usb cable. Power on the phone and enter into Recovery. On some kernels, you will press repeatedly the volume down button; on others, you will press repeatedly on the back button or possibly the search button.
8. You MUST clear Data, Cache and Dalvik Cache. It is also recommended by some people to clear the battery stats.
9. Install zipfile from sdcard. Select the FXP112 file first. Allow it to install and then reboot the phone. (I usually clear data, cache and dalvik again just to be sure.)
10. Activate your phone on the Verizon network.
11. Now shut down and reboot into Recovery again.
12. This time, clear ONLY cache and dalvik cache. Do NOT clear data.
13. Install zipfile from sdcard. Select the FXP113 file this time. Allow it to install and then reboot the phone.
14. Copy the build.prop file into /system. You may want to rename the current one first.
15. Reboot and enjoy! You should be up and running with full data, wifi access now.
re
So for step #10 do u get charged from verizon to activate ur new roms data?
And for #14 do u just copy it via root explorer to /system?
Thanks for taking time to write this
FPlusPS3 said:
So for step #10 do u get charged from verizon to activate ur new roms data?
And for #14 do u just copy it via root explorer to /system?
Thanks for taking time to write this
Click to expand...
Click to collapse
#10 There is no charge to activate the phone if you already have service. It's like dialing *228 and choosing option 1, only the system does it for you.
#14 Yes, you can just copy it to \system, but don't forget to change access to RW before pasting. You may also want to rename the old file first as a backup, although I never have.
Sent from my R800x using XDA
my phone gets stuck at the android screen after i flash fxp112
johnboyjr said:
my phone gets stuck at the android screen after i flash fxp112
Click to expand...
Click to collapse
What kernel did you use?
Did you clear data, cache and dalvik cache before you installed FXP112?
If yes, just for kicks, go clear it again.
Also, remember, the first boot after a clean install takes longer than normal.
Sent from my R800x using XDA
yes i cleared them and and i tried DarkForest4 and fxp112
i waited over 15 min still nothing
johnboyjr said:
yes i cleared them and and i tried DarkForest4 and fxp112
i waited over 15 min still nothing
Click to expand...
Click to collapse
OK. Well, if it were me, the next thing I would do is to flash back to totally stock and get that working. Then try it again.
Sent from my R800x using XDA
What changes are in your build.prop? I've been running fine (except for one or two small problems) with the standard build.prop from FXP112.
crono141 said:
What changes are in your build.prop? I've been running fine (except for one or two small problems) with the standard build.prop from FXP112.
Click to expand...
Click to collapse
I think it was just edited to identify the phone properly as an R800x. PaxChristos told me to use it when he helped me install FXP111 and I have used it ever since. I haven't had any issues at all with it, so you might give it a try if you're on Verizon.
Sent from my R800x using XDA
That was only needed the first time Chevy made FXP111 work, he missed some things in the build.prop that created graphical artifacts in menus and such. All of his builds after that have the correct build.prop now.
Sent from my R800x using XDA
*22899 is the shortcut for activating service in case anyone wanted to just store it for future reference
-and you can also use flashtool to flash back to stock or flash a new kernel
*228 worked fine for me. semcsuite.apk won't show up in my app drawer. I moved it to /system/app and fixed permissions. Still not there.
Sent from my R800x using XDA
Wallrunner said:
That was only needed the first time Chevy made FXP111 work, he missed some things in the build.prop that created graphical artifacts in menus and such. All of his builds after that have the correct build.prop now.
Sent from my R800x using XDA
Click to expand...
Click to collapse
Thanks! Good to know, and one less thing to screw with in the future!
Sent from my R800x using XDA
re
Does Psxperia or XPERIA GAMEPAD games even work on cm9
For some reason, trying use videocall in gtalk worked fine at first, but changing to rear camera made gtalk fc. After that no camera works at all.
GPS only works on maps (no on gps status, or any other app), since my wifi neighbours are all on the google database i'm not sure if the true gps is really working.
And have another annoying things.
I'm hacking all my phones since android 2.1, and I cant consider this release as an true release candidate. Its more beta.
I have a r800i.
FPlusPS3 said:
Does Psxperia or XPERIA GAMEPAD games even work on cm9
Click to expand...
Click to collapse
From what I have read... no. That is why I have not jumped ship to CM. Otherwise I would be there right now. So until they get the touchpads working I will wait, although I have also read they are working on creating from scrathc their own drivers for the touchpads as the current drivers now require SE framework...... so cross your fingers.
Nighty0 said:
For some reason, trying use videocall in gtalk worked fine at first, but changing to rear camera made gtalk fc. After that no camera works at all.
GPS only works on maps (no on gps status, or any other app), since my wifi neighbours are all on the google database i'm not sure if the true gps is really working.
And have another annoying things.
I'm hacking all my phones since android 2.1, and I cant consider this release as an true release candidate. Its more beta.
I have a r800i.
Click to expand...
Click to collapse
Not to be rude or by any disrespect but how isn't it a "true" release? A release is a release..being that it's in beta status doesn't mean it's any less, cm is always changing and improving so there is no hey this is the final version kind of thing..CDMA isn't even supported by cm at all so the fact we have cm9 before verizon gives it to us is amazing. Just to point out, this isn't hacking by any means, android is open source..it's like going into an open store and saying you're breaking in
agraceful said:
Not to be rude or by any disrespect but how isn't it a "true" release? A release is a release..being that it's in beta status doesn't mean it's any less, cm is always changing and improving so there is no hey this is the final version kind of thing..CDMA isn't even supported by cm at all so the fact we have cm9 before verizon gives it to us is amazing. Just to point out, this isn't hacking by any means, android is open source..it's like going into an open store and saying you're breaking in
Click to expand...
Click to collapse
Yes, giving their release to us is amazing, but saying that camera works on changelog, and not even the basic apps like gtalk and camera works, this barely can be considered as working.
As a software engineer I label as a beta, not RC anything. beta is to fix stopper bug like this, RC is for the little annoyances lonely.
For example, my work friend installed another rom on their htc sensation, labeled as beta and all features works, with jagged areas here and there.
And yep, I know the Team FreeXperia is a one guy team
I'm happy with all this releases, only frustrated because the thing is being labeled as working, when not. So I made a report here to make sure another person doesn't make the same mistake as me.
netizenmt said:
Thanks! Good to know, and one less thing to screw with in the future!
Sent from my R800x using XDA
Click to expand...
Click to collapse
actually this build.prop works better it lets Plants Vs Zombies and Asphalt 6 RUN and work
How do install install the custom rom and set up fastboot?
This is my first ever ROM to post up. I just recently started building them. This is a stock deodexed Nougat ROM that is pre rooted. It is 100% AT&T Nougat with just a few fixes. I have left all Samsung and AT&T bloat for those that want all the bloat but like to be rooted and deodexed.
Follow the steps below for installation:
Step 1: You must already be on Nougat firmware. There are various threads on how to do this but if you can not figure it out just ask and i will try to assist you the best i can.
Step 2: Once on Nougat, root your device. Follow this guide https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502
Step 3: Once Rooted, install Flash fire from playstore.
Step 4: Open Flashfire and grant SuperSU access, once you are at the main menu, press the + and select Flash ZIP or OTA, go to the place you stored the ROM and selecet it. On the next screen MAKE SURE "Mount /system read/write" is selected and click the check mark in the upper right hand corner.
Step 5: Click the + sign again and select "Wipe", leave the defaulted boxes checked (System data, 3rd party apps, and Dalvik cache) and click the check mark in the upper right corner again. ( optional, you can select internal storage but you don't have to).
Step 6: VERY VERY IMPORTANT, select and hold down on Wipe and move it above "Flash ZIP or OTA"
Step 7: Make sure EverRoot is disabled and Reboot is set to normal.
Step 8: Click the lightning bolt and then yes on the next prompt, and let FF do it's thing.
*****Be patient, it will take up to 15 min to boot but most times it is quicker than that.*****
* Fixes i added
Fingerprint fix after root. Thanks to @qwewqa
Replaced IMSService.apk to remove hurricane icon.
CPU Fixes. Thanks to @stang5litre
Issues:
Phone forgetting Bluetooth devices after reboot, I am trying to find a fix for it and will update when i do.
Thanks @stang5litre for countless hours and days of walking me through so many steps from setting up my kitchen to fixing my phone via TV and ADB.
Thanks @SuperR. for the kitchen and all the continued support
Thanks @Chainfire for Flashfire and SuperSU
Download link: https://www.dropbox.com/s/17w8ut192jwixnw/G930AUCS4BQE1.zip?dl=0
Where did you get the ATT stock firmware?
Edit: nevermind I thought you had the latest firmware sorry. Good luck on your first rom
jrkruse said:
Where did you get the ATT stock firmware?
Edit: nevermind I thought you had the latest firmware sorry. Good luck on your first rom
Click to expand...
Click to collapse
Thanks bud. I've been looking for the latest but can't find it. I tried to pull it from my phone using superR kitchen but couldn't deodex it correctly. So inn still working on it. Lol
Congrats bud!!!
Cool. Does adoptable storage work with this ROM?
yuejon said:
Cool. Does adoptable storage work with this ROM?
Click to expand...
Click to collapse
This is 100% stock rooted, deodex, if it didn't work on stock unrooted, chances are that it don't work on this one either.
Hello, I've flashed the rom and loving it so far, it is buttery smooth and seems to have the same battery drain as in stock, but two problems... Every reboot or when I just turn off the wifi, it forgets the password. I've tried build prop editor and set ro.securestorage.suppprt to false, but no success. Another problem, Blutooth won't turn on. It used to before I changed the build prop, but now, it just doesn't turn on. I'm not sure if it is a problem with nougat root or your rom itself, I would love some answers. Otherwise the rom is great and I hope you continue to update it as there isn't a lot of development in AT&T.
OfferedBison said:
Hello, I've flashed the rom and loving it so far, it is buttery smooth and seems to have the same battery drain as in stock, but two problems... Every reboot or when I just turn off the wifi, it forgets the password. I've tried build prop editor and set ro.securestorage.suppprt to false, but no success. Another problem, Blutooth won't turn on. It used to before I changed the build prop, but now, it just doesn't turn on. I'm not sure if it is a problem with nougat root or your rom itself, I would love some answers. Otherwise the rom is great and I hope you continue to update it as there isn't a lot of development in AT&T.
Click to expand...
Click to collapse
Thank you for your feedback. I have experienced the Bluetooth issue on another more custom rom that I'm building, i haven't pin pointed it yet but am still working on it. I was originally thinking it had something to do with something that i removed from the rom (bloat) because when i run this rom with all the bloat i didn't have the issue. I will switch back to this rom and run it for a few days and see if the issue pops back up. As for the WiFi password, i have no problem with that and i have mine set to "true". I'll look into it though and get back with you.
For the battery drain, install kernel auditor, settings menu in top left corner, go to cpu, and set the governor to "on Demand" that will help a little bit.
dirtydodge said:
Thank you for your feedback. I have experienced the Bluetooth issue on another more custom rom that I'm building, i haven't pin pointed it yet but am still working on it. I was originally thinking it had something to do with something that i removed from the rom (bloat) because when i run this rom with all the bloat i didn't have the issue. I will switch back to this rom and run it for a few days and see if the issue pops back up. As for the WiFi password, i have no problem with that and i have mine set to "true". I'll look into it though and get back with you.
For the battery drain, install kernel auditor, settings menu in top left corner, go to cpu, and set the governor to "on Demand" that will help a little bit.
Click to expand...
Click to collapse
Thank you. The Bluetooth problem was fixed when I reverted the changes I made in build prop, and for the wifi problem I think it was something I froze in titanium backup, since I froze some bloat etc.
OfferedBison said:
Thank you. The Bluetooth problem was fixed when I reverted the changes I made in build prop, and for the wifi problem I think it was something I froze in titanium backup, since I froze some bloat etc.
Click to expand...
Click to collapse
The changes you made in build.prob? You mean by setting the secure.storage to false? I do know that on the custom Rom I'm building, i had it set to false and i was having the blue tooth issue, for the WiFi issue, it could be something you froze, can you SS your frozen list.
dirtydodge said:
The changes you made in build.prob? You mean by setting the secure.storage to false? I do know that on the custom Rom I'm building, i had it set to false and i was having the blue tooth issue, for the WiFi issue, it could be something you froze, can you SS your frozen list.
Click to expand...
Click to collapse
Here,
OfferedBison said:
Here,
Click to expand...
Click to collapse
Thanks, the only two things that I'm not sure what it is, is UPSM_N and com.android.Samsung. M. I'm not saying that could be causing it but I'll habe to research what those two things are. Thank you.
dirtydodge said:
Thanks, the only two things that I'm not sure what it is, is UPSM_N and com.android.Samsung. M. I'm not saying that could be causing it but I'll habe to research what those two things are. Thank you.
Click to expand...
Click to collapse
I defrosted android.samsung, but cannot defrost upsm.n, weird. This doesn't seem to be the problem as it still persists.
OfferedBison said:
I defrosted android.samsung, but cannot defrost upsm.n, weird. This doesn't seem to be the problem as it still persists.
Click to expand...
Click to collapse
So your still having the WiFi problem not remembering password after reboot? My ro.secure is set to true and I'm not having the issue.
dirtydodge said:
So your still having the WiFi problem not remembering password after reboot? My ro.secure is set to true and I'm not having the issue.
Click to expand...
Click to collapse
Unfortunately, yes. Maybe something went wrong when I flashed the rom... I'll try reflashing the rom later , when I have time.
OfferedBison said:
Unfortunately, yes. Maybe something went wrong when I flashed the rom... I'll try reflashing the rom later , when I have time.
Click to expand...
Click to collapse
ok. Yea i would try that. I can't duplicate the issue on my end. Leave the ro.secure storage set to true and see if that fixed it. That's what mine is set at and I'm not having any problems with Bluetooth or passwords at this moment.
dirtydodge said:
ok. Yea i would try that. I can't duplicate the issue on my end. Leave the ro.secure storage set to true and see if that fixed it. That's what mine is set at and I'm not having any problems with Bluetooth or passwords at this moment.
Click to expand...
Click to collapse
I have reflashed the rom and also added a dual speaker mod. Everything is working like a charm. Bluetooth and Wifi are all working.
Flashed this and it works fine, but I also experience WiFi 'losing' passwords.
I just flashed it again and no change. In fact, from the time I enter the WiFi password during setup until setup is done, I have to re-enter WiFi password because it 'forgets' (it reports authentication error later after having worked fine initially)
Any other ways to fix this so I don't have to keep re-entering passwords like this?
JJHiemenz said:
Flashed this and it works fine, but I also experience WiFi 'losing' passwords.
I just flashed it again and no change. In fact, from the time I enter the WiFi password during setup until setup is done, I have to re-enter WiFi password because it 'forgets' (it reports authentication error later after having worked fine initially)
Any other ways to fix this so I don't have to keep re-entering passwords like this?
Click to expand...
Click to collapse
Use root explorer, go to system/build.prop and make sure ro.secure.storage is set to "true" as shown in the attachment. I live around Houston TX so we're prepping for the hurricane at the moment so I might be oit for a few days but I'll try to check back on here as soon as I can. Another issue that has been brought up is the phone forgetting Bluetooth device after a reboot. At this moment there is no fix for it that i can find. As soon as I can find a fix for this i will upload a new version.
same g930a-v models-same problem.pls wanted phone emergency backup file (g930a-v same
same g930a-v models-same problem.pls wanted phone emergency backup file (g930a-v same).help me pls all user phone no down mode.
http://forum.gsmhosting.com/vbb/f10...0a-sbl-error-upload-mode-pls-help-me-2301220/
dirtydodge said:
This is my first ever ROM to post up. I just recently started building them. This is a stock deodexed Nougat ROM that is pre rooted. It is 100% AT&T Nougat with just a few fixes. I have left all Samsung and AT&T bloat for those that want all the bloat but like to be rooted and deodexed.
Follow the steps below for installation:
Step 1: You must already be on Nougat firmware. There are various threads on how to do this but if you can not figure it out just ask and i will try to assist you the best i can.
Step 2: Once on Nougat, root your device. Follow this guide https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502
Step 3: Once Rooted, install Flash fire from playstore.
Step 4: Open Flashfire and grant SuperSU access, once you are at the main menu, press the + and select Flash ZIP or OTA, go to the place you stored the ROM and selecet it. On the next screen MAKE SURE "Mount /system read/write" is selected and click the check mark in the upper right hand corner.
Step 5: Click the + sign again and select "Wipe", leave the defaulted boxes checked (System data, 3rd party apps, and Dalvik cache) and click the check mark in the upper right corner again. ( optional, you can select internal storage but you don't have to).
Step 6: VERY VERY IMPORTANT, select and hold down on Wipe and move it above "Flash ZIP or OTA"
Step 7: Make sure EverRoot is disabled and Reboot is set to normal.
Step 8: Click the lightning bolt and then yes on the next prompt, and let FF do it's thing.
*****Be patient, it will take up to 15 min to boot but most times it is quicker than that.*****
* Fixes i added
Fingerprint fix after root. Thanks to @qwewqa
Replaced IMSService.apk to remove hurricane icon.
CPU Fixes. Thanks to @stang5litre
Issues:
Phone forgetting Bluetooth devices after reboot, I am trying to find a fix for it and will update when i do.
Thanks @stang5litre for countless hours and days of walking me through so many steps from setting up my kitchen to fixing my phone via TV and ADB.
Thanks @SuperR. for the kitchen and all the continued support
Thanks @Chainfire for Flashfire and SuperSU
Download link: https://www.dropbox.com/s/17w8ut192jwixnw/G930AUCS4BQE1.zip?dl=0
Click to expand...
Click to collapse