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
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.
Many people who have bought phones from the US and are using them outside of US, are having problems with connecting to the Wifi. For me it started to happen on OGP after Jan 21, 2014 CM11 nightlies.
A workaround was to check anyone of the countries in the settings>wifi>advanced> Region codes. Problem was that this region code would not persist after a reboot and you would have to go through the settings again.
The reason for this problem is the change in code in the MccTables in system>framework> telephony-common.jar which queries the SIM for the locale and since the locale codes in the SIM do not match the Wifi codes in the MccTables, the region does not persist as a permanent entry.
All credits to the dev who figured this out in the HTC sensation Forums: http://forum.xda-developers.com/showthread.php?t=2368501
The method that this dev has posted is based on adding a line in the MccTables which skips the locale checking from the SIM during startup and so the Wifi is able to scan the available networks and connect to the desired one.
The telephony-common.jar is slightly different in different custom roms, therefore we need to patch this file for the individual Roms.
Attached below are the zip files which can be flashed in recovery right after flashing the rom if on a new installation or can be flashed at any time on an older installation in which case after reboot it stops for a while at android is upgrading and then boots normally into the rom.
March 19,2014
Added new Version for newer CM11 nightlies
Note: A wiki page on this problem also provides a lot of insight into this problem: http://forum.xda-developers.com/wiki/WiFi_regional_problem_on_Android#CyanogenMod_based_ROM
Note: The CM11 patched file works on the Mokkee nightlies as well.
March 25 Note: Added zip for new versions of Commotio Rom
Hope this helps the poor sods like me who have been stuck with this problem for a while now.
A word of caution. Make a Nandroid and flash at your own risk
arifqur said:
Many people who have bought phones from the US and are using them outside of US, are having problems with connecting to the Wifi. For me it started to happen on OGP after Jan 21, 2014 CM11 nightlies.
A workaround was to check anyone of the countries in the settings>wifi>advanced> Region codes. Problem was that this region code would not persist after a reboot and you would have to go through the settings again.
The reason for this problem is the change in code in the MccTables in system>framework> telephony-common.jar which queries the SIM for the locale and since the locale codes in the SIM do not match the Wifi codes in the MccTables, the region does not persist as a permanent entry.
All credits to the dev who figured this out in the HTC sensation Forums: http://forum.xda-developers.com/showthread.php?t=2368501
The method that this dev has posted is based on adding a line in the MccTables which skips the locale checking from the SIM during startup and so the Wifi is able to scan the available networks and connect to the desired one.
The telephony-common.jar is slightly different in different custom roms, therefore we need to patch this file for the individual Roms.
Attached below are the zip files which can be flashed in recovery right after flashing the rom if on a new installation or can be flashed at any time on an older installation in which case after reboot it stops for a while at android is upgrading and then boots normally into the rom.
Note: A wiki page on this problem also provides a lot of insight into this problem: http://forum.xda-developers.com/wiki/WiFi_regional_problem_on_Android#CyanogenMod_based_ROM
Note: The CM11 patched file works on the Mokkee nightlies as well.
Hope this helps the poor sods like me who have been stuck with this problem for a while now.
A word of caution. Make a Nandroid and flash at your own risk
Click to expand...
Click to collapse
why is it theming the system?
personally im happy with the kernel change, M2 kernel is as good as M3 or later
atifsh said:
why is it theming the system?
personally im happy with the kernel change, M2 kernel is as good as M3 or later
Click to expand...
Click to collapse
The flashing zip package that I used is an old vr theme package. It just says that its theming when actually it is replacing the required file in the system>framework.
The rationale for using this workaround is that if we keep flashing the old kernel we would miss out on all the new changes that are incorporated in every build.
You don't want to be left happy with an old kernel on a spanking new build.
arifqur said:
The flashing zip package that I used is an old vr theme package. It just says that its theming when actually it is replacing the required file in the system>framework.
The rationale for using this workaround is that if we keep flashing the old kernel we would miss out on all the new changes that are incorporated in every build.
You don't want to be left happy with an old kernel on a spanking new build.
Click to expand...
Click to collapse
no it is changing morethan just the framework, ill build the file myself and see if it works, thanks anyway.
atifsh said:
no it is changing morethan just the framework, ill build the file myself and see if it works, thanks anyway.
Click to expand...
Click to collapse
Why don't you unzip the file and see what's inside?
Anyways you can re-download the files.I have deleted the lines in the updater-script that said stuff about theming.
arifqur said:
Why don't you unzip the file and see what's inside?
Anyways you can re-download the files.I have deleted the lines in the updater-script that said stuff about theming.
Click to expand...
Click to collapse
i did and only required file is the framework, but as i say ill try to build one myself later, im kinda like that . seems pretty simple in the link you provided, just have to edit a line.
atifsh said:
i did and only required file is the framework, but as i say ill try to build one myself later, im kinda like that . seems pretty simple in the link you provided, just have to edit a line.
Click to expand...
Click to collapse
Yup it is pretty simple. Glad this problem has been sorted out, kind-of
arifqur said:
Yup it is pretty simple. Glad this problem has been sorted out, kind-of
Click to expand...
Click to collapse
yeah flashing every time you update is a mess
atifsh said:
yeah flashing every time you update is a mess
Click to expand...
Click to collapse
Hey it isn't that bad. We flash the rom, gapps, sometimes supersu, so flashing another zip is not going to mess up your whole day.
The reality is that any workaround this problem would involve some work. You can't complain at a simple process which rids you of a problem which cannot be solved in any other way and gets you to enjoy the finest and brightest of latest kernel/rom development.
BTW the only other way to get out of this mess is to go to the US and get an AT&T connection.LOL
arifqur said:
Hey it isn't that bad. We flash the rom, gapps, sometimes supersu, so flashing another zip is not going to mess up your whole day.
The reality is that any workaround this problem would involve some work. You can't complain at a simple process which rids you of a problem which cannot be solved in any other way and gets you to enjoy the finest and brightest of latest kernel/rom development.
BTW the only other way to get out of this mess is to go to the US and get an AT&T connection.LOL
Click to expand...
Click to collapse
strange just tried latest nightly on moto atrix hd and it doesn't have this issue, atrix HD also an ATT phone
atifsh said:
strange just tried latest nightly on moto atrix hd and it doesn't have this issue, atrix HD also an ATT phone
Click to expand...
Click to collapse
Not all phones have this problem and also a lot of custom rom devs apply this patch directly in their roms.
I have an S3, S4, HTC One, Note 2, S2 Skyrocket, Nexus4 and none of them have this problem. Even on OGP this problem started from CM11 Jan 22, 2014 build. The Jan 21st build flashes without this issue.
Flashable zip added for new Commotio Rom Nightlies
Any chance to apply the patch to a stock rooted rom?
Thanks
Region Code
Hi can someone fix this file for region code?
nagi_007pk said:
Hi can someone fix this file for region code?
Click to expand...
Click to collapse
Sorry man.
Tried to patch it but seems to be way different in code from the rest of the roms that I have seen.
Can someone post the patch for latest cm nightlies?
nagi_007pk said:
Can someone post the patch for latest cm nightlies?
Click to expand...
Click to collapse
I think the latest cm11 nightlies have this fixed by default.
Had no problems with the April 21st nightly.
If you still have trouble let me know and I will make a patch for you.
arifqur said:
I think the latest cm11 nightlies have this fixed by default.
Had no problems with the April 21st nightly.
If you still have trouble let me know and I will make a patch for you.
Click to expand...
Click to collapse
Yeah man here. Patch this file for me. It's from the rom I'm currently using. It's cm11 based
nagi_007pk said:
Yeah man here. Patch this file for me. It's from the rom I'm currently using. It's cm11 based
Click to expand...
Click to collapse
Here you go.
Hope it works
arifqur said:
I think the latest cm11 nightlies have this fixed by default.
Had no problems with the April 21st nightly.
If you still have trouble let me know and I will make a patch for you.
Click to expand...
Click to collapse
just tried it latest nightly, still the same.
I am having issues with 4g and 3g switching on the device. Some times there will be no signal at all. 80% of the time doing an Airplane mode cycle will fix it. however this is dozens of times a day. This has been an issue since the M8 release. Can anyone send clear directions to a fix please.
System:
LS970
Cm version 11-20140916-SNAPSHOT-M10-ls970
Kernal 3.4.0-CM+
Maybe this post will help. I believe it's in the forum of the ROM you are using. In the future, try reading here for issues.
http://forum.xda-developers.com/showthread.php?t=
HdMsTrTeCh said:
Maybe this post will help. I believe it's in the forum of the ROM you are using. In the future, try reading here for issues.
http://forum.xda-developers.com/showthread.php?t=
Click to expand...
Click to collapse
Not sure if you are being intentionally funny or not, but that link does not go to any thread....
If it was an accident, I think this would be the correct one, right?
http://forum.xda-developers.com/showthread.php?t=2562988
I am not sure what post you were directing that at though.
EDIT: see below for intended post.
Sorry my paste didn't work as expected. here it is....
http://forum.xda-developers.com/showthread.php?p=55462340
Tried that
i couldnt get the APN settings to open up. Through the shortcut maker or terminal. I tried this before posting a new thread. i would have responded to the ongoing thread but XDA rules wont let me post to that one. Had to post here.
domcarreno said:
i couldnt get the APN settings to open up. Through the shortcut maker or terminal. I tried this before posting a new thread. i would have responded to the ongoing thread but XDA rules wont let me post to that one. Had to post here.
Click to expand...
Click to collapse
No problem, everyone starts somewhere.
Try the app "APN Change" from the play store.
better but . . .
So I tried the recommended settings change. Used the Change APN app. LTE is more reliable however when it switches from lte to 3g it will hang for some time or have no connection at all until i cycle airplane mode.
domcarreno said:
I am having issues with 4g and 3g switching on the device. Some times there will be no signal at all. 80% of the time doing an Airplane mode cycle will fix it. however this is dozens of times a day. This has been an issue since the M8 release. Can anyone send clear directions to a fix please.
System:
LS970
Cm version 11-20140916-SNAPSHOT-M10-ls970
Kernal 3.4.0-CM+
Click to expand...
Click to collapse
What radio do you have? (What was the last version of stock you were on?)
Can you get a logcat and radio logcat (logcat -b radio) of the issue happening?
I am using ZVC. The last stock rom i was on was Stocktimus CE 1.5
I dont know how to pull a logcat. Although i have quite a bit of experience flashing and recovering a device from soft brick, I am not much help with troubleshooting. I know just enough to be dangerous.
Hi it was my post that was linked to about adding APNs. I have found that after I flashed stock rooted zvc, updated prl and profile, and restored my CM11 backup, data works fine without requiring a manual APN edit.
However, currently I am running the unofficial GEE-based CM build. I had problems with NFC and battery life last time I tried the official builds (late September), and I do not know the cause or status of those issues. Maybe Shelnutt can weigh in
dwielunski said:
Hi it was my post that was linked to about adding APNs. I have found that after I flashed stock rooted zvc, updated prl and profile, and restored my CM11 backup, data works fine without requiring a manual APN edit.
However, currently I am running the unofficial GEE-based CM build. I had problems with NFC and battery life last time I tried the official builds (late September), and I do not know the cause or status of those issues. Maybe Shelnutt can weigh in
Click to expand...
Click to collapse
i just came from using stocktimus again because i tired of the radio nfc and battery issues as well. dwielunski, what stock rom do you use?
In CM and some others, if you go to settings>mobile networks, there is a built-in shortcut to the APN settings
But honestly, this issue is the most frustrating thing among the AOSP roms, at least for me. It's the one thing that makes me keep flashing back to stock-based ROM's every time I try CM or PA or anything. Why isn't there a clear-cut solution to this when it's such a common problem and we've known about it for so long?
domcarreno said:
i just came from using stocktimus again because i tired of the radio nfc and battery issues as well. dwielunski, what stock rom do you use?
Click to expand...
Click to collapse
Stock rooted zvc as I said. At one point I was using that with a bunch of xposed mods but pretty happy with cm these days. Probably will stay on this until L drops and we get a port. I haven't had any data issues but not sure about NFC
Q&A for [KERNEL][ROM][TW][T800] yTab 1.01 12Nov (want T805 testers)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [KERNEL][ROM][TW][T800] yTab 1.01 12Nov (want T805 testers). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Bug reply
i want to use The private mode ,but it can't work .
Shinine said:
i want to use The private mode ,but it can't work .
Click to expand...
Click to collapse
seems to be due to secured storage not working. will check it again
thanks
edit
ok i know how to solve it, will try it out later today
Shinine said:
i want to use The private mode ,but it can't work .
Click to expand...
Click to collapse
done
Installing from TWRP
I did install this ROM from TWRP 2.8.1.0 on SM-T800. It did install without any issues. Great ROM by the way. Thanks to dev for his great work.
tijgetje13 said:
I did install this ROM from TWRP 2.8.1.0 on SM-T800. It did install without any issues. Great ROM by the way. Thanks to dev for his great work.
Click to expand...
Click to collapse
thanks for your feedback
I can be an additional T805 tester
Hi,
I bought myself a T805 this weekend, and still discovering all features of it.
So I'd like to support the developer here by testing his kernel, but if possible, only the parts where he has doubts about the 805 stability:
I'm still growing in to this tablet, I rooted it this morning. Somehow, it seems more difficult than I thought to say goodbye to 6 months of netflix, 50gb of storage and 2 years of warranty
so, is it possible to limit the kernel install only to the features which are important for the 805 so I can test them for you but still give myself the time to grow into everything?
Installed fine on sm-t800 with twrp 2.7.1. Everything seems fine so far. Got a nice little bump with antutu kudos to the dev
I don't see any extra option in reboot menu, however. Is there something I need to activate?
Hi the roms is great. Very smooth. What i prefer is the float apps. It make some screen bugs when we exit from apps but it works....
do you know that skype doesn't work ? It wouldn't launch. And i have an error with maildroid too.
Your work is wonderfull i hope you continue with this roms
Thanks
jpsollie said:
Hi,
I bought myself a T805 this weekend, and still discovering all features of it.
So I'd like to support the developer here by testing his kernel, but if possible, only the parts where he has doubts about the 805 stability:
I'm still growing in to this tablet, I rooted it this morning. Somehow, it seems more difficult than I thought to say goodbye to 6 months of netflix, 50gb of storage and 2 years of warranty
so, is it possible to limit the kernel install only to the features which are important for the 805 so I can test them for you but still give myself the time to grow into everything?
Click to expand...
Click to collapse
I am not quite sure about your questions. eg what do u mean by llimiting the kernel for 805's features? appreciated if u can explain your thoughts and sorry for my english
barth2 said:
Installed fine on sm-t800 with twrp 2.7.1. Everything seems fine so far. Got a nice little bump with antutu kudos to the dev
I don't see any extra option in reboot menu, however. Is there something I need to activate?
Click to expand...
Click to collapse
I was trying to make the shutdown/restart more simple but still in progress. the current flow is stock power off menu, then a simplier restart menu. what other extra optiona u r looking for?
scritchs said:
Hi the roms is great. Very smooth. What i prefer is the float apps. It make some screen bugs when we exit from apps but it works....
do you know that skype doesn't work ? It wouldn't launch. And i have an error with maildroid too.
Your work is wonderfull i hope you continue with this roms
Thanks
Click to expand...
Click to collapse
yeah, there are some minor problems with the floating apps atm, I will try to make it better later when incorporating the new note 4 floating apps style. however it seems the display comes with the tab s has placed some limitations on the graphics side so problems may occur
I dono skype, maildroid doesnt work since I don use them and no related problems were reported so far. can u send me the log files so that I can take a look at that pls? tell me if u need help for getting the logs
and, I m sorry that I was not checking this q&a section often coz it's a new feature but I don like it actually and always forgot to check this page. so, sorry for the late reply. but pls don get me wrong, I am not ignoring new comers' requests or comments. everyone was a new comer including me
on the other hand pls try to meet the 10 posts barrier (better post them elsewhere or u will have to wait until I remember to check this page again! ) so that u can post in the main thread for better support
thanks
Could you please explain me to catch the log please
scritchs said:
Could you please explain me to catch the log please
Click to expand...
Click to collapse
ok
first, make sure logging is enabled in yTab Synapse Control, then
use adb or terminal emulator, immediately after the skype crashed, for instance, type the following command
logcat -d > /sdcard/20141123xxx.logcat (and press enter, and pls note there r space between every word)
the log will be saved in the sdcard with the filename 20141123xxxx.logcat. u can choose a filename of you choice but I suggest adding the date time as prefix so as to distinguish the logs, add a short desc will help too
or, download catlog from google play, start it before starting skype
after u have the log file, upload it some where and send me the link, better in pm, and tell me about the problems for each log files so that I can addresse the problems eaiser
Ok i will install another tome your rom and i will show uou the log
ykkfive I'm getting periodic freezes where the t800 freezes up completely and I have to do a reset with power+ volume up+ volume down. It seems pretty random and hard to see any pattern. Possibly happening when clicking home and opening another app.
Not using xposed and not over clocking. Nova launcher. ytab update 1.01a
Anyone else getting this? How can I help diagnose this problem
barth2 said:
ykkfive I'm getting periodic freezes where the t800 freezes up completely and I have to do a reset with power+ volume up+ volume down. It seems pretty random and hard to see any pattern. Possibly happening when clicking home and opening another app.
Not using xposed and not over clocking. Nova launcher. ytab update 1.01a
Anyone else getting this? How can I help diagnose this problem
Click to expand...
Click to collapse
hi
have not tried nova but occasionally freezed with tw. but later I found that it's not freezed all the time but just crashed, magazine showed up sometimes when I swiped to the right and then it worked again. I googled and found that it's an open issue not yet fixed
I knew this problem and started to fix it and tested with several changes. looks much better now and will release an update later
thanks
I have flashed a multitude of ROMs on my tab S 10.5 since getting it last summer. Somewhere along the line my tab S lost its US identity. About 4-5 ROMs back after installing a new ROM I no longer could see wireless N 5 ghz SSIDs.
On KitKat the fix was easy, wifi/advanced and pick the correct region. On Lollipop that option is no longer present under wifi/advanced (at least under CM12 it isn’t).
For Lollipop I am using a multi step process to fix the country code.
It works, but given how often I flash ROMs it is kind of a PITA.
At one point I installed stock Samsung European firmware without realizing it was European until it was too late. Recently I installed stock Samsung US firmware. That did not fix it.
I do a clean flash every time I install ROMs. I am currently running CM 12 (cm-12-20141226-UNOFFICIAL-chagallwifi.zip) Bootloader is T800XXU1ANK1.
Any tips on how to fix this permanently so I don’t have to apply the fix every time I flash a ROM would be greatly appreciated.
would you please tell me your multi step process to fix wifi country code on lollipop?! Thanks.
francesco totti said:
would you please tell me your multi step process to fix wifi country code on lollipop?! Thanks.
Click to expand...
Click to collapse
No "multi step" approach, but a solution for changing country code easily:
http://forum.xda-developers.com/showpost.php?p=59172354&postcount=506
nvertigo67 said:
No "multi step" approach, but a solution for changing country code easily:
http://forum.xda-developers.com/showpost.php?p=59172354&postcount=506
Click to expand...
Click to collapse
this didnt work for me on my 8.4. I ended up switching the 5ghz channel to 48 I think. instead of auto.
NJ_RAMS_FAN said:
this didnt work for me on my 8.4. I ended up switching the 5ghz channel to 48 I think. instead of auto.
Click to expand...
Click to collapse
What does not work? Rom? What does your ccode lines look like after editing? What 5GHz channel do you originally want to use?
Have you edited BOTH files? Have you disabled wlan for a couple of seconds?
I can't read your thoughts and your router config, so it is always a good idea to provide as much information as possible to get help.
nvertigo67 said:
What does not work? Rom? What does your ccode lines look like after editing? What 5GHz channel do you originally want to use?
Have you edited BOTH files? Have you disabled wlan for a couple of seconds?
I can't read your thoughts and your router config, so it is always a good idea to provide as much information as possible to get help.
Click to expand...
Click to collapse
yup, i changed both field and rebooted wlan. 5hz originally was on 149. maybe it was the rom I was using on the 8.4. I just gave up on it and left the 5ghz channel on 48 for now. it works. all that matters.. haha..