vB Easy Archive - v3xx and java permissions....

Pages: 1

v3xx and java permissions....
(Click here to view the original thread with full colors/images)

Posted by: mbranscum

Did anyone every come up with any fix other than deleting a file to fix the nagging java permissions on this phone???

Posted by: opdaddy

Yeah, it's called, Use the Search Feature.

Posted by: mbranscum

Quote:

Originally Posted by opdaddy

Yeah, it's called, Use the Search Feature.

If you will look at my post count and the time I've been on the forum, you would realize I probably know how to use the search feature. If you don't know the anyswer to my question, please don't post sensless replies.

If you know of any other way to mod the phone besides deleting the j2me_domain_registry.sm file, which also corrupts certain certified java programs, please share your wealth of knowledge with the rest of us...after all, that is what this forum is all about, sharing information.

Posted by: zephxiii

Quote:

Originally Posted by mbranscum

I've deleted it and manage to get the phone to do everything i need it to. Could you write to cingular and complain about the issue, i know you'll get a stupid response from them. However, our voices must be heard, and maybe if enough of us complain, they will stop this nonsense.

Make sure you tell them you won't be buying any of their java apps/games since they no longer work thanks to their stupidity

The CS lady tried to pawn it off as Motorola's fault.. lol yea right.

BTW the IM client still works after deleting the file.

Posted by: TechnoCat

Quote:

Originally Posted by mbranscum

Did anyone every come up with any fix other than deleting a file to fix the nagging java permissions on this phone???

There are only two possible fixes to the problem. One is to delete the certificates file, the other is to reflash the phone with a less intrusive firmware or perhaps find a SEEMS edit that would disable the checks. That's it for possible solutions on a phone-wide scale. The reason is that while Cingular took some liberties with the Java J2ME implementation rules, they did it consistently (and close to what BREW requires, a good reason to avoid Verizon.)

But you can delete the permissions file and then hack the JAD files of the applications that are otherwise disabled. The only one I wasn't able to get working afterwards was OZMail, but since I prefer the Motorola internal (text but integrated and fast) client, that wasn't an issue for me.

Posted by: mbranscum

OK...found this over in the Moto forum. Replaces pemissions file with an edited file allowing pre-installed programs to work while eliminating the always ask feature. Hope this helps others...

http://www.howardforums.com/showpos...9&postcount=752

Posted by: cingulartx

Quote:

Originally Posted by opdaddy

Yeah, it's called, Use the Search Feature.

http://howardforums.com/showthread.php?t=1181584

Quote:

Originally Posted by opdaddy

Is the cu500v the only phone right now that is capable of videoshare?

Posted by: zephxiii

Quote:

Originally Posted by mbranscum

OK...found this over in the Moto forum. Replaces pemissions file with an edited file allowing pre-installed programs to work while eliminating the always ask feature. Hope this helps others...

http://www.howardforums.com/showpos...9&postcount=752

incredible find man, this should be stickied somewhere!!

Posted by: efparri

Quote:

Originally Posted by zephxiii

Make sure you tell them you won't be buying any of their java apps/games since they no longer work thanks to their stupidity

Most of the Java applications which do not work tell you that they are not signed or authenticated. How is this the fault of the wireless carrier? Maybe Google and others should get their applications signed.

Posted by: zephxiii

Quote:

Originally Posted by efparri

Because the carrier was the one who caused the java nag, wich is in reality unnecessary for it to pop up on every data connection attempt instead of just doing it once on the first time, wich is fine by me.

Why should google and others, have to spend the money for just a couple of handsets when what they offer is free? Why would att even want to have google maps signed, a free kick arse application that defeats their own that they charge for.

Why should ATT be crippling my phone? Hmm, just one of the many reasons why handsets shouldn't be tied to carriers

Posted by: mbranscum

Quote:

Originally Posted by zephxiii

Because the carrier was the one who caused the java nag,

This is exactly right. What's confusing is that ATT doesn't do this one every handset. The Nokia N75, Pearl, Nokia 6126, Samsung A717, Sync and others do no have the ask every time nag.

Posted by: TechnoCat

Quote:

Originally Posted by efparri

The carrier specifies what level of certification authentication is required to allow certain accesses, and against what certificate. If Google Maps or Opera were to self-sign (which is completely legal in the Java spec), this still wouldn't enable them to work properly on a Cingular phone. If they were to sign with a Verisign certificate (even better under the spec), they still wouldn't work as designed on a Cingular phone that checks against the Cingular certificate.

To suppress the warnings via signature, the app must be signed with a "qualifying" certificate, which in this case means precisely the Cingular certificate. But Cingular owns the certificate and charges $800 per signature. And that won't allow the application any rights on a Verizon or T-Mobile phone. So to really bypass this, Google would need to have each carrier sign the application for their phone, and would need to determine which of the many possible resulting distributions (JAR/JAD files) to send to a particular phone.

This is remarkably similar to how Qualcomm's BREW works. Which is, as you may have noticed, a resounding failure.

But the carrier has the option also of not crippling the phone this way. They didn't used to do it. The fault is entirely 100% with Cingular for configuring the phone this way; an unlocked unsubsidized V3xx won't have this problem. Unfortunately, it also won't support cingular's 850MHz frequency, which is a cingular exclusive.

Does this answer your question?

Posted by: xj911

someone should figure out a way to sign these apps for cingular....that would fix problems with the e62 as well...