Can anyone tell me what needs to be edited in the build.prop file to remove the sprint stuff from the phone. I'm using ES File Explorer and can edit the file with this just not sure what needs to be changed.
For instance this is what is there for the screen resolution under
#Following property will be referenced by Settings.
ro.product.display_resolution = 4.3 inch WVGA resolution
Just not sure if changing it to the proper size will do the trick or is there more?
Also see the 4 references to sprint under #Welly_Fang_12/30/2010
do I just delete sprint-us and put in verizon in the four lines of code?
Okay I installed a froyo backup to compare the build.prop files and tehy are quite different.
Under #Welly_Fang in froyo there are only two lines:
ro.cdma.home.operator.numeric = 310012
ro.cdma.home.operator.alpha = Verizon
So I'm assuming this should be the same for the gingerbread build.prop though it has four lines of code referencing sprint-us not two.
Also there is no reference to screen resolution in the froyo build.prop file and when I checked settings its not listed under hardware either. So Im thinking of just changing this to 3.7 in gingerbreads build.prop and see what happens.
If any thing goes wrong I can always flash a backup.
Well when I got into the gingerbread build.prop again I noticed there were actually two #Wolly_Fang sections. One for Verizon and one for Sprint so I just deleted all the Sprint lines of code. Then under resoluton I just changed it to 3.7 and then rebooted without any problems and it says 3.7 under hardware now.
Now I just need to figure out how to get rid of Sprint in the Market app. I'm assuming that can be done by replacing the market in system apps folder, probably market updater and market provider too. I tried doing it by installing a copy of teh new market over it but that didn't work. Any one know?
kzoodroid said:
Well when I got into the gingerbread build.prop again I noticed there were actually two #Wolly_Fang sections. One for Verizon and one for Sprint so I just deleted all the Sprint lines of code. Then under resoluton I just changed it to 3.7 and then rebooted without any problems and it says 3.7 under hardware now.
Now I just need to figure out how to get rid of Sprint in the Market app. I'm assuming that can be done by replacing the market in system apps folder, probably market updater and market provider too. I tried doing it by installing a copy of teh new market over it but that didn't work. Any one know?
Click to expand...
Click to collapse
What ROM are you on?
frostincredible said:
What ROM are you on?
Click to expand...
Click to collapse
This is just rooted stock gingerbread not a custom ROM. I read that you could edit the build.prop file using just a file explorer in a thread for another phone. Now I'm trying to find how to get rid of Sprint from the market. Not sure where they put it. I could always load the kitchen back on to my laptop and buld a custom ROM again to try and get rid of it.
I've noticed that Sprint doesn't show up in the old market just the new market. Just not sure where the market is getting this info from to know to display it.
sprint was just replaced by verizon in my market today so it must have been something on googles end as i didn't do anything to change it.
Related
does HTC_IME from deire 2.2 froyo rom work on DINC?
edit: Here's a link I think you will find very useful.
http://www.incredibleforum.com/forum/htc-incredible-hacks/791-design-your-own-htc-ime-keyboard.html
Have been unable to get the calibration tool to work with this.
Currently, I am using a theme generated version which works great, but I need to calibrate it to better for how I type.
Using Calibrate FC on me.
I attempted to update the clicker.apk but it won't load.
Anyone run into this, have a fix.
Ref:
http://www.gimpsta.com/themer/main.php
krelvinaz said:
Have been unable to get the calibration tool to work with this.
Currently, I am using a theme generated version which works great, but I need to calibrate it to better for how I type.
Using Calibrate FC on me.
I attempted to update the clicker.apk but it won't load.
Anyone run into this, have a fix.
Ref:
http://www.gimpsta.com/themer/main.php
Click to expand...
Click to collapse
If your rooted and nand unlock, use rootexplorer to move the clicker_hi.apk to /system/app/ make sure you set permissions and reboot your phone, the calibration tool should work.
Did something similar to that... I moved the clicker*.apk (there were two of them) files to and oldapp directory and then I was able to install the new one. No reboot was needed.
Now the keyboard is calibrated to my typing reach and is back to what it was like before the 2.2 update.
krelvinaz said:
Did something similar to that... I moved the clicker*.apk (there were two of them) files to and oldapp directory and then I was able to install the new one....
Click to expand...
Click to collapse
Sitting here for hours trying to figure out how to regain my old DINC 2.1 HTC_IME keyboard, without any success. Rooted, w/S-OFF, Froyo (2.2) under Virtuous 2.6. Edit_01: Then, not sure what I did that was different, but I was able to update my HTC_IME keyboard with a "new" version that I created at the gimpsta.com site. So, my DINC (Rooted, w/S-OFF, Froyo (2.2) under Virtuous 2.6) is working without issue.
Before I was successful in loading a new keyboard, and during my research using Root Explorer (RE), I saw that there were a couple of HTC_IME files in the system and cache directories, but RE said they were read only and would not allow me to move or delete them. Krelvinaz, what was your secret? I saw a clicker.apk and HTC_IME.apk files under the phone data and system folders, even though the apps had been uninstalled in Astro Manager and no longer show(ed) in the Language and Keyboard or in the Applications/Manage Applications settings section. There was only one program called HME IME Test listed in Manage Apps during my troubleshooting searches.
At one time, I did try to load a current version of the clicker.apk, but I got an error message. Is there a clicker calibration utility, for the keyboard and how do I load it.
bmoke said:
Sitting here for hours trying to figure out how to regain my old DINC 2.1 HTC_IME keyboard, without any success....
Click to expand...
Click to collapse
While I did stumble into a successful keyboard installation, I have spent yet more time to figure out how to change permissions in Root Explorer(RE). Not wanting to complicate a working HTC_IME, I tested my RE ability and changed the startup boot mp3 sound in the system directory. So far, so good. However, I am reluctant to delete the clicker.apk, at this time, hoping I might get some knowledgeable feedback about my question on whether there is a calibration utility, for this keyboard. I cannot remember if I actually ran the clicker.apk, way back when I got the phone. I was unable to install it today, because it already exists in the system, and I would need to remove it first. Still hopeful someone might expand on the keyboard and the clicker.apk.
So, I have read that it's an issue with all Froyo ROM's on the EVO... You can't see paid/protected apps in the Marketplace; supposedly, the apps not showing are not verified to work on Froyo.
Could someone just patch the build_prop like they did on the Nexus One before Google released the official fix?
N1 Fix Thread for Reference: http://forum.xda-developers.com/showthread.php?t=693102
If anyone wants to tackle it, the dev of the N1 fix explained what needs to be done here: http://forum.xda-developers.com/showthread.php?t=693102
I don't have an EVO, nor am I much of a developer; but I just rooted my friend's EVO and was looking for a fix for him when I realized that the N1 had a very similar issue when it was running leaked versions of Froyo.
Just throwing it out there... I could be way off.
I think this should be easy to do. Theoretically you should be able to take buildprop swticher v0.3.1.zip and replace /buildprop/build.2.1 with the build.prop from stock and /buildprop/build.2.2 with the build.prop from CM6 and then follow the directions from that post.
I'm about to test it out myself and see if it works...
Let me know... If it does, could you post the build.prop files that you used?
EDIT: Awesome to see another SC member!
Okay, first attempt boot looped. I think build.2.1 needs to be a 2.2 build.prop modified to look like 2.1 because the stock 2.1 build.prop won't work with 2.2. Should've looked at that more instead of rushing Going to see if I can find the lines to change real quick, gotta go back to work in a few minutes...
It also cleared my Google Account settings haha... trying a new modification but may not be able to upload anything until tonight!
Thanks for your help... Can you post your build.props before going back to work? If so, I will try to work on this more if you aren't able to get it before going back.
Thanks
Just printed and compared the build.props for the N1 fix and see that there are only 2 lines that were changed. If someone wants to provide me with a 2.1 build.prop and the CM6 build.prop, I might be able to get this working.
Don't bother with it man.
I'm the one posted the Nexus thread. I already tried changing the build.prop fingerprints & it didn't fix the issue.
Only thing keeping me from using CM6
Geniusdog254 said:
Don't bother with it man.
I'm the one posted the Nexus thread. I already tried changing the build.prop fingerprints & it didn't fix the issue.
Only thing keeping me from using CM6
Click to expand...
Click to collapse
I was just about to post saying what I tried didn't work and I was hoping you'd pop in here. I was thinking about digging into it more this weekend but if you haven't been able to get anywhere I doubt I could either.
Well... that blows... Sorry guys
Wish I could've been of more help!
Geniusdog254 said:
Don't bother with it man.
I'm the one posted the Nexus thread. I already tried changing the build.prop fingerprints & it didn't fix the issue.
Only thing keeping me from using CM6
Click to expand...
Click to collapse
After you changed the lines in build.prop did you try reseting Market?
settings > Applications > Manage Applications > ALL > Market > Clear data
Geniusdog... what all does the ro.build.fingerprint line do?
spiicytuna said:
After you changed the lines in build.prop did you try reseting Market?
settings > Applications > Manage Applications > ALL > Market > Clear data
Click to expand...
Click to collapse
Yep. Even tried pushing it while still in recovery, right after wiping and flashing the ROM. Still a no go
Edit: the to.build.fingerprint is the "fingerprint" it shows when it accesses the Market. So its how the Market decides what apps to show, and sees what kind of device it is & its version
Geniusdog254 said:
Yep. Even tried pushing it while still in recovery, right after wiping and flashing the ROM. Still a no go
Edit: the to.build.fingerprint is the "fingerprint" it shows when it accesses the Market. So its how the Market decides what apps to show, and sees what kind of device it is & its version
Click to expand...
Click to collapse
We need a setting like most of the android browsers to allow us to spoof ourselves as stock 2.1 EVO.
Geniusdog254 said:
Yep. Even tried pushing it while still in recovery, right after wiping and flashing the ROM. Still a no go
Edit: the to.build.fingerprint is the "fingerprint" it shows when it accesses the Market. So its how the Market decides what apps to show, and sees what kind of device it is & its version
Click to expand...
Click to collapse
Hmmm...editing fingerprint and description *SHOULD* work but it did not work when I tried adding the fingerprint/description from Avalaunch's Froyo ROM. It seems that Ava's Froyo ROM fixed the missing apps issue. It's so very bizarre that we can't get certain market apps to show on CM6 and drives me crazy. There has to be some type of solution, I'm just not sure what it is yet
ok this is what we did on the Hero when we was with 1.5 and got the leak of 2.1 the market didnt show all the apps so we just change it with the nexus one, so i am guessing maybe we can get a 2.2nexus one build.prop and push it to the Evo, make sure to clear the market chache though , it took like 5-6hours for the apps to start showing up on the Hero!! just an Idea
jabbawalkee said:
Hmmm...editing fingerprint and description *SHOULD* work but it did not work when I tried adding the fingerprint/description from Avalaunch's Froyo ROM. It seems that Ava's Froyo ROM fixed the missing apps issue. It's so very bizarre that we can't get certain market apps to show on CM6 and drives me crazy. There has to be some type of solution, I'm just not sure what it is yet
Click to expand...
Click to collapse
Have you tried just using the whole build.prop from Ava's ROM? Should work ok since they're both 2.2, no idea if it'll fix the issue though.
datajosh said:
Have you tried just using the whole build.prop from Ava's ROM? Should work ok since they're both 2.2, no idea if it'll fix the issue though.
Click to expand...
Click to collapse
bootlooops
Edit: nvm, was incomplete.
Sense build.prop files & AOSP build.prop files don't play nice together. Neither do CDMA files & GSM files.
It takes some changes to get the phone to boot with them, or to get radio access with them.
I've already tried a stock Nexus fingerprint, but it still doesn't give access. Like I said, I even pushed the file before even booting the phone (I.E, wipe, flash CM6, push file in recovery, then reboot) and it still didn't work.
Ava's build prop comes up, but no Market. Something else is going on.
Geniusdog254 said:
Sense build.prop files & AOSP build.prop files don't play nice together. Neither do CDMA files & GSM files.
Click to expand...
Click to collapse
Duh, forgot it was Sense for a minute there. I feel like looking into it more but I'm not sure if anyone's going to find a solution.
Ok. So I have been reading a lot around many different Forums about the Voicemail Notifications and it also sending an SMS Notification. Seems the quick fix is the obvious which is installing another SMS Agent and deleting the Stock. Problem is is that to me that is like having the check engine light on in your car and just putting black tape over the light or pulling the bulb. yes it hides the notification but still leaves it broken. My question is What files handle the voicemail? Since all custom roms do not have this problem it seems there is a fix somewhere.
Another question is how can there be a rom with no SystemUI.apk? I flashed Elite Rom and I have searched through every file and folder with Root Explorer,Rom Toolbox,ESFile Explorer and Astro File Manager and yet to find the first thing that even as much as says systemUI.
What Rom are you running? Does the voicemail thing happen on Elite Rom? Just block the sms text that it sends you. As for systemui.apk its in system/app, and if its not there try looking in data/sysapp or something similar
Sent from my PC36100 using xda app-developers app
At the moment I am running Energy Rom. No it doesn't happen on Stock whether odex or not. Doesn't happen on Elite or a few others either. It happens on nearly all ICS or JB Roms and anything with the newer versions of Sense built in.
As for the other I have looked those locations many,many times. What got me to looking is I do not like the Status Bar and it doesn't have screen capture. I tried to just flash both but no go so I decided to just change the systemui.apk file to one that does work. If your interest is now peeked I would say download and unzip the Rom and search for yourself. There isn't a file or folder I can find that I haven't checked. Also flashed it and checked via root to see if it was a file that I would only find once flashed. Haven't located it in 2 days looking but the Rom does work except I can't change the ui to something else.
Fangstien said:
At the moment I am running Energy Rom. No it doesn't happen on Stock whether odex or not. Doesn't happen on Elite or a few others either. It happens on nearly all ICS or JB Roms and anything with the newer versions of Sense built in.
As for the other I have looked those locations many,many times. What got me to looking is I do not like the Status Bar and it doesn't have screen capture. I tried to just flash both but no go so I decided to just change the systemui.apk file to one that does work. If your interest is now peeked I would say download and unzip the Rom and search for yourself. There isn't a file or folder I can find that I haven't checked. Also flashed it and checked via root to see if it was a file that I would only find once flashed. Haven't located it in 2 days looking but the Rom does work except I can't change the ui to something else.
Click to expand...
Click to collapse
SystemUI.apk is right here (see attachment)
Its in /system/app.
As for the ics thing, i cant help you there because i never run those.
Thanks for the screenie but it is Elite Rom with no SystemUI.apk but after much travel through Google Search the best I can figure is that the version used for the Rom doesn't have this file. I read somewhere that 2.1 and before didn't use the file which is what this Rom was based off.
As for the voicemail coming in SMS I found 2 different fixes but 1 doesn't work for me and the other I do not know how to do. First is an SMS to 9999 saying Block 9016. Got a reply saying blocked but the very next message also sent an SMS. Not sure if it is just my phone or no so......The other is to replace the Phone.apk in system/app with one from a rom which doesn't have this problem. I tried many different Roms using Root Explorer to copy/paste the file and recovery to fix permissions but always came up with stopping unexpectedly errors. I did do the wipe cache/davlik also. Is there another step to this process I am overlooking? This SMS 9016 is what is causing me to not use a ICS Rom that is really awesome otherwise. I really don't want to install the bloated GoSMS or HandscentSMS.
I had the original optimus g on att and had been running a leaked version of 4.1.2 and was able to get an aosp version of the mms.apk to run (didnt like the one on the rom, no emojis haha) and since this is running 4.1.2, would it be possible to swap in that same mms app if i root the decive? If anyone braver than me wants to give it a try i still have the mms.apk i had on my OG. Or possibly root, install tb and then freeze stock/restore backup of mms.apk? If anyone has done this already then awesome, if not maybe ill do it this weekend (became a bit of a flash-o-holic with my OG so i cant wait for someone to tear into this and get some nice roms loaded
vinniemac84 said:
I had the original optimus g on att and had been running a leaked version of 4.1.2 and was able to get an aosp version of the mms.apk to run (didnt like the one on the rom, no emojis haha) and since this is running 4.1.2, would it be possible to swap in that same mms app if i root the decive? If anyone braver than me wants to give it a try i still have the mms.apk i had on my OG. Or possibly root, install tb and then freeze stock/restore backup of mms.apk? If anyone has done this already then awesome, if not maybe ill do it this weekend (became a bit of a flash-o-holic with my OG so i cant wait for someone to tear into this and get some nice roms loaded
Click to expand...
Click to collapse
You can install the MMS.apk as a user app and not a system app. Makes it quite a bit less risky. If it causes problems you can just uninstall it.
whenever i try to install it it keeps saying its a system app and then fails cuz it says there is an app with a conflicting signature. is there a special way to install it as a user app instead of system or does it all depend on the apk?
I was messing around with this the day after I first got mine. Since they have the same signature, you can't install both at the same time. The only way that I would suggest doing this safely is to be rooted, set the system\app folder to read/write, rename the UniMessagebin.apk to UniMessagebin.apk.bak, then rename UniMessagebin.odex to UniMessagebin.odex.bak. Copy your mms.apk file to the system\app folder and rename it to UniMessagebin.apk then set permission on it to -rw-r--r--. Then set you system\app folder permissions back to rwxr-xr-x.
You should NOT need to reboot at this point. If the apk is valid and will work the the current system framework, you should see it show up in your app drawer. I was able to get the AOSP 4.1.2 mms.apk to run ok on my phone, but MMS messages weren't working (apparently a known issue with 4.1.2 AOSP). If the apk force closes or doesn't show up as valid, go and delete it from your system\app folder and rename the other two files back to their original names before you attempt to reboot.
Good luck!
i actually found one that worked but didnt have the popup like i had on my original og and the stock one on pro has it...plus the notifications didnt work at all...only reason i knew i had msgs waiting was cuz i happened to open the app...thankfully gf knows wat a geek i am and believed me when i told her haha. back to hunting i guess...thanks for all the help
and then i came across this one...so far has everything i wanted and a dark theme too http://bit.ly/125siHO lets see if notifications work...sux being the only night owl i know haha
I've spent the last day or so looking here on xda and across the web for an answer to this, and I can't seem to find it.
I just freshly installed the Nightly from 2/20 onto my T-Mobile OP7P, and one of the things I always do first is edit the APN settings, including adding 'dun', so I have the option of tethering when I travel. You can't do it through the Settings, so you have to edit the .XML file if you want that.
However, I noticed that the list of APNs in Settings doesn't match the normal file that I would edit in stock. The one in stock being in /system/etc/apns-conf.xml, searched that file for some of the ones showing in the APN list in Settings, and they're nowhere in that file, including my own.
So, obviously Lineage OS is pulling the APNs from a different file, but for the life of me, I have no idea where that file is. Anyone here have any idea?
otrap said:
I've spent the last day or so looking here on xda and across the web for an answer to this, and I can't seem to find it.
I just freshly installed the Nightly from 2/20 onto my T-Mobile OP7P, and one of the things I always do first is edit the APN settings, including adding 'dun', so I have the option of tethering when I travel. You can't do it through the Settings, so you have to edit the .XML file if you want that.
However, I noticed that the list of APNs in Settings doesn't match the normal file that I would edit in stock. The one in stock being in /system/etc/apns-conf.xml, searched that file for some of the ones showing in the APN list in Settings, and they're nowhere in that file, including my own.
So, obviously Lineage OS is pulling the APNs from a different file, but for the life of me, I have no idea where that file is. Anyone here have any idea?
Click to expand...
Click to collapse
What carrier are you currently using? I can send you mine. I had to use my stock apns-conf.xml with lineage and havok
Sent from my moto g(6) play using Tapatalk
Sands207 said:
What carrier are you currently using? I can send you mine. I had to use my stock apns-conf.xml with lineage and havok
Sent from my moto g(6) play using Tapatalk
Click to expand...
Click to collapse
Hey man. I use T-Mobile. I'm good on editing it. I'm not good on actually locating it in the root file system. The APNs reflected in the settings aren't the same as the ones reflected in the /system/etc/apns-conf.xml file, so they've gotta be pulling from somewhere else.
otrap said:
Hey man. I use T-Mobile. I'm good on editing it. I'm not good on actually locating it in the root file system. The APNs reflected in the settings aren't the same as the ones reflected in the /system/etc/apns-conf.xml file, so they've gotta be pulling from somewhere else.
Click to expand...
Click to collapse
What i did to get around that was pretty easy on my end. I deleted the current apns in android settings so none were listed. Then i used fx root browser and copied my stock apns-conf.xml and then went back to apns settings and reset to default. I rebooted and my carrier was there, I am using LTE so i had to enable it as it was set by default to global initially. I also screenshotted my stock apn settings values in case i got lost in the process. I do have a master apns-conf.xml with t-mobile included for some of the ROM's i make. Let me know if you get stuck. Good luck!
Sent from my moto g(6) play using Tapatalk