Most of the AOKP Roms for this device are "Excellent" but all lack one simple feature.....you can't use Dialpad function codes ( like; **87284 for Diag Mode ). As advanced as these Roms are why is it so difficult to add to the Roms? Someone please shed some light on this subject or even a "FIX" would be better. I am definitely no expert at any of this but surely compared to building a Rom, incorporating those functions shouldn't be that big of a deal. Correct me if I'm wrong....
If there is a 4.0+ AOKP Rom for this device that the Dialpad Functions work on PLEASE let me know...Thanks!!
devo3d said:
Most of the AOKP Roms for this device are "Excellent" but all lack one simple feature.....you can't use Dialpad function codes ( like; **87284 for Diag Mode ). As advanced as these Roms are why is it so difficult to add to the Roms? Someone please shed some light on this subject or even a "FIX" would be better. I am definitely no expert at any of this but surely compared to building a Rom, incorporating those functions shouldn't be that big of a deal. Correct me if I'm wrong....
If there is a 4.0+ AOKP Rom for this device that the Dialpad Functions work on PLEASE let me know...Thanks!!
Click to expand...
Click to collapse
in an excerpt from djp952 GeeWiz he explains it best... LINK
http://forum.xda-developers.com/showthread.php?p=40639862
He Says::
the reason those codes don't work is because they are not part of AOSP. GeeWiz 2.9 is Samsung TouchWiz, GeeWiz 4 is AOSP, so those codes do not exist. 772 is to set the serial mode for CDMA diagnostics, right? My kernel doesn't support that either, it was removed when I updated the USB drivers to get rid of all the Samsung proprietary stuff like the CD-ROM mode. It could probably be re-added, but I think most people that would want to do things like this would be better off with a different more feature-rich ROM anyway. The other code seems to be for other CDMA related activities, my knowledge of telephony is limited and I won't be adding support for either of these codes. Sorry. It kinda is what it is. If you want to access everything that Samsung designed into the phone, I think your only real option is stock, GeeWiz 2.9, or other older Gingerbread ROMs based on Samsung's code base.
.
hhp_211 said:
in an excerpt from djp952 GeeWiz he explains it best... LINK
http://forum.xda-developers.com/showthread.php?p=40639862
He Says::
the reason those codes don't work is because they are not part of AOSP. GeeWiz 2.9 is Samsung TouchWiz, GeeWiz 4 is AOSP, so those codes do not exist. 772 is to set the serial mode for CDMA diagnostics, right? My kernel doesn't support that either, it was removed when I updated the USB drivers to get rid of all the Samsung proprietary stuff like the CD-ROM mode. It could probably be re-added, but I think most people that would want to do things like this would be better off with a different more feature-rich ROM anyway. The other code seems to be for other CDMA related activities, my knowledge of telephony is limited and I won't be adding support for either of these codes. Sorry. It kinda is what it is. If you want to access everything that Samsung designed into the phone, I think your only real option is stock, GeeWiz 2.9, or other older Gingerbread ROMs based on Samsung's code base.
.
Click to expand...
Click to collapse
Wow, really :silly::silly:
Related
I have been looking for a good CM 7.1 based ROM and am having a hard time deciding on one. The main thing I am looking for is the advanced lock screen delay and timeout settings. I cannot tell if this is a difference between CM 7.1 and 7.0.3 or if it is just a setting that some ROMs have and some do not.
Can someone shed some light on this for me? Is there a way to add this functionality? (I care because work enforced a security lock on my phone for email access, but I don't want to have to type i tin EVERY time the screen goes off. iPhones and WinMobile don't. It seems to be a flaw in Android's ActiveSync).
Thanks in advance.
This feature is new in CM 7.1. However, other users have reported success using Delayed Lock + WidgetLocker apps from the market to effect the same functionality, though I am uncertain how well they play with the Exchange server's demands.
Alternately, if you really don't want this security lock feature at all then you can find versions of Email.apk that will just lie to the Exchange server about the phone's configuration. Then you can configure your lock settings however you like. Ah, the classic fallacy of a security model that trusts the client...
I actually like the security of the password. I just wish it behaved like ActiveSyns on every other type of device (Win Mobile, iphone, etc) and let you set a delay (defined by the system administrator) for when the device security locks, not every time the screen goes off.
I wish we had a good CM7.1 ROM. Oh Z, wherefore art thou?
Yeah, running a nightly (or a ROM that pulls from nightly) is currently the only practicable choice to get the feature.
I backported the feature's code to the CM 7.0.3 codebase and built a custom ROM for my own device. I wanted the feature but didn't want to run the unstable nightly on my primary phone. Well, "backport" isn't the correct term, because the feature was developed against 7.0.3 and was rebased to 7.1 for submission to the source repo. But you know what I mean (haha).
organophosphate said:
Yeah, running a nightly (or a ROM that pulls from nightly) is currently the only practicable choice to get the feature.
I backported the feature's code to the CM 7.0.3 codebase and built a custom ROM for my own device. I wanted the feature but didn't want to run the unstable nightly on my primary phone. Well, "backport" isn't the correct term, because the feature was developed against 7.0.3 and was rebased to 7.1 for submission to the source repo. But you know what I mean (haha).
Click to expand...
Click to collapse
Care to share?
rearview said:
Care to share?
Click to expand...
Click to collapse
You know, I realized after posting that I probably look like a jerk for not offering. I apologize. There are issues that seem to preclude this, however.
The target of the relatively minor code changes necessarily included one of the fundamental framework jars.
When I was developing the feature, I only compiled CM for the Droid Incredible. Didn't make sense to compile for platforms I can't use/test, especially given the next point.
It takes my machine 90+ minutes to compile a ROM for a platform.
I believe that if I gave you a flashable update.zip to replace the affected jars it would have a high probability of cacking your ROM and would result in bootloops. Not absolutely certain, but fairly concerned about the possibility. I believe you would have better luck running a nightly that people report as "relatively stable" in the forums (some nightlies are better than others).
When the feature was merged, I really thought CM 7.1 would be out soon. RC1 dropped a month *before* the new feature was merged. That sounds odd in retrospect, because most projects freeze feature additions before entering the RC phase of a release (ie. they accept bugfixes only).
I just assumed it was for an X10 since we were in the X10 forums. Since this phone isn't officially CM supported I'm at the mercy of ROM developers to make a nice CM7.1. There are a couple out there, and they all have issues. One is close, but the dev seems to have gone missing. I hope he returns soon.
Is modifying one jar file all that it would take? Which file? If I knew that I could possibly take the jar file from one of the CM7.1 ROMs for my device (which has issues) and put it into a 7.0.3 that works smoothly and be happy.
rearview said:
Is modifying one jar file all that it would take? Which file? If I knew that I could possibly take the jar file from one of the CM7.1 ROMs for my device (which has issues) and put it into a 7.0.3 that works smoothly and be happy.
Click to expand...
Click to collapse
I like your train of thought. Unfortunately, even if that were to work you would be unable to configure the feature, because the UI is in the CM Settings apk (ie. the apk that makes "CyanogenMod Settings" menu option appear in your Android settings). If you were to also grab the CM 7.1 settings APK and install it, then that would replace the old version. The CM 7.1 version has all sorts of changes, controls for other new features, and so forth; therefore, that would break much of your other functionality.
How conversant are you in software development? You may be able to join one of those CM 7-derived ROM projects for your platform. It should be relatively easy for someone with a CM dev environment configured for your platform to grab these patches via git cherry-pick and build a 7.0.3 "Gold Edition" with this feature added. Because it should be easy, you might be able to persuade one of those custom ROM developers to grab this feature and include it.
If you are interested, here are the links to my patchsets that were merged to implement the feature:
Framework Implementation
CM Settings UI
I believe the patches will merge "nearly cleanly" into a CM 7.0.3 derived branch. That is to say, if there are merge conflicts they will not be substantive and will merely involve wholesale cut/paste reordering of methods within the given class files rather than requiring a rewrite of any part of the actual implementation.
I know that this simple reordering is all I changed between my 7.0.3 development version and the 7.1-derived submission. Seems Steve Kondik did a little further rearrangement to accommodate other patches that had been accepted/merged while mine was pending. Same deal there: still should be relatively simple.
I'm not much of a developer, though I'm an IT guy with some unix background. I'll look at it.
Hi there, I always liked aosp/aokp builds, but I never kept them.
I run on samsung based roms.
so there is the question:
customization over features?
only in samsung rom we have the best FM radio, camera, MHL and others
which cannot run on aosp.
can't we mix the frameworks to have the best of 2 worlds?
can we hack samsung apps to run on aosp?
There is no way to get these features working on AOSP/AOKP. But if you use a ROM that is based on Sammys software, you will get these features, plus some tweaks and modifications that give it more speed/better battery/more customisation etc.
firstly, there is a mixed-framework rom afterall. :good:
second:
WHO copies OUR posts and re publishes them with different names in other sites?
http://samsunggalaxyandroid.net/2012/05/samsung-vs-aosp/
Hi there! I was curious as to the ROM developer workflow. I'm somewhat familiar with building AOSP for x86 VMs and have done some skinning and manipulating system apk's ... but I have some other questions:
1. What distinguishes a ROM package from other zip installers, I guess since it is *nix, everything's a file and most ZIPs then just have the files changed?
2. Jokersax makes mention of doing all development on the device itself... What this workflow, just doing a lot of nandroid backups then, or just replacing things on the fly and hoping for the best?
3. What options exist for adapting system level native code, perhaps I guess I'm asking if, for instance, the camera works with Blur stock SBFs, how could one go disassembling the functionality and deriving CM9 compatible packages? Are the drivers that tightly coupled with the UI elements? That would seem impossible to maintain, and say what you want about Motorola, I couldn't imagine this to be the case.
Thanks -ap
Sent from my MB855 using xda app-developers app
antipasto said:
Hi there! I was curious as to the ROM developer workflow. I'm somewhat familiar with building AOSP for x86 VMs and have done some skinning and manipulating system apk's ... but I have some other questions:
1. What distinguishes a ROM package from other zip installers, I guess since it is *nix, everything's a file and most ZIPs then just have the files changed?
2. Jokersax makes mention of doing all development on the device itself... What this workflow, just doing a lot of nandroid backups then, or just replacing things on the fly and hoping for the best?
3. What options exist for adapting system level native code, perhaps I guess I'm asking if, for instance, the camera works with Blur stock SBFs, how could one go disassembling the functionality and deriving CM9 compatible packages? Are the drivers that tightly coupled with the UI elements? That would seem impossible to maintain, and say what you want about Motorola, I couldn't imagine this to be the case.
Thanks -ap
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
1) You are pretty much correct....and rom can be turned into a simple one file zip or vice versa
2) He actually uses the device along with a build machine. You can do some simple stuff on the device itself, but if you're going to get into decompiling jars or apks, you will need a bot or a PC.
3) Apktool (Linux/Windows) or Android Suite (Windows) will allow you to break down the apks like you are describing. I'm sure you can make a blur apk work with CM9 (obviously app developers on the Play market do manage to make both). I'm not very familiar with Blur/CM7, as I started work on ROMs after ICS had hit, and I really didn't see much real desire to do something that wasn't forward from where my phone was.
Mainly, you can do source work, which you are most likely familiar with the process of.
I do "port" work...taking the framework, apps and some other necessary functionality-related parts and making a new rom for my device with it.
If you are interested in the process, by all means get in touch with me via PM. We are in need of some people to help with a void that has been left by our team member Spleef taking on a second job.
Thank you so much for the extensive reply. I have about a kabillion personal projects, it would be perhaps interesting to ruminate some on the metadevelopment as it were, I do notice that the Cyanogen project seems to have a lot more ability to automate their workflows, it would be cool to try and get more people into those kinds of logistics to help out... Anyway, I'm trying to remain productive, I'm a long time lurker, and I can't bring myself to post unnecessarily to even get to the 10 posts I need to provide feedback in the development forums, but I'll try
I've been really inspired with the Clojure / Java community, especially "Leiningen" and things like Jenkins for continuous integration. Could be cool to try and think at this level, perhaps like a chrooted VM or something that enthusiasts could run to assist in build CPU times, or hell I dunno, this kind of thinking is all pie in the sky and is hell to set up possibly for little gain, although I'm encouraged that Bittorrent is being used a little more here and there perhaps to offload some of the hosting costs. FWIW I have used S3 in my own projects, and for various static sites I have, I've been hard pressed to pass 30 cents a month in hosting costs on S3, but this is all low traffic stuff and there's a lot of options out there with various kinds of advantages and disadvantages.
All in all, thank you all for your continued efforts, especially going into the later part of this year when JB will mature, and the possibility of ICS drivers being integrated. You guys rock!
Download Link:
http://goo.im/devs/agrabren/cm10/shooter/cm-10-DisarmedToaster-0.1-shooter.zip
GAPPS:http://goo.im/gapps/gapps-jb-20120726-signed.zip
TERMS AND CONDITIONS
0. Definitions.
“This License” refers to version 2 of the GNU General Public License.
“Copyright” also means copyright-like laws that apply to other kinds of works, such as semiconductor masks.
“The Program” refers to any copyrightable work licensed under this License. Each licensee is addressed as “you”. “Licensees” and “recipients” may be individuals or organizations.
To “modify” a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a “modified version” of the earlier work or a work “based on” the earlier work.
A “covered work” means either the unmodified Program or a work based on the Program.
To “propagate” a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well.
To “convey” a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.
An interactive user interface displays “Appropriate Legal Notices” to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion.
1. Source Code.
The “source code” for a work means the preferred form of the work for making modifications to it. “Object code” means any non-source form of a work.
A “Standard Interface” means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language.
The “System Libraries” of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A “Major Component”, in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.
The “Corresponding Source” for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work.
The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source.
The Corresponding Source for a work in source code form is that same work.
Toolchain: GCC ARM version 4.4.3
Kernel Source: https://github.com/agrabren/android_kernel_htc_shooter
This is a Discussion thread for the rom and is only to be used for that purpose.
This ROM Thread is posted with Permission of Agrabren
WORKING:
SOUND
WI-FI
CALLING
DATA
You Tell Me!
Note I AM NOT the creator of this rom. IT IS AGRABREN
He gave me permission to post a discussion thread
I will keep this open until he feels like the build is alpha quality
I will then close this thread
I'm posting a thread as he has not.
Also If you phone explodes or you create a black hole I Take NO RESPONSIBILITY
I'm fine with the thread, at least until the ROM is stable enough to meet my standards to be posted as an alpha. People in the CM9 thread wanted to see it, since I had posted a build for the GSM phones (to test if I had the basic infrastructure working) and they were thrilled. So I posted for CDMA after the last builds came out.
Now everyone, settle down. You're all more than welcome to use this thread to discuss what works, doesn't work, and how to help each other make the most out of it.
This forum is supposed to be about helping each other. Is the ROM in development? Yes. Does it work up to my requirements for alpha quality? No. Why? Because the microphone doesn't work right. If that were fixed, I'd likely switch to developing for CM10 instead of CM9, because the camera won't kill me to get working and everything else is trivial between the two for me to not lose any time or features.
Thread moved to GENERAL - it will stay here as a discussion thread.
Edited OP and thread title to reflect that, also left a couple posts from agrabren so people know he's ok with this thread.
Any and all flames or name calling will get you an immediate infraction and likely a ban if you cross the line too much.
Keep XDA what it shold be, open and a place to learn.
Have a nice day.
im still confused why the dictionary exists in the OP? - why not just link to where that was copied and pasted from? its pretty distracting from the actual OP
Xda is the best...
Sent from my GT-XPERIA S using xda app-developers app
Can't wait to install this once I get home.
Thank you il Duce! I'm excited to see CM10 on the Shooter, and can't wait to see how far Agrabren and others take this rom!!
minieod said:
im still confused why the dictionary exists in the OP? - why not just link to where that was copied and pasted from? its pretty distracting from the actual OP
Click to expand...
Click to collapse
It's the op decision to put what they want there. You'll live.
jasonvanfebr said:
Xda is the best...
Sent from my GT-XPERIA S using xda app-developers app
Click to expand...
Click to collapse
I agree.
I've been running this for a little over 12 hours now. It's very nice and makes me very excited to see where we can see Jellybean in the future.
Not Working:
4G will not enable
3D
Camera
Google Now/Search FCs
Headphones are not detected - sound continues to play through external speaker
Potential battery drain - BetterBatteryStats shows phone as awake 100% of the time, though I had an app running that may have been the cause of it
Watching Youtube can cause a reboot after 20-30 seconds
I also was unable to boot with the stock kernel, and if I had the newer ICS firmware it refused to boot at all with any combination I tried.
It's incredibly fast though, you can definitely feel the Butter in play. I'm very impressed with the ROM and will continue to run it until I go back to the USA, at the very least.
Hi.
I've been out for a bit, glad to see much hasn't changed (sarcasm).
One troll has already been banned from the mess that had to be deleted. Please behave yourselves, I really don't like spending my free time deleting drivel and banning people. The op has permission to post this, it's compliant, just discuss away. Don't be rude to each other.
Thanks and have a pleasant evening
Can't Wait
wwjoshdew said:
Thank you il Duce! I'm excited to see CM10 on the Shooter, and can't wait to see how far Agrabren and others take this rom!!
Click to expand...
Click to collapse
I feel the same way.
I would feel better when an official RUU is available then I would start ROM'ing all crazy lol.
FusionNeo said:
I've been running this for a little over 12 hours now. It's very nice and makes me very excited to see where we can see Jellybean in the future.
Bugs:
4G will not enable
3D
Camera
Google Now/Search FCs
Headphones are not detected - sound continues to play through external speaker
Potential battery drain - BetterBatteryStats shows phone as awake 100% of the time, though I had an app running that may have been the cause of it
I also was unable to boot with the stock kernel, and if I had the newer ICS firmware it refused to boot at all with any combination I tried.
It's incredibly fast though, you can definitely feel the Butter in play. I'm very impressed with the ROM and will continue to run it until I go back to the USA, at the very least.
Click to expand...
Click to collapse
4g is not integrated into this build , neither is camera , neither is 3d , neither is voice search - that is why those are bugs
Love the idea here, just dropped in to see only shooter, not shooteru.
Perhaps a CDMA thread title, or people posting whether they are gsm or cdma.
We all want to ditch sense after all.
scariola said:
Love the idea here, just dropped in to see only shooter, not shooteru.
Perhaps a CDMA thread title, or people posting whether they are gsm or cdma.
We all want to ditch sense after all.
Click to expand...
Click to collapse
you can get a fully functioning cm9 rom (no sense) for gsm in the gsm developers section
minieod said:
4g is not integrated into this build , neither is camera , neither is 3d , neither is voice search - that is why those are bugs
Click to expand...
Click to collapse
Oh I know, I wasn't expecting them to work. I just wanted people to be aware of what isn't working, even if it's things people shouldn't expect to work.
FusionNeo said:
Oh I know, I wasn't expecting them to work. I just wanted people to be aware of what isn't working, even if it's things people shouldn't expect to work.
Click to expand...
Click to collapse
:good: - OP should be updated reflecting a "not working" feature set
Found another bug - attempting to watch Youtube for more than 30 seconds or so causes a reboot. Will update my post to reflect this (in 5 minutes, due to my lack of user permissions). I agree that these bugs should be listed in the OP, to make them easier for people to find as well as remove all the posts like "DOES FOUR GEEZ WORK" from people who only choose to read the OP.
minieod said:
you can get a fully functioning cm9 rom (no sense) for gsm in the gsm developers section
Click to expand...
Click to collapse
yes, a cm9 and cm10 Rom if you know where, the thread hasn't been created for 10 yet.
Was just hoping someone could find out why audio goes out after phone connects call through SIP(Internet calling) ?
Problem with all cm9+ roms, by 3 different gsm devs.
Titanium backup won't restore Facebook.
It's not critical, but it is a problem I've been having. Unchecking Facebook fixes it.
It hung on something else too - had to force close TB a couple times, but I got most of my stuff back.
Over all, very fast, and the phone (the old neglected bit some people actually use to talk with other people verbally, rather than via txt) works well.
I've also had issues downloading paid apps from the market - and TB warned me that my device ID had changed. It offered to change it back, which also crashed TB.
After restoring accounts from TB (and possibly the device ID as well - not sure if that completed or not), the market issues have gone away.
Hi!
Some guys and me are working on Android now for long time. Most times we had clear different parts we where working on, so two guys working on kernels, one on adaption of Android, one was testing and keeping contact to the community.
Now, cloning a kernel and merging some changes on drivers is a simple thing. And even changing a file on android, putting it into a git or simply on an ftp is easy too...
Well, now things have changed. Android is getting more complex and kernel work is mostly done.So we do more and more work in Android with more and more people.
Ok, one would say, take a plain android by using repo sync. Add your vendor parts for kernel and android and add them as a separate git. Ready you are...
Unfortunately that may work if you build your own device, based on plain naked android and a well supported mainlined kernel... But reality is different and chinese reality is even different^2. Hacking andoid devices where you do not have access to the OEM gits, kernels, not even datasheets or schematics is a hell of work... and all of these OEMs just checked out the complete android, put it in their own git and modified 1000 parts 'n pieces of it.
This isn't only a problem of bandwidth to upload such a monster, but all your friends supporting you have to clone that monster again. And after a while a new android version comes and you have great mess:
You cannot find differences from your old version to the new google version as many files have been changed by the OEM.
But you cant just "repo upload" cause google or CM might not be very eager to get dumb chinese deep down below android changes in their repos.
How do you team up with others and sync your android changes? Is there a good tutorial that handles not only the way it should be, but covers all these real-life issues?
I'd really appreciate your tips
Astralix