Develop Bugs

Bug tracker website? Would that help? (I'm offering)

Ok. Short story of what I want to do and why.
I am a developer and I feel that I don't contribute enough to this fantastic site and its users. After the recent unpleasantness I went away and thought about what it is that I could do to try and fix this. My idea is a site or section of the wiki built specifically to track bugs and issues in new roms (I was specifically thinking WMXL but there is no reason this can't be used for all of them).
I am currently working on my own XML based site with PHP5 driving and if people think it will be useful I'd write and host this service before I continued with my own site (hopefully before WMXL 0.30 is released).
I want to try and restrict the way people enter and search the information relating to problems with new roms and try to cut out the background noise. I was thinking about having fields such as ROM version (drop down list), radio version (text box), boot loader (drop down list), main program affected (text box), extent of interference (drop down list), description of problem (text area), how to reproduce error (mandatory text area!).
This will hopefully encourage more people to think about what might be causing the problem rather than just posting what they cant do and expecting someone else to work everything out. Forcing a description of how to recreate the problem will hopefully find most users not needing to post after they work it out, and if the recreation steps dont work then the post will be closed. Hopefully people will think enough that I will be able to moderate this forum (type thing) myself and maybe someone in another timezone (closer to the UK) can take care of it while im asleep.
No one can stop n00bs posting silly questions but hopefully we can reduce the amount this annoys everyone else.
Sorry it took so long to describe my idea.
Maz
UPDATE: STARTED!
I got started as soon as I'd got a couple of replies but I still need you all.
For the chef's and other brilliant people:
1. What info do you need with each ticket to try solve them?
2. Do you want to be the only one to close tickets? Or should the submitter be able to?
3. What info do you want to store for the roms to filter to the smallest pool of specific tickets?
For the users:
1. How do you want to be able to search this?
I DON'T ASK FOR DONATIONS! ALL I ASK IS THAT PEOPLE SEARCH BEFORE SUBMITTING!
---------------
http://maz.net.au/

Bugzilla? yes please

This is a very good idea. In fact, I think that we need too a place to store the temporary fixes generated after each ROM publishing. It will be a good place for this too.

Good Idea.
It Would Help A Lot, Sounds Like Finding Answers Would Be Easier And Should Cut Down On The Hostile Atmosphere.
Cheers

Yes, very good idea.
This become easyest forum for everyone.

If it would be of any use, i can host this on one of our UK servers so we get very good speeds? I know 'iammaz' has said he can host it but he is in Australia so for the UK guys it might be a tad slow.
If not then no worries, but just trying to do my bit!

jaso2005 said:
If it would be of any use, i can host this on one of our UK servers so we get very good speeds? I know 'iammaz' has said he can host it but he is in Australia so for the UK guys it might be a tad slow.
If not then no worries, but just trying to do my bit!
Click to expand...
Click to collapse
Cheers and I'm sure everyone appreciates the offer. My site is hosted in the US. At the moment this is being built as a module to my current CMS. Whether or not this adds too much overhead I won't know until I try. The problem will be if I use too much cpu time im sure it's against the ToS with my hosting company and they will shut me down.
I hope that I will have it built as a stand alone object by then and anyone else can take this and run this on php5 hosting or in fact I could run it as web services from my personal server at home.
Progress goes well. Just working on possible searching and indexing algorithms to make searching fast and useful.
Maz
-------------------
I can't believe I forget to type this.
http://maz.net.au/

Great idea

It's 2am. I'm piking for the night. I'm expecting a phone call at 7am tomorrow so will be back into it then for 5 or 6 hours. Hopefully will be almost done by the end of that.
I need to work out how you want to have logins work. I don't think i can make it authenticate against this forum (i havent tried integrating with vBulletin before). Do I allow open registration? do I try make it force you to register the same name but PM'ing the password to that username here? do i manually add people as they ask and restrict the group?
let me know in the next 6 hours or so.
Maz
----------------------
Badly styled CMS can be seen here. (new version looks so much better )
http://maz.net.au/

Open registration, but obviously grant privileges to those of us who classify as developers.

Olipro said:
Open registration, but obviously grant privileges to those of us who classify as developers.
Click to expand...
Click to collapse
And super-user privileges for the chef's for bug tickets that apply to their cooked roms.
Maz
----------------
hard at work again at http://maz.net.au/

are permsissions too obtuse for the average user?

i think guy brings up a good point and perhaps a decent solution. why not allow/encourage the dev's to explain a bit more. I'm a fairly adept nerd but when i'm installing an app sometimes i'm just not sure why in the world this app needs that permission...how is my mom or sister or anyone that i advocate Android to going to figure it out? why does this app need my coarse or fine location or full network access or access to the contact list etc...
and please do not say 'if you don't like what's listed, don't install the app'. that is exactly the point of this thread. the line items in the Review Permissions window don't always make sense. how can the average end user make a educated guess with the current system...they don't, they just start doing the same thing they do on their Windows Desktops...just click right on thru it. then what happens? some jerk writes a piece of malware. user has an issue. now its all androids fault. and viola, proof that linux based devices are still too geeky for avg use.
http://tech.shantanugoel.com/2010/08/14/android-permissions-malware.html

Unfortunately, there's no denying the cold, hard facts - ignorance is not bliss. Everything has a learning curve. Time and effort must be spent to educate users as to why <this> is happening and what it is doing for them. It's sad but true. Besides, if everything that required higher learning could be easily figured out I'm sure humanity would be freed from the shackles of poverty, war and hunger by now. So, yes, permissions are too obtuse for the average user. Unless they want to educate themselves on more generalized computing skills they'll never get it.
That's just my two cents. Sorry I couldn't be of better assistance

ok. so i wish to educate myself. please provide a full and detailed example listing why which permissions may be needed/used so that i will be able to make an educated choice. where is that link again?
i'm bringing up an issue...not asking for others to chime in and tell me how stoopid the end user base is. i'm an admin for over 10yrs. trust me ... i know. in this case i am also confused as are a large numer of folks. i understand the huge development curve android has experienced over the last 18mths. my concern is that if this issue is not addressed, even the folks that would take the time to read the Review Permissions page will give up. i know i have on more than one occasion. that's a bad trend.

Wow. You bring up a good point. Didn't mean to offend you or anything. I still don't have a good answer for you but I will let you know that I only install apps that I can trust usually after researching them via Google searches and talking about them with people here. I too am an admin (been a long, long 15 years now) and if there's 2 things I learned about recommending custom Android setups they are:
- If you think the user is going to use you as Wikipedia it's probably best to leave them at stock
and
- Only recommend this kind of stuff to users who are willing to accept responsibility for their actions otherwise you'll be the fall guy every time something goes wrong.
Again, I'm sure you know this and I didn't mean to offend you so..... bye.

Users can be pretty obtuse, and I think you're completely correct about the current permission system. However, I don't think it could be made much clearer without multiplying the number of permissions. Malware can exist because users consider certain permissions to be common. Conversely, apps with a good reputation can include permissions that make them wonder, "why would they need that?" Look at keyboards and how many people freak out when they go to enable them.
One thing that would be nice for users is if you could tap on a permission and the phone would display a short explanation of that permission. They probably aren't self explanatory for everyone.

beatblaster said:
- If you think the user is going to use you as Wikipedia it's probably best to leave them at stock
and
- Only recommend this kind of stuff to users who are willing to accept responsibility for their actions otherwise you'll be the fall guy every time something goes wrong.
Again, I'm sure you know this and I didn't mean to offend you so..... bye.
Click to expand...
Click to collapse
no offense. i do understand. there was a point in time where i used to openly provide paid tech support to home systems of my coworkers....it was a short point in time. lol. but i digress ... i may have come off too strong in my reply, i was just trying to prevent the thread from wandering off.
I've tried to post on this topic in the past but have not nothing useful. in and of itself, i find that kinda sad. I've even seen some folks suggest that people "take a trusting stance because most developers do not intend harm". i wish i could. but i'm out of college.
it would be wonderful if someone (ie: a google dev or just someone with knowledge of these things) were able to create a page that could give real world examples and general rules of thumb. currently i have only found a couple pages that cover a couple settings. not nearly enough to be of much use.

Saturn2K said:
One thing that would be nice for users is if you could tap on a permission and the phone would display a short explanation of that permission. They probably aren't self explanatory for everyone.
Click to expand...
Click to collapse
I concur.....I look at the permissions that apps ask for all the time. However, if I see a battery management app is asking me for full internet access and access to my contacts, I just pass on it. A lot of times you can figure out if an app is requesting bogus permissions just by using common sense.

rugedraw said:
I concur.....I look at the permissions that apps ask for all the time. However, if I see a battery management app is asking me for full internet access and access to my contacts, I just pass on it. A lot of times you can figure out if an app is requesting bogus permissions just by using common sense.
Click to expand...
Click to collapse
if your app is paid for by advertisements then it will need Internet Access so it can retrieve ads...thus paying the developer. often that's where i see 'coarse location' used as well...for regional specific ads. so in those cases, not nefarious use but a perfect example of what I'm talking about. thank you.

the problem with the current permissions system is twofold;
1) as mentioned, there is no details WHY or WHAT FOR a particular permission is required
2) its all or nothing, ie you can't give permission for network access and restrict access to contact list, etc. You have to accept all the requested permissions or deny and not install the app.

fwiw: There is an app in the market called "permissions" that tells you not only the permissions each app requires but it gets VERY specific. Within each permission category there is a whole list of specifics.
It won't help with apps you haven't installed yet but it's good info on the ones you already have.
*edit- Just revisited this app, it's not as detailed as I remember.

just a lil bump...

bumpity bump ...

nothing? at all?

The WindowBreak Project

"What am I doing, why am I here, what is this about, and where am I going with this."
Hello all. After dealing with rumors, rumors of rumors, and the like, I've finally managed to disclose something I hold very dear to me: the WindowBreak project.
As the name suggests, this is a jailbreak project for Windows Phone 7. I started something a while back that had little success, but through the months, I've managed to figure out something that should bring light into the Windows Phone jailbreaking scene.
Real quick, though:
What this is: A project, with information about some interesting exploits I found, and a call for the community to dive in.
What this isn't: A full fledged jailbreak. Please don't post replies such as "when will XXXX device be supported". It just wastes time, and I assure you, I want every device included.
It also is not a full unlock. Just interop.
The details
So here's the sitch. We all know how Heathcliff74's interop unlock works. XAP files are just ZIP files, and ZIP files can have entries that allow extracting in parent directories.
Interesting thing is, this can be done using the ZipView application, which normally stores data in \Application Data\Volatile\Zipview\<random id>
Thus, creating a directory in a ZIP file called ../../../../provxml will copy all those files into the \provxml\ folder upon extraction.
See what I did there?
Limitations
Of course, there are limitations.
1) We cannot extract into \Windows\. There's a policy that prevents it.
2) The bad one: We can only extract known MIME types, at least to my knowledge. This is because the files are only extracted when they are clicked on in ZipView. And clicking on a .dbz file, for example, will just say the file type is not supported. Bummer.
What we can do...
As mentioned above, this can be used for a fresh out of the box jailbreak for Samsung devices, using provxml. Here's a video of that:
Try it yourself: with a Samsung device, go to http://windowsphonehacker.com/windowbreak and press WindowBreak Me.
In theory, this would be all we need to jailbreak most Windows Phone devices. Unfortunately, Nokia and HTC devices block the registry entries in provisioning files. I'm not sure what the extent of this "whitelist" (or is it a blacklist?) is, and details/tests on this would be appreciated.
What needs to be done...
Nokia: I don't have a Nokia device, but I've been working a great deal on figuring out how to crack it's shell, and have a couple of ideas. If I'm able to get my hands on a Nokia device soon, I'll try some of these unorthodox exploits out, otherwise I'll need some daring volunteers.
HTC: I do have an HTC device, but I can't figure out how to extract the files for the Connection Setup program. If someone can give me details on what the password encryption is on it, etc, for the HTC interop unlock, that would be much appreciated.
Other devices: Not a lot of demand for these (and LG needs no jailbreak, since it has MFG), but if something comes up, feel free to share where the provisioning files exist and I'll see about "windowbreaking" them.
So this is my little project, and I hope the details I'm sharing will lead to further development. My personal device (Samsung Focus) is easily interop unlocked now, without costing me a cent. I'd really like this to be the case for everyone; I'm not saying the $9 unlock for Chevron Labs is bad, in fact, it's greatly supported homebrew. What I am saying, though, is that freedom is still possible, and regardless, any developments made here will further support interop unlocking on Chevron/apphub unlocked devices. With that in mind...
Merry Christmas.
Special thanks to: Heathcliff74 for much of the research and idea behind the exploit
All the supporting members of XDA, who bring appreciation for what we do. Thank you.

Cool! Ridiculous that I didn't think of this myself
I will send you the password of the dbz files when I get home. I don't have it here.
But the real problem for HTC and NOKIA are the whitelists. I've been working on this for the past time. And today I made more progress. I developed a new way of debugging native 3rd party dll's/drivers. U can isolate functions and call them from a test app for unit-testing. This makes testing a lot easier. This will help me find exploits much faster. I can even call the whitelist functions of HTC and NOKIA on my Samsung now Working on it right now.
Good find!!
Heathcliff74

Heathcliff74 said:
Cool! Ridiculous that I didn't think of this myself
I will send you the password of the dbz files when I get home. I don't have it here.
But the real problem for HTC and NOKIA are the whitelists. I've been working on this for the past time. And today I made more progress. I developed a new way of debugging native 3rd party dll's/drivers. U can isolate functions and call them from a test app for unit-testing. This makes testing a lot easier. This will help me find exploits much faster. I can even call the whitelist functions of HTC and NOKIA on my Samsung now Working on it right now.
Good find!!
Heathcliff74
Click to expand...
Click to collapse
Haha, I knew you would say that when you saw this. Most credit of this goes to your work, in fact, which gave me much of the idea.
As for the whitelists, do you know exactly how it's blocking? Is just registry blocked, or all non-APN related settings?

^-- This is why I nominated you guys for those free Nokia Lumias. Keep up the good work!

Jaxbot said:
Haha, I knew you would say that when you saw this. Most credit of this goes to your work, in fact, which gave me much of the idea.
As for the whitelists, do you know exactly how it's blocking? Is just registry blocked, or all non-APN related settings?
Click to expand...
Click to collapse
Both brands have very similar mechanisms. They both have a driver dedicated to provisioning. The whitelists are implemented in those drivers. HTC has whitelisted only specific registry keys for APN's and stuff. NOKIA does not have the registry on the whitelist at all.
Heathcliff74

Heathcliff74 said:
Both brands have very similar mechanisms. They both have a driver dedicated to provisioning. The whitelists are implemented in those drivers. HTC has whitelisted only specific registry keys for APN's and stuff. NOKIA does not have the registry on the whitelist at all.
Heathcliff74
Click to expand...
Click to collapse
Shame it's a whitelist instead of a blacklist :\
Do you know which CSPs are allowed? I've managed to move files around using provxml on my Samsung, but it seems to allow just about anything.

Yeah I want you two to get the free Nokia Lumia's too! You both do great work - thank you keep giving love to the Omnia 7 too please since it's my girlfriend who has the Lumia 800 (dammit!)

Indeed a very cool solution ! Thanks button pressed.
Is it limited to 1st gen samsung devices or does it work on 2nd gen devices too ?

contable said:
Indeed a very cool solution ! Thanks button pressed.
Is it limited to 1st gen samsung devices or does it work on 2nd gen devices too ?
Click to expand...
Click to collapse
Both first and 2nd gen will work, though some interop won't work on 2nd gen devices (e.g., last I heard, registry editors were all read only)

DBZ Password
030D681B-1DFC-4bd0-A72A-A9B3CCCDA653
---------- Post added at 10:30 AM ---------- Previous post was at 10:29 AM ----------
Oh and it was found here http://forum.xda-developers.com/showthread.php?p=18916888

When I go to http://windowsphonehacker.com/windowbreak/
I don't get any buttons, just these text :
WindowBreak
By WindowsPhoneHacker
WindowBreak is a project with the goal of enabling true jailbreaking on Windows Phones.
We believe in freedom, both in gratis and in libre.
For details on WindowBreak, see here [add XDA link here].
BTW Nice worrk, hope to see more nice hacks these Xmas!

DJSave said:
When I go to http://windowsphonehacker.com/windowbreak/
I don't get any buttons, just these text :
WindowBreak
By WindowsPhoneHacker
WindowBreak is a project with the goal of enabling true jailbreaking on Windows Phones.
We believe in freedom, both in gratis and in libre.
For details on WindowBreak, see here [add XDA link here].
BTW Nice worrk, hope to see more nice hacks these Xmas!
Click to expand...
Click to collapse
You visit it on your phone, silly
And thanks, forgot to add the XDA links to that page.

Damn, purchased yesterday chevron labs-.-
But great work! I appreciate that!

Jaxbot said:
You visit it on your phone, silly
And thanks, forgot to add the XDA links to that page.
Click to expand...
Click to collapse
Yep Had desctop version in settings
10X it worked like a charm

Wait and hope for a solution for HTC devices

yea I can't wait for this. I have a HTC HD7.

Well done man, exactly what worked also with calling provxml files from the iso storage in DiagProvXML. Just do "../the entire path to iso storage/provxml.ext" this worked also on htc. Although of course your mechanism is different as you have to copy it to the correct folders while we just needed to change the default paths of the drivers to a custom folder.
Well done and nice creative solution. It would be great if you manage to get this working for more devices.
Maybe somebody can somehow find the exact provisioning the Developer Registration Tool makes, so you can use that one as that should be white listed I assume.

The Registration tool actually uses a socket connection to send a partly modified cookie string to the phone. The phone then goes and checks that against microsoft's servers and goes OK.

hey ii was just wonderiing, as nobody rarely mentions the dell venue pro, if something was going to be actually done for it. I know you said dont post stuff liike this but its just that ive never heard something like this or anything done about the Dell Venue Pro.
Thanks

Is the point of this for it to go from out of the box to interop unlocked, or from chevron/dev unlock to interop?
In /Classes Root/ registry part you can add the file type so it's known...

Great Idea

Well.. I believe it is a great idea...
Picture this...
You have a pattern lock or password on your phone...
Someone asks to use your phone...
You input the code backwards.. i.e. if your code is 1234 you enter 4321
That enables a "guest"/safe mode for the user...
What you guys think?

It would be easier to just have a "safe" mode that's activated by choosing it either when already unlocked or when unlocking - but still using the same password.
The "backward password" thing is a cute urban legend about ATM PINs, but examination of the legend reveals the flaws in a "backward pin" idea. Say your password is "3553" or something - it would be silly to limit passwords by prohibiting those when the "safe mode" could be entered another way.
Of course, this also questions what "safe mode" really is and how it would function - would developers have to develop the functionality for this per-app ?
It's an interesting idea, but it doesn't seem useful enough to me to be worth the time and money spent in development. It might be better just to not give your phone to people who want to snoop or take it out of eyesight.

Pennycake said:
It would be easier to just have a "safe" mode that's activated by choosing it either when already unlocked or when unlocking - but still using the same password.
The "backward password" thing is a cute urban legend about ATM PINs, but examination of the legend reveals the flaws in a "backward pin" idea. Say your password is "3553" or something - it would be silly to limit passwords by prohibiting those when the "safe mode" could be entered another way.
Of course, this also questions what "safe mode" really is and how it would function - would developers have to develop the functionality for this per-app ?
It's an interesting idea, but it doesn't seem useful enough to me to be worth the time and money spent in development. It might be better just to not give your phone to people who want to snoop or take it out of eyesight.
Click to expand...
Click to collapse
There was a ROM that had this mode.. all your texts disappear.. pictures are hidden.. background is plain.. recent calls are hidden.. stuff like that.. my idea, i guess, would be for people who do not want to make it so obvious as to making it guest mode and doing it in a hidden way

I'm still not keen on guest user idea. Nobody touches my phone..period. ..

i think its a cool idea

This is a great idea, I'd do it to all my iSheep friends that want to feel the greatness that rests in my pocket. Post the idea where it can be possible to happen in Android General... I'm guessing that'd be best for it to get some eyes on it, maybe an app dev will jump on it for you.

4.2 Jelly already has guest mode right? Shouldn't be too hard to implement this if anyone actually wants this feature..

Does it?
Sent from my SGH-T999 using xda premium

My nexus 7 guest mode which is vanilla android.

Need help bypassing "can't take screenshot due to security policy"

Hello. I am using a Samsung Galaxy S20+ 5G, Model SM-G986U
Android Version 11
Kernel version 4.19.113-20290031
Build number RP1A.200720.012.G986USQS1CTL1
I did both a Google search and a search using the xda-forum search bar.
First off: Kudos to whoever worked on the forum search feature. It is infinitely better today than it was years ago.
Unfortunately, while the question I have has been asked several times, it looks like no clear answer is given to any of the inquirers.
I would like to be able to bypass or override whatever flag or feature it is that lets app developers disallow users to take screenshots. I would like to be able to take screenshots in apps like Microsoft Teams (and a few other apps), even when the organization has chosen not to permit it. This is something I need to do for work. I can take screenshots in Teams just fine from a Windows PC regardless of policy. I am trusting there exists some method of doing the same from an android device.
What I would not like to do is have a discussion about the merits of enabling or disabling this security feature. Some of the previous users that have inquired were met with discussion about the wisdom of their decision instead of answering their questions directly. This time, I'd like for replies to assume that my mind is already made up and that it isn't changing. If this is something that simply cannot be done, I can accept that answer. Though I don't readily believe it. I believe that just like with a PC, there exists some method of capturing all data sent to the phone, regardless of the sender's intention.
Thank you.

Try any third party app to capture what is on screen, I think you can't do it with stock method of taking screenshot. From android 7 or 8 , they introduced new Methods to not to capture what is available on screen so that any hackers can't capture our passwords using banking apps. I think ms have implemented same strategy. So you can't do it until you have root permissions

I am 100% willing to root the device if necessary, but do want some confirmation beforehand that rooting it will enable me to screen capture from whatever app I want.

r0b126 said:
Hello. I am using a Samsung Galaxy S20+ 5G, Model SM-G986U
Android Version 11
Kernel version 4.19.113-20290031
Build number RP1A.200720.012.G986USQS1CTL1
I did both a Google search and a search using the xda-forum search bar.
First off: Kudos to whoever worked on the forum search feature. It is infinitely better today than it was years ago.
Unfortunately, while the question I have has been asked several times, it looks like no clear answer is given to any of the inquirers.
I would like to be able to bypass or override whatever flag or feature it is that lets app developers disallow users to take screenshots. I would like to be able to take screenshots in apps like Microsoft Teams (and a few other apps), even when the organization has chosen not to permit it. This is something I need to do for work. I can take screenshots in Teams just fine from a Windows PC regardless of policy. I am trusting there exists some method of doing the same from an android device.
What I would not like to do is have a discussion about the merits of enabling or disabling this security feature. Some of the previous users that have inquired were met with discussion about the wisdom of their decision instead of answering their questions directly. This time, I'd like for replies to assume that my mind is already made up and that it isn't changing. If this is something that simply cannot be done, I can accept that answer. Though I don't readily believe it. I believe that just like with a PC, there exists some method of capturing all data sent to the phone, regardless of the sender's intention.
Thank you.
Click to expand...
Click to collapse
My simple reply,, is when I got that security
policy violation I was either A) trying to capture a
Kodak moment of my current bank balance in hopes of an securing an outcome, that while only temporary was nonetheless a mutually desired and shared experience with a member of the opposite gender, also, FLAGGED AS GOOD TO GO, or, MAJORLY way less interesting, B) the never to miss a trick bastards just don't want me swiping an awesome wallpaper idea right from under their greedy noses! Dammit man, I'll always choose A)..habit, I guess? lol

'back in the day' i've used smalipatcher.
This disables the security flag completely.
Not sure if it works with android 11.
Requires root.
Easiest way; You could also mirror the screen to your pc, and make screenshots from your pc.

r0b126 said:
Hello. I am using a Samsung Galaxy S20+ 5G, Model SM-G986U
Android Version 11
Kernel version 4.19.113-20290031
Build number RP1A.200720.012.G986USQS1CTL1
I did both a Google search and a search using the xda-forum search bar.
First off: Kudos to whoever worked on the forum search feature. It is infinitely better today than it was years ago.
Unfortunately, while the question I have has been asked several times, it looks like no clear answer is given to any of the inquirers.
I would like to be able to bypass or override whatever flag or feature it is that lets app developers disallow users to take screenshots. I would like to be able to take screenshots in apps like Microsoft Teams (and a few other apps), even when the organization has chosen not to permit it. This is something I need to do for work. I can take screenshots in Teams just fine from a Windows PC regardless of policy. I am trusting there exists some method of doing the same from an android device.
What I would not like to do is have a discussion about the merits of enabling or disabling this security feature. Some of the previous users that have inquired were met with discussion about the wisdom of their decision instead of answering their questions directly. This time, I'd like for replies to assume that my mind is already made up and that it isn't changing. If this is something that simply cannot be done, I can accept that answer. Though I don't readily believe it. I believe that just like with a PC, there exists some method of capturing all data sent to the phone, regardless of the sender's intention.
Thank you.
Click to expand...
Click to collapse
very well put, i don't get it, what's wrong with these androids
actually considering getting an iphone for this stupid problem
youre best bet would be without rooting use this method, i used it, it worked on some apps and unfortunately some banking apps are just not cloneable, whatsapp is not too