Related
I'm working on HTC support for WP7 Root Tools. I made a test-app. If you have an unlocked HTC with NoDo, I'd appreciate it if you can run it and post the test-results.
UPDATE: Very useful test results!! (see my comments in post #4) Updated test app attached. Please run this test and let me know the results (in detail).
More info here and here.
Thanks a lot!
Heathcliff74
T-Mobile HD7 Nodo 7392
Test 1: error: Incorrect function
Test 2: error: Incorrect function
Test 3: Pass
Test 4: error: Incorrect function
Test 5: error: Incorrect function
Test 6: error: Incorrect function
Test 7: error: Incorrect function
Test 8: Pass
Test 9: Pass
HD7 Nodo 7392
Test 1: error: Incorrect function
Test 2: error: Incorrect function
Test 3: Pass
Test 4: error: Incorrect function
Test 5: error: Incorrect function
Test 6: error: Incorrect function
Test 7: error: Incorrect function
Test 8: Fail
Test 9: Pass
OK guys. Very useful info. Looks like a lot of errors, but this is actually a very good result! Test 3 was the most important one and that one passed. This actually confirms I can make WP7 Root Tools compatible with HTC devices!!
I would like to have some more details, so I made a second test app. If you have an HTC with RTM or NoDo, please download the second version of the test-app (in the opening post of this thread) and run it. This will provide me info that I can use for optimal implementation. Please let me know all the details on screen and the version and device model you use.
Thanks very much!!
Heathcliff74
Heathcliff74 said:
.If you have an HTC with RTM or NoDo, please download the second version of the test-app (in the opening post of this thread) and run it. This will provide me info that I can use for optimal implementation. Please let me know all the details on screen and the version and device model you use.
Click to expand...
Click to collapse
Hi Heathcliff74!
nice to see that we can support you.
will trying to thest the tool as soon as I'm back from work.
Do you prefer testing on NoDo or Mango?
btw I can test it on each subversion (Mango betaversion) when I update my phone
EDIT:
European HD7 ==> PD291000
Cotulas HSPL
Fresh flashed Ansars WWE 3.04 Rom (7.0.7390.0) and deinstalled all unecessarry htc stuff
7390:
Test 1: Pass
Test 2: Pass
Test 3: 3
Test 4: 5
Test 5: 0x0000007E
7403:
Test 1: Pass
Test 2: Pass
Test 3: 5
Test 4: 5
Test 5: 0x0000007E
cant't update any further :-(
flash ansars 1.69 rom (7.0.7389.0) & 5.66a radio
7389 & 7403:
Test 1: Pass
Test 2: Pass
Test 3: 3
Test 4: 5
Test 5: 0x0000007E
7712 & 7720
The type initializer for ÄY threw an exeption...
HD7 Nodo 7392, O2 Sim
Test 1: Pass
Test 2: Pass
Test 3: 3
Test 4: 5
Test 5: 0x0000007E
Edit: looked up your DLL in IDA, some nice stuff is coming really looking forward to how you managed to circumvented the chamber model!
HD7 Nodo 7392
Test 1: Pass
Test 2: Pass
Test 3: 3
Test 4: 5
Test 5: 0x0000007E
OK guys! Thanks very much. I know enough to support HTC now. Very cool. I will keep you posted on the progress in the WP7 Root Tools thread.
Thanks again!
Heathcliff74
PS. HTC really need to hire some decent coders for their drivers
rudelm said:
Edit: looked up your DLL in IDA, some nice stuff is coming really looking forward to how you managed to circumvented the chamber model!
Click to expand...
Click to collapse
Heheh... I have put a lot of nice stuff in WP7Native01ARM.dll. But my native code-base is a lot bigger right now! I have done a ton of research and I build a lot of abstraction layers to make all this possible. Most of the REAL magic will be in WP7Native02ARM.dll And there's also WP7Native03ARM.dll. These will be in the new version of WP7 Root Tools. So, when it is released, you should open up IDA again
About the chamber model.. I've been studying it over the past weeks. It is really cool, when you start to understand it. If I'd had to guess I'd say that I completely understand 80% of all the implementation details of the policy-system. I almost completely reverse engineered and re-engineered the policy-engine
Ciao,
Heathcliff74
wowowowww Nice m8...
We will Wait for this...Thanks for hard work
I'm working on a new version of WP7 Root Tools. I have new exploits, that should make it possible to support more devices. I will support Samsungs and HTCs, but I though I would give it a try to support LGs, although it will be very hard without having a hands-on device. But I made a test-app. If you have an unlocked LG with NoDo or RTM (not Mango!), I'd appreciate it if you can run it and post the test-results (in detail!) Hopefully that will help me to build LG support in the next version of WP7 Root Tools.
More info here.
UPDATE: First test was not going well. I improved the tests and added 2 new tests. Please run them again and let me know the results in detail!
UPDATE: Third version of the test-app...
UPDATE: Fourth version of the test-app...
UPDATE: Fifth version of the test-app...
UPDATE: Sixth version of the test-app...
UPDATE: Seventh version of the test-app...
UPDATE: Version 8 of the test app is now uploaded. There is a slight risk involved that it screws up. So make sure you make a backup in advance! You can find a backup app here. Follow the on-screen-instructions: Run the tests. Write down the results in detail. Then reboot (there's a reboot-button). After the reboot start the app again and run the tests again. Write down the results again. Please report the results of both test-runs.
UPDATE: Previous test went well. Also the risky part seems to be no problem anymore. Almost certain now that I can support LG devices in WP7 Root Tools. But I need more details. So here's version 9 of the test app. I hope this will provide all the info I need. But it could be possible that the results of this test app raise more questions. In that case I might need to create another test app. Anyway, I hope this is going to be the last version of the test app. It will perform 20 (!) tests. Please run the tests twice. After the first run, write down the results, reboot, run again and write down the results again. Report the results in full detail. I expect that some of the tests fail or throw errors. That's no problem. I just need some confirmations and details for implementation.
UPDATE: Test app v10. Please test it. You know the drill. Test, reboot, test again.
UPDATE: We're still not there yet. Test app v11 now. Please test it. Like before, test it twice.
UPDATE: Unfortunately the last tests were not successful. For now I'm out of ideas to get this working on LG's. I'm very close, but I can't get the last part to work. I will leave it to rest now. Chances are that when I'm working on other things I might get ideas to continue the work for LG's. So I don't write this off yet. Too much effort already put into this by me and everybody who helped me testing. Thanks to everyone so far and I hope to get new inspiration for this soon.
UPDATE: I think I got some great news. I have just found 2 new hacks that can probably be used for LG. I think both will work. And I need only one of them to work to get WP7 Root Tools working for LG's! All the previous testing has not been wasted, because I will use a combination of exploits, including the ones I already found and tested with you. I will have to test if this all works, how it works and how it is best implemented. So expect another round of test apps soon! It may take some research first before I can make a new test app and I'm also working very hard on a couple of other things, but I think you can expect a new version of the test app before the end of the week. I'm glad it seems this has not been a waste of time and energy!
UPDATE: Test app v12 is ready for testing. No need to run it twice. Please let me know the results.
UPDATE: Test app v13 is ready for testing.
UPDATE: Test app v14 is ready for testing.
UPDATE: Test app v15 is ready for testing.
UPDATE: Test app v16 is ready for testing.
UPDATE: Test app v17 is ready for testing. I optimized some of the other tests. They might fail where they passed before. I that case I will have to revert. I hope test 6 and 12 will pass now.
UPDATE: Test app v18 is ready for testing. I got a good feeling...
UPDATE: Ok Guys. Thanks a lot for testing. I have enough info to build support for LG devices in the next version of WP7 Root Tools. As I wrote earlier, I'm finishing up a lot of code. All test code is there, just need to glue it all together. Not sure how long it will take me, but it will be a very cool release. So bear with me.
Will keep you posted!
Heathcliff74
I must say I'm a bit disappointed. No interest from LG users. Guess there won't be support for LG devices then...
I'd help, but I'm already on Mango. But I bet there are interested users, give them a fair chance to actually test and post. Under 24 hours might not be enough.
\J
Version: 7392
Test 1: error: The handle is invalid
Test 2: fail
Test 3: 0
Test 4: 0
Test 5: 0x0000000
Now, there is an update for Zune, will try it once more after that update
EDIT: After Zune update are the results the same
Hope i can help you more
ziko said:
Version: 7392
Test 1: error: The handle is invalid
Test 2: fail
Test 3: 0
Test 4: 0
Test 5: 0x0000000
Now, there is an update for Zune, will try it once more after that update
Click to expand...
Click to collapse
Thanks. This didn't work yet. Do you have an email address where I can reach as soon as I have more tests? Since there are not that much LG users, it's easier if I can reach you directly. If you want you can PM me your email-address.
You can try the update, but I don't think it will help. I will probably have to find out what I have to change to my code.
Thanks again,
Heathcliff74
jontatas said:
I'd help, but I'm already on Mango. But I bet there are interested users, give them a fair chance to actually test and post. Under 24 hours might not be enough.
\J
Click to expand...
Click to collapse
Guess you were right
yea finnaly some LG love But Sadly im on 7712 already .. maybe I'm gonna downgrade just to check this out
jontatas said:
I'd help, but I'm already on Mango. But I bet there are interested users, give them a fair chance to actually test and post. Under 24 hours might not be enough.
\J
Click to expand...
Click to collapse
I'm betting there's lots of people in the Mango camp. Myself included.
First test was not going well. I improved the tests and added 2 new tests. Please run them again and let me know the results in detail! Download is in the opening post.
Thanks!
Heathcliff74
lg test 2 results:
Test 1: error:a device attached to the system is not....(end of screen, cant reed the rest)
Test 2: Fail
Test 3: 0
Test 4: 0
Test 5: 0x00000000
Test 6: Pass
Test 7: error: The handle is invalid
ziko said:
lg test 2 results:
Test 1: error:a device attached to the system is not....(end of screen, cant reed the rest)
Test 2: Fail
Test 3: 0
Test 4: 0
Test 5: 0x00000000
Test 6: Pass
Test 7: error: The handle is invalid
Click to expand...
Click to collapse
Thanks. A little step further. But the essential tests are still failing. I will have a look, create a third version and post it here later.
Ciao,
Heathcliff74
thaks for supporting lg devices for your homebrew
will help as much as i can
Hi,
I have LG E900 with NoDo (unlocked 7.0.7392.0). Today (after 4-5 hours) I will try test.
Version 3 of test-app now. Please try again! Thanks!
Heathcliff74
lg test 3 results:
Curios, it says "Performing 7 Tests" but there are only 5....hhmmm
The results are the same as with Test v1.
Please have a look on the XAP.
Test 1: error:a device attached to the system is not....(end of screen, cant reed the rest)
Test 2: Fail
Test 3: 0
Test 4: 0
Test 5: 0x00000000
Click to expand...
Click to collapse
ziko said:
lg test 3 results:
Curios, it says "Performing 7 Tests" but there are only 5....hhmmm
The results are the same as with Test v1.
Please have a look on the XAP.
Click to expand...
Click to collapse
Hi ziko,
This app has 5 tests. The 7 is a typo. Could you please try to turn off your phone completely and then power on and then try the test again? Thanks.
Sent from my OMNIA7 using XDA Windows Phone 7 App
Hi Heathcliff74,
Unistaled the app
removed battery
started again
installed the V3 again
...sorry, the results are the same as above...
7.0.7392
Test 1: error: A device attached to the system is not ...
Test 2: Fail
Test 3: 0
Test 4: 0
Test 5: 0x00000000
Same how fb401:
Test 1: error: A device attached to the system is not ...
Test 2: Fail
Test 3: 0
Test 4: 0
Test 5: 0x00000000
i'm not at home this weekend but i will try it on Monday on my Optimus 7.
Thanks for suppporting LG Phones.
Hello
I try to install Cisco AnyConnect on my Touch Pro (FRX07)
but when it start, I have error: failed to connect to VPN service.
Can you say me if you can run it, and how?
I want diag my problem, but log are not very explicite
Thank's for your help
I join the apk I use.
and my debug log
seems it's buz the bundle still not supports VPN
likounin said:
seems it's buz the bundle still not supports VPN
Click to expand...
Click to collapse
We've never supported VPN's. If there's some way to make them work, we will gladly implement the code. As always, patches welcome.
arrrghhh said:
We've never supported VPN's. If there's some way to make them work, we will gladly implement the code. As always, patches welcome.
Click to expand...
Click to collapse
ok, thank's. I understand now.
I am new on Android, but I known Linux
What patch may we do? kernel, daemon, ...
ejantzen said:
ok, thank's. I understand now.
I am new on Android, but I known Linux
What patch may we do? kernel, daemon, ...
Click to expand...
Click to collapse
First, if I knew it would already be patched lol. Second, I don't have any VPN to test with - so you're going to have to tell us what needs patched. It seems like a userland issue, but I honestly don't know. Perhas some kernel module is missing? Again, I don't know for sure. I don't have any way to test it, and I think that's the problem most have - they have no way of testing VPN, and I think most probably use OpenVPN if it's in their home. At work, it's probably mostly PPTP.
So if you find something to patch, please submit it. If you can't... well then we just won't be able to support VPN's. Pretty minor feature, but I'm sure it would be nice for some.
arrrghhh said:
It seems like a userland issue, but I honestly don't know. Perhas some kernel module is missing? Again, I don't know for sure.
Click to expand...
Click to collapse
ok, thank's
but on the debig file, we can't see where is the problem?
ejantzen said:
ok, thank's
but on the debig file, we can't see where is the problem?
Click to expand...
Click to collapse
If by "we" you mean me, no. I'm no expert on the matter of deciphering logs and determining what exactly needs to be fixed. I can usually pinpoint problems, but pinpointing exactly which element needs fixing... I'm pretty new to.
In my horrible estimation, these three lines are where it starts going badly:
Code:
09-04 10:27:28.770 I/vpnagent( 1847): Function: scanAvailableModule File: PluginLoader.cpp Line: 745 Scanning plugin libvpncommoncrypt.so
09-04 10:27:28.770 W/vpnagent( 1847): Function: STGetProcAddress File: HModuleMgr.cpp Line: 263 Invoked Function: dlsym Return Code: 0 (0x00000000) Description: Symbol not found:
09-04 10:27:28.770 E/vpnagent( 1847): Function: scanAvailableModule File: PluginLoader.cpp Line: 783 Invoked Function: CHModuleMgr::STGetProcAddress Return Code: -33554427 (0xFE000005) Description: GLOBAL_ERROR_NULL_POINTER
The "Scanning plugin libvpncommoncrypt.so" portion really interests me. Does this lib exist? Have you been able to find perhaps another version of it? I know very little about VPN's... never had the desire to use one on a phone. I don't even use 'em on computers really... my office has a VPN that requires a PC, and is far from a 'traditional' VPN.
Looking further thru the log, it seems the app is just going thru libs. It would appear we're either missing these libs, or the libs we have aren't playing nicely. I keep seeing the same "Symbol not found" errors... I'm betting we simply don't have the right libs for this type of VPN app.
thank's
I will try in this direction.
Compatibility Test Suite
There are many company & people want to know, what is CDD & CTS testing, how to get android CTS certificate.
How to get CTS Certificate, whom can I contact, What is the procedure.
[email protected]
[email protected]
CTS Team, [email protected]
Thank you for the reply.
CTS got passed 100% in single test, please let me know, whom to send the result.
1 For whom I have to send result.
2 Its necessary to send Device also?
3 After sending the CTS report, how long I have to wait..
On Thu, Nov 29, 2012 at 2:02 PM, Android CTS <[email protected]> wrote:
Hi Vinoth,
Thank you for writing to us and sorry for the slow response. The Android
Compatibility program is designed around self-certification, but you do
need a license from Google to distribute any Google apps, including Google
Play (the new Android Market). To inquire about licensing the Google
Mobile Services apps for Android devices, please contact our business team
at [email protected]. Note that achieving Android
compatibility is a pre-requisite for consideration as a licensee.
Regarding your question below, are you saying that some of these tests
fail when you run the entire plan, but pass when you run them
individually? This typically points to issues with memory leaks, memory
pressure or general device stability. The goal is definitely to pass all
tests in a single run. If the device is incapable of passing 100% in a
single run, you should investigate the issues to understand why.
Again, thanks very much for your interest in Android.
- The Android Compatibility Team
CTS STEPS
How does the CTS work?
The CTS is an automated testing harness that includes two major software components:
The CTS test harness runs on your desktop machine and manages test execution.
Individual test cases are executed on attached mobile devices or on an emulator. The test cases are written in Java as JUnit tests and packaged as Android .apk files to run on the actual device target.
Workflow
Download the CTS and CTS media files.
Attach at least one device (or emulator) to your machine.
For CTS 2.1 R2 and beyond, setup your device (or emulator) to run the accessibility tests:
adb install -r android-cts/repository/testcases/CtsDelegatingAccessibilityService.apk
On the device, enable Settings > Accessibility > Accessibility > Delegating Accessibility Service
For CTS 2.3 R4 and beyond, setup your device to run the device administration tests:
adb install -r android-cts/repository/testcases/CtsDeviceAdmin.apk
On the device, enable all the android.deviceadmin.cts.* device administrators under Settings > Location & security > Select device administrators
For CTS 2.3 R12 and beyond, the CTS media files must be copied to the device's external storage. Check section 4.2 of the latest CTS manual for further details on copying these files:
Unzip the CTS Media zip file.
Run copy_media.sh [720x480|1280x720|1920x1080|all] [-s serial]. If no resolution is specified, the default maximum resolution of 480x360 is assumed.
Launch the CTS. The CTS test harness loads the test plan onto the attached devices. For each test in the test harness:
The test harness pushes a .apk file to each device, executes the test through instrumentation, and records test results.
The test harness removes the .apk file from each device.
Once all the tests are executed, you can view the test results in your browser and use the results to adjust your design. You can continue to run the CTS throughout your development process.
When you are ready, you can submit the report generated by the CTS to [email protected]. The report is a .zip archived file that contains XML results and supplemental information such as screen captures.
Types of test cases
The CTS includes the following types of test cases:
Unit tests test atomic units of code within the Android platform; e.g. a single class, such as java.util.HashMap.
Functional tests test a combination of APIs together in a higher-level use-case.
Reference application tests instrument a complete sample application to exercise a full set of APIs and Android runtime services
Future versions of the CTS will include the following types of test cases:
Robustness tests test the durability of the system under stress.
Performance tests test the performance of the system against defined benchmarks, for example rendering frames per second.
Please click thanks.. if its good info..
please elevate this post to sticky
Ok
schlager said:
please elevate this post to sticky
Click to expand...
Click to collapse
Thanks, feel free to contact me for any doubts in CTS.
Android CTS Testing Status
Hi,
I have executed the tests plan by plan. Can I submit this report to Google for getting certification.
Thanks & Regards,
Ethen
Sure
julyhunt said:
Hi,
I have executed the tests plan by plan. Can I submit this report to Google for getting certification.
Thanks & Regards,
Ethen
Click to expand...
Click to collapse
you can do that, any help contact me [email protected]
Holy thread resurrection.
I am trying to get a bespoke device certified, when I run the CTS plan, 154k tests are Not Executed though? This seems like an outrageously large amount, is there any reason they wouldn't run? Is this normal?
Passed 44996, Failed 496, Not Executed 154677
https://m.youtube.com/watch?v=Bm1FggPu-Zs
Please watch the whole video first before starting anything, then try to replicate step by step.
Of course, there is the risk of the lzplay app being malicious, please keep that in mind, you have to grant the app some privileges.
Hi Yir!
I follow this steps to the detail and the GMS app still does not work (same message at
)
My build number is a little different and my phone is an ARE-AL10 model. No more updates are received.
Any ideas?.
Thanks!