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 I'm trying to decide which custom ROM to use to get off Google's grid on my smartphone.
I wonder which and how custom Android ROMs are better able to deliver privacy? To better evaluate that, I guess you need to seperate exactly which Google services monitor details on a typical ROM. Also, which of those services, if any, are used in popular custom ROMs like Cyanogen, anything AOSP /K/ MIUI etc. To prevent over-analysis, the bottom line is about finding a custom ROM that uses as few Google services as possible.
Do any of the above custom ROMs use more or fewer Google services? Is there is still a base of Google services which report back to Google regardless of it being custom? Is there any ROM built from the ground up (of Android open source)?
I hope this thread can find like-minded, respectful people and no critics, trolls, *****ness or 'noob' talk.
SharpnShiny said:
Hi I'm trying to decide which custom ROM to use to get off Google's grid on my smartphone.
I wonder which and how custom Android ROMs are better able to deliver privacy? To better evaluate that, I guess you need to seperate exactly which Google services monitor details on a typical ROM. Also, which of those services, if any, are used in popular custom ROMs like Cyanogen, anything AOSP /K/ MIUI etc. To prevent over-analysis, the bottom line is about finding a custom ROM that uses as few Google services as possible.
Do any of the above custom ROMs use more or fewer Google services? Is there is still a base of Google services which report back to Google regardless of it being custom? Is there any ROM built from the ground up (of Android open source)?
I hope this thread can find like-minded, respectful people and no critics, trolls, *****ness or 'noob' talk.
Click to expand...
Click to collapse
I am in exactly the same boat. I'm beginning my search on how to do this with my Nexus 7. That's how I got here. I am a noob and I did watch the "Noob Video". Hilarious! Any info I can find, I will post back here.
Hi..
im so curious about this, what is the difference between:
1. AOSP Webview and Google Webview?
2. What are the advantages of them?
3. Which one is better (or suggest) to using in custom roms nougat?
i noticed, mostly all custom roms preinstalled with AOSP webview (as you can see it in dev. options on "webview implementation".) but once we donloaded google/android system webview in playstore it automatically replaced the AOSP webview with Google one. and theres no option to switch or choose between them.
4. does the Dev's or AOSP webview will always be updated?
(since google webview always does within playstore)
If anyone have ideas about them, a bit of explanations which one should i pick on custom rom, i would be much appreciated, and im sure people would like to know also, thanks a lot!
It honestly depends on the developers to update the WebView implementation themselves. The difference comes in that ROMs ship Chromiums implementation instead of Chromes meaning that we lack the proprietary stuff shipped in Google's standard WebView. You will also notice that Chrome can provide WebView features too. Often Canary is the best route to take on this as it provides the latest implementation of WebView, and in my experience, has been more than stable (WebView at least, the browser isn't excactly a joy)
I've found Google Webview to be more stable than some ROM's builds of AOSP Webview. If you notice apps using that little web browser within apps crashing more often than normal switch it.
I prefer the Android Web Viewer because its less invasive. MHO They may crash more because of google play's aggressiveness as an intrusive APP
Hey,
so i wanted to ask if someone knows mor about when 3rd party apps adapt their icons to material you?
Not even those popular apps like Instagram or Whatsapp etc have adapted to it.
Is it even possible? I never developed android apps so i don't know if its possible, but i'm sure if google can do it other devs can too right?