Before you continue further, here are the prerequisites
1.) Root permissions
2.) Root explorer or similar file manager with root access
Please google on how the GPS transceiver in your Ace works. Basically what i am doing is to change the ntp time servers that your Ace contacts. You will be tasked to change the time servers to those which are physically closer to your current location.
Why? Because before the GPS transceiver is able to establish the rough position(s) of the satellite, it needs to contact time servers.
Also, Skyhook (again please google) and A-GPS will enabled in your gps.conf that will help your Ace acquire GPS locks more quickly.
There are two files that you need to acquire from here.
gps.conf and secgps.conf
gps.conf
Code:
NTP_SERVER=0.sg.pool.ntp.org
NTP_SERVER=0.asia.pool.ntp.org
NTP_SERVER=3.asia.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
XTRA_SERVER_4=http://xtra4.gpsonextra.net/xtra.bin
INTERMEDIATE_POS=0
ACCURACY_THRES=0
DEBUG_LEVEL=3
ENABLE_WIPER=0
ENABLE_XTRA=TRUE
SUPL_HOST=supl.google.com
SUPL_PORT=7276
SUPL_SECURE_PORT=7275
SUPL_NO_SECURE_PORT=3425
SUPL_HOST=supl.skyhook.com
SUPL_PORT=7278
CURRENT_CARRIER=common
#REPORT_POSITION_USE_SUPL_REFLOC=1
DEFAULT_AGPS_ENABLE=TRUE
DEFAULT_SSL_ENABLE=FALSE
DEFAULT_USER_PLANE=TRUE
#START_MODE=WARM
#OPERATION_MODE=STANDALONE
PHONE_TYPE=UMTS
Instructions:
Observe that in the top most section of the code there is the line "NTP_SERVER=". I want you to go to this website http://www.pool.ntp.org/en/, click on your country and find the list of NTP servers that can be used. For e.g. for my case in Singapore it will be
0.sg.pool.ntp.org
0.asia.pool.ntp.org
3.asia.pool.ntp.org
Next, insert the servers which you have just copied onto the line "NTP_SERVER=" immediately after the = without the quotations. Please verify by using cmd in Windows to ensure that the time servers you have chosen are active and online. Just simply do a ping and a tracert.
Note: if you find the ping times are ridiculous, you can opt to use the continental time servers e.g. i can use Asia NTP servers instead. Good ping times are about 20ms or less.
Ok, now copy and paste the whole code (which you have inserted your new NTP servers earlier on) onto Notepad and saved as gps.conf (all files instead of .txt)
Copy and paste this gps.conf to overwrite the original gps.conf at /system/etc.
Original gps.conf
Code:
NTP_SERVER=north-america.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
SUPL_HOST=supl.google.com
SUPL_PORT=7276
PHONE_TYPE=UMTS
secgps.conf
Code:
#Generated by GpsLocationProvider.
#Thu Dec 02 13:09:21 EST 2010
SSL=1
SSL_TYPE=0
POSITION_MODE=7
OPERATION_TEST_MODE=0
ACCURACY=50
SESSION_TYPE=1
SERVER_MODE=0
ENABLE_NMEA=false
START_MODE=HOT
GPS_LOGGING=0
AGPS_MODE=0
DYNAMIC_ACCURACY=1
ADDRESS_MODE=1
TIME_BTW_FIX=2000
OPERATION_MODE=MSBASED
USE_DEFAULT=true
DYNAMIC_ACCURACY_VALUE=50
SUPL_PORT=7276
ENABLE_XTRA=true
SUPL_HOST=supl.google.com
NUM_OF_FIX=999999999
TIMEOUT=3600
Instructions:
Copy and paste the code above for secgps.conf onto Notepad and save as secgps.conf (all files type instead of .txt) Use Root explorer to copy and paste this file in /data/gps.
=========================================================================================================================================
I was inspired by the thread over here
http://forum.xda-developers.com/showthread.php?t=1034631
My motivation to do up my gps.conf and secgps.conf is partly of the fact that PFGPS fix didn't work for me and configuring the GPS using the secret code ie *#*#1472365#*#* didn't work as well.
Please don't blame me if this breaks anything. I have tested this on my system and i got a GPS lock by the windowside (indoors) under a minute. Accuracy is 6~8m which i thought was impressive. it should work on all ROMs because i have tested this on a stock ROM, XXKPO.
Note: if you have applied PFGPS fix, this WILL overwrite whatever settings PFGPS fix has made. Be warned.
======================================================
If you are wondering about permissions, it should be
rw-r-r for both files
=======================================================
Update! New set of gps.conf and secgps.conf files provided.
After reviewing the literature and discovering that there is a good chance the GPs module in the S5830 might be Qualcomm's GpsOne, i did some sleuthing and research. I realised that while the gps.conf and secgps.conf did gave vast improvements over the stock settings, it still wasn't optimised as far as it should be.
For one, most values in the secgps.conf (Secondary GPS Configuration file) was left stock. So the lowdown is this. I basically enabled full A-GPS mode and moved away from standalone mode. GPS operation modes come in the following
1.) Standalone (Slowest using positioning information in cache and smart polling)
2.) MS-Based (Sends data to nearby cell tower(s) and makes use of GPS transceivers in the cell tower(s)
3.) MS-Assisted (Similar to MS-Based BUT data connectivity is broken when GPS transceiver is online. I don't quite like that!)
4.) MS-Based/Hybrid (You need to have superb data connectivity probably cell tower signal strength should be in the -50dBm region. Not very useful in real life usage)
As such, i have tweaked the gps.conf and the secgps.conf files to use MS-based operation. HOWEVER, this means that your GPS transceiver now DEPENDS on your carrier signal to establish super fast GPS lock. So, if you
1.) Go overseas with no roaming
2.) Are in a vicinity with no cell towers
This would means that the latest tweaks wouldn't help in that case so do exercise some discretion on your end. Kapish?
Also, i have changed the values in secgps.conf to be more aggressive all in the name of performance. I have found in my experience that GPS locks are now more stable.
TTFF ~25 seconds
Subsequent GPS Locks ~ 5 seconds
gps.conf
Code:
NTP_SERVER=0.sg.pool.ntp.org
NTP_SERVER=0.asia.pool.ntp.org
NTP_SERVER=3.asia.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
XTRA_SERVER_4=http://xtra4.gpsonextra.net/xtra.bin
INTERMEDIATE_POS=0
ACCURACY_THRES=0
DEBUG_LEVEL=3
ENABLE_WIPER=0
ENABLE_XTRA=TRUE
SUPL_HOST=supl.google.com
SUPL_PORT=7276
SUPL_SECURE_PORT=7275
SUPL_NO_SECURE_PORT=3425
SUPL_HOST=supl.skyhook.com
SUPL_PORT=7278
CURRENT_CARRIER=common
#REPORT_POSITION_USE_SUPL_REFLOC=1
DEFAULT_AGPS_ENABLE=TRUE
DEFAULT_SSL_ENABLE=FALSE
DEFAULT_USER_PLANE=TRUE
#START_MODE=WARM
#OPERATION_MODE=MS-ASSISTED
PHONE_TYPE=UMTS
secgps.conf
Code:
#Generated by GpsLocationProvider.
#Thu Dec 02 13:09:21 EST 2010
SSL=1
SSL_TYPE=0
POSITION_MODE=121
OPERATION_TEST_MODE=0
ACCURACY=50
SESSION_TYPE=1
SERVER_MODE=0
ENABLE_NMEA=false
START_MODE=HOT
GPS_LOGGING=0
AGPS_MODE=0
DYNAMIC_ACCURACY=1
ADDRESS_MODE=1
TIME_BTW_FIX=1000
OPERATION_MODE=MS-ASSISTED
USE_DEFAULT=false
DYNAMIC_ACCURACY_VALUE=50
SUPL_PORT=7276
ENABLE_XTRA=true
SUPL_HOST=supl.google.com
NUM_OF_FIX=999999999
TIMEOUT=1000
As always backup your original files before modifying and your mileage may vary.
Youtube Link
Thanks for sharing. for me PFGPS didnt work either. well it kind of worked, until i rebooted and then it couldnt find any sattelites at all. i went to sangingerace 3.6 and now it fixes almost instantly. well after reboot i have to wiat about 1 min or so, but thats all, and theres only 2 lines in my gps.conf:
Code:
SUPL_HOST=supl.google.com
SUPL_PORT=7276
If i get a chance (if i find my usb cable ), i'll try out your settings for sure. I wonder if it will work also on other phones - then again - why shouldnt it??
kalkar said:
Thanks for sharing. for me PFGPS didnt work either. well it kind of worked, until i rebooted and then it couldnt find any sattelites at all. i went to sangingerace 3.6 and now it fixes almost instantly. well after reboot i have to wiat about 1 min or so, but thats all, and theres only 2 lines in my gps.conf:
Code:
SUPL_HOST=supl.google.com
SUPL_PORT=7276
If i get a chance (if i find my usb cable ), i'll try out your settings for sure. I wonder if it will work also on other phones - then again - why shouldnt it??
Click to expand...
Click to collapse
hmmm by right your gps.conf should look like the default one i have posted. I am not sure why your gpd.conf only rely on SUPL to achieve GPS locks.
Thank you, now the accuracy reaches 6 feet in less than a minute.
App: fasterfix.
Does it do the same thing?
consegregate said:
App: fasterfix.
Does it do the same thing?
Click to expand...
Click to collapse
here the fasterfix didnt works ;x
consegregate said:
App: fasterfix.
Does it do the same thing?
Click to expand...
Click to collapse
I personally have not tried but in theory it may do for you the same thing. Well, what happen for me is that i came across this tool called Captivate SGS Tools which is meant for SGS users. There was a function to supposedly fix your GPS and i thought that it will rollback my gps.conf after i thought that FGPS fix made it worse. However, i used Captivate SGS Tools and when i opened up gps.conf, it still had FGPS's code comments in it. In addition, i realise i don't even have secgps.conf!
So i resorted to this good old manual way!
Hope this clarifies matters.
kalkar said:
Thanks for sharing. for me PFGPS didnt work either. well it kind of worked, until i rebooted and then it couldnt find any sattelites at all. i went to sangingerace 3.6 and now it fixes almost instantly. well after reboot i have to wiat about 1 min or so, but thats all, and theres only 2 lines in my gps.conf:
Code:
SUPL_HOST=supl.google.com
SUPL_PORT=7276
If i get a chance (if i find my usb cable ), i'll try out your settings for sure. I wonder if it will work also on other phones - then again - why shouldnt it??
Click to expand...
Click to collapse
Hey!
Just wanted to ask, dose it really worked for you?
I want to know, REALLY.
TIA!
CHEERS!
Tried it today. Worked like a charm. Thanks!
Permissions
Could anyone please tell me the correct Permissions for these files in Root Explorer....thanks in advance
Cheers Norrie
norrie2204 said:
Could anyone please tell me the correct Permissions for these files in Root Explorer....thanks in advance
Cheers Norrie
Click to expand...
Click to collapse
Permissions: rw-r-r
from terminal: chmod 644
How do I set permission for the file? Through cwm?
Sent from cyanogen7ace
spicediablo said:
How do I set permission for the file? Through cwm?
Sent from cyanogen7ace
Click to expand...
Click to collapse
Easiest way is via an app called Root Explorer. Long press on the file and you tap on Permissions in the pop up menu. Edit permissions as rw-r-r row wise (top to bottom)
happily1986 said:
Easiest way is via an app called Root Explorer. Long press on the file and you tap on Permissions in the pop up menu. Edit permissions as rw-r-r row wise (top to bottom)
Click to expand...
Click to collapse
Thanks!!. I was looking through the guide. Strange enough, I couldn't find /data/gps folder in my CM7. Anything wrong with my phone?
Currently my gps.config looks like this:
NTP_SERVER=europe.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
SUPL_HOST=supl.google.com
SUPL_PORT=7276
I'm in Malaysia. So I should edit line 1-4?
spicediablo said:
Thanks!!. I was looking through the guide. Strange enough, I couldn't find /data/gps folder in my CM7. Anything wrong with my phone?
Currently my gps.config looks like this:
NTP_SERVER=europe.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
SUPL_HOST=supl.google.com
SUPL_PORT=7276
I'm in Malaysia. So I should edit line 1-4?
Click to expand...
Click to collapse
Read my 1st post please. it tells you exactly what to do.
Yes i've read the first post. Couldn't find the location for secgps.conf which should be placed in /data/gps.
spicediablo said:
Yes i've read the first post. Couldn't find the location for secgps.conf which should be placed in /data/gps.
Click to expand...
Click to collapse
As taken from the 1st post,
Copy and paste the code above for secgps.conf onto Notepad and save as secgps.conf (all files type instead of .txt) Use Root explorer to copy and paste this file in /data/gps
Click to expand...
Click to collapse
I tried to change the permission but encountered error.what should I do?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from cyanogen7ace
spicediablo said:
I tried to change the permission but encountered error.what should I do?
Sent from cyanogen7ace
Click to expand...
Click to collapse
Set the permissions AFTER your have moved the files to /system
Related
This is how I fixed my GPS issue on Captivate. It would not lock on, not even after 5 minutes of me standing still.
Found this thread - http://forum.xda-developers.com/showthread.php?t=786486
Was trying to follow the steps and realized I wished it was spelled out more. So this is what I am doing in this thread, to make it easier for everyone else, if they decide to try. After an hour of googling commands and trial and error - its done, and my phone's GPS locks on under 10 seconds.
I downloaded that zip file. Then installed Droid Explorer on my PC. I already had USB drivers installed for the Galaxy S, so during install I unchecked it. When I opened Droid Explorer I realized I cant write to the /system/bin and the other two. The Write permissions for the system folder were not set, so when I dragged files over - they wouldnt copy over to my phone. It would kinda "refresh" but files wouldnt show up in there.
Easy way seemed to be to buy and install Root Explorer on my phone from the market. And click on Mount R/W for the system folder. However I am waiting for credit card replacement in the mail and was so fed up with GPS that I wanted to do it NOW, and was not gonna stop until its done. Today.
So the other way to make /system/bin , /system/etc and /system/lib folders writable was thru command prompt.
First off my phone has Cog 5.5 on it so it is rooted.
1. set phone in usb debugging mode and connect to pc
2. navigated to my sdk/tools directory on my hard drive. In my case it looked like this
Code:
cd c:\sdk\tools
<hit enter> but it depends on where you downloaded and unzipped your android SDK folder
3. typed
Code:
adb shell
<hit enter> then
Code:
su
<hit enter> to give me root access to the phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The phone will ask if you want to grant permissions to unknown, hit Yes.
4. Now we need to set system as writable. While googling commands it seemed that the command should be
Code:
mount -o rw,remount /system
But in my case that didnt work, telling me location was invalid. I obviously was missing something. Duh! correct location! So -
type
Code:
mount
<hit enter> It will list the root directory. We need t locate exactly where system is on the phone. In my case it was /dev/block/st19 /system
So the command should be then
Code:
mount -o rw,remount /dev/block/st19 /system
<enter>
then
Code:
chmod 777 /system
<enter>
Code:
chmod 777 /system/bin
<enter>
Code:
chmod 777 /system/etc
<enter>
Code:
chmod 777 /system/lib
<enter>
Code:
exit
<enter>
and one more time
Code:
exit
<enter>
The folders are now writable.
5. Opened Droid Explorer, copied files over, lbstestmode launch app was already installed on my phone. So it didnt have to do that step, as it was in j101399j's thread
6. Rebooted the phone, opened lbstestmode, deleted GPS data.
Started testing. It wouldnt lock. Went to Get Position Test in lbstestmode app. It would see the sattellites, 8 of them but wouldnt give me my lat/long! So I remembered this post - http://forum.xda-developers.com/showpost.php?p=9150551&postcount=7862 by cnewsgrp
and changed
3. In the LBSTestMode menu change “Operation Mode” to MS Based
4. In the LBSTestMode menu, find “SUPL/CP Settings” and change the SERVER & PORT to supl.google.com and port 7276 (DO NOT use www. in front of supl)
Click to expand...
Click to collapse
Didnt even have to reboot. Went to Get Position Test again and it saw like 8 or 9 satellites and had * next to 4 of them in 10 seconds. Give me my lat/long with precision. Wanted to mention that I tried cnewsgrp 's method a week ago, just by itself, and it gave me no results.
So to summarize. Combination of those 2 fixes worked wonders for me. And the Captivates GPS issue is definitely not hardware based.
I do have a question however,lol, how do I revoke write settings for my system folder, and go back to how it was? Would that be
Code:
chmod 755
?
I hope these detailed instructions help someone.
And this is why people who don't know what they are doing shouldn't be poking around with root. chmod'ing everything 777 is only one step removed from just running rm -rf * and deleting everything.
There has to be a much easier way of doing things.
And you can "revoke" the settings by remembering what each and every file in those directories had their permissions set to and setting them back with chmod. I guarantee they were not all 755.
chmod 777???
NO THANK YOU!!
zerojay said:
And this is why people who don't know what they are doing shouldn't be poking around with root. chmod'ing everything 777 is only one step removed from just running rm -rf * and deleting everything.
There has to be a much easier way of doing things.
And you can "revoke" the settings by remembering what each and every file in those directories had their permissions set to and setting them back with chmod. I guarantee they were not all 755.
Click to expand...
Click to collapse
it didnt change file settings inside folders, just folder setting
also this is where I got chmod 777 from - http://android-tricks.blogspot.com/2009/01/mount-filesystem-read-write.html and http://karuppuswamy.com/wordpress/2009/04/25/mounting-system-partition-in-read-write-mode-in-android/
was obviously for android.
There's a reason why 777 permissions weren't there to begin with
also I love how there are currently 7 views and 6 replies. which means almost everyone is going - Aaah!!!!! NOOO!!! Must post and warn her!!!
my phone's GPS locks on under 10 seconds
Click to expand...
Click to collapse
This is meaningless. A quick lock does not mean the GPS is "fixed", I wish people would stop making misleading threads
sinoth said:
This is meaningless. A quick lock does not mean the GPS is "fixed", I wish people would stop making misleading threads
Click to expand...
Click to collapse
ok, misleading threads? it was combination of two threads that I linked to, with explanation. Obviously it works for me, and stuff in other threads worked for other people. Enough already with GPS thread policing, hate and trolling.
Yes there is a
"a reason why 777 permissions weren't there to begin with"
Click to expand...
Click to collapse
It is a system folder after all. Same as Windows warns you not to modify windows folder contents. People wrote to and modified android system folder for years. Your point is non existent.
And regarding chmod 777 - look at my screenshot, file permissions arent changed. what was changed was ability to write to those folders. Also Root Explorer function to mount system as R/W obviously does the same thing. Why is it there, if it is soooo dangerous
Went and did chmod 755 on the folders I 777'd. Everything is back to the way it was and works fine.
bmvik said:
ok, misleading threads? it was combination of two threads that I linked to, with explanation. Obviously it works for me, and stuff in other threads worked for other people. Enough already with GPS thread policing, hate and trolling.
And regarding chmod 777 - look at my screenshot, file permissions arent changed. what was changed was ability to write to those folders. Also Root Explorer function to mount system as R/W obviously does the same thing. Why is it there, if it is soooo dangerous
Went and did chmod 755 on the folders I 777'd. Everything is back to the way it was and works fine.
Click to expand...
Click to collapse
I do agree that it takes a while to get a lock...but the BIG concern here is tracking. Hows the accuracy, the tracking? Does it stay locked while driving? That is the REAL problem here...
kletiz said:
I do agree that it takes a while to get a lock...but the BIG concern here is tracking. Hows the accuracy, the tracking? Does it stay locked while driving? That is the REAL problem here...
Click to expand...
Click to collapse
I agree. I'll let you know regarding tracking as I test. Before however, not only it would take 5 min to lock on, but would lose me while I was driving, constantly. Accuracy was jumping to 200 meters or so. So instant lock was a good sign to me.
bmvik said:
Yes there is a It is a system folder after all. Same as Windows warns you not to modify windows folder contents. People wrote to and modified android system folder for years. Your point is non existent.
Click to expand...
Click to collapse
Wow, the cluelessness.
kletiz said:
I do agree that it takes a while to get a lock...but the BIG concern here is tracking. Hows the accuracy, the tracking? Does it stay locked while driving? That is the REAL problem here...
Click to expand...
Click to collapse
For me it does. I have been using GPS with any issues for past few days. And to give credit what ever steps I have posted have been around for a long time just search for "Vibrant GPS fix". The only reason I needed to do that was my GPS stopped working after applying Cog 2.4 ROM with is Vibrant ROM. I applied Vibrant GPS fix and voila GPS now works!!
I must stress here that I have had no GPS issues with any of the Captivate ROMS or Stock ROMS. I usually get lock in 10 - 30 seconds and it tracks well for me. I used GPS test and I an see around 8-9 satellites with S/N ratio of 35 and accuracy of 16.5 regularly.
Oh the boogeyman
I also would like to add, had anything went wrong during these steps - I would've just reflashed my phone to another Cognition ROM and started from scratch. Voila!
bmvik said:
Same as Windows warns you not to modify windows folder contents. People wrote to and modified android system folder for years. Your point is non existent.
Click to expand...
Click to collapse
bmvik said:
Also Root Explorer function to mount system as R/W obviously does the same thing. Why is it there, if it is soooo dangerous
Click to expand...
Click to collapse
It's clear you don't understand the issue. It's not about editing the file system. Heck we all do that if we are in the dev section . It's about having /system permanently open to editing by anything. It's just problematic from a security point of view.
If I run an unverified app not from the android market, I sleep soundly knowing that it stays within its borders (unless I give it superuser permissions). I like to have the choice of saying, root explorer I trust you, you have SU permissions. Okay I trust who made this framework-res.apk, I can add this to /system/framework. I don't want /system permanently open.
installing unverified app and installing fishy framework on phone that is the problem .. not the permissions , I ran my (previous) android phone for a long time with random folders / files at 777 absolutely no damage can nor did happen from doing this alone
thishread is being filled wit los of misinformation while its sole purpose was to 'help the community with a ( well needed it seems ) gps fix
I dont know why everyone is bashing the OP I dont need the fix but its nice to know there is one ..
bashing is all I saw in here nbody told the OP something like ' why wouldnt it work with 644 nor any other suggestions no everybody started bashing .. I m like wow .
/end rant
DAGr8 said:
installing unverified app and installing fishy framework on phone that is the problem .. not the permissions , I ran my (previous) android phone for a long time with random folders / files at 777 absolutely no damage can nor did happen from doing this alone
thishread is being filled wit los of misinformation while its sole purpose was to 'help the community with a ( well needed it seems ) gps fix
I dont know why everyone is bashing the OP I dont need the fix but its nice to know there is one ..
bashing is all I saw in here nbody told the OP something like ' why wouldnt it work with 644 nor any other suggestions no everybody started bashing .. I m like wow .
/end rant
Click to expand...
Click to collapse
It would help if OP can take a snapshot of before and after to list what files had changed. That would help pinpoint what is being used by the GPS that needs more permissions.
DAGr8 said:
installing unverified app and installing fishy framework on phone that is the problem .. not the permissions , I ran my (previous) android phone for a long time with random folders / files at 777 absolutely no damage can nor did happen from doing this alone
thishread is being filled wit los of misinformation while its sole purpose was to 'help the community with a ( well needed it seems ) gps fix
I dont know why everyone is bashing the OP I dont need the fix but its nice to know there is one ..
bashing is all I saw in here nbody told the OP something like ' why wouldnt it work with 644 nor any other suggestions no everybody started bashing .. I m like wow .
/end rant
Click to expand...
Click to collapse
Thank you. I mean, really.
fatttire said:
It's clear you don't understand the issue. It's not about editing the file system. Heck we all do that if we are in the dev section . It's about having /system permanently open to editing by anything. It's just problematic from a security point of view.
If I run an unverified app not from the android market, I sleep soundly knowing that it stays within its borders (unless I give it superuser permissions). I like to have the choice of saying, root explorer I trust you, you have SU permissions. Okay I trust who made this framework-res.apk, I can add this to /system/framework. I don't want /system permanently open.
Click to expand...
Click to collapse
Let me spell it out for you. In this thread http://forum.xda-developers.com/showthread.php?t=786486 OP suggests
2. Using root explorer or droid explorer, copy the files from each folder.
Click to expand...
Click to collapse
For root explorer to be able to write to system folder it would HAVE to change that folders permissions. I didnt have the app, so changed them manually, then used droid explorer. Then changed permissions right back to 755.
cnewsgrp said:
It would help if OP can take a snapshot of before and after to list what files had changed. That would help pinpoint what is being used by the GPS that needs more permissions.
Click to expand...
Click to collapse
Well I just copied the files from the zip file I linked to in the OP, over to the system/bin, /etc and /lib I dont know how screenshot would help
aaaand uhhhhhh can you non-haters vote the thread up, plz? some 5 haters hit 1 star
OP is trying to help. Geez, cut some.slack.
Sent from my SAMSUNG-SGH-I897 using XDA App
skinien said:
OP is trying to help. Geez, cut some.slack.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Lol stop using the samsung keyboard the period is in the wrong spot.
btw op can you plz post some tracking results with mytracks or something. Locking on is not the problem, tracking is.
If you do ill vote this thread up
Some great stuff from Amazing devs
-Androguide.fr Pimp My Rom {the best tweak :good:} ((October 2012))
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1908269[/url]
- AC!D AUDIO ENGINE Developers ((amazing sound experince))
Code:
[url]http://chautemseric.wix.com/acidaudiotechnology#!devices-support/cdfs[/url]
-croniccorey CronMod-A2SD/D2EXT/INT2EXT {best A2SD tweaks} ((updated 09/19))
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1909374[/url]
- CarlDeanCatabay Increase RAM using Swap File and Swap Partition and SD card partitioning ((great one try it))
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1659231[/url]
-hyperbolic The Complete Guide For Maximum Battery Life {great battery life}
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1909996[/url]
-PIT Tech GameBooster ★ root {great games experience }
Code:
[url]https://play.google.com/store/apps/details?id=com.burakgon.gamebooster[/url]
-OOM groupings and priorities tweaks - SuperCharger ((add it with loopy))
Code:
[url]http://forum.xda-developers.com/showthread.php?t=991276[/url]
-Loopy Smoothness tweak ((add it with SuperCharger))
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1137554[/url]
[url]http://forum.xda-developers.com/showthread.php?t=1205744[/url]
-droidphile Kernel Governors, Modules, I/O Schedulers, CPU Tweaks, AIO App Configs ((15th September 2012))
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1369817[/url]
-jader13254 MooDeD Holo Camera
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1742758[/url]
-Rizal Lovins Camera Mod v.4.0 Cybershot Experience
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1918744[/url]
-Arcatarc NotificationLedFix for 4.1.B.0.587 ((17th September 2012))
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1840114[/url]
Other tweaks or guidelines
-Patch your hosts file for blocking Ads
(please think before doing this; many developers are supported through this way)
You can use AdFree application for this or changing manually your hosts file.
Code:
[url]http://www.mvps.org/winhelp2002/hosts.txt
http://pgl.yoyo.org/adservers/serverlist.php?showintro=0;hostformat=hosts[/url]
-Use UOT kitchen for basic theming on your device.
Code:
[url]http://uot.dakra.lt/[/url]
-Disable sync feature in sqlite
(author: ownhere - needs a source for your device so you can compile the /system/lib/libsqlite.so)
Code:
[url]http://forum.xda-developers.com/showthread.php?t=903507[/url]
-Use CyanogenMOD's APN list file - one of the most complete located in
Code:
/system/etc/apns-conf.xml
-Do not use task killers.
for GOD sake ... don't use them all... SELECT/MODIFY according to your ROM and what you want.
WARNING
Note: if you don't know what you are doing please don't try. read first and make sure you understand what you are doing and make a backup before doing any mods. i am not responsible for messing up your device but the ARC community and i may assist.
TO WHO CARE TO KNOW
What is build.prop:
- The build.prop file is your android handset’s ‘ID card’.
- It tells applications the specifications of your device, so that apps can change their interface or function for your specific device.
- Editing the build.prop file is most commonly used for changing LCD density, build number and your device’s model or manufacturer.
- Changing your ‘fingerprint’, model or manufacturer can trick some apps in the market to become compatible with your device.
- The build.prop file is a powerful tool for root users to modify the behavior of various aspects of the Android experience. However, there are no secret values here that are going to instantly make your phone run faster, better, smarter, or more efficiently. In fact, if you don't know what you are doing, you can actually decrease the performance of your device. Over time I will investigate more build.prop properties to determine which ones can actually enhance your Android experience and which ones only create a placebo effect
XperienceD said:
...it helps to know what works and what doesn't, causes conflicts, do you need to use one tweak if you're using another etc and all those classed as "busted" I'll never use again. So while it's great to have it all collected in one place lets also sift through what works and what doesn't.
Click to expand...
Click to collapse
WAIT
REQUIREMENT BEFORE YOU START :-
- Make a NANDROID BACKUP
- If you have any V6 Supercharger tweaks installed, un-supercharge before doing these tweaks. Once finished, you may re-supercharge and
- Root (Superuser/Busybox/Terminal Emulator/ES File Explorer),
- kernel that supports "init.d" scripts (script files that are stored in /system/etc/init.d/)This requires edits in build.prop and the use of terminal emulator
- If your build.prop has an additional build properties section the line of code needs to go in there
(If lines starting with dalvik.vm.checkjni=false or windowsmgr.max_events_per_sec=300 exist already in build.prop, please modify them as shown below. Obviously if it isn't already in build.prop, just add it in.)
How to
Replace OR tweaks Build.prop :-
1. Download Es File Explorer ((OR ANY APP LIKE IT))
2.CLick menu, settings, check Root Explorer and Mount File System
3.Copy the Build.prop file into the sd card and copy with file manager
4.Click Favorites tab, Click Phone icon /
5.Navigate to system/
6.Rename build.prop to build.bak
7.Paste build.prop you copied earlier Reboot! Done! :good:
Build.prop tweaks((UPDATED 26-Oct))
Add these at the end of your build.prop
Code:
IN THE ATTACHMENT
~ Free Up More RAM, Make Apps Load Faster ~
1) Open Terminal Emulator on phone or adb shell from PC and type the following.
Code:
su
setprop dalvik.vm.verify-bytecode false
setprop dalvik.vm.dexopt-flags v=n,o=a,u=y,m=y
As shown:((here written v=n,o=v so the new one is v=n,o=a,u=y,m=y))
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2) Add these lines to the bottom of build.prop using Root Explorer -- or any other app of your favorite
.
(If lines starting with dalvik.vm.verify-bytecode or dalvik.vm.dexopt-flags exist already in build.prop, please modify them as shown below. Obviously if it isn't already in build.prop, just add it in.)
Code:
dalvik.vm.verify-bytecode = false
dalvik.vm.dexopt-flags=v=n,o=a,u=y,m=y
As shown:((here written v=n,o=v so the new one is v=n,o=a,u=y,m=y))
After this, run these two commands in adb shell or terminal emulator
Code:
rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
reboot
3) Okay, this step is only for those who experience errors from typing the following lines from Step 2:
Code:
rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
**If you got the error, make sure to undo the tweak since now you are probably experiencing FC's right now and start all over. The undo process**
How to UNDO this tweak
Type the following in adb shell or terminal emulator
((also u can users, skip the 3rd and 4th lines. That starts with "rm" and instead, reboot in recovery and clear cache partition and dalvik-cache but better to do it all))
Code:
su
setprop dalvik.vm.verify-bytecode true
rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
reboot
So just make sure you have done Step 1 and the edits of build.prop from Step 2 correctly. After that, reboot into recovery and clear cache partition and clear dalvik-cache. Thats all.
Init.d tweaks ((UPDATED 26-Oct))
(needs ROM with init.d access and busybox, open empty file, insert header #!/system/bin/sh and put these there, save in /system/etc/init.d and name it something like 77tweaks)
Note:
1- If you have init.d problem or if not have init.d folder try add this line at hw_config.sh
2- some (needs zipalign bin) #!/system/xbin/bash,so it needs the bash file in the /system/xbin folder in order to work
Code:
I COLLECT A LOT OF THEM
IT TOOK ME ALLOT OF TIME AND EFFORT
I PUT THEM IN TEXT
IN THE ATTACHMENT
DELETED WHICH IS DUPLICATED
& MODIFIED SOME
I COULDN'T WRITE THEM ALL HERE
CAUSE ITS SO BIG TO WRITE IT HERE
THEY JUST ALLOW AMOUNT OF LINE FOR ME
SO I PUT THEM ALL IN TEXT DOCUMENT IN THE ATTACHMENT
EVERY DEVS NAME NEAR HIS SCRIPTS
ANYONE COULD DO THEM IN FLASH ABLE ZIP IT WILL BE GREAT
GOOD LUCK TO ALL
THE RAR IS JUST THE TWEAK NOT FLASH ABLE ONE
sysctl tweaks ((UPDATED 26-Oct))
To make them work:
1. make a new file in /system/etc/init.d, name it sysctl tweaks
2. make a new file in /system/etc, name it sysctl.conf
3. Paste the right code in the right file
-To activate sysctl tweaks
Code:
#!/system/bin/sh
# grep sysctl /etc/init.d/*
/etc/init.d/02vm:# Load /sys/etc/sysctl.conf
/etc/init.d/02vm:sysctl -p
-sysctl.conf
Code:
IN THE ATTACHMENT
Tweaks wich didnt wrok "busted" we will never use again and been test by users ((thanx to XperienceD for this great idea))
I COLLECT MOST OF THEM AND WE WILL POINT WHAT IS FAKE AND WHAT IS NOT
Build.prop tweaks
some was big placebo
and i was saying way my phone gone bad and my gf and my friends
cause alllllllllll was fake
some are not but its already been put to the tweaks up
prove of what i said
first one thanx to the amazing XperienceD
- first one by XperienceD thanx
second
3g tweak its just a big lie
http://forum.xda-developers.com/showthread.php?t=1610444
http://forum.smartphonegeeks.in/index.php?topic=2414.0
i will keep digging to clean the net from placebo tweaks so my plan is not to **** any phone any more and make universal tweaks works with every one
and point out what is never worked and was just a placebo effect. and which have compatibility issues with ICS
so we can Unleash our device Hidden Powers thats my goal
Thanks for the info man
But just some advice, I found that some of the tweak mentioned above is somewhat experimental
I forgot which ones, but after doing some research on google, they are indeed not yet fully tested (the effect is still unnoticeable)
And it will be great if you make the thread (2nd post to be more specific) to be more tidy
There are same tweaks mentioned more than one time, it might not good for people to copy and paste the tweaks directly from your thread
Cheers
fakhreza said:
Thanks for the info man
But just some advice, I found that some of the tweak mentioned above is somewhat experimental
I forgot which ones, but after doing some research on google, they are indeed not yet fully tested (the effect is still unnoticeable)
And it will be great if you make the thread (2nd post to be more specific) to be more tidy
There are same tweaks mentioned more than one time, it might not good for people to copy and paste the tweaks directly from your thread
Cheers
Click to expand...
Click to collapse
MAN
First thanx to tell me about my mistake of putting the same tweaks twice
Second i tidy it more now every tweak title will start with #
Third experimental yes some r but u will see improvment
thanx again
dr said:
Third experimental yes some r but u will see improvment
thanx again
Click to expand...
Click to collapse
And some just don't work - http://www.jeffmixon.com/examining-build-prop-tweaks-for-android-ics-a-comprehensive-guide-part-1/
XperienceD said:
And some just don't work - http://www.jeffmixon.com/examining-build-prop-tweaks-for-android-ics-a-comprehensive-guide-part-1/
Click to expand...
Click to collapse
sorry for that :angel:
am just trying to help
i just updated for other new stuff and cool tweaks
best wishes
i add huge update and new tweaks and arrange it in better way
dr said:
i add huge update and new tweaks and arrange it in better way
Click to expand...
Click to collapse
thanx great collection
dr said:
am just trying to help
Click to expand...
Click to collapse
So am I.
If these things really improve experience, why Sony didn't add theme to their devices in official roms ?
They are professional developers after all ?
XperienceD said:
So am I.
Click to expand...
Click to collapse
thanx :good:
n4ki said:
If these things really improve experience, why Sony didn't add theme to their devices in official roms ?
They are professional developers after all ?
Click to expand...
Click to collapse
why sony didn't fix led bug and they did it here
why sony roms vs good modified stock roms suck
so simple
welcome to android world
dr said:
thanx :good:
Click to expand...
Click to collapse
I found that link whilst searching for mods and used to use some myself, but when you take in to account...
The build.prop file is a powerful tool for root users to modify the behavior of various aspects of the Android experience. However, there are no secret values here that are going to instantly make your phone run faster, better, smarter, or more efficiently. In fact, if you don’t know what you are doing, you can actually decrease the performance of your device.
Click to expand...
Click to collapse
...it helps to know what works and what doesn't, causes conflicts, do you need to use one tweak if you're using another etc and all those classed as "busted" I'll never use again. So while it's great to have it all collected in one place lets also shift through what works and what doesn't.
yes as i already said in an other thread, it would be helpful known which of these improove our Arc/Arc S and which one deprove some roms, for example the JS 6.1 which im using
XperienceD said:
I found that link whilst searching for mods and used to use some myself, but when you take in to account...
...it helps to know what works and what doesn't, causes conflicts, do you need to use one tweak if you're using another etc and all those classed as "busted" I'll never use again. So while it's great to have it all collected in one place lets also shift through what works and what doesn't.
Click to expand...
Click to collapse
noooooooooooooooooooooooooooooooooooooooooooo
noooooooooooooooooooooooooooooooooooooooo
noooooooooooooooooooooooooooooooooo
i didnt take it in to account really its my first time to make thread and i thought u attak me while those not mine
in other way u can say it in deffrent way so i will understand what u want me to understand i will add ur link to the collection
am sorrrrrrrrrrrrrrrrry really soooooooooooo much if i efended u
and thats right lets start to see what is working and what is not
by the way i add and correct some
and trying to do what i can do for helping whom i can
again thanx and soooooooooory if i did something bad
danybhai said:
thanks
Click to expand...
Click to collapse
at ur service alll the time welcome
deniel said:
yes as i already said in an other thread, it would be helpful known which of these improove our Arc/Arc S and which one deprove some roms, for example the JS 6.1 which im using
Click to expand...
Click to collapse
for me i dont use any rom i just root the stock one and play with it for me the last build one works with me
although i went through the web and see some and puts the best value for the best berformance and whats work with me maybe didnt work with u so try and tell us it will be great help
dr said:
again thanx and soooooooooory if i did something bad
Click to expand...
Click to collapse
No offence taken, obviously just a mis understanding.
Thankx for ur hardwork
xperienced said:
no offence taken, obviously just a mis understanding.
Click to expand...
Click to collapse
glad to hear that
cimi244 said:
thankx for ur hardwork
Click to expand...
Click to collapse
all the time welcome
glad to help
why
i get bootloop
alllllllllllllllllllllllllllllllllllllllllllllll
the time when i update the Build.prop tweaks
in JELLY SANDWICH 6.1
and i noticed also the same thing
some Build.prop tweaks repeated twice but with deffrint value in defferint tweak pak
but the rom work like charm :laugh: any idea
dr said:
Tweaks wich didnt wrok "busted" we will never use again and been test by users ((thanx to XperienceD for this great idea))
- first one by XperienceD thanx
Click to expand...
Click to collapse
The battery tweaks that you posted in the second post - what does they improve? Huh?
[GUIDE] Build.prop tweaks, more free ram, Splitwindow all apps, LTE & more (25aug)
This GUIDE is to make your G3 awesome
Requirement
1. Root
2. File Manager with Root Access (Solid Explorer,Root Explorer)
3. Text Editor (920text editor)
4. ADB debug must be on *for backup and restore build.prop
GUIDE
1. open file manager, go to /system/build.prop
2. backup your original build.prop
(copy to sdcard, rename to build.prop.bak)
3. open build.prop
4. Edit your build.prop with these value.
All of this code is tested
Code:
[B]#you can use multiwindow for all apps
#Default value is false, edit to true[/B]
persist.splitwindow.support_all=true
[B]#Edit OOM value for more free ram
#this is the best value for me[/B]
ro.sys.fw.mOomMinFree4=146880
ro.sys.fw.mOomMinFree5=215000
ro.sys.fw.mOomMinFree6=398048
[B]#Enable Permanent LTE Option
#default value is 9[/B]
ro.telephony.default_network=12
[B]#Disable all android log
#add this to your build.prop[/B]
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
logcat.live=disable
ro.kernel.android.checkjni=0
ro.kernel.checkjni=0
ro.config.nocheckin=1
[B]#Wi fi scan interval[/B]
wifi.supplicant_scan_interval=143
[B]#Best dpi for G3
#default value 640[/B]
ro.sf.lcd_density=560
5. save it
6. fix the permission to rw-r-r or 644 (chmod 644 build.prop)
7. Make sure you set the correct permission!
8. Check the permission again.
9. reboot
Kitkat SDcard fix
If you want sdcard read write on kitkat
1. Open /system/etc/permissions/platform.xml
2. Search for android.permission.WRITE_EXTERNAL_STORAGE
3. Edit it like this
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
4. save it
5. fix the permission to rw-r-r or 644 (chmod 644 platform.xml )
6. reboot
LG Smart Notice Multidpi FIX
Flash this for Fixing Smart Notice widgets custom dpi problem
if you have pc with ADB - *download auto batch file*
or
if you have custom recovery - *download flashable zip*
I Recommended using 920 Text Editor
and SOLID EXPLORER and Root Explorer for setting correct permission
without the right editor you will get soft bricked, bootloop, or even worse.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[Tweaks] Lollipop Battery Tweak + 4096 ReadAhead Cache
you will amaze how many hours you'll get with this tweaks
See this thread : Lollipop Battery Tweaks
.
DISLAIMER
Do with your own risk, I'm not responsible for your devices
I'm not responsible if you are using another apps and cause bootloops.
make you you know what you are doing.
tested and works fine on my 10E G3
SCRIPT to BACKUP and RESTORE Build.prop
avicohh said:
Here is a simple script I wrote to Backup and restore build.prop file
http://sourceforge.net/projects/avicohh/files/Android/Backup_Restore_build.prop.zip/download
Enjoy
Click to expand...
Click to collapse
More Tweaks from fellow XDA member
danny_and_2 said:
Hey Spiderio!
First thank you for all these amazing tweaks, I currently use some of them, but I'd added a little bit more to it.
I'm currently testing the following running ART & so far so good.
Credits goes to these threads:
http://forum.xda-developers.com/showthread.php?t=1933099
http://forum.xda-developers.com/showthread.php?t=1685342
http://forum.xda-developers.com/showthread.php?t=1210341
It feels a little bit more snappy, but the main reason to all this is ofc battery life. As I said i'm testing them atm, with a fresh flashed rom (Version F) on ART.
Code:
## TWEAKS
#Battery saving
pm.sleep_mode=1
ro.ril.disable.power.collapse=0
#improve battery under no signal
ro.mot.eri.losalert.delay=1000
# LG flags
persist.service.pcsync.enable=0
persist.service.lgospd.enable=0
#Decrease dialing out delay
ro.telephony.call_ring.delay=0
#Helps scrolling responsiveness
windowsmgr.max_events_per_sec=240
#Increase overall touch responsiveness
debug.performance.tuning=1
video.accelerate.hw=1
# Fast Reboot
persist.sys.purgeable_assets=1
#Faster Scrolling
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
#### New Tweaks : somboons ####
persist.android.strictmode=0
persist.sys.ui.hw=true
ro.com.google.networklocation=0
ro.vold.umsdirtyratio=2
Click to expand...
Click to collapse
Another Method for editing build.prop and more tweaks
http://forum.xda-developers.com/showpost.php?p=54970011&postcount=171
I do have root but it wont let me edit the build.prop
Sent from my LG-D851 using XDA Premium 4 mobile app
"more free ram" is rather deceiving and is not the magic fix most people reading this thread will be looking for all this change will mean is android is far more strict when it comes to killing apps, so in the long run it will keep having to relaunch apps rather than pull it from cache and therefore will take more time to open and more battery, also you may find apps you want to run all the time (persistent apps) will be killed.
fordstang99 said:
I do have root but it wont let me edit the build.prop
Sent from my LG-D851 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Same here, I can not edit the file.
macfreaker said:
Same here, I can not edit the file.
Click to expand...
Click to collapse
fordstang99 said:
I do have root but it wont let me edit the build.prop
Sent from my LG-D851 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Have you guys enabled root in the file manager you're using and mounted /system r/w?
Sent from my G3
Guys,
Do you have some tested DPI for this mobile? I'm little afraid of changing that value. I want a little more space on screen. IMO: This screen resolution is begging for change the DPI value from stock one.
On my Samsung Galaxy S3 I was using DPI 220 and for this screen it was perfect form me.
beats4x said:
Have you guys enabled root in the file manager you're using and mounted /system r/w?
Sent from my G3
Click to expand...
Click to collapse
Yes, i did. It is really strange
macfreaker said:
Yes, i did. It is really strange
Click to expand...
Click to collapse
the build prop is truncated this means you cant change alot of things in it so far i know only dpi can be change..
soo now what.. copied youre build promp to pc open it with tekst editor then change the lines save it and then copied it back to system set permission reboot ALWAYS BACKUP..
Solid Explorer can make changes to the build.prop with no problems.
Sent from my LG-D851 using Tapatalk
I am not able to make change 9 to 12 on lte setting in build.Prop using solid Explorer, I am rooted, it just won't take anything beyond one digit
Sent from my LG-F400K using Tapatalk
deKofi said:
Guys,
Do you have some tested DPI for this mobile? I'm little afraid of changing that value. I want a little more space on screen. IMO: This screen resolution is begging for change the DPI value from stock one.
On my Samsung Galaxy S3 I was using DPI 220 and for this screen it was perfect form me.
Click to expand...
Click to collapse
540 works aside from some image scaling issues.
The G3's native DPI is 534, but I haven't tested that
Been using rom toolkit pro and root explorer and it wont let me edit the build.prop
Sent from my LG-D851 using XDA Premium 4 mobile app
Edited with build prop editor by jrummy. Set split window to true as indicated in op. Phone shows LG splash and then black screen with blue/green LED. Tested huh?
ins5736 said:
Edited with build prop editor by jrummy. Set split window to true as indicated in op. Phone shows LG splash and then black screen with blue/green LED. Tested huh?
Click to expand...
Click to collapse
tested, I have not encountered any issue..
I can provide screnshot.. look here
ARE YOU SURE YOU KNOW WHAT YOU ARE DOING??
don't play around with system if doesn't know anything about it
blame jrummy apps if you want..
does the app setting the correct permission??
I edited build.prop with Solid Explorer...
TESTED..
see it for yourself, click the images attachment
Split view and LTE edit both working fine here. Thanks.
vineet381 said:
I am not able to make change 9 to 12 on lte setting in build.Prop using solid Explorer, I am rooted, it just won't take anything beyond one digit
Sent from my LG-F400K using Tapatalk
Click to expand...
Click to collapse
try edit it using 920text edit
and set permission with solid explorer
spiderio said:
try edit it using 920text edit
and set permission with solid explorer
Click to expand...
Click to collapse
Edit: Restored -- Got it working.
deKofi said:
Guys,
Do you have some tested DPI for this mobile? I'm little afraid of changing that value. I want a little more space on screen. IMO: This screen resolution is begging for change the DPI value from stock one.
On my Samsung Galaxy S3 I was using DPI 220 and for this screen it was perfect form me.
Click to expand...
Click to collapse
I'm using 560dpi... it looks great and never had any problems
zimmerAndy said:
the build prop is truncated this means you cant change alot of things in it so far i know only dpi can be change..
soo now what.. copied youre build promp to pc open it with tekst editor then change the lines save it and then copied it back to system set permission reboot ALWAYS BACKUP..
Click to expand...
Click to collapse
That works, thank you for the help.
EDIT: The latest oat2dex solves this issue altogether.
WTF IS THE PROBLEM?
The OpenGL and Google Play Store refuse to work because baksmali inside the oat2dex tool misinterprets some fields in a single smali file and breaks "services.jar" when deodexing, and the main problem it causes is mistakenly setting your OpenGL version to 0 (instead of 3), basically disabling it.
oat2dex, for some reason, flips just a few specific fields (name and type) when deodexing, as if there is an ambiguity between 2 fields on the same offset.
When you flash the deodexed services.jar back to your phone and clear dalvik-cache, Android re-optimizes it (takes the "classes.dex" inside your new JAR file, does dex2oat on it, and saves it in /data/dalvik-cache/arm/). The deodexed file is broken, so that optimized file is broken too.
You take that broken odex file from dalvik-cache and deodex it again. Since it contains those flipped field names, this time it flips them again but to the correct fields.
The result DEX file you get by that second deodexing is a properly working DEX file, and if you rename it to "classes.dex" and replace "classes.dex" inside your broken "services.jar", you'll get a working "services.jar" and all your OpenGL and Google Play Store problems will disappear immediately.
HOW TO QUICKLY GET A WORKING DEX?
* Extract classes.dex from the JARs, rename them to framework.dex and services.dex.
* Copy them to your internal SD.
* Enable "USB debugging" in Developer options.
* Connect your device to your PC and open Command Prompt:
Code:
[B]adb shell[/B] (confirm ADB on your device)
[B]su[/B] (confirm SU on your device)
[B]dex2oat --dex-file=/sdcard/framework.dex --oat-file=/sdcard/framework.odex[/B]
[B]dex2oat --dex-file=/sdcard/services.dex --oat-file=/sdcard/services.odex[/B]
* Copy these odex files to your PC and deodex them again with oat2dex.
* Rename the new framework.dex and services.dex to classes.dex and add them to their JARs, replacing the broken classes.dex.
JARS AFFECTED BY THIS BUG
framework.jar/classes.dex --- only a single non-critical error in NumberPicker.smali (classes2.dex is fine)
http://forum.xda-developers.com/attachment.php?attachmentid=3338076&d=1432918042
services,jar/classes.dex --- Total of 8 errors, described below...
http://forum.xda-developers.com/attachment.php?attachmentid=3335118&d=1432772056
BUG REPRODUCTION
Requirements:
1) Java installed
2) oat2dex_bug.zip
ZIP contents:
* baksmali.jar
* oat2dex.jar
* boot.oat --- taken from /framework/arm/
* services.dex --- this is "classes.dex" from the deodexed "services.jar" (which breaks OpenGL)
* services-from-dcache.odex --- this is the odex file taken from "/data/dalvik-cache/arm/" that was created by Android after flashing the broken deodexed "services.jar" and clearing dalvik-cache
Reproduction steps:
1) Open "oat2dex_bug" folder, right-click inside it and then select "Open command window here".
2) Write the following lines exactly as follows:
java -jar oat2dex.jar boot boot.oat
java -jar oat2dex.jar services-from-dcache.odex odex
java -jar baksmali.jar -o services-from-dcache services-deodex.dex
java -jar baksmali.jar -o services services.dex
3) With WinMerge, compare folders "services" and "services-from-dcache".
You'll see that only one file has differences, and it's "ActivityManagerService.smali", that's the file you need to fix.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In the above images are the only affected areas you need to fix.
Holy @#%. Well done! This issue was a real pain. Thanks
What about fixing framework.jar ? Play store compatibility ?
Sent from my C6903 using XDA Free mobile app
dstrikersZ1 said:
What about fixing framework.jar ? Play store compatibility ?
Sent from my C6903 using XDA Free mobile app
Click to expand...
Click to collapse
framework.jar has only 1 error in NumberPicker.smali, and it's not very critical. Has nothing to do with the Play Store bug. After you've fixed services.jar by deodexing it twice, Play Store is fixed.
IaguCool said:
WTF IS THE PROBLEM?
The OpenGL and Google Play Store refuse to work because baksmali inside the oat2dex tool misinterprets some smali files and breaks "services.jar" when deodexing, and the main problem it causes is mistakenly setting your OpenGL version to 0 (instead of 3), basically disabling it.
oat2dex, for some reason, flips just a few specific fields (name and type) when deodexing, as if there is an ambiguity between 2 fields on the same spot.
When you flash the deodexed services.jar back to your phone and clear dalvik-cache, Android re-optimizes it (takes the "classes.dex" inside your new JAR file, does dex2oat on it, and saves it in /data/dalvik-cache/arm/). The deodexed file is broken, so that optimized file is broken too.
You take that broken odex file from dalvik-cache and deodex it again. Since it contains those flipped field names, this time it flips them again but to the correct fields.
The result DEX file you get by that second deodexing is a properly working DEX file, and if you rename it to "classes.dex" and replace "classes.dex" inside your broken "services.jar", you'll get a working "services.jar" and all your OpenGL and Google Play Store problems will disappear immediately.
JARS AFFECTED BY THIS BUG
framework.jar/classes.dex --- only a single non-critical error (classes2.dex is fine)
services,jar/classes.dex --- described below
BUG REPRODUCTION
Requirements:
1) Java installed
2) oat2dex_bug.zip
ZIP contents:
* baksmali.jar
* oat2dex.jar
* boot.oat --- taken from /framework/arm/
* services.dex --- this is "classes.dex" from the deodexed "services.jar" (which breaks OpenGL)
* services-from-dcache.odex --- this is the odex file taken from "/data/dalvik-cache/arm/" that was created by Android after flashing the broken deodexed "services.jar" and clearing dalvik-cache
Reproduction steps:
1) Open "oat2dex_bug" folder, right-click inside it and then select "Open command window here".
2) Write the following lines exactly as follows:
java -jar oat2dex.jar boot boot.oat
java -jar oat2dex.jar services-from-dcache.odex odex
java -jar baksmali.jar -o services-from-dcache services-from-dcache.dex
java -jar baksmali.jar -o services services.dex
3) With WinMerge, compare folders "services" and "services-from-dcache".
You'll see that only one file has differences, and it's "ActivityManagerService.smali", that's the file you need to fix.
And here are the only differences you find in the file (notice especially the first one and the last one):
Click to expand...
Click to collapse
java -jar baksmali.jar -o services-from-dcache services-from-dcache.dex
Click to expand...
Click to collapse
Error: "Can´t find the file services-from-dcache.dex"
There is no such file in the zip either - only services-from-dcache.odex, but with this file it did not work
moonryder said:
Error: "Can´t find the file services-from-dcache.dex"
There is no such file in the zip either - only services-from-dcache.odex, but with this file it did not work
Click to expand...
Click to collapse
Then you made a mistake somewhere.
IaguCool said:
Then you made a mistake somewhere.
Click to expand...
Click to collapse
tried it again, step 1 and 2 without problems, but step3 the same error as mentioned before
there is a new file in the folder called "services-deodex.dex"
moonryder said:
tried it again, step 1 and 2 without problems, but step3 the same error as mentioned before
there is a new file in the folder called "services-deodex.dex"
Click to expand...
Click to collapse
Ahh I see that oat2dex renames the file for some reason. I fixed line 3 to
java -jar baksmali.jar -o services-from-dcache services-deodex.dex
You could figure that out yourself, you know... by looking inside the folder, I don't see why you repeat every step like a robot uncritically.
IaguCool said:
...I don't see why you repeat every step like a robot uncritically....
Click to expand...
Click to collapse
cause i am not a programmer and a noob in this field contrary to you (maybe you are a genius and i am a little user :angel: )
moonryder said:
cause i am not a programmer and a noob in this field contrary to you (maybe you are a genius and i am a little user :angel: )
Click to expand...
Click to collapse
So basically it's like pushing a screwdriver into a wall socket without knowing what electricity is... I don't get why people that don't develop even try to deodex themselves in the first place. Deodexing is meant for developers, not "little users"...
so its must to be writen GL_ES_VERSION:I
its i/1/L ?
Alvian_P said:
so its must to be writen GL_ES_VERSION:I
its i/1/L ?
Click to expand...
Click to collapse
It's "I" for Integer. Seriously what are you people doing here? It's for *developers*, normal users have nothing to gain from this process.
That's how I have fixed it too, well done
Take care that mWentToSleep must also be fixed.
Both lines are inverted.
Edit: nevermind, your method is inverting both... I did it manually.
Please tell what command compiles the folder "services" into file "services.dex" back?
Bazooka Joe said:
Please tell what command compiles the folder "services" into file "services.dex" back?
Click to expand...
Click to collapse
Google for "smali-2.0.5.jar" for that. baksmali only decompiles.
IaguCool said:
It's "I" for Integer. Seriously what are you people doing here? It's for *developers*, normal users have nothing to gain from this process.
Click to expand...
Click to collapse
@laguCool
1. thx for discovering that problem and its solution
2. all devs began once upon a time, so i think threads like this one are very helpful for users who want to learn and become a dev in future too. So
3. please be soft with all of them who asks questions here.
Thx again for your excellent work and knowledge.
m.
moonryder said:
@laguCool
1. thx for discovering that problem and its solution
2. all devs began once upon a time, so i think threads like this one are very helpful for users who want to learn and become a dev in future too. So
3. please be soft with all of them who asks questions here.
Thx again for your excellent work and knowledge.
m.
Click to expand...
Click to collapse
Well, being soft isn't my thing, it's against my nature...
Anyways, if a person doesn't know what "I" means in Dalvik opcode, they are doing the learning process wrong. They need to be familiar with Dalvik datatypes beforehand.
IaguCool said:
It's "I" for Integer. Seriously what are you people doing here? It's for *developers*, normal users have nothing to gain from this process.
Click to expand...
Click to collapse
just look around , anyways my college is IT
ah sorry if this thread not open for normal users
IaguCool, Big, big Thanks!!! OpenGL worked now! :good:
There is a more simple way for obtain dirty odex from dirty dex file. Just copy deodexed services.dex to sdcard and type in terminal
dex2oat --dex-file=/sdcard/services.dex --oat-file=/sdcard/services.odex
Then copy created /sdcard/services.odex to PC and deodex them again to obtain correct services.dex.
_SIL_ said:
IaguCool, Big, big Thanks!!! OpenGL worked now! :good:
There is a more simple way for obtain dirty odex from dirty dex file. Just copy deodexed services.dex to sdcard and type in terminal
dex2oat --dex-file=/sdcard/services.dex --oat-file=/sdcard/services.odex
Then copy created /sdcard/services.odex to PC and deodex them again to obtain correct services.dex.
Click to expand...
Click to collapse
Thank you I rarely use the terminal so I missed that. I actually copied all /framework/ odex files from dalvik-cache to see if there are more JARs affected by this bug, will add them to the list if I find any.
As ive been reading about this very much lately, after people have flashed Marshmallow and rooted, many are having issues editing their build.prop files. And many arent having any issues at all. Well, the fix is rather easy. You are going to have to change your SElinux to be permissive. Many that arent having the issue is because they are either using a custom kernel that has set SElinux to be permissive, or are using an app to change it. I use an app, dir viper4, because it needs to gave SElinux at permissive. There arent any apps that do it in the play store, because google removed them. But.. theres a site called xda that somebody is posting their SElinux changer app in http://forum.xda-developers.com/showthread.php?t=2524485
setenforce 0 don't work no mo on dat m?
Sent from my Nexus 6 using Tapatalk
713brianp27 said:
setenforce 0 don't work no mo on dat m?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
probably does, but an app that does it would be easier, for most. but you are right
Why did Google remove the apps that allow you to do this?
rester555 said:
Why did Google remove the apps that allow you to do this?
Click to expand...
Click to collapse
security?
simms22 said:
About Google removing apps . . . . . . .security?
Click to expand...
Click to collapse
Just assuming . . . Google dev's have managers that puts them under pressure. . . Why. . .
1. Deals with telecom providers; demanding special factory images. Project Fi.
2. Ignoring many user requests; forcing encryption and forcing to use apps with text on white background.
3. Dark material removed since M-preview 3.
4. Use of RRO layers needs root access.
5. Deals with banks for Android Pay; not working when rooted.
6. Bloat. Built-in apps that should be in the play store.
7. Privacy. Services that can't be blocked.
8. Boot message device corrupt when it isn't.
This 6.0 update is a much bigger pain in the ass then it needs to be. Especially for Nexus devices which are suppose to be "mod" friendly. What gives Google?
First thing that comes to mind, is that you shouldn't EVER BE editing /system/build.prop. Its purpose is that it is generated by the build, hence "build".prop. If you need custom properties added to the system, use /data/local.prop.
Second thing is that most of the problems with system partition edits are NOT due to selinux problems. Most are because the factory sysimage bloats it absolutely FULL of crap. Delete some junk like google photos (which is a bloated pig).
Third, there is *absolutely no* reason to disable selinux. Just switch your context to one that matches the files you are trying to interact with. The su command has a parameter "--context" that lets you do this. Look it up.
NLBeev said:
Just assuming . . . Google dev's have managers that puts them under pressure. . . Why. . .
1. Deals with telecom providers; demanding special factory images. Project Fi.
2. Ignoring many user requests; forcing encryption and forcing to use apps with text on white background.
3. Dark material removed since M-preview 3.
4. Use of RRO layers needs root access.
5. Deals with banks for Android Pay; not working when rooted.
6. Bloat. Built-in apps that should be in the play store.
7. Privacy. Services that can't be blocked.
8. Boot message device corrupt when it isn't.
Click to expand...
Click to collapse
There are many logical reasons, however.
1)ProjectFi actually NEEDS special factory images
2)Security
3)It was unstable and needs more work (they are improving it for future releases)
4)I'm actually not sure about this one... I agree with you
5)Security
6)They've remove most apps like PinyinIME and HindiIME from the system with 6.0
7)Security
8)Security
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Dang old security. Pha. Lol. Don't need permissive w viper. [emoji12]
Official Team Bliss Flo, Deb, v410 Maintainer
Sent from my Nexus 6 using Tapatalk
if i make any changes to build.prop at reboot my phone just sits at the Google screen. Even after setting SElinux to be permissive.
Any other solutions???
I'm running MRA58k rooted with supersu v2.50
mrizvi66 said:
if i make any changes to build.prop at reboot my phone just sits at the Google screen. Even after setting SElinux to be permissive.
Any other solutions???
I'm running MRA58k rooted with supersu v2.50
Click to expand...
Click to collapse
What kind of changes did you make? Did you do a backup of the build.prop file before the changes?
Pecata said:
What kind of changes did you make? Did you do a backup of the build.prop file before the changes?
Click to expand...
Click to collapse
yes, I made a backup. so i'm up and running.
all i tried to add was:
net.tethering.noprovisioning=true
i added it at the very bottom. i've done it before on lollipop and it worked before i'm not sure why it's not working now tho.
mrizvi66 said:
yes, I made a backup. so i'm up and running.
all i tried to add was:
net.tethering.noprovisioning=true
i added it at the very bottom. i've done it before on lollipop and it worked before i'm not sure why it's not working now tho.
Click to expand...
Click to collapse
if you make any spelling errors or gramatical errors, or miss any spaces, your phone wont ever boot up.
Pecata said:
What kind of changes did you make? Did you do a backup of the build.prop file before the changes?
Click to expand...
Click to collapse
simms22 said:
if you make any spelling errors or gramatical errors, or miss any spaces, your phone wont ever boot up.
Click to expand...
Click to collapse
does it need an extra space at the end of the file? i think i might have removed that.
mrizvi66 said:
does it need an extra space at the end of the file? i think i might have removed that.
Click to expand...
Click to collapse
no.
i use root explorer to edit my build.prop btw. what ill do is just copy/paste the line in, save it, then reboot. and it always is fine(unless i write it myself and mess it up).
simms22 said:
no.
i use root explorer to edit my build.prop btw. what ill do is just copy/paste the line in, save it, then reboot. and it always is fine(unless i write it myself and mess it up).
Click to expand...
Click to collapse
that's exactly what i do.
i just tried it again right now and it worked. strange.
thanks for you help both of you :good:
doitright said:
First thing that comes to mind, is that you shouldn't EVER BE editing /system/build.prop. Its purpose is that it is generated by the build, hence "build".prop. If you need custom properties added to the system, use /data/local.prop.
Second thing is that most of the problems with system partition edits are NOT due to selinux problems. Most are because the factory sysimage bloats it absolutely FULL of crap. Delete some junk like google photos (which is a bloated pig).
Third, there is *absolutely no* reason to disable selinux. Just switch your context to one that matches the files you are trying to interact with. The su command has a parameter "--context" that lets you do this. Look it up.
Click to expand...
Click to collapse
Great advice on local.prop. Did not know this before. Read up on it and sounds more useful especially when applying edits you dont want to re-enter after each flash.
(Take all this with caution) Good to note for others that local.prop is read after build.prop in boot up (hope i got that right), so you can use the same lines in build.prop in local.prop with changes in the values. Those values in local.prop will override those in build.prop! *except if the same line in build.prop begins with ro. "read only". **apparently the addition of qemu. in place of ro. in local.prop will override the build.prop line setting that had ro. at the beginning. Now does anyone know what qemu is exactly? Emulator? For hardware?
MunkinDrunky said:
Great advice on local.prop. Did not know this before. Read up on it and sounds more useful especially when applying edits you dont want to re-enter after each flash.
(Take all this with caution) Good to note for others that local.prop is read after build.prop in boot up (hope i got that right), so you can use the same lines in build.prop in local.prop with changes in the values. Those values in local.prop will override those in build.prop! *except if the same line in build.prop begins with ro. "read only". **apparently the addition of qemu. in place of ro. in local.prop will override the build.prop line setting that had ro. at the beginning. Now does anyone know what qemu is exactly? Emulator? For hardware?
Click to expand...
Click to collapse
qemu is the virtual machine infrastructure used for the android emulator. It is far more generic than for just the android emulator, but android does use it. The prefixes used imply a priority, and qemu (because of its association with the emulator for testing) is considered as for testing and development purposes, so it can, as you say, override.
doitright said:
First thing that comes to mind, is that you shouldn't EVER BE editing /system/build.prop. Its purpose is that it is generated by the build, hence "build".prop. If you need custom properties added to the system, use /data/local.prop.
Second thing is that most of the problems with system partition edits are NOT due to selinux problems. Most are because the factory sysimage bloats it absolutely FULL of crap. Delete some junk like google photos (which is a bloated pig).
Third, there is *absolutely no* reason to disable selinux. Just switch your context to one that matches the files you are trying to interact with. The su command has a parameter "--context" that lets you do this. Look it up.
Click to expand...
Click to collapse
I am sorry if this is a stupid question but when you say data/local.prop-do you mean root/data/ or just data/ in internal memory?
and if I create local.prop and add the line qemu.hw.mainkeys=1 in local.prop would that be able to hide the navigation bar even if the I don't touch build.prop?