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.
Related
Anyone with easy access to Linux want to run the latest NC CM 7.1 stable through THIS to see if it works? I think it would be useful to be able to control access to data directly vice random permission blocking. I think it would be VERY useful to be able to not have apps not work because of access that you chose to block which is what this claims to do.
Edit: CM7.1 stable from racks11479 in post 5 - http://forum.xda-developers.com/showpost.php?p=20923834&postcount=5
Edit(s): Latest Mirage from gumnaam.sur usually found near the bottom
tonydl said:
Another nice advantage is that we won't need an IMEI Generator with this app anymore - as PDroid can generate a random/fixed value here
Click to expand...
Click to collapse
Is there a patch available for Nook
Not sure I see the necessary Nook patch for install.
Thomas Droid said:
Not sure I see the necessary Nook patch for install.
Click to expand...
Click to collapse
I think that JJ was asking for someone to run the auto-patcher script to create a Nook-specific patch.
I'm running Pdroid on my Evo and it is a really sweet app. Would love to have it on the Nook as well, but I don't have access to a Linux machine to run the script.
PDroid
Heck yea.. I use it too on my EVO CM7. Incredible how these apps try to get more their fair share of us. Got alot of apps to run on full block.
You requested and I had a minute so here you go. This is patched for the latest stable for CM7.1 for the Nook Color of course.
**As usual the disclaimers of me not being responsible for what happens to your devices is stated! Whatever you do, just don't blame it on me, go ahead and "blame it on the rain" if you want! **
PDroid Patch for Nook Color-CyanogenMod 7.1:
PDroid-v1.27-update-cm-7.1.0-encore-signed.zip
MD5: b0fe3b81d045f2ee291bdd7ed25fd187
Click to expand...
Click to collapse
PDroid Restore Patch for Nook Color-CyanogenMod 7.1:
PDroid-RESTORE-update-cm-7.1.0-encore-signed.zip
MD5: b5d326969a4f2b52717c4bb3c4130d93
Click to expand...
Click to collapse
Enjoy!
-Racks
Great to finally have this.
For what it is worth, I initially installed the pdroid patch on the mirage 7.2 kang, but no dice. pdroid runs, but the battery icon and many settings are scrambled and/or unusable.
Back to cm7 stable it is. Pdroid is that great.
Many thanks to the Dev and the script runner.
Yea I tried too but put my Nook into SOD . I read elsewhere the suggestion to clear dalvik cache?..
I clear davlik with every flash just be sure. I can't say for sure that it would cause SOD just because Orbison so common with 7.1. I had eliminated the problem by upgrading to the Mirage kang with the SOD patch, but rolled back to 7.1 specifically to apply the patch for pdroid.
I am one of those paranoiacs that guards their info super jealously. It is a burden.
With the large number of people rolling up to MiRaGe though, I am hoping to stumble across a patch so I can permanently run that ROM until ICS comes out. I have burned the card for racks cm7.2/9 nightly dual boot, but haven't installed it yet. I will do so, but probably wont stick with it full time until I find a pdroid patch for the 7.2 kang at least.
If any of you kind souls has already made one, please let me know.
My Patch
Here's my patch for the MiRaGe Kang Build CM-7.2-RC0, build date 01-13-2012.
I made the patch on Ubuntu 11.x 32bit.
It works perfectly for me. The only time I get SOD, is when I keep WIFI on all the time, and the nook goes to deep sleep. But that SOD is regardless of whether I have pdroid installed or not. So I am sure pdroid has nothing to do with that SOD.
When WIFI off is set to 'never when charging' then I don't get any SOD.
Hope some of you can find this patch useful. and if so, please click 'THANKS'.
Paranoia is a very healthy thing
I wish I could thank you twice. I have been running tests with Droidwall, Shark for Root and Sharkreader among other apps, and you literally would not believe the amount of data that gets sent from your tablet, no matter how you try limiting permissions. I have found LBE to simply not stop it. Uninstalled two previously trusted apps just this morning after discovering they were sending packets to ad sites. I may share that info, after some more confirmation, but for now I am just glad I can control/block their information through PDroid.
If I have data sent out, I at least want to control its quality. Seriously, I don't have a PC where I am at, so I am relying on the kindness of strangers like you to keep me from chewing the walls.
Update: Atfter I applied tis patch, everything seems to work with Pdroid, but my battery icon reads as if it is charging when it is not plugged in, and has phone data bars instead if any battery indicator when the charger is attached. I had a similar problem when I tried the 7.1 stable patch on the mirage kang in the first place, although far more drastic that time. This is livable as is, although since I applied mirage's theme, i can't just replace the icon, or can I? Anyone know a fix?
Edit 2: changed the battery from icon to percentage in settings. No pictoral representation, but who cares, the info is there. Thanks again for posting that patch!
so this does work for Phiremod 7.1
I can verify it.
Well the 1st link works for it obviously, because it is 7.1 not 7.2
Patch for Mirage Kang build 7.2-RC0 build 0126
Here are the patches for the latest Kang build 7.2.
I installed them directly on top of the kang build, w/o having to reboot in between.
i.e. in CWM , wipe cache/dalvic-cache, then install kang build, then install pdroid patch, then reboot and enjoy.
Hit 'Thanks' if you found these useful.
My man! Every new build its a hard choice to either go without Pdroid or stay with older build. Until i can run thebpatcher through my nook itself, I will be relying on the largesse of the forum members ifbibwant to update. Luckily for me and others like me, XDA consistently takes care of its own.
Thanks again to you and the ones before you. This is shaping up to be a nice companion thread to the ROM thread. I'm going to link to your post in that thread, so more people can find it.
Thanks for your work, gumnaam.sur!
I use your patch with the 01132012 Kang build, no problems so far (I didn't have even the battery icon problem reported by mateorod - though I use the special transparency theme).
patches Kang Build 02012012
Patches for the latest Kang Build (02012012).
Stay paranoid
Thanks a lot for building and sharing these files gumnaam.sur!
Another nice advantage is that we won't need an IMEI Generator with this app anymore - as PDroid can generate a random/fixed value here
I ran this and just can't see the advantage in running it unless I'm really paranoid about the what I do getting into strange hands. I don't do banking or anything other that I'm really concerned about others getting info about. Is there something I should be concerned about?
I am a little paranoid which is why I don't do banking and such from any android device. It even drives me nuts knowing my wife does some banking from her non-rooted droid incredible phone. It just seems to me that overall android is not secure enough to use for anything private. Am I missing something?
Sent from my NookColor running CM7.2 -RC0 MiRaGe -
KANG 02012012 using TapaTalk
I use Pdroid in conjunction with several other apps which gives me a pretty good idea of what is sending data from my phone. Any app I don't think needs to communicate with the internet for functionality, I block with the firewall and use the log to do discovery on any blocked packets. I have caught several apps (market, no less) attempting to send packets to bogus http sites (most likely keystroke captures) and also to group ad sites that presumably disburse to the developers by the visit.
Any app I feel does need internet access, I pair Pdroid with Shark for root and Shark Reader, and use a winnowing process to analyse any suspect traffic.
I have found very few market apps that are involved with much more than unethical ad traffic, which while irritating and scummy, is a little less than dangerous. I just believe in stymying the efforts of unscrupulous developers ad publicizing any results I find. Last week I found that the trending market app Cartoon Wars was using its permissions to register users info with KRNIC, which is the National Internet Registry of south Korea. I, personally, like to know when my info is being sold to foreign intelligence commissions, info related to permissions as varied as network location and imei(good luck on the nook, right?) to incoming phone numbers (HA!)
I use Pdroid to compromise the integrity of the data should anything fall through the cracks. The more unnecessary permissions I find, the more attention I pay. Good developers explain theirir permissions, and avoid asking for unnecessary ones. I should feel comfortable buying cables on amazon, and Pdroid helps me get there.
Wow! You've definitely got security. I'm just not as worried I guess, but I'm glad there are people like you that are keeping an eye out. I just can't see using so much time spying on the spies.
You have convinced me into looking into this further though. So thank you.
Sent from my NookColor running CM7.2 -RC0 MiRaGe -
KANG 02012012 using TapaTalk
Yeah, I I have trust issues.
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!
I'm working on a JellyBean port of Cornerstone. It is currently building with CM10, but does not work very well at all. I'm not sure if this has to do with the resolution of my tablet, 1900x1200 TF700T, which I tried to account for, but may have screwed up. I could use some help on this, as I have very little time and not much experience with building Android from source. Specifically, any advice on toolchains/testing code without needing to do an entire build would be appreciated. What would be more appreciated is if I could get some help with the project itself to get it to a stable place, and perhaps to include a path for continuous updates with as new releases come out.
https://github.com/emil10001/cornerstone
My current build environment is an Ubuntu VM, just using the commandline. I write the code and try a build. It usually fails and I go in and fix the errors that it gives me. This process means that I spend about 1-10 minutes coding and 2 hours waiting for it to build and fail. At present, it's actually building just fine, but it isn't working very well.
I really like the idea of Cornerstone and would like to see it working on newer builds. I am also reaching out to the Cornerstone Google Group, but they have been fairly silent for months. https://groups.google.com/forum/?fromgroups=#!topic/cornerstone-dev/Gz345pbd-co
Thanks,
John
I did talk with them a while back and the did say they're working on updating the codebase to support jellybean.
I had a quick glance at your fork.
This way its really hard to test, you could better just fork frameworks/base from android and then modify the files instead of the copying the changed files.
That would make it easier to test, view what changed, etc.
You could also use gerrit.
mmm path/to/it will do a quick rebuild.
I've had the apps up on github.com/sgt7 but they haven't been updated since way too long, will update them when I find some time.
Sent from my GT-P1000
...
Thanks for the tips!
The reason that I am keeping them separate is mainly for sanity, I wanted to try to keep the cornerstone stuff outside the main android code so that I can keep the android codebase relatively up-to-date, and also very obvious about what's a part of cornerstone for anyone that wants to grab the source from me. I'm also wondering if it's possible to pull part of this, say frameworks/base, into Eclipse (without it taking a day and a half to build the workspace).
Also, with gerrit, I wanted to keep this separate from the CyanogenMod stuff, mainly due to the comments that Dianne Hackborn made on G+ to Steve Kondik. I have a feeling that that's what killed the project.
I'd also really like to see how this works on a 1200x800 device, since that's what Cornerstone was originally designed for. I'm thinking that I screwed up the data in the xml resources, and that that's a big reason as to why it looks so funky on my device.
emil10001 said:
Thanks for the tips!
The reason that I am keeping them separate is mainly for sanity, I wanted to try to keep the cornerstone stuff outside the main android code so that I can keep the android codebase relatively up-to-date, and also very obvious about what's a part of cornerstone for anyone that wants to grab the source from me. I'm also wondering if it's possible to pull part of this, say frameworks/base, into Eclipse (without it taking a day and a half to build the workspace).
Also, with gerrit, I wanted to keep this separate from the CyanogenMod stuff, mainly due to the comments that Dianne Hackborn made on G+ to Steve Kondik. I have a feeling that that's what killed the project.
I'd also really like to see how this works on a 1200x800 device, since that's what Cornerstone was originally designed for. I'm thinking that I screwed up the data in the xml resources, and that that's a big reason as to why it looks so funky on my device.
Click to expand...
Click to collapse
Just checkout a new branch with the modified code, that's what version control is for.
Also, i believe it should be fine now if there is some sort of a whitelist implementation, and only few apps are supported by it. (*le Samsung Mutli Window)
cdesai said:
Just checkout a new branch with the modified code, that's what version control is for.
Also, i believe it should be fine now if there is some sort of a whitelist implementation, and only few apps are supported by it. (*le Samsung Mutli Window)
Click to expand...
Click to collapse
What happens when you try to use an unsupported app anyway? I have Note 2 with the multiview hack and every app I've tried with it has worked, though I've never tried anything like say Angrybirds, just google voice and Trillian and stuff like that.
Is this still something that you are trying to work on? GOD I would love cornerstone on my tf700!!!
Need some help testing/coding ect? I would love to help, not an advanced dev but working on my android chops daily.
I am available to help with testing.
Am a rom developer.
Is this source meant to be compiled for devices other than non AOSP because I got device files and everything and so far its going well.
Droid RAZR XT912
Sent from my XT912 using xda app-developers app
Nvm. I need some file called init
Sent from my XT912 using xda app-developers app
From 11/19:
CM 10.1 Status Update
So we continue to work through the merger of 4.2 code and our CM enhancements. A branch in our github repos called mr1-staging has been created to facilitate the merger and is the target for core CM items (not features).
mr1-staging is not meant to be compile-able, its only purpose is to be a staging grounds for our core work. Chances are, it is useless for independent builders.
CM 10.0 (4.1.2) code is in jellybean-stable, if you are working on a bug-fix for the last stable release, patches should be submitted against that branch. If/when we do another 4.1.2 release (ie CM 10.0.x), it will originate from code in this branch.
Once staging is done in mr1-staging, we will push all that code to a 'CM10.1' branch, and eventually back to our primary 'jellybean' branch. This process is in place to make sure that we effectively move forward from CM 10.0 code, instead of starting over as was seen with the jump from Gingerbread to ICS. Patches from gerrit will be accepted towards CM 10.1, but for now, please have patience while we work through mr1-staging.
While the 4.2 updates are on a smaller scale, they do present some changes that will need to be considered and will effect our implementation of features. Just to name them briefly: Telephony Split, Multi-User, Quick Settings, and Lock-Screen Widgets. These items will be a strong focus when the initial CM10.1 branch is created.
On the feature front, David van Tonder (dvtonder) decided to make his weekend productive, and has already worked on the code for the majority of our MMS enhancements: Emoji support, sms split, gestures and templates, quick messaging. Notably MMS auto retrieve is not being forward ported as Google fixed that themselves. As stated above, patches will hit gerrit review after this staging process is completed.
As always, a timeline isn't and won't be available. We will continue to provide updates as we have them.
Click to expand...
Click to collapse
and 11/21:
Cry havoc and let slip the...
...developers of CM. Hmm, not quite the same oomph to it. Back on topic...
mr1-staging as it's manifested in github right now, is good to build. Theme Engine support is not yet enabled, so if you attempt to build, remove vendor/tmobile. Everything else is in working shape with regards to AOSP devices, so if any of you are waiting for a working tree to move on to har
dware support, you can start now.
A bunch of our repositories have already been merged into mr1. The usual CM externals are in place, the CM build scriptage is also in and working. Features are not incorporated wholesale, and will be applied as conflicts with 4.2 changes are resolved.
Those watching at home, you should be able to break out a Mako (unofficial) build at this time. Our frequent contributors have been given the green light to send patches for review as features are rebased, recoded, and uploaded.
*Nightlies will not be available immediately, as even though CM may be build-able we consider it incomplete at its current stage. When we are happy with the product, the flood gates will open.*
Happy Dev'ing and say thanks to your patient lady/man for putting up with you
Click to expand...
Click to collapse
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