Related
Phantisy said:
It seems that in all the custom ROM's you can only set the maximum message size to 300k. In the stock T-Mobile ROM you can set it to 1000k. Any reason for this and is there a way to fix this WITHOUT installing any 3rd party apps?
Click to expand...
Click to collapse
Stratis1978 said:
I'm running the SlideMeRoot rom where I have the option of 300, 600, or 1000k message size...
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Gootah said:
I investigated this myself and I came to a conclusion. The 1MB limit is a product of the stock Espresso SENSE. Every other ROM is an older Sense version or the stock Android messenger which has the 300k limit.
Click to expand...
Click to collapse
shadowmike said:
that doesnt explain stratis1978 slideme. unless eug changed between versions
Click to expand...
Click to collapse
sino8r said:
which version is that? I'm not familiar with that particular rom. what Gootah said explained it perfectly. the settings were ripped from another rom basically. only tmo esspresso roms gave the option for 1MB. its possible to change the xml and edit them yourself. I haven't really looked into that very far. I used handcent as a replacement messaging app in slide mr1 v3 since the stock one had problems. I prefer stock but since still even in v4, mms is limited to 300kb... it's a good option.
alright, I took a look at data/data/com.android.mms/shared_prefs fold and there is an file called com.android.mms_preferences.xml Change it if you dont wanna use handcent or another 3rd party app.
Click to expand...
Click to collapse
shadowmike said:
com.android.mms_customizationBySIM.xml also
Click to expand...
Click to collapse
sino8r said:
yeah there should be another called mms_config.xml in mms.apk under res/xml folder but it isn't in this particular rom. so that's 3 different options for folks to change mms size. if your(other members) rom doesn't have that folder or xml, check one of the other 2 options. thanks for finding that one, mike!
Click to expand...
Click to collapse
shadowmike said:
oh btw i flashed eng build and still have 300 max.. i guess it might be the eng causing probs what do you think, btw im back to 100% stock and back to 1000KB max. im going to root and flash eng to make sure and then a rom.
Click to expand...
Click to collapse
the engineering build is limited to 300KB. Im going to attempt a nandroid of factory prduction after root
i ended up running the production nandroid on after downgrading to engineering.
this allowed me to have the 1000kb and still have the unlocked recovery.
however i was unsuccesfull at installing busybox and app2sd forsome reason the the production with root. so i ended up installing slidemeroot5r1 again.
ive tried installing production rom mms.apk and various other files but i cant seem to find the magic settings file with the right values for mms size.
I rooted my Slide the other day and made nandroid backup of it immediately. I hadn't installed any specific rom. I decided to install one rom to try it out, but ended up restoring my nandroid backup that I had. I actually prefer stock and like it a lot. I'm at stock and rooted, but message size limit is still 300kb max.
Is there still any workaround for this?
Anyone know how we can change this text? XML location?
This rom gives you the option to personalize the carrier text AOKP V9
Sent from my Galaxy Nexus using Tapatalk
Push spn-conf.xml to /system/etc
http://www.multiupload.com/Y2NEG07OI8
Edit it before you do. You need to change number 262 (=Germany) to the number for your country and the following 01 (= T-Mobile) to the number for your network.
At the end of the line you can enter the text you want to appear. Push it and reboot, enjoy
This works with EVERY Rom
Auf meinem Galaxy Nexus geschrieben
Tag, looking through the framework for this and other tweaks are on my lst for this weekend.
nachtschicht said:
Push spn-conf.xml to /system/etc
http://www.multiupload.com/Y2NEG07OI8
Edit it before you do. You need to change number 262 (=Germany) to the number for your country and the following 01 (= T-Mobile) to the number for your network.
At the end of the line you can enter the text you want to appear. Push it and reboot, enjoy
This works with EVERY Rom
Auf meinem Galaxy Nexus geschrieben
Click to expand...
Click to collapse
Anybody know the numbers for USA and Verizon?
BeADroid said:
Anybody know the numbers for USA and Verizon?
Click to expand...
Click to collapse
I'd like to know this too.
Just went into /system/etc with Root Explorer. Can't find the spn-conf.xml file anywhere (even did the search). Possibly different on the Verizon LTE SGN since the one from Germany is GSM...
http://forums.androidcentral.com/ve...d-removed-verizonwireless-lock-drop-down.html
here is a guide
SpinDisc said:
Just went into /system/etc with Root Explorer. Can't find the spn-conf.xml file anywhere (even did the search). Possibly different on the Verizon LTE SGN since the one from Germany is GSM...
Click to expand...
Click to collapse
That's OK, it won't be there. Just copy it there so it will be recognized
It doesn't have anything to do with GSM or LTE.
I just realized that you can start Market Enabler and it will tell you the correctly number
nachtschicht said:
That's OK, it won't be there. Just copy it there so it will be recognized
It doesn't have anything to do with GSM or LTE.
Click to expand...
Click to collapse
Thanks for the info! I'm still a newb. My family & friends think I'm a genius (rooted their D.Incredible, D2, Eris, etc). But none of it's possible without the knowledge on XDA. Still learning, and hoping to learn more. Thanks for the info on how to change the banner info, too!
If you want to customize/edit the banner I can confirm this method works 100% with the Gnex
http://d-h-o.us/home/?p=282
I have found the best way to flash it is to create an update.zip or to find file in the ROM you are using and flash it with the ROM. By doing this you lose no data, no need to restore any setting.
The method I posted on my site will nuke your account data (aka just sign into google again).
I have a VZW GNX.
The first method did not work, tried all the numbers I found for Verizon, unless I did something wrong, heh.
DHO's method, when I look for "64…Verizon Wireless" it's just "64...65..." on the Nexus.
So I'm assuming it's pulling the 'Verizon Wireless' information from something else. It would be nice to find that.
mrZoSo said:
I have a VZW GNX.
The first method did not work, tried all the numbers I found for Verizon, unless I did something wrong, heh.
DHO's method, when I look for "64…Verizon Wireless" it's just "64...65..." on the Nexus.
So I'm assuming it's pulling the 'Verizon Wireless' information from something else. It would be nice to find that.
Click to expand...
Click to collapse
I'll update my write up over the weekend as it is for the OG, but look for
HTML:
EriInfo......Verizon Wireless...64...65.
So in the Gnex it is immediately before 64
Can toss a link to market enabler
Sent from my Galaxy Nexus using xda premium
This is what's in the stock one now:
EriInfo...... Google ...64...65...
Nevermind that was a different one I had here, my bad.
I'm going to pull the one off the phone now.
mrZoSo said:
This is what's in the stock one now:
EriInfo...... Google ...64...65...
Click to expand...
Click to collapse
I am still running a stock 4.0.2 based ROM. When I look at some of the ASOP 4.0.3 that I am playing with, one has google, one has verizon. Changing whatever comes before ...64...65 will edit both the lock screen and the tag at the bottom of the notification bar.
CM9 based ROMs seemed to have moved this value to a different file. It would take some digging to determine where they move it to.
DHO said:
If you want to customize/edit the banner I can confirm this method works 100% with the Gnex
http://d-h-o.us/home/?p=282
I have found the best way to flash it is to create an update.zip or to find file in the ROM you are using and flash it with the ROM. By doing this you lose no data, no need to restore any setting.
The method I posted on my site will nuke your account data (aka just sign into google again).
Click to expand...
Click to collapse
Thanks for linking to your great write-up! I followed it (for the most part), and it works...until my screen shuts off (from no activity), and then it goes back to Verizon Wireless. I've tried it two different ways (I'm currently on Deoxed Stock ICL53F with APM & Softkeys):
1. I edited the eri.xml, repackaged it in the APM .zip (since I found that installing other framework-res.apk's broke the APM). Re-flashed the APM .zip, and the new banner "Galaxy Nexus" stuck until the screen shut off. Back on, and it's back to VW
2. I just repackaged the framework-res.apk, and took it out of the APM.zip. Placed it in the "sdcard" section, copied in Root Explorer, and pasted into /system/framework/. After a reboot, same this as #1.
So, how do I get it to stick? Does it have anything to do with the ROM I'm on? Or with APM? I feel like it should work, but something's just not sticking...ugh...
SpinDisc, I'm not sure. I think it may be a function of APM. I have been trying to replicate that bug and I cannot. What launcher are you using?
I cannot replicate it running a ROM compiled from Pete's 4.0.2 AOSP source and NOVA launcher. I will further explore this over the weekend.
This weekend I plan on testing/modding a few different 4.0.3 ROMs, if I find any nuances I will let you know.
If you're rooted, you can use Root Tools.
https://market.android.com/details?...51bGwsMSwxLDEsImNvbS5qcnVtbXkucm9vdHRvb2xzIl0.
A few people have been asking lately;
Use root explorer and go to system>etc>security and rename the otacerts.zip to otacerts.zip.bak
Probably reboot phone for good measure.
That should be it.
Or just disable the Google-Services-Framework in Settings --> Apps --> All
then even the software update option in settings disappeared.
Sent from my Galaxy Nexus using XDA
blockbusta said:
Or just disable the Google-Services-Framework in Settings --> Apps --> All
then even the software update option in settings disappeared.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
No! You're messing around with all possible things by doing that!
May I ask why people want to turn off the OTA firmware update notification? We are not going to receive it every other day like the Firefox browser.
Amowagou said:
May I ask why people want to turn off the OTA firmware update notification? We are not going to receive it every other day like the Firefox browser.
Click to expand...
Click to collapse
I think it's not disabled in some roms and people don't want to be bothered getting it all the time (it is annoying). If you're waiting for the rom dev to update to 4.0.4 (Apex) then the official update is of no interest to you. I don't think it would install anyway if you're rooted.
Vangelis13 said:
A few people have been asking lately;
Use root explorer and go to system>etc>security and rename the otacerts.zip to otacerts.zip.bak
Probably reboot phone for good measure.
That should be it.
Click to expand...
Click to collapse
this didn't work for me on AOKP M4. it worked initially after reboot, but reappeared.
ashman5 said:
this didn't work for me on AOKP M4. it worked initially after reboot, but reappeared.
Click to expand...
Click to collapse
Odd. Check that file again, did it stay renamed (.bak) after the reboot? Maybe root explorer doesn't have su rights.
Vangelis13 said:
Odd. Check that file again, did it stay renamed (.bak) after the reboot? Maybe root explorer doesn't have su rights.
Click to expand...
Click to collapse
double checked. the file stayed .bak after reboot.
root explorer has root access and the folder needed R/W access, which it has for the renaming.
:-\ It probably doesn't work. Scheiße..
http://forum.xda-developers.com/showthread.php?p=24412053
Sent from my Galaxy Nexus using Tapatalk
this method work for another devices, may be will work on the GN (root need):
open build.prop, find string
Code:
ro.build.description=yakju-user 4.0.2 ...another symbols...
ro.build.fingerprint=google/yakju/maguro:4.0.2 ...another symbols...
...and change it like this:
Code:
ro.build.description=yakju-user 4.0.4 IMM76D 299849 release-keys
ro.build.fingerprint=google/yakju/maguro:4.0.4/IMM76D/299849:user/release-keys
it can be a strings from another not updated GN ROM.
I changed 5 strings in build.prop file:
Code:
ro.build.id=IMM76D
ro.build.version.incremental=299849
ro.build.version.release=4.0.4
ro.build.description=yakju-user 4.0.4 IMM76D 299849 release-keys
ro.build.fingerprint=google/yakju/maguro:4.0.4/IMM76D/299849:user/release-keys
now it seems to work fine for me. will be testing for more...
parker22 said:
I changed 5 strings in build.prop file:
Code:
ro.build.id=IMM76D
ro.build.version.incremental=299849
ro.build.version.release=4.0.4
ro.build.description=yakju-user 4.0.4 IMM76D 299849 release-keys
ro.build.fingerprint=google/yakju/maguro:4.0.4/IMM76D/299849:user/release-keys
now it seems to work fine for me. will be testing for more...
Click to expand...
Click to collapse
That is overkill. All you need to change is the ro.build.fingerprint line.
I have checked and double checked. I have tried everyone's ideas here but none works for me on my rooted stock 4.0.2. I'm still getting the notification to upgrade. I can't upgrade as 4.0.4 will stop the touch screen from working.
Anyone else have any ideas? It's really annoying having the upgrade screen come up while your doing stuff.
Regards
Maximo
maximo123 said:
I have checked and double checked. I have tried everyone's ideas here but none works for me on my rooted stock 4.0.2. I'm still getting the notification to upgrade. I can't upgrade as 4.0.4 will stop the touch screen from working.
Anyone else have any ideas? It's really annoying having the upgrade screen come up while your doing stuff.
Regards
Maximo
Click to expand...
Click to collapse
You are doing something wrong then. Changing the ro.build.fingerprint in the build.prop file (to the latest for your build) and rebooting will disable the notification.
Your right. Mine is the i not the D version.
Thanks for that. I appreciate your quick responce, time and help.
Its great having my phone back to how I like it. )
Regards
Maximo
maximo123 said:
Your right. Mine is the i not the D version.
Thanks for that. I appreciate your quick responce, time and help.
Its great having my phone back to how I like it. )
Regards
Maximo
Click to expand...
Click to collapse
Of course he's right. It's efrant..
Vangelis13 said:
A few people have been asking lately;
Use root explorer and go to system>etc>security and rename the otacerts.zip to otacerts.zip.bak
Probably reboot phone for good measure.
That should be it.
Click to expand...
Click to collapse
Hi.
I tried this method and it seems to really work on my Galaxy Nexus.
Thank you.
I'm on Takju 4.1.2 (rooted) and want to stay there for a while. Which of the above methods is best to avoid 4.2.1?
rseiler said:
I'm on Takju 4.1.2 (rooted) and want to stay there for a while. Which of the above methods is best to avoid 4.2.1?
Click to expand...
Click to collapse
Unless you really only want the stock version you might want to try Cyaogenmod. It's stable as can be. It was my solution to avoid 4.2.1.
Hi there, happens to be my first post here. Have installed succesfully Cyanogen Mod succesfully but now my p350 doesnt detect my sim card, dont know exactly why and cant figure it out, I am new to android, would aprreciate any sugestions, thanks there in advance.
Flash Any other stable rom...
and please tell link of the Cynogen Mod ROM which you installed....
theprakhar said:
Flash Any other stable rom...
and please tell link of the Cynogen Mod ROM which you installed....
Click to expand...
Click to collapse
Hi there, thanks for the response.
I have installed this Cynogen Mod ROM: http://forum.xda-developers.com/showthread.php?t=2263963
And also this one: http://forum.xda-developers.com/showthread.php?t=1971158, which has recognized the sim card but still cant use my network.
Been reading a few things and now I feel inclined to try sim unlocking it, but dont know very well which road to take:
# Baseband: I suppose no, that handles radio and gps, no?
# Firmware: I think maybe that can work, but not sure, some info link?
# Editing files like build.prop?
# What about permissions?
Is there a way? Some guy has done it here apparently: http://forum.xda-developers.com/showthread.php?t=1365486, but wasnt kind enough to say how.
Thanks again
Follow this video https://www.youtube.com/watch?v=nRTJ0OG0Hzk&list=UULaB0FBE-vYUKyb8qr35D5A ...it MIGHT work..
It actually worked, I was able to change the firmware more than once, but I was able to chan it to official firwares which actually remains locked, changes only the company of use. Now, I suppose the sim to be locked or not to be will depend of the .kdz file of use. Can recommend one that will do the unlocking? Thanks, you have been very helpful.
juancamisani said:
It actually worked, I was able to change the firmware more than once, but I was able to chan it to official firwares which actually remains locked, changes only the company of use. Now, I suppose the sim to be locked or not to be will depend of the .kdz file of use. Can recommend one that will do the unlocking? Thanks, you have been very helpful.
Click to expand...
Click to collapse
Bro, I think to unlock network ,
ROOT and install a ROM ...It might work ...
Best of luck..:good:
P.S.-if u want funky rom ...check mine http://forum.xda-developers.com/showthread.php?t=2045150 and don't forget to replace the original build.prop with this http://www.mediafire.com/download/91e4ds0x1pc0p19/build.prop[its not for unlocking but for increasing performance]...
theprakhar said:
, I think to unlock network ,
ROOT and install a ROM ...It mighr the work ...
Best of luck..:good:
P.S.-if u want funky rom ...check mine http://forum.xda-developers.com/showthread.php?t=2045150 and don't forget to replace the original build.prop with this http://www.mediafire.com/download/91e4ds0x1pc0p19/build.prop[its not for unlocking but for increasing performance]...
Click to expand...
Click to collapse
Ok, will continue to try some differents roms. Thanks for the links, the roms looks cool. I am just trying to find a certain way to unlock it, maybe there isn't an "unlocked" firmware, maybe itsn't possible. That variant that maybe unlocks it has to have a background. Anyway, the lock code for the IMEI unlock seems to be hackeable somehow, if there is a code to introduce that unlocks it, there is a rainbow table that holds it, no? Will continue trying and update if success. Thanks theprakhar for all the answers, good day gentlemens.
I found the A1's camera pretty good sometimes, but the stock camera is quite useless, and no other 3rd party app seemed to be able to make good use of the camera.
Is there any way to get a good camera app, perhaps the Google camera, or the Samsung note 8 camera app?
U can't, u have to edit the build prop to enable camera HAL either it would not work.
Roykooiman said:
U can't, u have to edit the build prop to enable camera HAL either it would not work.
Click to expand...
Click to collapse
In that case, how would you suggest on improving the camera? The camera hardware is itself quite capable, but the software is not upto the mark.
leroyjd123 said:
In that case, how would you suggest on improving the camera? The camera hardware is itself quite capable, but the software is not upto the mark.
Click to expand...
Click to collapse
The answer is root lol, why u don't want to root it?
There is actually no root required for editing build.prop. You unlock the bootloader, then you can boot (not flash) the TWRP and mount system with W permissions. Pull the build.prop file, edit it and push it back to its place. Then you need to set the permissions of the file through the shell. As the last thing you can relock the bootloader and have the edited build.prop file without having the root.
Google it and you will find the guide.
I tested it myself. It works.
maross said:
There is actually no root required for editing build.prop. You unlock the bootloader, then you can boot (not flash) the TWRP and mount system with W permissions. Pull the build.prop file, edit it and push it back to its place. Then you need to set the permissions of the file through the shell. As the last thing you can relock the bootloader and have the edited build.prop file without having the root.
Google it and you will find the guide.
I tested it myself. It works.
Click to expand...
Click to collapse
Hi, can you post the guide that you are used for A1, because in google are many variants
mqdjo said:
Hi, can you post the guide that you are used for A1, because in google are many variants
Click to expand...
Click to collapse
Safer option is to use a Magisk module which does exactly the thing but without having to add the lines into build.prop manually and setting the permissions etc
maross said:
There is actually no root required for editing build.prop. You unlock the bootloader, then you can boot (not flash) the TWRP and mount system with W permissions. Pull the build.prop file, edit it and push it back to its place. Then you need to set the permissions of the file through the shell. As the last thing you can relock the bootloader and have the edited build.prop file without having the root.
Google it and you will find the guide.
I tested it myself. It works.
Click to expand...
Click to collapse
What about OTA after that?
mqdjo said:
Hi, can you post the guide that you are used for A1, because in google are many variants
Click to expand...
Click to collapse
Google "how to edit build.prop without root mi a1" and pick the guide posted on themefoxx website. I am not allowed to post external links [yet].
---------- Post added at 07:10 PM ---------- Previous post was at 07:07 PM ----------
nitroax said:
What about OTA after that?
Click to expand...
Click to collapse
Does not work. After downloading the proposed update I get installation error at the very beginning. Maybe after restoring the build.prop file the same way as I modified it, it might work.
Once you mount the system as read/write, you can't apply OTA. This is why it's better to use Magisk instead of altering system files directly.
maross said:
There is actually no root required for editing build.prop. You unlock the bootloader, then you can boot (not flash) the TWRP and mount system with W permissions. Pull the build.prop file, edit it and push it back to its place. Then you need to set the permissions of the file through the shell. As the last thing you can relock the bootloader and have the edited build.prop file without having the root.
Google it and you will find the guide.
I tested it myself. It works.
Click to expand...
Click to collapse
Hey there!
I just joined XDA for the sole purpose of finding this tutorial that I have seen floating around the web lately. But unfortunately, every website has a different version of how exactly this should be done. Do you know where I can find the exact steps to take in order to edit the build.prop without having to root my phone and without losing the OTA updates?
Cheers!
adrflg said:
Hey there!
I just joined XDA for the sole purpose of finding this tutorial that I have seen floating around the web lately. But unfortunately, every website has a different version of how exactly this should be done. Do you know where I can find the exact steps to take in order to edit the build.prop without having to root my phone and without losing the OTA updates?
Cheers!
Click to expand...
Click to collapse
If u edit build.prop means u will break OTA. 100%
just root guys using magisk safetynet pass through.
under magisk hide , chose the apps if you face issue against root, it will open
Rajeev said:
If u edit build.prop means u will break OTA. 100%
Click to expand...
Click to collapse
adrflg said:
Hey there!
I just joined XDA for the sole purpose of finding this tutorial that I have seen floating around the web lately. But unfortunately, every website has a different version of how exactly this should be done. Do you know where I can find the exact steps to take in order to edit the build.prop without having to root my phone and without losing the OTA updates?
Cheers!
Click to expand...
Click to collapse
Hi,
Rajeev is right. You can edit the build.prop this way. And it is going to work. But you are gonna loose OTA, because you need to mount system with write privileges through TWRP in order to modify system file.
Is it possible to unlock the bootloader, root, make some minor modifications (activation of camera api, copying fm radio apk to system folder, etc), unroot, and finally relock (flashing stock boot.img before, of course) ?
I want to have it unrooted because of bank payments, banks apps and streaming TV apps, but I would like to have proper camera and fm radio... Is it possible??
no
erunamor said:
Is it possible to unlock the bootloader, root, make some minor modifications (activation of camera api, copying fm radio apk to system folder, etc), unroot, and finally relock (flashing stock boot.img before, of course) ?
I want to have it unrooted because of bank payments, banks apps and streaming TV apps, but I would like to have proper camera and fm radio... Is it possible??
Click to expand...
Click to collapse
Not possible
erunamor said:
Is it possible to unlock the bootloader, root, make some minor modifications (activation of camera api, copying fm radio apk to system folder, etc), unroot, and finally relock (flashing stock boot.img before, of course) ?
I want to have it unrooted because of bank payments, banks apps and streaming TV apps, but I would like to have proper camera and fm radio... Is it possible??
Click to expand...
Click to collapse
How about rooting the phone with Magisk and use Magisk Hide to hide root from those apps?
Htf do you think miui camera is useless. I am a photographer. And find it quit usefull and makes full use dual lens. Have you even tried HHT? Never compare two different apps. HDR+ is google's algorithm. You won't get in miui camera. HHT is miui's thing. You won't get in Gcam. Anyways HDR+ is not mandatory, you can get it from any post processing app.
yashgumaste said:
Htf do you think miui camera is useless. I am a photographer. And find it quit usefull and makes full use dual lens. Have you even tried HHT? Never compare two different apps. HDR+ is google's algorithm. You won't get in miui camera. HHT is miui's thing. You won't get in Gcam. Anyways HDR+ is not mandatory, you can get it from any post processing app.
Click to expand...
Click to collapse
A1 camera is superb in Day light only. It can't beat Google Camera in very low light. Everyone trying Google Camera here for getting Selfie Portrait mods. That not available in A1 camera .. I am not a photographer. But i can tell as a normal user in low light Google Camera perform really better than A1 camera. May be some 3rd party apps can do that but someone loves Google Camera