Related
I shall take no credit for any of this. Smartsreenath first put me onto the idea, and pretty much anyone if this forum could've managed it. I just had the time to do it all.
Woo! Snakehult, being a genius, has made a clever little zip that uses proper scripts to just change the required value, instead of the whole file. So! Instead of me making an insane number of zips every time ROMs are updated use these instead. Cheers Snakehult!
Attached is a zip file with a whole lot of flashable zips in it. Don't flash the zip you download, extract that one somewhere and look inside
How to use:
Download the attached zip file, and extract it to somewhere on your computer. Inside the zip are a bunch of folders, each folder named after a ROM for the HTC Legend. Navigate into the folder that shares the name of whatever ROM you are using and inside you will find 6 zip files. These zips are flashable. The the zips are names thus: xxx.zip, where xxx is a number. The lower the number, the higher the apparent resolution. Choose a zip, copy it to your SD card and flash it like any other zip. To revert back to how it was simply flash the "160.zip". This just flashes a completely un-modified version of build.prop for your ROM. Make sure you only use the zips form the correct folder for your ROM, or funny things *might* happen.
More info:
By editing the build.prop file it is possible to increase the dpi of an Android device. This essentially scales everything down, so you can fit more on the screen. This is especially nice for browsing the market and the internet; as well as improving, in my opinion, the overall Android experience. The lower the number in the name of the zip, the higher the apparent resolution. It's worth noting that this does *not* change the actual resolution of the Legend; it's still a HVGA device. So you still can't install apps designed for bigger, more powerful phones, like the HTC Desire or Nexus One. This is a somewhat flawed way of achieving this effect, and can have some ugly side effects:
Some apps simply don't scale
HTC-IME mod ends up screwed
Games *can* be rendered unplayable, but not always. Often the menu is the worst affected part.
A work around to fix a number of issues is to disable the built in compatibility mode of Android, and if I knew a way to do this through a zip, rest assured that I would. It'd save me having to explain how to do it. Alas, I don't know how, so here's how:
In your ROM look for an app called "Spare parts". If it's not there look for it in the market. If you open that app and scroll down to the bottom you will find a checkbox option for "Compatibility mode". Ensure that this is *un-checked*, then reboot. Most issues will be resolved. As I learn more about Android I shall keep an eye out for a way to force apps to scale correctly, and if I ever find one I'll update these.
I have also tried values higher than usual, just for kicks. I don't expect them to be useful, nor will I make actual zip files for them, but I went all the way up to 200; and it felt like I was using an HTC wildfire: everything was really quite cramped.
My personal favourite setup is as follows:
CM 6.1, with a 768MHz overclock
My "lcd-density" (this MOD) set to 130
Launcher Pro Plus with 5 icon rows
Below is a paste of what was the first post (when I was just trying to fix a ****-up on my part), and is now here for reference. It has all of the original build.prop files attached.
Attached is a .zip file, which you will need to extract somewhere. It's not for flashing. Within this zip are several folders, each containing a "build.prop". You'll notice that each folder is named after a ROM: Azure, NeonMOD etc. The "Based-on-stock" folder should cover these ROMs:
[ROM] Based on Official WWE_2.03.405.3 ROM + A2SD [Rev 03 - released]
[ROM] UPDATED Almost Stock Legend HTC WWE 2.03.405.3 Radio 7. 08.35.21
You'll need to use ADB to push these files, as I haven't had time to make flash-able zip's for them yet
Instructions:
1. Extract the zip to a suitable directory, and locate the appropriate build.prop
2. Copy the build.prop to your AndroroidSDK/tools folder
3. Reboot your phone into ClockworkMOD recovery and navigate the the "Partitions menu", then click "mount /system"
4. Connect your phone to the PC and start CMD/a terminal window in your AndroidSDK/tools folder
5. Run the command "adb devices" to ensure that the ADB server is running, and that the PC has detected your device correctly
6. Run these commands in this order:
adb push build.prop /sdcard/build.prop
adb shell
mount -o remount,rw /dev/block/system /system
cp /sdcard/build.prop /system/build.prop
This will put your resolution back to default, but should fix everything else too. If you still want a higher resolution then follow the guides in posts 1 and 2 of the other thread. This one.
If you can't use ADB for whatever reason you'll just have to wait it out until myself or someone else create proper, flash-able, fixes. I have done this to try and quickly rectify the issue; assuming, of course, that most people in this forum can use ADB
I will make proper zips, but it's getting late for me...
Click to expand...
Click to collapse
hi
here is a zip for neonmod 0.21 with 135lcd, flashed it on my legend today with rom manager
Wow do we have a lot of ROMs...
Anyhoo, I am currently working on appropriate flashable zips for each ROM, and each ROM will have the following versions:
110
120
130
140
150
160 (original)
I'm doin' 'em as fast as I can..
EDIT:
Current thoughts:
All build by Ali Ba have nice, short build.prop files. The current record for the longest one it held by MyTouch Legend...
TheGrammarFreak said:
Wow do we have a lot of ROMs...
Anyhoo, I am currently working an appropriate flashable zips for each ROM
Click to expand...
Click to collapse
Awesome!
All our lovely ROMs are actively being used, and its great.
Thx for all hard work!
No worries, I hope I haven't missed one
Now to sign 50 60 zip files...
EDIT:
DONE! All finished. I really hope they work. I can't test them all, but there is no reason why they won't work. Lemme know either way.
nice job
thanks bro
nice
spare parts is also in neonmod
xennr3 said:
nice
spare parts is also in neonmod
Click to expand...
Click to collapse
Cool, and you can turn compatibility mode off?
TheGrammarFreak said:
Cool, and you can turn compatibility mode off?
Click to expand...
Click to collapse
sure
1234
TheGrammarFreak said:
Cool, and you can turn compatibility mode off?
Click to expand...
Click to collapse
thanks for your work! i just tried 130 dpi and it seems really good.. i'll try also others zip asap!
yes with compatibility mode off all softwares i tried work really well!
xennr3 said:
sure
1234
Click to expand...
Click to collapse
Cool, thanks for the info. I'll update the OP when I'm home
Sent from my Legend using XDA App
Wow, really cool mod Love it!
Good job!
Cool, glad you like it
Just flashed 130 for SpeedLegend and it worked like a charm
HTC_IME works here (this isnt the mod)
images dont look so good anymore and stuff, but alright
works fine
edit; TBH I find the 140 to be 'more' compatible overall, and show a better picture (ive tried all the flashables)
thats besides the orgnal setting btw, it gives the best picture by far.
Im on the same DPI and rom as you TheGrammarFreak. works great. Too bad there is no function for more icons on the homescreens with LauncherPro...
SimDroid said:
Im on the same DPI and rom as you TheGrammarFreak. works great. Too bad there is no function for more icons on the homescreens with LauncherPro...
Click to expand...
Click to collapse
Yeah it does. On your homescreen press menu, then preferences. In advanced options there is something for it.
Sent from my Legend using XDA App
i glad to hear that someone like you got the idea from my thread........good work ...........and nice job.....you will get all help from me and from my friends
FOLLOW ME http://smartsreenath.blogspot.com/
TheGrammarFreak said:
Yeah it does. On your homescreen press menu, then preferences. In advanced options there is something for it.
Sent from my Legend using XDA App
Click to expand...
Click to collapse
yeah, that is for 5 rows on a screen, but you still can't have 5 icons on a row... That's what I want. I tried ADWLauncher again, but it feels so god damn slow.
Ummm, I have 5x5 icons on my desktop with the stock ADW launcher. Just check out "Settings > ADW > Screen prefs > Desktop cols/Desktop rows"
**NOTE FOR VEGAN TAB USERS** Steps 1-5 are no longer necessary for you, as the build.prop file in your /system directory has a working market fingerprint out of the box. Just apply the standard Market Fix (steps 6-8) and you are good to go.
I've seen several people complaining that the "full market" we had on G Tablet after the established market fixes wasn't quite full. Well, I've solved that problem, through a mixture of reading what others have done with other devices and experimentation. I will not promise that this gives you *everything*, but I do believe it gives you apps that otherwise required the release-keys status. Some of the apps you get may of course not work. But several applications I looked for before (TV.com for example, with streaming CBS video content) were not available with the previous market fix, and are now available with this fix. In fact, TV.com even works, except for a very minor video glitch in the upper left corner of the screen, and it's a cool app to get some quick streaming video content going on your G Tablet.
**NOTE** I take no responsibility for you screwing up your G Tablet. Please backup your system in Clockwork Recovery before doing any of this!
**EDIT** Removed unneccessary steps after feedback in this thread. Process is now very simple. Edited step 1 to clarify you need paid version of Root Explorer.
Here's how to do it:
0) Backup in Clockwork Mod. Please. I don't want you mad at me if this messes up your ROM.
1) Get the paid version of Root Explorer installed on your G Tablet. Apparently the free version lacks a text editor. If you only have the free version, the text editing step will need to be done in a separate program, or you will need to copy build.prop to your desktop, edit it there, and copy it back. Or use adb to push an edited build.prop to your tablet. Just buy Root Explorer though, it makes this very easy.
2) Browse in Root Explorer to /system. Then click on Mount R/W.
3) Long click on build.prop and click on Open In Text Editor.
4) Scroll down to the line ro.build.fingerprint=....
You are going to replace that with the following text:
ro.build.fingerprint=google/passion/passion/mahimahi:2.2/FRF91/43546:user/release-keys
5) Now you are going to click on Save and Exit. And then remount the /system directory as R/O.
6) Now you are going to re-do the original Market Fix. I used the simple version illustrated here: http://www.youtube.com/watch?v=7l-nySibzeA&feature=related First, make sure Market is running, and browse around in it for a few seconds. If you don't do this, there may be no cache to clear and for some reason the market fix may not work. Then, go to Settings->Applications->Manage Applications->Running and scroll down to Market. Then hit Clear Cache, followed by Force Stop **DO NOT CLEAR DATA FOR MARKET, JUST CACHE**. Then go back, scroll down to Google Services Framework, hit Clear Data, then Force Stop.
7) Now try starting Market again and you get the famous Market Error. Now shut down the G Tablet, then turned it back on. Wait for Wifi to connect to your network before doing anything! I forgot to do that on the first try, so I rebooted again, waited for wifi to connect this time.
8) Now restart Market again. It seems to have sourced the fingerprint from build.prop somewhere in steps 6-7. Searches for previously missing apps now show up. Voila! A truly full market!
And steps 6 and 7 can almost certainly be replaced by the equivalent steps using Titanium Backup that I know a lot of people have been using, particularly with TNT Lite. I am running ZPad 2.2 here, so YMMV with TNT Lite. Please keep me informed if this works/doesn't work for you if you try it!
Credit goes to: Paul at Modaco for hacking on the Advent Vega and making the Market work fully on that device and for coming up with a working build.prop for the Advent Vega, Roebeet for inspiring me to look at the Vega ROM stuff with his current work on the VEGAn ROM, Rothnic for his excellent work on the ZPad ROM that I'm currently using. Basically, I'm just hacking and slashing here, this wasn't any sort of rocket science.
Paul from Modaco is awesome -- and you are as well, for making this post!
Any apps in particular that you found after this, that were missing before? I might want to try this on my device. Thanks again!
FWIW my Nexus One running a CM 6.0 nightly from 2 days ago has
ro.build.fingerprint=google/passion/passion/mahimahi:2.2.1/FRG83/60505:user/release-keys
Note the more up-level version (2.2.1) and build (FRG83). I haven't tried this on my GTab yet but I will as soon as I can get it up and running.
roebeet said:
Paul from Modaco is awesome -- and you are as well, for making this post!
Any apps in particular that you found after this, that were missing before? I might want to try this on my device. Thanks again!
Click to expand...
Click to collapse
The only specific things I can tell you off the top of my head are TV.com which I know wasn't there because I searched for it a few hours ago. Also, I tried searching Market for Handcent before and found 14 or 15 results, and after this process I was able to retrieve 24 results.
There were a bunch of random apps I saw in the Top Apps list that I don't remember seeing earlier today. So that was enough to convince me that most of the missing 10-20% of apps are there now.
And thanks for the compliment, especially coming from the guy who made the G Tablet useful!
short/y said:
FWIW my Nexus One running a CM 6.0 nightly from 2 days ago has
ro.build.fingerprint=google/passion/passion/mahimahi:2.2.1/FRG83/60505:user/release-keys
Note the more up-level version (2.2.1) and build (FRG83). I haven't tried this on my GTab yet but I will as soon as I can get it up and running.
Click to expand...
Click to collapse
I'm sure that will work too, though the FRF91 build string seems to match the existing data in the ZPad ROM at least. I'm guessing the two signatures will produce essentially identical Market results.
rcgabriel said:
I'm sure that will work too, though the FRF91 build string seems to match the existing data in the ZPad ROM at least. I'm guessing the two signatures will produce essentially identical Market results.
Click to expand...
Click to collapse
Yeah. I may be somewhat overoptimistic going with FRG83. The build and version numbers identify the version of the system code so apps may read them and make some assumptions as to certain API characteristics. We're probably closer to FRF91 than FRG83 on TnT Lite.
This one worked ok for me
ro.build.fingerprint=samsung/SGH-T849/SGH-T849/SGH-T849:2.2/FROYO/UVJJB:user/release-keys
ewitte said:
This one worked ok for me
ro.build.fingerprint=samsung/SGH-T849/SGH-T849/SGH-T849:2.2/FROYO/UVJJB:user/release-keys
Click to expand...
Click to collapse
Is that from the Samsung Tablet? That may be closer to what we're really running.
short/y said:
Is that from the Samsung Tablet? That may be closer to what we're really running.
Click to expand...
Click to collapse
Yes this is Galaxy Tab. Probably better a Tegra tab once a full market one comes out.
I did the following:
1) Edited build.prop as described in step 4, rebooted and searched for tv.com - no results
2) I preformed the edits in step 4a, rebooted and searched for tv.com - no results
3) I stopped Market & Google Services Framework & wiped Google Services Framework, rebooted after getting Market Error, waited for wifi and opened Market to search for tv.com - no results.
I can't say if it works. I haven't had trouble finding apps, but I can't find tv.com before or after the steps above. Perhaps, I missed something.
Wait!!!! It does work. I tried again after posting and it's there! Thanks!
Is it possible to post the TV.com app? I don't want to do the mod but would love that app!
Great post man worked like a charm, I can get my slingbox app from the market now.
Edit: dammit I can't get the downloaded sling client to launch even after trying it many times which usually worked.
I'm going to give it a shot but being a newbie I'm not clear on this step:
5) Now you are going to click on Save and Exit. And then remount the /system directory as R/O
Will "remount as r/o" be an option to select at this point? If not, can you provide more detail.
The rest of the mod is easy enough to follow.
Thanks.
jdnyc said:
I'm going to give it a shot but being a newbie I'm not clear on this step:
5) Now you are going to click on Save and Exit. And then remount the /system directory as R/O
Will "remount as r/o" be an option to select at this point? If not, can you provide more detail.
The rest of the mod is easy enough to follow.
Thanks.
Click to expand...
Click to collapse
No worries its just a button on root explorer, download it and you will see it fairly quick.
NM..........
Fixed
Thanks works great
Can't get this to work. When I toto building.prop there s no option to open it in text editor. Only toopen as text. But then there is no way to edge the sentence.
ewitte said:
This one worked ok for me
ro.build.fingerprint=samsung/SGH-T849/SGH-T849/SGH-T849:2.2/FROYO/UVJJB:user/release-keys
Click to expand...
Click to collapse
Replaced this line only, did the Market fix via Settings and it worked like a charm. And Swype continues to work as well.
-=Sent from my ViewSonic G Tablet using Tapatalk=-
Worked perfectly thanks! Steps 4a and 6 are not necessary as you precicted
This is meant to be a guide for people interested in building AOSP based roms and is strictly for developers only. If you wish to have gesture typing in your rom the most simple way is to include/install "LatinImeGoogle.apk".
Not everyone wants to always use google's stock input apk, particularly if you have made modifications into AOSP latinime keyboard if your own and want it to propagate through to your roms without sacrificing gesture input (which i have found is quite useful). Well after some digging around there's good news and bad news.
The good news is that the gesture typing is already in the source tree on the java side and can be enabled by changing packages/inputmethods/LatinIME/java/res/values/gesture-input.xml or using the overlay in devices/../mako (not within scope of this post).
Code:
<bool name="config_gesture_input_enabled_by_build_config">true</bool>
However, just changing the value you will notice that it will draw the gesture but list no words. Thats because google didnt include the "gesture decoder" in the AOSP sources because it is super secret. You can see the code stubs in the C++ part of latinime under native/jni/src/gesture/* .
As a result, libjni_latinime.so will not contain code to decode the gestures and will not read from the dictionary.
BUT! There is a way! You can drop in replace the lib from "LatinImeGoogle.apk" into your system/lib and you will have your gesture decoder!
The library inside the apk is called "libjni_latinimegoogle.so" under /lib/<arch_type>/ inside the apk. You can extract this library from within android using program like root explorer and on PC using android apktool (http://code.google.com/p/android-apktool/). Rename this shared library to "libjni_latinime.so" to replace the AOSP built one and it will decode the gestures through the AOSP based keyboard.
Enjoy!
-removed-
Thanks for sharing the detailed instructions. This was a major annoyance..
kabir_sharma009 said:
Thanks for sharing the detailed instructions. This was a major annoyance..
Click to expand...
Click to collapse
I see you too have recently had an issue with this. I've followed everything, even using different sources for the libjni_latinimegoogle.so (noticed varing sizes) but none of them have worked for me. I installed the apk out of CM10.2.1, and the gesture trail shows up but still no library it seems. Any idea what I might have missed? Renamed file as directed and put in in the system\lib folder.
Thanks in advance for any help you may have to offer.
Edit:
Got it. Restart the phone...I feel like I should have called tech support
Re-Edit:
Negative, didn't realize at first it was set to Samsung Keyboard...Help still needed.
TheLastRebel1123 said:
I see you too have recently had an issue with this. I've followed everything, even using different sources for the libjni_latinimegoogle.so (noticed varing sizes) but none of them have worked for me. I installed the apk out of CM10.2.1, and the gesture trail shows up but still no library it seems. Any idea what I might have missed? Renamed file as directed and put in in the system\lib folder.
Thanks in advance for any help you may have to offer.
Edit:
Got it. Restart the phone...I feel like I should have called tech support
Re-Edit:
Negative, didn't realize at first it was set to Samsung Keyboard...Help still needed.
Click to expand...
Click to collapse
I've attached the file in .rar format for you, extract the .so file from the archive using WinRAR and replace the existing file in System/Lib with this one.
You might get an error while trying to replace the file if AOSP Keyboard is selected as default input method, so switch to another keyboard before replacing the file (Swype Keyboard Trial is what I used).
Thanks for getting back to me. Unfortunately it additional didn't work. Any other ideas?
kabir_sharma009 said:
I've attached the file in .rar format for you, extract the .so file from the archive using WinRAR and replace the existing file in System/Lib with this one.
You might get an error while trying to replace the file if AOSP Keyboard is selected as default input method, so switch to another keyboard before replacing the file (Swype Keyboard Trial is what I used).
Click to expand...
Click to collapse
Works perfectly for me. Thanks a lot!
Fantastic trick. Worked on my wife's S3 mini running MacClaw's latest KitKat. Thanks so much for this.
Didn't work for me, AOSP keyboard just FCs
not much of a difference between aosp & google keyboard
Sorry I thought I was on a different thread
How I got gestures working on cm11
So, I'm uncertain if this is exactly what this thread is about, but it might help someone.
Some backstory:
I had cm11 for a long time with a working Android AOSP keyboard.
After trying cm12.1 for a while I went back to cm11 with a fresh install, and noticed my gestures not doing much, and causing the FC.
I did a lot of searching, but nothing seemed to fix my problem, including the suggestions from this thread.
Since I had a nandroid of my previous installation, I did some comparisons, and came across the file libjni_unbundled_latinimegoogle.so in the /system/lib.
Copying this to my new installation fixed gesture typing for me. So now I share my solution to whoever can use it.
I hope this helps someone!
FreakyJoost said:
So, I'm uncertain if this is exactly what this thread is about, but it might help someone.
Some backstory:
I had cm11 for a long time with a working Android AOSP keyboard.
After trying cm12.1 for a while I went back to cm11 with a fresh install, and noticed my gestures not doing much, and causing the FC.
I did a lot of searching, but nothing seemed to fix my problem, including the suggestions from this thread.
Since I had a nandroid of my previous installation, I did some comparisons, and came across the file libjni_unbundled_latinimegoogle.so in the /system/lib.
Copying this to my new installation fixed gesture typing for me. So now I share my solution to whoever can use it.
I hope this helps someone!
Click to expand...
Click to collapse
Did you mean copying that lib file in location mentioned by you alone should give gesture typing ability? Because it didnt work on my zenfone with custom rom, blisspop 6.0.1
harpy.eagle said:
Did you mean copying that lib file in location mentioned by you alone should give gesture typing ability? Because it didnt work on my zenfone with custom rom, blisspop 6.0.1
Click to expand...
Click to collapse
In my situation it did, bat as mentioned I use cm11. Seems however the name is kind of related to the build of the apk. Apparently this was the same file as the one mentioned before, just with a different name.
You could try finding an older version of suitable gapps that provides a libjni_latinime.so and see if that one works...
I was able to enable gesture typing on a fresh install of CM13 without installing Gapps by extracting the file libjni_unbundled_latinimegoogle.so from the keyboard apk in openGapps for android6 (the "stock" version includes google keyboard). I placed the file in the /system/lib folder. Only difference is that I renamed that file to libjni_latinimegoogle.so . All was left was to soft reboot and enable gesture typing!
forgot to mention I set permission to -rw-r--r--
First off this work is based on Digiblur's PRL Write Enabler from the Sprint Galaxy S3 forum. I simply modified it & packaged it for our Sprint Galaxy S4 devices.
Here is the original S3 post that this was found in... http://forum.xda-developers.com/showthread.php?t=2159054
Also, post #8 below provides additional info.
I tested it by flashing with TWRP and it worked on my stock, rooted S4 with the MDC and MDL releases.
If you're on a stock rooted Rom and not using TWRP, you can just copy the HiddenMenu.apk from inside the zip file downloaded into /system/app/ and overwrite the one that's there. (You'll need a root enabled file browser to do this of course).
Thanks to Unknownforce here is a version for MJA...
http://www.androidfilehost.com/?fid=23212708291676468
Enjoy!!
This certainly will save me from having to use CDMA WS to switch like I just did yesterday. 55014 was not working well for me in my market so I switched back to 25014.
What is write enabler?
Keeps aborting for me
THEGAMEPLAY94 said:
Keeps aborting for me
Click to expand...
Click to collapse
You mean the install of the zip?
If so, you can pull the APK out of the zip and replace HiddenMenu.apk in the system folder (make a backup first). You may want to also set the permissions to rw-r-r after replacing the system app. Reboot, then you should be good to go.
@ChadH42,
I know it seems like I'm harping on you but I'm really not..
You need to update the OP on - 1. What is this? 2. What does this do? 3. Why is this in the Development Section.. ?
A good OP leads to less questions.. Development Sections aren't for information. That would be considered a Discussion Thread that belongs in General.
Let's keep the Dev section clean from the start.
My suggestion - Edit the OP on the What's/Why's?/How To's and you won't get posts like mine.
To the OP, updated your title as [WIP], and I suggest you provided additional information so that folks aren't bricking their new devices.
I will check in, if you need anything, let me know.
What this MOD does (in case the OP takes a little while to chime in)
What this MOD does is modifies our ##DATA# (select View) menu to allow for the PRL Write option to appear and function. With this menu option, the user can change their PRL on the fly from the device itself by placing a copy of the desired PRL in the root directory of Internal Storage and name it "test.prl" (no quotes), dial ##DATA# (choose View), tap Write PRL, tap the sub-menu option Write PRL ---wait--- and then the device reboots with the test.prl PRL applied upon reboot. Not every PRL works and sometimes it takes a couple of tries.
A tip for multiple PRL options is to, of course, keep a folder of the PRLs you like and keep them labeled in there. Copy the desired PRL to proper place as needed and just remember to rename the copy to "test.prl". Switch back and forth as you please. I hope this helps clear some confusion and helps some find purpose with the MOD like I have.
For a clear set of instructions that I did not want to just copy verbatim, check the link below. Also, if you are having issues with the zip not installing in CWM, just extract the APK from the ZIP (inside the system/app folder), use Root Explorer or your favorite root-access file explorer to place the APK in the APP folder, apply the proper permissions and reboot.
Ref from the GS3: http://forum.xda-developers.com/showthread.php?t=1748516
So I unzipped the file, replaced the hidden menu original apk with the new one, then set permissions, rebooted, then tried ##3282# and the view and edit options do not appear.. .. It just blanks out the items I just entered
Sent from my SPH-L720 using Tapatalk 2
jayjay7411 said:
So I unzipped the file, replaced the hidden menu original apk with the new one, then set permissions, rebooted, then tried ##3282# and the view and edit options do not appear.. .. It just blanks out the items I just entered
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
Did you clear Cache when you rebooted?
What ROM are you using?
ChadH42 said:
Did you clear Cache when you rebooted?
What ROM are you using?
Click to expand...
Click to collapse
+1...same thing is happenening to me...Im on force rom. when i type in the dialer code it just blanks out.
lilmikeyv said:
+1...same thing is happenening to me...Im on force rom. when i type in the dialer code it just blanks out.
Click to expand...
Click to collapse
I just tried this mod with the Force ROM and it did the same thing (blank options). The only thing I can think of is that it works with the odex version of the stock ROM so maybe its a problem with deodex ROMs of which Force is one.
O okay. Its currently not a necessary thing for me at the moment, just nice for when I travel to Alabama. Hopefully later on someone gets it working on deodex.
Sent from my Nexus 4 using Tapatalk 2
ChadH42 said:
I just tried this mod with the Force ROM and it did the same thing (blank options). The only thing I can think of is that it works with the odex version of the stock ROM so maybe its a problem with deodex ROMs of which Force is one.
Click to expand...
Click to collapse
I am actually running it on the Rooted Stock DeOdexed ROM. So I don't think it is an Odex/DeOdex issue...might be a Force ROM issue.
Also, moot point for Force ROM (1.0+) anyway because the PRL Write mod is already included with that.
I'm also having this problem and I'm pretty sure it was working this morning. I haven't flashed anything since then.
edit-- I tried:
1. wiping both cache's
2. killing background process "OIThiddenmenu"
neither fixed it.
I reinstalled the stock odex ROM and flashed this again and it worked.
Just an FYI, OP, I get Error Status 6 when trying to flash this via recovery, which indicates one of two things. Either the format of the file is incorrect or there is a syntax error. The syntax looks fine, but opening in basic Notepad shouldn't "look pretty" like it currently does. So it's likely it was edited with a non-Unix-compatible text editor like Notepad or MS-Word...
To make modifications to an updater-script (or just about any Android/Linux files like this) you need something like Notepad++ or gVim.
Anyways, I did a quick test with this, and it does in fact not work on my ROM as it is, but I see why it's failing, but I don't know what exactly it's trying to reference yet. (It fails with an id number instead of a name, so I'll have to de-compile some things to find it.)
I'm not sure it's a ROM issue or a MOD issue yet. (meaning it might have to be updated for each custom ROM, depending on how they are configured) But I'll track it down and update when I can.
Unknownforce said:
Just an FYI, OP, I get Error Status 6 when trying to flash this via recovery, which indicates one of two things. Either the format of the file is incorrect or there is a syntax error. The syntax looks fine, but opening in basic Notepad shouldn't "look pretty" like it currently does. So it's likely it was edited with a non-Unix-compatible text editor like Notepad or MS-Word...
To make modifications to an updater-script (or just about any Android/Linux files like this) you need something like Notepad++ or gVim.
Anyways, I did a quick test with this, and it does in fact not work on my ROM as it is, but I see why it's failing, but I don't know what exactly it's trying to reference yet. (It fails with an id number instead of a name, so I'll have to de-compile some things to find it.)
I'm not sure it's a ROM issue or a MOD issue yet. (meaning it might have to be updated for each custom ROM, depending on how they are configured) But I'll track it down and update when I can.
Click to expand...
Click to collapse
Thanks for all your help here..
I had the error status 6 problem in the beginning and thought I fixed it. You are correct that I used MS WordPad to edit the files.
ChadH42 said:
Thanks for all your help here..
I had the error status 6 problem in the beginning and thought I fixed it. You are correct that I used MS WordPad to edit the files.
Click to expand...
Click to collapse
I think TWRP can read the non Unix type characters, which is why it works on a different recovery.
I'm hoping it's a mod issue and I can just modify the mod to work universally regardless of the rom. But we'll see.
Sent from my SPH-L720 using xda app-developers app
fails in recovery for me.
says error executing updater binary in zip
in stock rooted...
[GUIDE] How to fix "Domestic Roaming" on Sprint (and other) Nougat (and other) ROMs
One of the issues with running the latest Nougat ROMs on this device is that they all say "Domestic Roaming" instead of "Sprint" and also display an R instead of 3G, 1x, etc on the signal display. After much research, I've found out it's that the phone doesn't recognize the tower as a Sprint tower and thus assumes you're roaming. The fix for that is in a little file called eri.xml. What I did was take the file from this OP (all credit goes to him) and modify it a little to get it working properly (it only had three of the four needed Roaming Indicators). I've attached my modified version to the OP of this thread, but here are the steps if you want to create your own. Note that this can be done on a PC or on your phone directly. You will need root! (but since you are most likely needing this for a custom ROM, you probably have it).
If you are just using my file directly:
Download the file and copy to phone if not downloading from there.
Copy and paste the eri.xml file to /data using the file manager of your choice (must be able to browse using root).
Change the permissions on the file to 777 (ie to Read Write eXecute for Owner, Group, and Others).
Reboot phone.
If you are going to make adjustments:
Download the file.
Unzip the file and then open eri.xml in a text editor.
Open up this list of Roaming Indicators from this Github eri.xml source
On that site, use your browser's find feature to search for your carrier. For Sprint, there are four of them (0, 1, 99, 123).
In your text editor, edit RoamingIndicator="#" to match your carrier's roaming indicator number and edit EriText="Sprint" to match your carrier's name. Note that you can change the name to whatever you want and it will scroll if it's too long (or so I've read).
Repeat step 5 for all the roaming indicator numbers for your carrier.
If you need to add extra ones, use copy and paste to do so.
Make sure that NumberOfEriEntries="#" matches the number of entries you have when you finish.
Save eri.xml and copy it to your phone if it's not already there.
Copy and paste file to /data using the file manager of your choice (must be able to browse using root).
Change the permissions on the file to 777 (ie to Read Write eXecute for Owner, Group, and Others).
Reboot phone.
At this point, you should see Sprint as your carrier and no more R on the network meter in the status bar.
I almost didn't create a new thread as I didn't do much, but I wanted to keep all the Q&A and troubleshooting in one place and not clutter the other threads. Plus, I wanted to expand upon some of the steps on what you have to do. If you have any questions or need help, please let me know.
Credits:
snandlal for his eri.xml file and tutorial to get me started (give the man a thanks!)
Hexagon ROM guys for displaying their source on Github
Works for me, thanks a ton!
Tried this; got "Changing permissions was not successful. Please note that some file systems do not allow permission changes." Please help!
clarkkentdroid said:
Tried this; got "Changing permissions was not successful. Please note that some file systems do not allow permission changes." Please help!
Click to expand...
Click to collapse
The only time I see something like that is if the file manager isn't root capable, it doesn't get root permissions somehow, or the phone isn't rooted. What file managing app are you using? I did this successfully using Solid Explorer File Manager, although I'm sure any other one that gets root would do.
coal686 said:
The only time I see something like that is if the file manager isn't root capable, it doesn't get root permissions somehow, or the phone isn't rooted. What file managing app are you using? I did this successfully using Solid Explorer File Manager, although I'm sure any other one that gets root would do.
Click to expand...
Click to collapse
I used root browser on Resurrection Remix. It has Privacy Guard which asked if I wanted to grant root browser access, and I granted it. Root browser asked me to install busybox, which I did. I moved the file to /data successfully. However, it still didn't gain permission successfully.
clarkkentdroid said:
I used root browser on Resurrection Remix. It has Privacy Guard which asked if I wanted to grant root browser access, and I granted it. Root browser asked me to install busybox, which I did. I moved the file to /data successfully. However, it still didn't gain permission successfully.
Click to expand...
Click to collapse
Hmm... I looked and that's the exact ROM I tested it on. You'll find my post on the first page and yours is on the second. I don't think I installed a different su program like SuperSU. Two ideas:
1. Make sure you give Root Browser permanent root access.
2. Try a different file manager. I used Solid Explorer with no issue. If you don't want to buy it, try other free ones first. I think MiExplorer (I think that's its name) is free on XDA and is nice.
Thanks for the suggestions. I used solid explorer and it seemed like it worked. Permissions were still 777 after reboot, but I still don't get mobile data. My network says "Sprint" instead of "Domestic Roaming", at least.
Changing roms doesn't help, correct?
clarkkentdroid said:
Thanks for the suggestions. I used solid explorer and it seemed like it worked. Permissions were still 777 after reboot, but I still don't get mobile data. My network says "Sprint" instead of "Domestic Roaming", at least.
Changing roms doesn't help, correct?
Click to expand...
Click to collapse
Not getting mobile data is different than what this file does. This just fixes the displaying Domestic Roaming issue - it's just cosmetic.
I had no data issues on that ROM. The One m7 lacks some of Sprint's LTE bands and well it's Sprint, but that's not a ROM issue. Maybe try flashing back to a Sense ROM and updating Profile and PRL and then flash back to RR.
Your GitHub link to the list of roaming indicators seems to 404.
Yankee14 said:
Your GitHub link to the list of roaming indicators seems to 404.
Click to expand...
Click to collapse
Thanks! I've fixed the link to a similar one. The original link was the same file as this one and both only seemed to include Sprint. But, you can find Verizon there as well. As for others, you may need to search to get the right numbers.
coal686 said:
Hmm... I looked and that's the exact ROM I tested it on. You'll find my post on the first page and yours is on the second. I don't think I installed a different su program like SuperSU. Two ideas:
1. Make sure you give Root Browser permanent root access.
2. Try a different file manager. I used Solid Explorer with no issue. If you don't want to buy it, try other free ones first. I think MiExplorer (I think that's its name) is free on XDA and is nice.
Click to expand...
Click to collapse
AFter having a similar issue, and switching to Solid Explorer, I was able to change the permissions on the file, however it's still showing up as "Domestic Roaming". File is in /data and shows permissions as "777 -rwxrwxrwx"
Any help or ideas?
Thanks
TalyWhackin said:
AFter having a similar issue, and switching to Solid Explorer, I was able to change the permissions on the file, however it's still showing up as "Domestic Roaming". File is in /data and shows permissions as "777 -rwxrwxrwx"
Any help or ideas?
Thanks
Click to expand...
Click to collapse
Are you on Sprint? Also, what ROM are you running?
Yes I'm on Sprint. Just installed Resurrection remix 5.8.2
TalyWhackin said:
Yes I'm on Sprint. Just installed Resurrection remix 5.8.2
Click to expand...
Click to collapse
I think I tested on that one and it worked. If you followed the steps completely (restarted?), then I'm not sure why it's still telling you "Domestic Roaming" unless you truly are roaming.
Problem is, my m7 isn't activated anymore, so I can't really verify that nothing's changed with the ROMs since I tested things. Although they shouldn't have since I don't think they've been updated (I'm pretty sure I tested on 5.8.2 or RR).