Hey guys, I've been struggling with this for a while. I am on the 2.3.5 Electrify ROM, so it says that my carrier is U.S. Cellular.
I'm trying to change that so the text says "Sprint".
I have tried almost everything I can think of.
I did an ADB pull of the framework-res.apk, decompiled it, hex edited the eri.xml file (changed out the "U.S. Cellular" with "Sprint "), saved it, recompiled the APK, then pushed that to the phone.
Tried all of the carrier name changing .apks, but none of them work.
Any ideas?
Thanks a ton in advance.
i think your main problem is that you are on an electrify rom and not a photon rom
Yeah, that's the root of my problem.
Sent from my Acer Iconia A500 using xda premium
i remeber reading some post a while back with same problem with no good outcome. Do you have insurence? they were saying that you would have to take it to sprint to get out of there. Hope it works out for you.
Read that thread. Someone posted an xml file that fixes it.
Sent from my MB855 using Tapatalk
Here it is http://forum.xda-developers.com/showthread.php?p=22012299
You need to change the eri xml in the framework-res.apk with one modified to say sprint. Its possible to do right on the phone using an app like ninja morph if you have no knowledge of decompiling, editing, and recompiling apks.
EDIT - I've attached a deodexed framework-res.apk from 2.3.5 which has been modified and displayed "sprint" as the carrier on my phone.
KSmithInNY said:
You need to change the eri xml in the framework-res.apk with one modified to say sprint. Its possible to do right on the phone using an app like ninja morph if you have no knowledge of decompiling, editing, and recompiling apks.
EDIT - I've attached a deodexed framework-res.apk from 2.3.5 which has been modified and displayed "sprint" as the carrier on my phone.
Click to expand...
Click to collapse
You rock! That worked! Thanks!
I edited the the eri.xml file a million times, recompiled, pushed, but it never worked.
I wonder if it's cause I am odexed?
npaulseth said:
You rock! That worked! Thanks!
I edited the the eri.xml file a million times, recompiled, pushed, but it never worked.
I wonder if it's cause I am odexed?
Click to expand...
Click to collapse
The odex was likely the culprit. That apk also has the apn.xml in it that I took from a sprint build. I used the apn-conf from a sprint build in /system/etc, changed the build prop to use the sprint apn (310120), replaced /data/data/com.Motorola.telephony/db/carriers with the Sprint one and still no go on MMS receiving using the stock app. I have 2 theories to check in my down time but go sms works in a pinch for now.
Cheers!
P.S. if you flashed the electrify zips around check your custom recovery. Install-recovery wasn't removed and it will revert to stock recovery upon booting the first time. CWM can be applied same as before but unless you delete the file it will do the same every time you boot up.
Awesome man. I just tried to APN switch-a-roo (oddly enough before reading your post), and I can't get it to work with the stock app either. I went in the APN.xml file and change the "Carrier: Sprint" to Carrier: U.S.Cellular", and that didn't work either.
Nah trust me, everything from easy to moderate difficulty has been ruled out. I have 2 remaining ideas to test but it will need to wait until I get some free time.
If I figure it out I'll let you know and someone can package a flashable zip with my framework-res, a replacement build.prop, the apn-conf, and whatever else is necessary to get it working. I want nothing to do with owning it so the community will be responsible to package it and support each other but id call that a fair deal.
Again no promises, its contingent on my free time and my GF's tolerance of me on my phone
KSmithInNY said:
Nah trust me, everything from easy to moderate difficulty has been ruled out. I have 2 remaining ideas to test but it will need to wait until I get some free time.
If I figure it out I'll let you know and someone can package a flashable zip with my framework-res, a replacement build.prop, the apn-conf, and whatever else is necessary to get it working. I want nothing to do with owning it so the community will be responsible to package it and support each other but id call that a fair deal.
Again no promises, its contingent on my free time and my GF's tolerance of me on my phone
Click to expand...
Click to collapse
Been down this road before...
If you look at a logcat of when trying to retrieve a mms you will notice that the remote network (sprint) rejects the connection due to an unkown device.
Unless we can figure out how to change the phone so it does not idenify itself as 2.3.5 then I think we are out of luck.
Spent many days on this and decided it was not worth it.
RJR
Anyone with a 2.3.5 electrify build running on a Sprint photon can download the attached build.prop.txt, edit the name and remove the .txt part so it's only named build.prop, place it in /system. Once you have it in, reboot. It's a sprint-a-fied build.prop for 2.3.5.
Also attached the sprint bootanimation.zip. Just download that and place in /system/media . I know thats bothering someone out there.
For the real purists, while you're in media you might want to check out audio/ringtones and audio/notifications because USC added their own sound file in each you may consider deleting.
EDIT- Almost forgot, you need to set the permissions properly once you move the file(s). Both files should be rw-r--r--
I did both of those things already. Ha.
They actually were really bugging me.
npaulseth said:
I did both of those things already. Ha.
They actually were really bugging me.
Click to expand...
Click to collapse
Use my build.prop and after a reboot, please check if MMS receive works. The device fingerprint is changed to the sprint photon fingerprint. I can't test because I currently have one of my blackberries activated to test some other work.
Thanks.
EDIT- also I noticed you said you've been playing around in the apn xml. Please put it back to stock. My build.prop should set your operator as 310120 on boot. Or at least it should. You could check to make sure.
Related
does anyone know the file i need to change that tells clockworkmod to say while loading a rom/mod/etc? like how liquid,th3ory,bamf and all them put their signatures in it? or is asking that question the first sign that im way too noob for that?
shelooga said:
does anyone know the file i need to change that tells clockworkmod to say while loading a rom/mod/etc? like how liquid,th3ory,bamf and all them put their signatures in it? or is asking that question the first sign that im way too noob for that?
Click to expand...
Click to collapse
ui_print("Your Text Here");
Just download any CWR flashable rom or kernel and open META-INF/com/google/android/updater-script and you can see anything they put in.
shelooga said:
does anyone know the file i need to change that tells clockworkmod to say while loading a rom/mod/etc? like how liquid,th3ory,bamf and all them put their signatures in it? or is asking that question the first sign that im way too noob for that?
Click to expand...
Click to collapse
How to create and package an update file for recovery:
http://www.londatiga.net/it/how-to-create-android-update-zip-package/
Basically you just make an bash script file (update-script) and echo out what you want to display or do with using that method.
Thanks guys! Very simple
So... you have it done? Ready to drop it?
Sent from my ThunderBolt using XDA App
DroidTh3ory said:
So... you have it done? Ready to drop it?
Sent from my ThunderBolt using XDA App
Click to expand...
Click to collapse
nah not yet. i got the framework themed, working on apps and the system ui. and then i got drop you some bucks too. but im tampering with everything at once. my gf is pissed!
hybrid base is a good starting point too, just gotta get all those widgets out. im about to just can it and go with aosp
thanks for all your help too, i get paid tomorrow so youll be hearing from me
shelooga said:
nah not yet. i got the framework themed, working on apps and the system ui. and then i got drop you some bucks too. but im tampering with everything at once. my gf is pissed!
hybrid base is a good starting point too, just gotta get all those widgets out. im about to just can it and go with aosp
thanks for all your help too, i get paid tomorrow so youll be hearing from me
Click to expand...
Click to collapse
NAH, that is NOT necessary at all. Can't wait to check it out. If you need anything, Feel free!!
DroidTh3ory said:
NAH, that is NOT necessary at all. Can't wait to check it out. If you need anything, Feel free!!
Click to expand...
Click to collapse
no i know i dont need to, but you earned it. i know youll be here to help
Well, it sounded simple. I thought I'd just need to change some text in the updater-script file before I amassed it all in the kitchen, but its not that simple apparently. Item 151 on today's glitch list
Edit: if I package the rom w the updater, then extract the updater n add at the beginning ui_print("jibberish");
repackage n sign, would that work?
Yes, but you can also do it before hand. When it is building, and it gets to the point of converting the "update" script to a "updater" script, you can go into your working folder and edit it.
But also, after the build is done, you can keep the file compressed and edit the script also
Either way.
Sent from my ThunderBolt using XDA App
DroidTh3ory said:
Yes, but you can also do it before hand. When it is building, and it gets to the point of converting the "update" script to a "updater" script, you can go into your working folder and edit it.
But also, after the build is done, you can keep the file compressed and edit the script also
Either way.
Sent from my ThunderBolt using XDA App
Click to expand...
Click to collapse
Nice. Now the question is, grab a beer n burger on lunch, or work on this?
I think im going to put it out without themeing any apps, just framework n the system. Its going to be a slimmer version of your hybrid. Doesn't seem as fast though but that might be bc I switched to adw ex from lpp, and I have every widget n animation going I can fit. I also might swap the music.apk with honeycombs, it goes w gallery3d well.
Hope u got my donation today, u deserve every penny for hooking us all up
shelooga said:
Nice. Now the question is, grab a beer n burger on lunch, or work on this?
I think im going to put it out without themeing any apps, just framework n the system. Its going to be a slimmer version of your hybrid. Doesn't seem as fast though but that might be bc I switched to adw ex from lpp, and I have every widget n animation going I can fit. I also might swap the music.apk with honeycombs, it goes w gallery3d well.
Hope u got my donation today, u deserve every penny for hooking us all up
Click to expand...
Click to collapse
Did you toss in the init.d scripts I have? That will give you your speed.
Sent from my ThunderBolt using XDA App
It's a bit spiffier than our default home. Can anyone deodex one for us? I'd appreciate it.
Sent from my Motorola Photon 4g
i am literally deodexing the d3 dump as we speak will update with progress
Edit
Hmmm I seem. To be having issues with the custom bootclass paths .. everything deodexes except blurhome 2. Lol. Any suggestions??
I don't have any off the top of my head. I was trying to deodex the single app from the D3 dump myself.
Sent from my Motorola Photon 4g
its just trying to figure out what other jars it needs to deodex the file i know one of them just based off of other deo s ive done but theres still something missing
com.motorola.app.admin.jar
is one
We could always just wait. I thinking they are working on porting clockwork to the D3 now. A deodexed stock rom should follow soon.
Sent from my Motorola Photon 4g
This would be awesome!!!!!!
Sent from my MB855 using XDA App
I i have painstakingly deodexed this whole rom . Trying to get this apk . Its a system file so it wont just install..
And renaming my current blurhome to blurhome.apk.bak causes forcecloses and i have to battery pull
its obviously beyond me because even when i do get it to recognize, it says This is not a blur device
i even setup motoblur and still no go
i also left my blurhome.apk there as well.. Still no go
this droid 3 blurhome should just work . But obviously its missing some dependiencies. If anyone can figure it out let me know
i have the whole rom deodexed so i can pull any file necessary
here she goes.. Giving it to the masses to troubleshoot
http://www.multiupload.com/B92RVMS087
seanzscreams said:
I i have painstakingly deodexed this whole rom . Trying to get this apk . Its a system file so it wont just install..
And renaming my current blurhome to blurhome.apk.bak causes forcecloses and i have to battery pull
its obviously beyond me because even when i do get it to recognize, it says This is not a blur device
i even setup motoblur and still no go
i also left my blurhome.apk there as well.. Still no go
this droid 3 blurhome should just work . But obviously its missing some dependiencies. If anyone can figure it out let me know
i have the whole rom deodexed so i can pull any file necessary
here she goes.. Giving it to the masses to troubleshoot
http://www.multiupload.com/B92RVMS087
Click to expand...
Click to collapse
I will mess with this tomorrow. Thanks for putting in the work.
[email protected] said:
I will mess with this tomorrow. Thanks for putting in the work.
Click to expand...
Click to collapse
Its dependency is in the framework mirror service.jar or something very similar however you have to modify the jar to mimic a blur device in order to use it
Nothing on this anymore??
Sent from my MB855 using XDA App
+1 10 char
Edit the build.prop file to use the same model and name as the Droid 3 and you'll be good.
mrinehart93 said:
Edit the build.prop file to use the same model and name as the Droid 3 and you'll be good.
Click to expand...
Click to collapse
Have you tried this yet? Would really like to see it working. We ended up with the crappy blur launcher somehow
coldblooded79 said:
Have you tried this yet? Would really like to see it working. We ended up with the crappy blur launcher somehow
Click to expand...
Click to collapse
I haven't tried it but I have a strong feeling it will work. That is how apps check what phone they're on. I used Swype on a phone running CM7 before by changing the build.prop to make it think it was an LG Optimus S (it WAS an Optimus S, but they changed the model and name in CM7).
Yeah I remember that swype problem on my evo. Took me a bit to find a working version.
Sent from my Motorola Photon 4g
coldblooded79 said:
Yeah I remember that swype problem on my evo. Took me a bit to find a working version.
Sent from my Motorola Photon 4g
Click to expand...
Click to collapse
Yeah as long as you have the correct version (MDPI, HDPI) and change the build.prop to a phone that has Swype pre-installed, you're good to go.
tried the build prop edit, still a no go. Maybe I did something wrong??
Can you post a build.prop from the Droid 3 and the Photon? I'll edit the Photon one and upload it back for ya.
here...i'll take the liberty of uploading the build props for you....i'm just as interested in getting this working as everyone else
Try this build.prop. Make sure you don't rename it or anything. If it doesn't work let me know because there is 1 more change that may affect it.
Anyone else running into this error? Only a few of my sms are going through. I saw a thread on the evo 4g about it but the solution didn't work for me.
pandamaja said:
Anyone else running into this error? Only a few of my sms are going through. I saw a thread on the evo 4g about it but the solution didn't work for me.
Click to expand...
Click to collapse
You need to get your msl as soon you have it go to the phone pad and enter this number ##72786# then is going to ask for a password enter the msl the press ok you're going to get 4 options you're going to hit menu the reset and just hit ok on every message...phone is going to turn off the back on by itself you going to get the handsfree activation just let it run after the updates are done test the messages
Sent From My HTC EVO 3D ROOTED
Cool thanks. The edit mode(##) or whatever they're called isn't working. I think it may have something to do with the ROM I'm running. Do you know where I can find a list of ## to try? When I try the ##72786# I'm not prompted for a password and it just goes back to recent calls list. Thanks!
pandamaja said:
Cool thanks. The edit mode(##) or whatever they're called isn't working. I think it may have something to do with the ROM I'm running. Do you know where I can find a list of ## to try? When I try the ##72786# I'm not prompted for a password and it just goes back to recent calls list. Thanks![/QUOTE
What rom.do u have
Sent From My HTC EVO 3D ROOTED
Click to expand...
Click to collapse
Just seeing this. It happens with multiple roms. some roms are fine though.
pandamaja said:
Just seeing this. It happens with multiple roms. some roms are fine though.
Click to expand...
Click to collapse
The secret dialer codes, ##xxxxx## should be picked up by the EPST.apk file located in /system/app. This is generally a Sprint developed and placed apk file.
I don't know why a ROM developer would remove this file from a Sense based ROM as any device on the Sprint network would want/need this file.
If the EPST.apk file is present in /system/app, then the dialer codes should work. Hope that helps answer your question!
joeykrim said:
The secret dialer codes, ##xxxxx## should be picked up by the EPST.apk file located in /system/app. This is generally a Sprint developed and placed apk file.
I don't know why a ROM developer would remove this file, other than out of ignorance, as any device on the Sprint network would want/need this file.
If the EPST.apk file is present in /system/app, then the dialer codes should work. Hope that helps answer your question!
Click to expand...
Click to collapse
Hi I am having the same issue. I don't have the EPST.apk file in /system/app though so the dialer codes dont work. Where can i download and install that apk?
My ROM is Prime XL 3D
joeykrim said:
The secret dialer codes, ##xxxxx## should be picked up by the EPST.apk file located in /system/app. This is generally a Sprint developed and placed apk file.
I don't know why a ROM developer would remove this file, other than out of ignorance, as any device on the Sprint network would want/need this file.
If the EPST.apk file is present in /system/app, then the dialer codes should work. Hope that helps answer your question!
Click to expand...
Click to collapse
Easy there killa.... cyanogenmod doesn't work with ## codes, and I wouldn't exactly call them ignorant
As for the error code, if the problem is intermittent, it should remedy itself if about 5-10-15 minutes. It is a network issue and not a phone issue. I would advise to just off/battery pull/on (which is always good to do periodically anyway)
Resetting the phone beyond that should not be necessary to remedy your situation. But you always can resort to that - it just might not be your solution
guyandhisdog said:
Easy there killa.... cyanogenmod doesn't work with ## codes, and I wouldn't exactly call them ignorant
As for the error code, if the problem is intermittent, it should remedy itself if about 5-10-15 minutes. It is a network issue and not a phone issue. I would advise to just off/battery pull/on (which is always good to do periodically anyway)
Resetting the phone beyond that should not be necessary to remedy your situation. But you always can resort to that - it just might not be your solution
Click to expand...
Click to collapse
I'm running sense 3.5 and I don't have the EPST.apk so he's not referring to AOSP ROMS like cyanogen
Sent from my PC36100 using xda premium
anyone ever figure this out? I just started getting this. Newest wtsb rom sense 3.5
ryudo423 said:
anyone ever figure this out? I just started getting this. Newest wtsb rom sense 3.5
Click to expand...
Click to collapse
This is a known issue with this Rom. Wes and Sac are working on it. I am running the same Rom and also having the same problem. Stay under 160 characters and you won't have a problem.
Sent from my PG86100 using xda premium
I am running the EnergyRom on my Evo and getting the same error. The under 160 characters thing does not apply. At times I'm trying to send less than 50 characters and get the same error. Last month this happened before I rooted and they reset something on the backend. All was well for like a week. Now its back again. I wish someone would figure this out. Being an east coast transplant on the west coast without being able to reach friends and family back home is getting quite bothersome.
Sent from my PC36100 using xda premium
http://forum.xda-developers.com/showthread.php?t=2033894
Can confirm working on Verizon stock:
Message: Enter key=new line
Web: Desktop as default and exit on menu
Camera: Shutter sound on/off menu
TW: Infinite scrolling
Others may work but I just didn't try. Excellent work kkoolpatz!
Sent from my SCH-I605 using xda app-developers app
Thanks for this. Currently on stock, rooted. Infinite scroll on TW launcher worked perfect.
Sent from my SCH-I605 using Tapatalk 2
Very cool. I'm on cleanrom vzw 1.0 and these work perfectly. All I added was to remove the software update in settings and the exit option on the browser.
Just tried out some of them... works well... thanks!
This is not original development. This topic needs to be moved.
I wasn't sure it belonged here either but the original thread in the International GN2 had it in original development so I just followed suit. Please feel free to move.
Sent from my SCH-I605 using xda app-developers app
Thread moved to General. Please remember that development is only for development and not all development related threads. In this case you were sharing development, therefore it wasn't actual development. Thanks for your understanding and cooperation.
~ The-Captain
Rename customer.xml and you get bubble notifications back on lockscreen.
Enable call blocking (Not blocking mode), add this to feature.xml:
<!--Call Blocking -->
<CscFeature_Setting_EnableMenuBlockCallMsg>true</CscFeature_Setting_EnableMenuBlockCallMsg>
adrynalyne said:
Rename customer.xml and you get bubble notifications back on lockscreen.
Enable call blocking (Not blocking mode), add this to feature.xml:
<!--Call Blocking -->
<CscFeature_Setting_EnableMenuBlockCallMsg>true</CscFeature_Setting_EnableMenuBlockCallMsg>
Click to expand...
Click to collapse
So just rename customer.xml or change .xml to something like .bak? Just seeking some clarification. Thanks!
johnsonvision said:
So just rename customer.xml or change .xml to something like .bak? Just seeking some clarification. Thanks!
Click to expand...
Click to collapse
Yup!
Tried this and Im not getting anything. Unless i don't know what it looks like..
Edit oh wait i got it.
Do you have to be rooted to do this?
adrynalyne said:
Yup!
Click to expand...
Click to collapse
Awesome, it works! Do you know what app needs to be frozen to stop with the help tip when the bubble is on the lockscreen?
johnsonvision said:
Awesome, it works! Do you know what app needs to be frozen to stop with the help tip when the bubble is on the lockscreen?
Click to expand...
Click to collapse
No. It eventually went away for me though. If I was to guess, I'd try setup wizard. I haven't really looked into it though because it went away.
fluidj said:
Do you have to be rooted to do this?
Click to expand...
Click to collapse
yes.
adrynalyne said:
No. It eventually went away for me though. If I was to guess, I'd try setup wizard. I haven't really looked into it though because it went away.
Click to expand...
Click to collapse
Cool, I appreciate the help. I found out after further research that you can go in to settings>application settings>all>help and then just disable that. That worked for me to get rid of the constant helpful tip.
Well I copy pasted the code into the features.xml file for the various Web browser additions, like perma-Desktop view mode and show user agent profile under advanced settings. But none of them worked. I looked through the web section to make sure there were no countering duplicates, and there wasn't.
I went ahead and rebooted into recovery, wiped cahce/dalvik, fixed permissions and booted back up and no go. Anyone get these settings working?
DaRkL3AD3R said:
Well I copy pasted the code into the features.xml file for the various Web browser additions, like perma-Desktop view mode and show user agent profile under advanced settings. But none of them worked. I looked through the web section to make sure there were no countering duplicates, and there wasn't.
I went ahead and rebooted into recovery, wiped cahce/dalvik, fixed permissions and booted back up and no go. Anyone get these settings working?
Click to expand...
Click to collapse
See, you shouldn't need to copy anything in, but simply change trues to false and so forth. If you pasted a line in, I'd be suspicious that you have the line in there already overriding the new one. Most of the CSC features are already in the file.
adrynalyne said:
See, you shouldn't need to copy anything in, but simply change trues to false and so forth. If you pasted a line in, I'd be suspicious that you have the line in there already overriding the new one. Most of the CSC features are already in the file.
Click to expand...
Click to collapse
Yeah I checked through for duplicate lines and didn't see any of the 3 lines that I added before pasting them in.
Just to add to the mix, somehow adding 3 lines that affected the browser only, I found that my Samsung keyboard symbol overlay was missing. So I just deleted my custom features.xml and restored the backup and it's all back to normal again. Was also seeing wierdness with MMS with the modified xml as well.
Anyway I'll look again just to be sure, but trying to decide if I really care enough for it at this point.
Update: yeah for sure there isn't a single duplicate. I copied the XML to my desktop and searched through with keywords and there was nothing that matched. Then read through it line by line and saw a few entries that seem similar in purpose, but are worded differently. I am unsure how to modify these or which one I should modify at all to get the desired affect, so I am leaving it alone for now.
Ironically enough however I found a solution to an annoying "feature" that's been plaguing me for awhile now. Whenever I toggle to Camcorder or open up the camera app into Camcorder, it would ask me what video mode I want to shoot in. This was driving me nuts, and sure enough it's being caused by a CSC feature. Well I false'd it up and yay no more annoying popup. Problem is, just like with the web browser changes/additions to feature.xml, whenever I modify the file all of a sudden a bunch of other things break including MMS and my keyboard's symbol overlay. Wtf =/ It's so frustrating being right there and having the solution to one problem, and then opening up a can of worms in another.
I could understand if I somehow modified parts to the keyboard CSC, and that would be why it's breaking, but I'm not. I'm going in, finding ONE line, and changing true to false. That's it. Why is this breaking other parts of my CSC? Any ideas Adrynalyne?
DaRkL3AD3R said:
Yeah I checked through for duplicate lines and didn't see any of the 3 lines that I added before pasting them in.
Just to add to the mix, somehow adding 3 lines that affected the browser only, I found that my Samsung keyboard symbol overlay was missing. So I just deleted my custom features.xml and restored the backup and it's all back to normal again. Was also seeing wierdness with MMS with the modified xml as well.
Anyway I'll look again just to be sure, but trying to decide if I really care enough for it at this point.
Update: yeah for sure there isn't a single duplicate. I copied the XML to my desktop and searched through with keywords and there was nothing that matched. Then read through it line by line and saw a few entries that seem similar in purpose, but are worded differently. I am unsure how to modify these or which one I should modify at all to get the desired affect, so I am leaving it alone for now.
Ironically enough however I found a solution to an annoying "feature" that's been plaguing me for awhile now. Whenever I toggle to Camcorder or open up the camera app into Camcorder, it would ask me what video mode I want to shoot in. This was driving me nuts, and sure enough it's being caused by a CSC feature. Well I false'd it up and yay no more annoying popup. Problem is, just like with the web browser changes/additions to feature.xml, whenever I modify the file all of a sudden a bunch of other things break including MMS and my keyboard's symbol overlay. Wtf =/ It's so frustrating being right there and having the solution to one problem, and then opening up a can of worms in another.
I could understand if I somehow modified parts to the keyboard CSC, and that would be why it's breaking, but I'm not. I'm going in, finding ONE line, and changing true to false. That's it. Why is this breaking other parts of my CSC? Any ideas Adrynalyne?
Click to expand...
Click to collapse
I have a feeling it is the editor you are using.
Things like notepad add extra characters to files which can invalidate the entries and cause other errors. Try something like notepad ++.
Hey everyone, I was wondering if anyone has been able to get their hands on the Optical Reader APK. I would really like to use it, but haven't been able to find anywhere on the internets that someone has uploaded it. While I am competent in basic root, etc. I don't know how to pull this from any roms myself. Would really appreciate any help if someone has the time to upload it as an APK, since I'm not rooted. Thanks!
I have been searching for the program as well all week and I've come to a couple conclusions:
There is one individual from the T-Mobile forums looking to help us less fortunate (Verizon) users with the .APK file, but unfortunately there is a .odex attached and he hasn't gotten into deconstructing that yet.
A lot of users are suggesting downloading a program called 'CamCard' from the Samsung App Store (also removed from our phone but downloadable). While this seems like a nice substitution (which I haven't tried), it seems it's only for the business card aspect, and not the all in one package deal that optical offers.
Update: If you do decide to go with 'CamCard', you would also want to add Photo Reader, but you still lose out on translation. 2 out of 3 features ain't bad.
RUMOR: It seems that someone was able to get a hold of Samsung, and confirmed that Big Red did remove the program. From what some users are saying (from their contact with customer support) is that Verizon merely disabled the program and may push it out in a future update. I've attempted to go through every system file and folder but wasn't able to come up with anything, so most likely it's just gone.
I'll be sure to come back and update this if I read any more information.
Stay away from CamCard. It's a piece of ****. I bought it 3 years ago i think it was and when I requested support they gave none so I disputed the charges with my bank and got refunded, It's probably the worst program I ever used. Funny thing is, I can still use it an update it with no issues.
Some of the answers are above. Using Hyperdrive RLS 4 ROM, which got Optical Reader from the international version. However, when you open it, it tries to update on Samsung Apps, and gives you an error that the device does not support it, and shuts it down. Tried getting it on Samsung Apps, and again gives an error that the device does not support it. CamCard is really for business cards only. Google Goggles does not do as great a job either (at least the formating sucks). Until then, I will practice patience....
richardhard said:
Some of the answers are above. Using Hyperdrive RLS 4 ROM, which got Optical Reader from the international version. However, when you open it, it tries to update on Samsung Apps, and gives you an error that the device does not support it, and shuts it down. Tried getting it on Samsung Apps, and again gives an error that the device does not support it. CamCard is really for business cards only. Google Goggles does not do as great a job either (at least the formating sucks). Until then, I will practice patience....
Click to expand...
Click to collapse
Same experience as you, (with the exception that I am running stock rooted) it appears that the file it is trying to download is a database, and it is just over 50 meg.
I've read the suggestions to download CamCard, but for me 1) It just looks shady (IMO) and 2) It looks to only be of use for business cards. So I plan on staying away from CamCard. I have used Google Goggles in the past, and while it works, Samsung's Optical Reader looks awesome, and I'm really itching to play with it. I appreciate the responses, really. Guess until someone has time to put it together, I will just have to patiently wait and continue to use Google Goggles.
Well, I guess as just a minor update:
I was able to find both the APK and ODEX files from somewhere in the depths that is XDA. I attempted to move both files into the system/apps folder and change the permissions to rw-r--r--, but after several restarts and do overs, I'm not having much luck on that front. There was one suggestions (via Hyper thread) that I would have to change the build.prop file device.name, but I would like to avoid making edits to the build.prop if possible.
Any suggestions?
n0_face said:
Well, I guess as just a minor update:
I was able to find both the APK and ODEX files from somewhere in the depths that is XDA. I attempted to move both files into the system/apps folder and change the permissions to rw-r--r--, but after several restarts and do overs, I'm not having much luck on that front. There was one suggestions (via Hyper thread) that I would have to change the build.prop file device.name, but I would like to avoid making edits to the build.prop if possible.
Any suggestions?
Click to expand...
Click to collapse
Wonder if you can change the build prop, then get it from Samsung then change it back?
Sent from my SCH-I545 using xda premium
gadget! said:
Same experience as you, (with the exception that I am running stock rooted) it appears that the file it is trying to download is a database, and it is just over 50 meg.
Click to expand...
Click to collapse
Running Hyperdrive 5.0 (before it was removed in 5.5). It works for a few seconds then, I get a black screen, then "Unfortunately, Optical Reader has stopped." .. Funny thing is it is working fine up until this point (the few seconds). Almost (just almost) feels like there is a service running in the background looking for, and killing this task. Grr Verizon.
(Crappy picture attached, could not screenshot the app)
I've got the apk and odex file pulled from an ATT GS4. Not rooted (and still not ready/willing to root. Eventually, maybe), so can't just drop them in sys/apps. Try to install and it acts like it is installing, then tells me application not installed. While I am capable of properly rooting a phone, I'm still a noob in terms of porting an app. Read somewhere on XDA that it probably needs a signed key for my Verizon GS4. So now I'm reading up on android app development and how to do that. Still learning so it will be a while before I make any progress. Anyone more skilled than I am that would like to take a stab at making a distributable APK that works on my Verizon GS4? You would be my hero. I can upload the files I have if so.
Sent from my SCH-I545 using Tapatalk 4 Beta
Do NOT use the odex file. It is probably used in phones that aren't verizon and has flags, so when they mismatch on app vs device it'll FC. Let the device build its own ODEX. Likely needs to be a /system app too. Try getting a build.prop from a T-Mobile user and editing a few lines from Verizon like brand, name, device, board, etc to a T-Mobile one. (installing their build.prop might work as well but idk). You could use a ROM like Synergy to block their "phone home" stuff or something.
I'm just spouting ideas here. They may or may not work.
Sent from my SCH-I545 using xda premium
Scott that makes CleanROM threw this together, flashable zip in recovery. Working for me on Odexed version of cleanrom 1.6.5 Verizon.
http://forum.xda-developers.com/showthread.php?t=2352726
TH3 ST1G said:
Scott that makes CleanROM threw this together, flashable zip in recovery. Working for me on Odexed version of cleanrom 1.6.5 Verizon.
http://forum.xda-developers.com/showthread.php?t=2352726
Click to expand...
Click to collapse
If anyone still wants this, here's the stock NC5 Samsung optical reader apk. I just followed the directions on the main Google code page for baksmali and smali to deodex and run this on custom ROMs. I can attach the deodexed version too if needed.