Scaling down display refresh rate from 60khz to 30khz - Nexus 6P Q&A, Help & Troubleshooting
I have a Nexus 6P and a Samsung s5 mini. The Samsung has an Ultra Low Power Saving Mode (UPSM) where various features/functions and low level hardware modifications are made to reduce the device to be a "dump phone" with a maximum 18.5 day battery life.
(http://www.extremetech.com/mobile/1...ltra-power-saving-mode-makes-10-last-24-hours).
One of the modifications of UPSM is scaling back the display refresh rate from 60khz to 30khz.
I have been able to replicate most of the UPSM functions with various tasker tasks, shell commands, and kernel/CPU mods.
The one thing I am stuck on is how to downscale the display refresh rate from 60khz to 30khz (or similar supported refresh rate.) I have searched the web, these forums high, and also contacted the ElementalX Kernel developers, and no one really know who to do this or has tried.
My understanding is that dropping the refresh rate by half should reduce the amount of time to refresh the same pixels my half. As well as lowering the FPS allowing the GPU to work less (for down scaling)
From what I have read, the refresh rate khz is usually hard set in the ROM. Apparently some ROMs are set differently, e.g 55khz and 60khz. But if the Samsung can change this on the fly then I imagine this is a value you set in a file within the shell. But which file, where, and how I am unsure.
The 6P has a Samsung WQHD AMOLED panel and the S5 has a Samsung Super AMOLED panel. Both AMOLED and from the same manufacturer I imagine the technology should be similar i.e be able to handle 30khz.
@BuLLeT_93 wrote an article / mod for changing the refresh rate on a G3 device from 60 to 50 but this is obviously specific to the G3 from the references.
(http://forum.xda-developers.com/lg-g3/development/mod-lcd-tweaks-fps-resolutionfor-t3140455)
Method for v4A (Work also for CM Users)
- Open file explorer
- Go to "/sys/devices/platform/g3-display.0/devfreq/g3-display.0/"
- Check "cur_freq" file, if values is 50 the mod work fine!
Method for v4B (Work also for CM Users)
- Open file explorer
- Go to "/sys/devices/platform/g3-display.0/devfreq/g3-display.0/"
- If "min_freq" values is 50 and "max_freq" is 60 the mod work fine!
I have poked around the 6P shell and found /sys/class/devfreq/ which contains all the QCOM related config which includes frequencies. Though I could find anything that had current freq "cur_freq" set to 60 so I am unsure.
Anyone have any ideas? Am I chasing my tail?
mrlb said:
I have a Nexus 6P and a Samsung s5 mini. The Samsung has an Ultra Low Power Saving Mode (UPSM) where various features/functions and low level hardware modifications are made to reduce the device to be a "dump phone" with a maximum 18.5 day battery life.
(http://www.extremetech.com/mobile/1...ltra-power-saving-mode-makes-10-last-24-hours).
One of the modifications of UPSM is scaling back the display refresh rate from 60khz to 30khz.
I have been able to replicate most of the UPSM functions with various tasker tasks, shell commands, and kernel/CPU mods.
The one thing I am stuck on is how to downscale the display refresh rate from 60khz to 30khz (or similar supported refresh rate.) I have searched the web, these forums high, and also contacted the ElementalX Kernel developers, and no one really know who to do this or has tried.
My understanding is that dropping the refresh rate by half should reduce the amount of time to refresh the same pixels my half. As well as lowering the FPS allowing the GPU to work less (for down scaling)
From what I have read, the refresh rate khz is usually hard set in the ROM. Apparently some ROMs are set differently, e.g 55khz and 60khz. But if the Samsung can change this on the fly then I imagine this is a value you set in a file within the shell. But which file, where, and how I am unsure.
The 6P has a Samsung WQHD AMOLED panel and the S5 has a Samsung Super AMOLED panel. Both AMOLED and from the same manufacturer I imagine the technology should be similar i.e be able to handle 30khz.
@BuLLeT_93 wrote an article / mod for changing the refresh rate on a G3 device from 60 to 50 but this is obviously specific to the G3 from the references.
(http://forum.xda-developers.com/lg-g3/development/mod-lcd-tweaks-fps-resolutionfor-t3140455)
Method for v4A (Work also for CM Users)
- Open file explorer
- Go to "/sys/devices/platform/g3-display.0/devfreq/g3-display.0/"
- Check "cur_freq" file, if values is 50 the mod work fine!
Method for v4B (Work also for CM Users)
- Open file explorer
- Go to "/sys/devices/platform/g3-display.0/devfreq/g3-display.0/"
- If "min_freq" values is 50 and "max_freq" is 60 the mod work fine!
I have poked around the 6P shell and found /sys/class/devfreq/ which contains all the QCOM related config which includes frequencies. Though I could find anything that had current freq "cur_freq" set to 60 so I am unsure.
Anyone have any ideas? Am I chasing my tail?
Click to expand...
Click to collapse
Don't you own a charger?
Heisenberg said:
Don't you own a charger?
Click to expand...
Click to collapse
I have no shortage of chargers but they're kind of useless when there's no power available. I spend 3 months a year doing aid work, usually in Africa or Nepal trekking between remote villages can spend any where from 3 days to 3 weeks without access to power, and then when it is available through a generator they can charge up $10 for 30 minutes. I would be nice to know for my family they could reach me or I can make emergency calls during extended periods away. Sure I have a solar panel and battery pack which is great when they work or are charged. Then when I'm home I might go out for one beer, the next thing I know I'm at a rave in the desert, pulled into a vortex where the space time continuum no longer follows the linear sequence where all used too, nek minute I'm spat out and been MIA for a week or more. I guess it would be a naive thought to think that everyone that has a smart phone lives in a bubble between home and work with always access to charging. Perhaps I am the only person in the world that doesn't. But then for example what if your work is actually cooking meth in an RV in the middle of the desert and the RV breaks down with a flat batt, would be such a shame to have to walk 10 of miles back to the city because the smart phone went flat and couldn't make a simple call for help. Wait I feel like I've seen this happen somewhere before. There was a guy on these forums, I can't recall his name now, but he wrote this awesome guide on how to Unlock/Root/Flash for Nexus 6P I wonder if he has any idea how to interpret my OP and provide any clarity of possibilities. It seemed like he knew a thing or two but I've been wrong once before I suppose!
mrlb said:
I have no shortage of chargers but they're kind of useless when there's no power available. I spend 3 months a year doing aid work, usually in Africa or Nepal trekking between remote villages can spend any where from 3 days to 3 weeks without access to power, and then when it is available through a generator they can charge up $10 for 30 minutes. I would be nice to know for my family they could reach me or I can make emergency calls during extended periods away. Sure I have a solar panel and battery pack which is great when they work or are charged. Then when I'm home I might go out for one beer, the next thing I know I'm at a rave in the desert, pulled into a vortex where the space time continuum no longer follows the linear sequence where all used too, nek minute I'm spat out and been MIA for a week or more. I guess it would be a naive thought to think that everyone that has a smart phone lives in a bubble between home and work with always access to charging. Perhaps I am the only person in the world that doesn't. But then for example what if your work is actually cooking meth in an RV in the middle of the desert and the RV breaks down with a flat batt, would be such a shame to have to walk 10 of miles back to the city because the smart phone went flat and couldn't make a simple call for help. Wait I feel like I've seen this happen somewhere before. There was a guy on these forums, I can't recall his name now, but he wrote this awesome guide on how to Unlock/Root/Flash for Nexus 6P I wonder if he has any idea how to interpret my OP and provide any clarity of possibilities. It seemed like he knew a thing or two but I've been wrong once before I suppose!
Click to expand...
Click to collapse
Unfortunately this is fast beyond my expertise! I was just having a little joke, I do hope someone is able to help you though.
Heisenberg said:
Unfortunately this is fast beyond my expertise! I was just having a little joke, I do hope someone is able to help you though.
Click to expand...
Click to collapse
Yes I know (So was I partially ) and thanks so do I!
The more I read up about refresh rates for displays the more I find conflicting answers about possibilities. It's obviously a complex topic with little experimentation from modders etc. Some say refresh rate is set in the hardware of the display and can't be changed, other says its in the display driver and potentially can be changed, some say yes it can be decreased but not increased, some say you can't change the refresh rate but you can change the clock/timer interval which essentially does the same thing.
I did an experiment yesterday which returned some interesting results capturing the output of "dumpsys display" on:
On S5 mini (Lollipop) - Normal
On S5 mini (Lollipop)- in UPSM
On N6 (Marshmallow)
The S5 mini Normal vs UPSM mode there were a few very minor difference between modes. However there was one major difference which fits close to a refresh rate (or similar change)
I've attached the results of the all 3 dumpsys should anyone wish to compare.
In the next post I will post summary of differences between S5 Normal and S5 UPSM
S5 Normal
DISPLAY MANAGER (dumpsys display)
mAllDisplayBlankStateFromPowerManager=1
Display Adapters: size=4
WifiDisplayAdapter
mCurrentStatus=WifiDisplayStatus{featureState=2, scanState=0, activeDisplayState=0, activeDisplay=null, displays=[], sessionInfo=WifiDisplaySessionInfo: Client/Owner: Client GroupId: Passphrase: SessionId: 0 IP Address: , connectedState=-1, networkQoS=0}
mFeatureState=2
mDisplayController:
mWifiP2pEnabled=true
mNetworkInfo=NetworkInfo: type: WIFI_P2P[], state: UNKNOWN/IDLE, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true, isConnectedToProvisioningNetwork: false
Display Devices: size=1
DisplayDeviceInfo{"Built-in Screen": 720 x 1280, 60.000004 fps, density 320, 326.571 x 328.404 dpi, touch INTERNAL, rotation 0, type BUILT_IN, FLAG_DEFAULT_DISPLAY, FLAG_ROTATES_WITH_CONTENT, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS}
mCurrentLayerStack=-1
mBlanked=true
Callbacks: size=81
0: mPid=3193, mWifiDisplayScanRequested=false
1: mPid=3485, mWifiDisplayScanRequested=false
2: mPid=3505, mWifiDisplayScanRequested=false
3: mPid=3570, mWifiDisplayScanRequested=false
4: mPid=3624, mWifiDisplayScanRequested=false
5: mPid=3642, mWifiDisplayScanRequested=false
6: mPid=3652, mWifiDisplayScanRequested=false
7: mPid=3742, mWifiDisplayScanRequested=false
8: mPid=3770, mWifiDisplayScanRequested=false
9: mPid=3787, mWifiDisplayScanRequested=false
10: mPid=3804, mWifiDisplayScanRequested=false
11: mPid=3834, mWifiDisplayScanRequested=false
12: mPid=3960, mWifiDisplayScanRequested=false
13: mPid=4000, mWifiDisplayScanRequested=false
14: mPid=4091, mWifiDisplayScanRequested=false
15: mPid=4144, mWifiDisplayScanRequested=false
16: mPid=4309, mWifiDisplayScanRequested=false
17: mPid=4325, mWifiDisplayScanRequested=false
18: mPid=4342, mWifiDisplayScanRequested=false
19: mPid=4999, mWifiDisplayScanRequested=false
20: mPid=5175, mWifiDisplayScanRequested=false
21: mPid=5198, mWifiDisplayScanRequested=false
22: mPid=5212, mWifiDisplayScanRequested=false
23: mPid=5228, mWifiDisplayScanRequested=false
24: mPid=5269, mWifiDisplayScanRequested=false
25: mPid=5300, mWifiDisplayScanRequested=false
26: mPid=5355, mWifiDisplayScanRequested=false
27: mPid=5657, mWifiDisplayScanRequested=false
28: mPid=5833, mWifiDisplayScanRequested=false
29: mPid=5874, mWifiDisplayScanRequested=false
30: mPid=5892, mWifiDisplayScanRequested=false
31: mPid=7569, mWifiDisplayScanRequested=false
32: mPid=7767, mWifiDisplayScanRequested=false
33: mPid=7941, mWifiDisplayScanRequested=false
34: mPid=8123, mWifiDisplayScanRequested=false
35: mPid=8145, mWifiDisplayScanRequested=false
36: mPid=8159, mWifiDisplayScanRequested=false
37: mPid=8284, mWifiDisplayScanRequested=false
38: mPid=8460, mWifiDisplayScanRequested=false
39: mPid=8603, mWifiDisplayScanRequested=false
40: mPid=8737, mWifiDisplayScanRequested=false
41: mPid=8862, mWifiDisplayScanRequested=false
42: mPid=9012, mWifiDisplayScanRequested=false
43: mPid=9064, mWifiDisplayScanRequested=false
44: mPid=9076, mWifiDisplayScanRequested=false
45: mPid=9135, mWifiDisplayScanRequested=false
46: mPid=9183, mWifiDisplayScanRequested=false
47: mPid=9269, mWifiDisplayScanRequested=false
48: mPid=9462, mWifiDisplayScanRequested=false
49: mPid=9484, mWifiDisplayScanRequested=false
50: mPid=9567, mWifiDisplayScanRequested=false
51: mPid=9582, mWifiDisplayScanRequested=false
52: mPid=9599, mWifiDisplayScanRequested=false
53: mPid=9652, mWifiDisplayScanRequested=false
54: mPid=9826, mWifiDisplayScanRequested=false
55: mPid=9846, mWifiDisplayScanRequested=false
56: mPid=9858, mWifiDisplayScanRequested=false
57: mPid=9903, mWifiDisplayScanRequested=false
58: mPid=9965, mWifiDisplayScanRequested=false
59: mPid=9977, mWifiDisplayScanRequested=false
60: mPid=9993, mWifiDisplayScanRequested=false
61: mPid=10009, mWifiDisplayScanRequested=false
62: mPid=10026, mWifiDisplayScanRequested=false
63: mPid=10030, mWifiDisplayScanRequested=false
64: mPid=10065, mWifiDisplayScanRequested=false
65: mPid=10083, mWifiDisplayScanRequested=false
66: mPid=10096, mWifiDisplayScanRequested=false
67: mPid=10108, mWifiDisplayScanRequested=false
68: mPid=10120, mWifiDisplayScanRequested=false
69: mPid=10133, mWifiDisplayScanRequested=false
70: mPid=10146, mWifiDisplayScanRequested=false
71: mPid=10158, mWifiDisplayScanRequested=false
72: mPid=10177, mWifiDisplayScanRequested=false
73: mPid=10191, mWifiDisplayScanRequested=false
74: mPid=10221, mWifiDisplayScanRequested=false
75: mPid=10237, mWifiDisplayScanRequested=false
76: mPid=10253, mWifiDisplayScanRequested=false
77: mPid=10273, mWifiDisplayScanRequested=false
78: mPid=10287, mWifiDisplayScanRequested=false
79: mPid=10378, mWifiDisplayScanRequested=false
80: mPid=10539, mWifiDisplayScanRequested=false
S5 UPSM
DISPLAY MANAGER (dumpsys display)
mAllDisplayBlankStateFromPowerManager=2
Display Adapters: size=4
WifiDisplayAdapter
mCurrentStatus=WifiDisplayStatus{featureState=1, scanState=0, activeDisplayState=0, activeDisplay=null, displays=[], sessionInfo=WifiDisplaySessionInfo: Client/Owner: Client GroupId: Passphrase: SessionId: 0 IP Address: , connectedState=-1, networkQoS=0}
mFeatureState=1
mDisplayController:
mWifiP2pEnabled=false
mNetworkInfo=null
Display Devices: size=1
DisplayDeviceInfo{"Built-in Screen": 720 x 1280, 60.000004 fps, density 320, 326.571 x 328.404 dpi, touch INTERNAL, rotation 0, type BUILT_IN, FLAG_DEFAULT_DISPLAY, FLAG_ROTATES_WITH_CONTENT, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS}
mCurrentLayerStack=0
mBlanked=false
Callbacks: size=35
0: mPid=3193, mWifiDisplayScanRequested=false
1: mPid=3485, mWifiDisplayScanRequested=false
2: mPid=3505, mWifiDisplayScanRequested=false
3: mPid=3570, mWifiDisplayScanRequested=false
4: mPid=3624, mWifiDisplayScanRequested=false
5: mPid=3638, mWifiDisplayScanRequested=false
6: mPid=3642, mWifiDisplayScanRequested=false
7: mPid=3652, mWifiDisplayScanRequested=false
8: mPid=3669, mWifiDisplayScanRequested=false
9: mPid=3689, mWifiDisplayScanRequested=false
10: mPid=3703, mWifiDisplayScanRequested=false
11: mPid=3720, mWifiDisplayScanRequested=false
12: mPid=3742, mWifiDisplayScanRequested=false
13: mPid=3770, mWifiDisplayScanRequested=false
14: mPid=3787, mWifiDisplayScanRequested=false
15: mPid=3804, mWifiDisplayScanRequested=false
16: mPid=3834, mWifiDisplayScanRequested=false
17: mPid=3902, mWifiDisplayScanRequested=false
18: mPid=3960, mWifiDisplayScanRequested=false
19: mPid=3979, mWifiDisplayScanRequested=false
20: mPid=4000, mWifiDisplayScanRequested=false
21: mPid=4035, mWifiDisplayScanRequested=false
22: mPid=4091, mWifiDisplayScanRequested=false
23: mPid=4098, mWifiDisplayScanRequested=false
24: mPid=4144, mWifiDisplayScanRequested=false
25: mPid=4163, mWifiDisplayScanRequested=false
26: mPid=4182, mWifiDisplayScanRequested=false
27: mPid=4217, mWifiDisplayScanRequested=false
28: mPid=4234, mWifiDisplayScanRequested=false
29: mPid=4259, mWifiDisplayScanRequested=false
30: mPid=4281, mWifiDisplayScanRequested=false
31: mPid=4293, mWifiDisplayScanRequested=false
32: mPid=4309, mWifiDisplayScanRequested=false
33: mPid=4325, mWifiDisplayScanRequested=false
34: mPid=4342, mWifiDisplayScanRequested=false
There is one major difference between the two modes, and that's with the amount of "Callbacks: size". In normal mode it is 81 and in UPSM it is 33. Now comparing this to N6 it is 58. These numbers line up very close to refresh rates 80kz, 30khz and 60khz respectively.
Now if I inspect the ASOP code for DISPLAY MANAGER (
android / platform / frameworks / base / feef9887e8f8eb6f64fc1b4552c02efb5755cdc1 / . / services / java / com / android / server / display / DisplayManagerService.java)
https://android.googlesource.com/pl...oid/server/display/DisplayManagerService.java
I can see the Callback size is printed from "mCallbacks.size()" but I am having trouble working out where "mCallbacks.size()" is defined and set.
Related
TomTom SDK and TomTom3
Hi. I use the TomTom SDK to set the target for TomTom Navigator (see following code). Line 4 sets the target and TomTom starts the route calculation - if there is a valid GPS position. The problem I noticed is that TomTom 3 never has a valid position after execution of the SDK function. I always get a dialog box "Invalid GPS Position - select starting point: last valid gps/middle of map/..." This happens no matter whether TomTom starts up, is already running, is in map view, ... Previous versions of TomTom would just wait for a valid GPS position without asking the user for any help. That's my desired behaviour. One solution I found is line 3: give TomTom some time to (re)aquire the GPS position. My questions are: Has anyone else observed this problem? Is there another (faster :wink: ) solution? Line 1: CTomTomNavigatorCom::TryCloseCurrentOpenedDialogs(); Line 2: CTomTomNavigatorCom::SendDirectCommand(CTomTomNavigatorCom::KCommandAutoRecalcOff); CTomTomNavigatorCom::SwitchToNavigatorView(); Line 3: Sleep(3000); Line 4: c = CTomTomNavigatorCom::NavigateToCoordinate((long)(x*1E6),(long)(y*1E6),name); Line 5: CTomTomNavigatorCom::TryCloseCurrentOpenedDialogs();
Polaris Benchmark Thread
So, i thought it would really good if we could compare our devices and help each other get more performance out of them. The aim of this thread is to see from ground up what tweaks and changes actually help improve the performance of our devices. Below i will list some methods of benchmarking i've looked up, and we all can contribute by testing our devices with the benchmark methods and help others reach the same results in the process by listing the ROM / tweaks you have used. I'll post the first benchmark myself to help us compare to it. Ill also explain a bit more in my second post so you might have to wait for me to finish things. For accurate results close all background applications and alarms before performing these tests. Benchmarking Methods: 1)D3D Demo: This is from the 3D Driver Tools provided by the 3D Driver development team, all i've done is separated them into seperate CAB's. You can find them in the attachments. Wait for the first example to see the format for displaying your benchmarks. 2)Lights 3D: Same as above, but since this one doesnt display the FPS like D3D Demo we rate the smoothness of it from 1-10 or one of the developer can supply us with a modified one to display the FPS. *hinthint* 3)Text 3D: Same as above. 4)Triangle GL: Same as above. 5)Video Decompression Benchmarking: Alright so i found this on one of the forums i go to but can't remember where so i don't take credit for it. What we will do here is test the CPU for its decompression speed using the same video in different encoding. The Video is part of the Movie Iron Man. To test this we will use Core Player and its probably a good idea to use the same version so lets use the latest v1.32. All you have to do is play the 4 files (1 by 1) provided in attachments on your device in CorePlayer and goto Menu > Tools > Benchmark and let it play. Then note down the 'Average Speed' and move on to the next video. 6)SPB Benchmark v1.6: Now i know not everyone can use every benchmark method here because these tools are not free. So just test whatever you can. SPB Benchmark basically tests everything from Read / Write Speed to applications usage to Battery and Network and CPU stress. Let just try to test whatever you think can benefit the community. I will although start by testing The 'Main' Group and the 'Storage Card' Group. The result are recorded and can be sync to your PC so you can easily copy paste it here. I will explain a bit more in the next post. 7)PocketPC Mark v1.03: This one is also somewhat similar to the above as it tests basically most of the hardware on stress levels, i will tell you how in the next post. 8)GLBenchmark v1.0: This is the only one i found if you have the other versions you can PM me and i'll add them here (1.1 or 2.0). Thats all the methods i could find if you have any more let me know, and any suggestions or comments don't hesitate to comment here. Wait for my second post to start comparing. Regards, Lord Meshadieme I can't seem to attach the video benchmark files, so i'll upload them. Below are the links: Video 1 Video 2 Video 3 Video 4
Ok, sorry for the delay its hard for me during the weekdays to do anything because of university and job. So below is the format and guidelines for posting your benchmarks. Benchmark 1: Device: HTC Polaris (Touch Cruise) CPU: Qualcomm MSM7200 @ 400Mhz Memory: 256MB ROM, 128MB RAM, 4GB Sanyo MSD ROM:RUU_Polaris_HTC_Asia_WWE_3.18.457.0_radio_sign_25.85.30.07_1.59.42.15 Notes:So i decided to post the first benchmark using the default HTC ROM without any tweaks to compare the actual improvements from it. Tweaks:None Benchmarks: 1)D3D Demo: Average FPS: 3.0 FPS @ 5 Mins This tools displays the FPS on the top left part of the screen so to to benchmark just run the tools for a period of time i used 5 minutes, and note down as many speeds as you can and try to average it out. I did this mostly in my head since the value didn't fluctuate to high or low. 2)Lights 3D: FPS Smoothness Rating: 1/10 Unfortunately this tool doesn't display the FPS, so we rate the smoothness of the FPS from a scale of 1 to 10. It gave alot of errors due to the missing driver but it did work but barely got even 1 FPS if i am assuming correctly. 3)Text 3D: Clearness Rating: 0/10 (N/A) Same as above but this time without drivers it doesn't display 3D at all so i can't rate it all though my second bench will include the drivers we can compare from there. 4)Triangle GL: FPS: (N/A) Same as above but this time without drivers it doesn't play at all so i can't rate it all though my second bench will include the drivers we can compare from there. 5)Video Decompression Benchmarking: Video 1 Average Speed: 222.09% Video 2 Average Speed: 114.72% Video 3 Average Speed: 166.7% Video 4 Average Speed: 60.54% So basically just run the four video's in CorePlayer 1.23 one by one and goto Menu > Tools > Benchmarking.. and Note down the 'Average Speed:' from each video's results. 6)SPB Benchmark v1.6: SPB Benchmark Index: 551.77 CPU Index: 1231.79 File System Index: 258.38 Graphic Index: 4918.45 Active Sync Index: 6410.58 We start by testing the 'Main', 'Storage Card', 'Active Sync' Benchmark modes You may compare battery if you like but the test requires you to complete a battery cycle and has minimum affect from tweaks and optimizations to my knowledge. Pocket Word is not compatible with this version or something so its better to not test for it. This test uses Pocket Internet Explorer so we have to disable Opera as the default browser, to do that just open Opera and deselect it as the default browser in settings. The test results can viewed on your computer so you can open it on your PC and use the SPB Benchmark Manager tool, goto Visualize results, copy paste the details from the first table showing the index scores like displayed above. 7)Pocket PCMark v1.03: CPU Dhrystone: 1.20.94 MIPS CPU Whetstone: 5.34 MWIPS Memory: 374.76 Points Memory Latency: 86.03 Points File System: 492.95 Points Storage Cards: 135.08 Points Graphics: 87.19 Points So for PCmarks select each test one by one and note down the results of 'Current Device:' as above. There is a problem with clicking the icons for the test it doesn't work normally but on some clicks it works, i can't seem to point out why if you do let me know but it takes awhile to get all of them clicked. When they are click the screen hangs without any notification that the test is running sometimes, so just wait until its done (Pressing Next in the result screen helps you start the next test easier). The Graphic Test gave some kind of crash is any ppc guru aware of the application gwes.exe? it crashed twice. 8)GLBenchmark v1.0: We'll this test cannot be run under this case because of the 3D Driver problem. So wait for the Second Benchmark for the rest. Basically what you do is test the benchmark upload to a username, and check the website for the results. Updated 19/5 Benchmark 2: Device: HTC Polaris (Touch Cruise) CPU: Qualcomm MSM7200 @ 400Mhz Memory: 256MB ROM, 128MB RAM, 4GB Sanyo MSD ROM:RUU_Polaris_HTC_Asia_WWE_3.18.457.0_radio_sign_25.85.30.07_1.59.42.15 Notes:So now the second benchmark will be with the 3D Drivers installed thanks to our developers. Please Note some of the benchmark tools from the 3D Driver don't exit properly so make sure close them before trying another benchmark. I actually suggest soft resetting after using them they seem to slow down my Device. Tweaks:3D Driver Added. Benchmarks: 1)D3D Demo: Average FPS: ?? FPS FPS Smoothness Rating: 7/10 (Somewhat slower when touch screen is pressed) The FPS didn't display on the top left part of the screen anymore so i rated it on a scale of 1 to 10, i suspect one of the developers can help fix this eventually same for the other tools. 2)Lights 3D: FPS Smoothness Rating: 5/10 3)Text 3D: Clearness Rating: 1/10 Although it works but the 3D text is not at all clear. 4)Triangle GL: FPS: 311 FPS @ 2 mins (N/A) The Second Screen (tap the triangle after a some minutes to get to the next screen) it will tell you the FPS to note down for this. 5)Video Decompression Benchmarking: Video 1 Average Speed: 221.35% Video 2 Average Speed: 117.86% Video 3 Average Speed: 167.3% Video 4 Average Speed: 60.04% Whats interesting here, the 3D drivers seem to have little to no effect on the frame rate but did seem to have visual effect on the decoding progress, i noticed a lot of lag in the videos although the frame rate was okay it seemed to be skipping frames (mainly in the 2nd, and audio is out of sync in the 1st, 4th and 3rd). Maybe some the of developers can look into this and improve upon the drivers. This is exactly why i made this topic to help find ways to test the device and tweaks to find out what causes it to tick. 6)SPB Benchmark v1.6: SPB Benchmark Index: 553.42 CPU Index: 1249.32 File System Index: 258.38 Graphic Index: 4796.72 Active Sync Index: 6410.58 Somewhat also awkward the Graphic index dropped, and the CPU index rose, could help if the developers research the Graphic tests performed in this software and use it. Note that i only tested the Graphics and Image related tests. 7)Pocket PCMark v1.03: CPU Dhrystone: 1.20.94 MIPS CPU Whetstone: 5.34 MWIPS Memory: 374.76 Points Memory Latency: 86.03 Points File System: 492.95 Points Storage Cards: 135.08 Points Graphics: 87.34 Points Not much of a Significant difference which would probably fluctuate anyway. Note that i only tested the Graphics Test. 8)GLBenchmark v1.0: 3D Rendering Quality: Bilinear Filter : 95% (Success) 3D Rendering Quality: Perspective Correction : 100% (Success) 3D Rendering Quality: Sub Pixel Precision : 95% (Success) 3D Rendering Quality: Trilinear Filter : 89% (Fail) 3D Rendering Quality: Z-buffer Precision : 99.1% (Success) CPU Performance: Float : 546 CPU Performance: Integer : 5792 Fill Rate: Multi-Textured, 2x2 : 16097 kTexels/s Fill Rate: Multi-textured, 4x2 : 18248 kTexels/s Fill Rate: Single-textured, 4x1 : 26757 kTexels/s GLBenchmark HD ES 1.0 : 1372 Frames GLBenchmark HD ES 1.1 : Failed / Not supported GLBenchmark Pro ES 1.0 : 77 Frames GLBenchmark Pro ES 1.1 : Failed / Not supported Lights: Ambient x 1 : 102160 Triangles/s Lights: Omni x 1 : 41885 Triangles/s Lights: Parallel x 1 : 103181 Triangles/s Lights: Parallel x 2 : 2385436 Triangles/s Lights: Parallel x 4 : 2363982 Triangles/s Lights: Parallel x 8 : 2262844 Triangles/s Lights: Spot x 1 : 42907 Triangles/s Swapbuffer speed : 2027 Texture Filter: LINEAR : 2391565 Triangles/s Texture Filter: LINEAR_MIPMAP_LINEAR : 2309837 Triangles/s Texture Filter: LINEAR_MIPMAP_NEAREST : 2395652 Triangles/s Texture Filter: NEAREST : 2251606 Triangles/s Texture Filter: NEAREST_MIPMAP_LINEAR : 2391565 Triangles/s Texture Filter: NEAREST_MIPMAP_NEAREST : 2396673 Triangles/s Texture Size: 1024x1024 : 2398716 Triangles/s Texture Size: 128x128 : 2390544 Triangles/s Texture Size: 256x256 : 2397695 Triangles/s Texture Size: 512x512 : 2400760 Triangles/s Texture Size: 64x64 : 2376241 Triangles/s Triangles: Flat Shaded + Color : 2415062 Triangles/s Triangles: Smooth Shaded + Color : 2414040 Triangles/s Triangles: Textured : 2389522 Triangles/s Triangles: Textured + Color : 2384414 Triangles/s So just goto 'Your Results' after logging in and copy paste the main results. I feel their can be alot more improvements in the drivers, lets hope our developers can do it for us. Thats it for now. Regards, Lord Meshadieme
how to get the scores to compare the benchmarks?
Updated, sry for the delay.
Updated with the 2nd Benchmark, I believe we can start comparing different ROMs and what they are better for so its time for the community to pitch in! Is this worthy of a sticky? Moderator.
The idea is interresting. Also comparing Energy use of different ROMs might be interresting.
Battery usage would also be a good comparison, i know of only 2 apps that give something like that, Pocket Battery Analyzer and one of the above mentioned SPB Benchmark has a battery selection but it will work once the battery has completely discharged once, plus the fact that a single comparison can become invalid because battery wear levels vary based on the usage of it.
Benchmark 3: Device: HTC Polaris (Touch Cruise) CPU: Qualcomm MSM7200 @ 400Mhz Memory: 256MB ROM ROM: M-Anime 2.0, Radio 1.59.42.23 Notes: Installed HTC-CA drivers after flashing ROM, required to take full advantage of drivers, plus Gfboost installed and working. Benchmarks: 1)D3D Demo: Average FPS: NA FPS Smoothness Rating: 10/10 (1/3 slower when touch screen is pressed, still smooth, read touch.dll thread) It doesn't display FPS, if you have problems closing the program, use attached tooglestart.exe before running D3Ddemo to hide taskbar and show X. 2)Lights 3D: FPS Smoothness Rating: 10/10 3)Text 3D: Clearness Rating: 0/10 It runs but the 3D text is not readable at all. 4)Triangle GL: 244 FPS @ 2 mins smoothness 10/10 5)Video Decompression Benchmarking: Video 1 Average Speed: 242.95% Video 2 Average Speed: 103.29% Video 3 Average Speed: 152.65% Video 4 Average Speed: not tested/broken link. I didn't test it with Qtv mode as it already uses accelerated mode more, it may break Gfxboost; I tested it using directdraw. As this is a 2D test, 3D drivers won't help much by itself, here Gfboost show it's muscles, read my post on Polaris 3D Driver Development Project thread, all three test do render without skipping frames, video/audio slighty desynced in 2nd and 3rd test. I don't get the idea of testing video or bitrates that are not adapted for PocketPC devices, they won't usually work fine as demostrated in 2nd and 3rd test, people should convert it before use, I use 320x240 H264 at 250kbps and stereo LE-AAC at 48kbps in mp4 container (Coreplayer still doesn't support HE-ACC), that's enough quality for the device. 6)SPB Benchmark v1.6: SPB Benchmark Index: Insufficient tests done CPU Index: 1552.28 File System Index: Not done Graphic Index: 4159.65 Active Sync Index: Not done 7)Pocket PCMark v1.03: CPU Dhrystone: 118.43 MIPS CPU Whetstone: not tested Memory: not tested Memory Latency: not tested File System: not tested Storage Cards: not tested Graphics: System hangs, test won't complete. Sad, because it seems to be a pure 2D test and I should get higher scores. 8)GLBenchmark v1.0: 3D Rendering Quality: Bilinear Filter : 95% (Success) 3D Rendering Quality: Perspective Correction : 100% (Success) 3D Rendering Quality: Sub Pixel Precision : 95% (Success) 3D Rendering Quality: Trilinear Filter : 89% (Fail) 3D Rendering Quality: Z-buffer Precision : 99.1% (Success) CPU Performance: Float : 546 CPU Performance: Integer : 5792 Fill Rate: Multi-Textured, 2x2 : 16097 kTexels/s Fill Rate: Multi-textured, 4x2 : 18248 kTexels/s Fill Rate: Single-textured, 4x1 : 26757 kTexels/s GLBenchmark HD ES 1.0 : 1372 Frames GLBenchmark HD ES 1.1 : Failed / Not supported GLBenchmark Pro ES 1.0 : 77 Frames GLBenchmark Pro ES 1.1 : Failed / Not supported Lights: Ambient x 1 : 102160 Triangles/s Lights: Omni x 1 : 41885 Triangles/s Lights: Parallel x 1 : 103181 Triangles/s Lights: Parallel x 2 : 2385436 Triangles/s Lights: Parallel x 4 : 2363982 Triangles/s Lights: Parallel x 8 : 2262844 Triangles/s Lights: Spot x 1 : 42907 Triangles/s Swapbuffer speed : 2027 Texture Filter: LINEAR : 2391565 Triangles/s Texture Filter: LINEAR_MIPMAP_LINEAR : 2309837 Triangles/s Texture Filter: LINEAR_MIPMAP_NEAREST : 2395652 Triangles/s Texture Filter: NEAREST : 2251606 Triangles/s Texture Filter: NEAREST_MIPMAP_LINEAR : 2391565 Triangles/s Texture Filter: NEAREST_MIPMAP_NEAREST : 2396673 Triangles/s Texture Size: 1024x1024 : 2398716 Triangles/s Texture Size: 128x128 : 2390544 Triangles/s Texture Size: 256x256 : 2397695 Triangles/s Texture Size: 512x512 : 2400760 Triangles/s Texture Size: 64x64 : 2376241 Triangles/s Triangles: Flat Shaded + Color : 2415062 Triangles/s Triangles: Smooth Shaded + Color : 2414040 Triangles/s Triangles: Textured : 2389522 Triangles/s Triangles: Textured + Color : 2384414 Triangles/s As this is a pure 3D test no surprise I get similar results as Lord Meshadieme. Battery usage testing is highly subjective, there are no two people that use the phone the same way and even if they do, there are other external factors that affect battery life like signal strength, etc, I don't think is a good idea to go ahead with it.
Video 4 Link Updated
(Q) Windows phone 7 secrets by Paul Thurrott
I managed to get hold of a book on Amazon called Windows phone 7 secrets by Paul Thurrott. I was just interested to see if anyone else has read it? I found it to be a good read and it has taught me quite a few things about WP7 that i didn't know. Best of all it tells you why Windows phones are MILES better than the Iphone 4!! You should all have a read if your into WP7. Its a good book (and i usually don't read books)
adamlayzell69 said: I managed to get hold of a book on Amazon called Windows phone 7 secrets by Paul Thurrott. I was just interested to see if anyone else has read it? I found it to be a good read and it has taught me quite a few things about WP7 that i didn't know. Best of all it tells you why Windows phones are MILES better than the Iphone 4!! You should all have a read if your into WP7. Its a good book (and i usually don't read books) Click to expand... Click to collapse Could you please make a summary of that book? Most of us know why it's going to be equal or better from android and iOS, it's because of the tools the sdk the programming language and the ease of converting or modifying existing windows applications to run on wp7 with little effort, plus the fact that there are tons of developers that they already know the programming language.
Contents. telas said: Could you please make a summary of that book? Most of us know why it's going to be equal or better from android and iOS, it's because of the tools the sdk the programming language and the ease of converting or modifying existing windows applications to run on wp7 with little effort, plus the fact that there are tons of developers that they already know the programming language. Click to expand... Click to collapse Here are a summary of the contents if it helps??! Contents Introduction xvii Chapter 1 3 Pre-Flight Checklist: What to Do Before You Get Your Windows Phone. Windows Live ID: One Online ID to Rule Them All 2 Using Windows Live ID to Access Your Social Networks and Other Services 11 Picking a Phone 25 Summary 32 Chapter 2 3 Unboxing and Getting Started 33 Unboxing Your Windows Phone 34 Windows Phone Usage 52 Summary 64 Chapter 3 3 Understanding the Windows Phone User Interface 65 The Way We Were: How Microsoft Screwed Up Mobile So Bad It Had to Start Over from Scratch 66 A New Beginning: Metro 69 Real-World Metro: A Whirlwind Tour of the UI 82 Hubs and Applications 86 Summary 100 Chapter 4 3 You and Your Friends: How to Connect with Others, Connect to the World103 Managing Your Digital Persona 104 Being a People Person: Managing Your Family, Friends, and Other Contacts 108 Configuring the People Hub 120 xiv Contents Chapter 5 3 Digital Memories: Using the Pictures Hub and Camera123 Using the Pictures Hub 124 Taking Pictures and Videos with the Camera 127 Moving Photos Between the Phone and Your PC 136 Sharing Photos and Customizing Your Phone 143 Configuring Pictures Hub Options 148 Summary 149 Chapter 6 3 Zune to Go: Music + Videos 151 Using the Zune PC Software with Windows Phone 152 Enjoying Music and Video Content on Windows Phone 165 Why Zune Is Different 182 More Music: Pandora and Other Services 186 Summary 187 Chapter 7 3 Having Fun: Windows Phone and Games 189 Windows Phone: Great Mobile Gaming Platform 190 Understanding Xbox Live 194 Xbox Live on Windows Phone: Not the Full Meal Deal 200 Using the Games Hub 202 Playing a Game 206 Finding More Games in the Marketplace 207 Summary 209 Chapter 8 3 Browsing the Web 211 A (Short) History of the Mobile Web 212 Using Internet Explorer on Windows Phone 214 Configuring Internet Explorer 232 Summary 235 Chapter 9 3 Searching on the Go with Bing 237 Bing: A Different Way to Search 238 Using Bing 244 Configuring Bing 265 Summary 265 Contents xv Chapter 10 3 Managing E‑mail on the Go 267 Push It: A Look at Mobile E‑mail 268 Understanding Accounts and E‑mail 269 Using Mail 273 Configuring Mail and E‑mail Accounts 292 Summary 294 Chapter 11 3 Tracking Your Schedule with Calendar 295 Connected Calendars 296 Glancing at Your Schedule on the Go 303 Using Calendar 305 Working with Appointments and Reminders 309 Configuring Calendar 315 Summary 316 Chapter 12 3 Getting Work Done on the Go with Office Mobile 317 Introducing the Tiniest Member of the Office Family 318 What You Can—and Can’t Do—with Office Mobile 320 Using the Office Hub 322 Accessing Online Documents 341 Configuring Office Mobile 351 Summary 352 Chapter 13 3 Making Calls and Using Voicemail 353 Configuring Contacts Accounts 354 Making and Receiving Phone Calls 355 Using Voicemail 367 Working with Bluetooth 368 Configuring Phone and Voicemail 370 Summary 375 Chapter 14 3 Text and Multimedia Messaging 377 Understanding Mobile Messaging 378 Messaging on Windows Phone 380 xvi Contents Configuring Messaging 389 Beyond Messaging 390 Summary 391 Chapter 15 3 Digging Deeper into Phone Configuration 393 Configuring What Happens When the Phone Is Locked 394 Configuring Sounds 397 Using Windows Phone on an Airplane 399 Configuring Accounts 400 Making Region and Language Configuration Changes 404 Wi-Fi Sync 405 Nuke It from Space and Start Over 407 Summary 409 Chapter 16 3 PC and Web Integration 411 You Can’t Get There from Here 412 Browsing and Buying in the Marketplace 412 Windows Phone on the Web 420 Updating Windows Phone 430 Summary 431 Index 433
400+ pages on the WP7 im impressed, think i might take a gander i sure as hell couldnt write 400+ pages on it so there must be something i dont know about it in there! Cheers
...Damn... There's a lot of reading there!
If you go to Google Books http://books.google.co.uk/books?id=...s by Paul Thurrott&pg=PP1#v=onepage&q&f=false you can view it there. There are a couple of pages missing though.
http://windowsphonesecrets.com/
neilarmes said: If you go to Google Books http://books.google.co.uk/books?id=...s by Paul Thurrott&pg=PP1#v=onepage&q&f=false you can view it there. There are a couple of pages missing though. Click to expand... Click to collapse I did have a look but there is over half the book missing.
[Updated title] Judge rules Galaxy/SGS2 violate patent. Easy fix coming from Sammy
http://www.engadget.com/2011/08/24/netherlands-judge-rules-that-samsung-galaxy-s-s-ii-violate-appl/ http://www.samfirmware.com/apps/blog/show/8211353-breaking-news-apple-wins-samsung-lost- I wonder what this means for SGS2's future in the U.S.? What are the reasons: EP 2.058.868 (Scrolling gallery) EP 2.098.948 (Picking UP the phone.) EP 1.964.022 (Lock screen) Patent system needs a complete redo. All in all, turned out to be a win for Samsung.
mattykinsx said: http://www.engadget.com/2011/08/24/netherlands-judge-rules-that-samsung-galaxy-s-s-ii-violate-appl/ http://www.samfirmware.com/apps/blog/show/8211353-breaking-news-apple-wins-samsung-lost- I wonder what this means for SGS2's future in the U.S.? What are the reasons: EP 2.058.868 (Scrolling gallery) EP 2.098.948 (Picking UP the phone.) EP 1.964.022 (Lock screen) All minor software concerns too. Sad. Patent system needs a complete redo. Click to expand... Click to collapse Lmao nice so much for Sept 9th Sent from my PC36100 using XDA Premium App
Glad I don't live in the Netherlands.
Actually the engadget article may have it wrong, scrolling through the comments there are a number of dutch speaking posters who claim the only patent infringed is the one for scrolling. This actually appears like a big win for sammy as they have tossed the other two patents. Further it is apparent the "look and feel" issue was thrown out. http://fosspatents.blogspot.com/ Big hit for android tho, as that gallery app is shipped on most android devices with the exception of sense and the SE gallery iirc.
I was quoting the samfirmware website for the three patents.
The Galaxy Tab wasn't banned, so Apple loses...
This is a non-victory for Apple. The patent only affects the gallery. Samsung has already stated that they'll simply replace the Gallery app with another one. Sales won't be interrupted one bit. The two other patents as well as the design stuff was thrown out. The patent is of course ridiculous, but that's nothing new in the world of software patents. Too bad I don't understand Dutch to read the court order: http://ieforum.nl/backoffice/upload...1-730, KG ZA 11-731 (Apple tegen Samsung).pdf (yes, that's a valid link)
COURT IN THE HAGUE Civil Law Judgement interim order of August 24, 2011 (in advance) in the case with case number / docket number: 396957 / KG ZA 11-730 of the legal entity under foreign law APPLE INC.., based in Cupertino, California, USA, Plaintiff, Lawyer: Mr. P.J.M. von Schmidt auf Altenstadt in The Hague, against 1. the company under foreign law SAMSUNG ELECTRONICS CO., LTD. LIMITED, located in Suwon City, Kyungki-Do, South Korea, 2. The private company with limited liability Samsung Electronics Benelux BV, established in Delft, 3. The private company with limited liability SAMSUNG ELECTRONICS LOGISTICS EUROPE BV, located in Rijswijk, 4. The private company with limited liability SAMSUNG ELECTRONICS OVERSEAS BV, established in Amsterdam, Defendants, Lawyer: Mr. B.J. Berghuis Woortman of Amsterdam, and in the case with case number / docket number 396959 / KG ZA 11-731 of the foreign law APPLE INC.., based in Cupertino, California, USA, Plaintiff, Lawyer: Mr. P.J.M. von Schmidt auf Altenstadt in The Hague, against 1. the company under foreign law SAMSUNG ELECTRONICS CO., LTD. LIMITED, located in Suwon City, Kyungki-Do, South Korea, 2. The private company with limited liability Samsung Electronics Benelux BV, established in Delft, 396957 / KG ZA 11-730 and 396959 / KG ZA 11-731 August 24, 2011 2 3. The private company with limited liability SAMSUNG ELECTRONICS LOGISTICS EUROPE BV, located in Rijswijk, 4. The private company with limited liability SAMSUNG ELECTRONICS OVERSEAS BV, established in Amsterdam, Defendants, Lawyer: Mr. B.J. Berghuis Woortman of Amsterdam. The treated cases were joined. The parties will hereinafter Apple (plaintiff) and Samsung (Collectively defendants) are named. For Apple, the cases handled by mr R.M. Kleemans, mr ir T.M. Blomme and mr A.A.A.C.M. van Oorschot, all lawyers Amsterdam. Samsung Cases handled by Mr. Berghuis of Woortman, said, and Mr. A. F. Kupecz, Mr. Ch. Gielen and Mr. R.C. of Oerle, also all lawyer in Amsterdam. 1. The procedure 1.1. The course of the proceedings appears in: - The summons of 27 June 2011; - Productions 1 to 24 (KG ZA 11-730) and exhibits 1 to 30 (KG ZA 11-730) Apple; - In both cases: statements of defense and including counter-claim, on July 20 Samsung 2011, with exhibits 1 to 21 (KG ZA 11-730) and exhibits 1 through 34 (KG ZA 11-731); - The letter of July 21, 2011 Apple, which Apple objects to the requirements counterclaim, and the response by letter dated July 22, 2011 by Samsung; - The email of July 22, 2011, which the judge makes his decision requirements that the counterclaims in both cases will not be treated as - briefly said - they were contrary to a due process; - The notes to productions of Samsung mailed by July 25, 2011; - The letter of August 3, 2011 by Samsung, with additional production 22 to 47 (KG ZA 11-730) and additional production 35 to 59 (KG ZA 11-731); - On July 28, 2011 letter received from Apple, with additional production 31 to 44 (In both cases), in which Apple's claims on Community Design 1260624-15 withdraws; - The bookmark (with respect to the soft IP) Samsung sent by email 2 August 2011; - The bookmark (in respect of the prior art for patents) sent by Samsung email from August 4, 2011; - The letter of August 5, 2011 Apple, with additional production 45; - The letter of August 8, 2011 by Samsung, with additional production 60 to 66; - The letter of August 8, 2011 Apple, with additional production 46 to 50; - The letter of August 9, 2011 by Samsung, with additional production 67; - The email of August 9th, 2011 Apple, with additional production 51; - The hearing held on 10 and 11 August 2011, on the occasion whose lawyers have submitted pleadings. 396957 / KG ZA 11-730 and 396959 / KG ZA 11-731 August 24, 2011 3 1.2. By email from the August 10 hearing and documents are as out of time denied. Furthermore, both in court and again on a provisional claim submitted. After consideration, the parties have indicated this further consultation to this issue. This consultation has resulted in the provisional claims need not be decision, as communicated by email from Mr. Kleemans of August 12, 2011. 1.3. Sentence is determined by September 15, 2011 but will now advance to be pronounced. 2. Facts 2.1. Apple is a global developer and manufacturer of computers, consumer electronics, operating systems and software. Its products include more the iPhone, a smartphone called, and the iPad, a tablet computer. Both Apple products are in different versions on the market. 2.2. Apple is the proprietor of European patent EP 2059868 (hereafter EP 868) for a "Portable Electronic Device for photo management", issued on September 29, 2010 application of 31 August 2007, claiming priority under seven U.S. patent applications: U.S. 824769 P (September 6, 2006), U.S. 883785 P (January 6, 2007), U.S. 879 253 P (7 January 2007), U.S. 879469 P (January 8, 2007), U.S. 937 993 U.S. 947 118 P and P (Both June 29, 2007) and U.S. 848210 (30 August 2007). Netherlands is one of the gedesigneerde countries. Against the grant of EP 868 is the time to sue no opposition. 2.3. The claims of EP 868 are in the original English language: 1. A computer-implemented method, comp rising: at a device (100) with a touch screen (112): detecting (2402) a first movement (2310) or a physical object on or near the touch screen Display (112); while detecting the first movement (2310), Translate (2404) a first digital object (2300-1) indication, on the touch screen (112) in a first direction, wherein the first digital object (2300-1) was associated with a set of digital objects, characterized in that: In response to display of a Previously Hidden Edge (2312) of the first digital object (2300 - 1) and continued detection of the first movement (2310), displaying (2406) an area (2314) Beyond the Edge (2312) of the first digital object (2300 - 1); After the first movement (2310) is no longer detected, translate (2408) the first digital object (2300-1) in a second direction (2316) Until The area (2314) Beyond the Edge (2312) of the first digital object (2300-1) is an indication, no longer; detecting (2410) a second movement (2318) or the physical object on or near the touch screen display (112), and In response to detecting the second movement (2318) Previously hidden while the edge (2312) of the first digital object (2300-1) is an indication,, translate (2412) the first digital object (2300-1) in the first direction and displaying a second digital object (2300-2) in the set of digital objects. 396957 / KG ZA 11-730 and 396959 / KG ZA 11-731 August 24, 2011 4 2. The computer-implemented method of claim 1, wherein, prior to the Translating while detecting the first movement, at least one edge of the first digital object extends beyond the touch screen in the first direction. 3. The computer-implemented method of claim 1 or 2, wherein the first movement is a horizontal swipe gesture. 4. The computer-implemented method of any one of claims 1 to 3, wherein the set of digital Objects is a set of digital images, a set of web pages, or a set of electronic documents. 5. The computer-implemented method of any one of claims 1 to 4, wherein the device is a portable electronic device. 6. The computer-implemented method of any one of claims 1 to 5, wherein the physical object a finger or a stylus. 7. A computer program with software code adapted to perform the method of any one of claims 1 to 6. 8. An electronic device (100), comp rising: a touch screen (112); One or more processors (120); Memory (102), and a program, wherein the program is stored in the memory and configured to be executed by the One or more processors, the program Including: instructions for detecting (2402) a first movement (2310) or on a physical object or near the touch screen (112); instructions for, while detecting the first movement (2310), Translate (2404) a first digital object (2300-1) indication, on the touch screen (112) in a first direction, wherein the first digital object (2300-1) was associated with a set of digital objects; characterized in that: instructions for, in response to display of a Previously Hidden Edge (2312) of the first digital object (2300-1) and continued detection of the first movement (2310), displaying (2406) an area (2314) Beyond the Edge (2312) of the first digital object; instructions for, after the first movement (2310) is no longer detected, Translate (2408) the first digital object (2300-1) in a second direction (2316) Until The Area (2314) beyond the edge of the first digital object (2300-1) is an indication, no longer; instructions for detecting (2410) a second movement (2318) or the physical object on or near the touch screen (112), and instructions for, in response to detecting the second movement (2318) Previously hidden while the Edge (2312) of the first digital object (2300-1) is an indication,, translate (2412) the first digital object (2300-1) in the first direction and displaying a second digital object (2300-2) in the set of digital objects. 9. The electronic device of claim 8, wherein, prior to the Translating while detecting the first movement, at least one edge of the first digital object extends beyond the touch screen display in the first direction. 396957 / KG ZA 11-730 and 396959 / KG ZA 11-731 August 24, 2011 5 10. The electronic device of claim 8 or 9, wherein the first movement is a horizontal swipe gesture. 11. The electronic device of any one of claims 8 to 10, wherein the set of digital objects is a set of digital images, a set of web pages, or a set of electronic documents. 12. The electronic device of any one of claims 8 to 11, wherein the device is a portable electronic device. 13. The electronic device of any one of claims 8 to 12, wherein the physical object is a finger or a stylus. 2.4. The undisputed Dutch translation of EP 868's conclusions: 1. By a computer implemented method, comprising: it in a device (100) with a display (112) Touch screen: detecting (2402) of a first movement (2310) of a physical object on or near the Display (112) touch screen; during the detection of the first movement (2310) Moving (2404) of the Display (112) touch screen with the first digital object (2300-1) in 1 / 1 direction, the first digital object (2300-1) involves a set of digital objects; characterized in that In response to displaying a previously hidden hoek1 (2312) of the first digital object (2300-1) and continued detection of the first movement (2310), an area (2314) appears beyond the edge (2312) of the first digital object (2300-1); after the first movement (2310) no longer detected, the move (2408) of The first digital object (2300-1) in a second direction (2316) until the area (2314) beyond the edge (2312) of the first digital object (2300-1) will no longer appear; detecting (2410) for half movement (2318) of the physical object on or near the Display (112) touch screen, and In response to detecting the second movement (2318) while the corresponding hidden edge (2312) of the first digital object (2300-1) is displayed, the move (2412) the first digital object (2300-1) in the first direction and displaying half digital object (2300-2) in the set of digital objects. 2. By a computer implemented method according to claim 1, wherein, prior to move during detection of the first movement, one edge of the digital object is in the first direction extends past the display with touch screen. 3. By a computer implemented method according to claim 1 or 2, wherein the first a horizontal movement sweeping gesture. 4. By a computer implemented method according to any one of claims 1-3, where the couple a set of digital objects, digital images, a set of web pages or a couple electronic documents. 1 This is a translation error. "A Previously hidden edge" is erroneously translated as "a pre-hidden corner" in Instead of "edge". 396957 / KG ZA 11-730 and 396959 / KG ZA 11-731 August 24, 2011 6 5. By a computer implemented method according to which any of claims 1-4, whereby the device a portable electronic device is. 6. By a computer implemented method according to which any of claims 1-5, where the physical object is a finger or a stylus. 7. Computer software code, designed for carrying out the method according to which any of claims 1-6. 8. Electronic device (100) comprising: a display (112) touch screen; one or more processors (120); a memory (102), and a program where the program is stored in memory and configured order to be executed by one or more processors, where the program includes: instructions for detecting (2402) of a first movement (2310) of a physical object on or near the display (112) touch screen; how to move (2404), while detecting the first movement (2310), 1 / 1 of the display (112) with touch screen digital object (2300-1) in a first direction, the first digital object (2300-1) involves a set of digital objects, characterized by instructions for displaying (2406), in response to display a previously hidden edge (2312) of the first digital object (2300-1) and continued detection of the first movement (2310), an area beyond the edge (2312) of the first digital object; how to move (2408), after the first movement (2310) no longer detected, the first digital object (2300-1) in a second direction (2316) until the area (2314) beyond the edge (2312) of the first digital object (2300-1) are not longer displayed; instructions for detecting (2410) for half movement (2318) of the physical object on or near the display (112) touch screen, and how to move (2412), in response to detecting the second movement (2318) while the corresponding hidden edge (2312) of the first digital object (2300-1) is shown, the first digital object (2300-1) in the first direction and displaying half of the digital object (2300-2) set in the digital objects. 9. Electronic device according to claim 8, wherein, prior to moving in detecting the first motion, one edge of the first digital object in the first direction extends beyond the display (112) touch screen. 10. Electronic device according to claim 8 or 9, wherein the first movement is a horizontal sweeping gesture. 11. Any electronic device according to any of claims 8-10, where the couple digital objects, a set of digital images, a set of web pages or a set of electronic documents. 12. Any electronic device according to any of claims 8-11, whereby the device comprises a portable electronic device is. 396957 / KG ZA 11-730 and 396959 / KG ZA 11-731 August 24, 2011 7 13. Any electronic device according to any of claims 8-12, where the physical object is a finger or a stylus. 2.5. In EP 868 includes images below. 2.6. Apple is also the proprietor of European patent EP 2098948 (hereafter EP 948) for a "touch event model", issued on 9 February 2011 on an application by March 4 2009, by claiming priority of U.S. patent application with U.S. 42381 Date March 4, 2008. Netherlands is one of the gedesigneerde countries. The granting of EP 948 until the moment of summon no opposition. 396957 / KG ZA 11-730 and 396959 / KG ZA 11-731 August 24, 2011 8 2.7. The claims of EP 948 are in the original English text: 1. A method for handling touch events at a multi-touch device (200, 210), comp rising: displaying one or more views (301, 302, 303, 304, 305, 306, 307, 308, 309, 310, 311, 312); executing one or more software elements, software elements being associated Each with a Particular view (301, 302, 303, 304, 305, 306, 307, 308, 309,310,311,312); associate a multi-touch or flag an exclusive touch flag With Each view (301, 302, 303, 304, 305, 306, 307, 308, 309, 310, 311, 312), said multi-touch flag Indicating whether a Particular view is allowed to receive multiple simultaneous touches and said exclusive Indicating whether a flag touch Particular view Allows other views to receive touch events while the view is Particular receive a touch event; Receiving one or more touches at the one or more views (301, 302, 303, 304, 305, 306, 307, 308, 309, 310, 311, 312), and selectively sending one or more touch events, Each touch event-describing a received touch to one or more of the software elements associated with the one or more views (301, 302, 303, 304, 305, 306, 307, 308, 309, 310, 311, 312) at All which was a touch received based on the values of the multi-touch and touch exclusive flags. 2. The method of claim 1, Further comp rising: if a multi-touch flag is associated with a Particular View, allo wing touch other events contemporaneous with a touch event received at the Particular View to be sent to software elements associated with the other views. 3. The method of claim 1, wherein if a multi-touch flag is associated with a Particular View, the Multi-touch flag indicates whether the software element associated with Particular That view is allowed to process multiple contemporaneous touches located in That view. 4. The method of claim 1, wherein the exclusive touch touch events from being Prevents flag presented to software elements associated with views other than a view with an asserted exclusive touch touch a flag while being received at the view with the touch asserted exclusive flag. 5. The method of claim 1, wherein the multi-touch device (200, 210) is a mobile telephone. 6. The method of claim 1, wherein the multi-touch device (200, 210) is a digital media player. 7. The method of claim 1, comp rising: associate a multi-touch flag with a first view; receive a first touch at the first view, the view being one of the first one or more views; sending a touch event-describing the first touch to a first software element, the first software component being one or the one or more software elements and associated with the first view; Determining whether the multi-touch flag associated with the first That view indicates the first view is a multi-touch view, and if the first view is not a multi-touch view, blocking all touch-describing any other events touches located in the first view Until The first touch is no longer received. 396957 / KG ZA 11-730 and 396959 / KG ZA 11-731 August 24, 2011 9 8. The method of claim 7, Further comp rising: associate an exclusive Touch With Each flag or the one or more views; Determining whether the exclusive touch flag associated with the first view indicates That The First View is an exclusive TouchView, and if the first view is an exclusive TouchView, blocking all touch-describing any other events touches located in any view other than the first view Until The first touch is no longer received. 9. The method of claim 8, wherein the first view is not an exclusive TouchView, the method Further comp rising: receive a second touch at the multi-touch panel, touch the second located at a second view and associated with a second software component; Determining whether the exclusive touch flag associated with the second view indicates thats the second view is an exclusive TouchView, and if the second view is an exclusive TouchView, Prevent a touch event associated with the second touch from being sent to the second software element Until The first no-touch longer received. 10. The method of claim 9, Further comp rising: if the second view is not an exclusive TouchView, sending a touch event-describing the second touch to the second software element. 11. A computer readable medium comp rising a plurality of instructions configured for execution at a multi-touch device (200, 210), the instructions being configured to cause the multi-touch device (200, 210) to: Display one or more views (301, 302, 303, 304, 305, 306, 307, 308, 309, 310, 311, 312); execute one or more software elements, software elements being associated Each with a Particular view (301, 302, 303, 304, 305, 306, 307, 308, 309, 310, 311, 312); associate a multi-touch or flag an exclusive touch flag With Each view (301, 302, 303, 304, 305, 306, 307, 308, 309, 310, 311, 312), said multi-touch flag Indicating whether a Particular view is allowed to receive multiple simultaneous touches and said exclusive Indicating whether a flag touch Particular view Allows other views to receive touch events while the view is Particular receive a touch event; receive one or more touches at the one or more views (301, 302, 303, 304, 305, 306, 307, 308, 309, 310, 311, 312), and selectively send one or more touch events, Each touch event received a touch-describing, to one or more of the software elements associated with the one or more views (301, 302, 303, 304, 305, 306, 307, 308, 309, 310, 311, 312) at A Touch All which was received based on the values of the multi-touch and touch exclusive flags. 12. The computer readable medium of claim 11, wherein the instructions are configured to Further cause the multi-touch device (200, 210) to: 396957 / KG ZA 11-730 and 396959 / KG ZA 11-731 August 24, 2011 10 if a multi-touch flag is associated with a Particular View, allo wing touch other events contemporaneous with a touch event received at the Particular View to be sent to software elements associated with the other views. 13. The computer readable medium of claim 11, wherein if a multi-touch flag is associated with a Particular view, the multi-touch flag indicates whether the software element associated with Particular That view is allowed to process multiple contemporaneous touches located in That view. 14. The computer readable medium of claim 11, wherein the exclusive flag Prevents touch touch events from being sent to software elements associated with views other than a view with an asserted exclusive touch flag while a touch is being received at the view with the asserted exclusive touch flag. 15. The computer readable medium of claim 11, wherein the multi-touch device (200, 210) is a mobile telephone. 16. The computer readable medium of claim 11, wherein the multi-touch device (200, 210) is a digital media player. 17. The computer readable medium of claim 11, wherein the instructions are configured to Further cause the multi-touch device (200, 210) to: associate a multi-touch flag with a first view; receive a first touch at the first view, the view being one of the first one or more views; send a touch event-describing the first touch to a first software element, the first software element being one of the one or more software elements and associated with the first view; determining whether the multi-touch flag associated with the first view indicates thats the First View is a multi-touch view, and if the first view is not a multi-touch view, block all touch-describing any other events touches located in the first view Until The first touch is no longer received. 18. The computer readable medium of claim 17, wherein the instructions are configured to Further cause the multi-touch device (200, 210) to: associate an exclusive Touch With Each flag or the one or more views; determining whether the exclusive touch flag associated with the first view indicates thats the First View is an exclusive TouchView, and if the first view is an exclusive TouchView, blocking all touch-describing any other events touches located in any view other than the first view Until The first touch is no longer received. 19. The computer readable medium of claim 18, wherein the first view is not an exclusive touch view and the instructions are configured to cause the Further multi-touch device (200, 210) to: receive a second touch at the multi-touch panel, touch the second located at a second view and associated with a second software component; 396957 / KG ZA 11-730 and 396959 / KG ZA 11-731 August 24, 2011 11 determining whether the exclusive touch flag associated with the second view indicates That the second view is an exclusive TouchView, and if the second view is an exclusive TouchView, Prevent a touch event associated with the second touch from being sent to the second software element Until The first no-touch longer received. 20. The computer readable medium of claim 19, wherein the instructions are configured to Further cause the multi-touch device (200, 210) to: if the second view is not an exclusive TouchView, send a touch event-describing the second touch to the second software element. 21. A multi-touch enabled device (200, 210) including a computer readable medium comp rising a plurality of instructions configured for execution at the device (200, 210), the instructions being configured to cause the device (200, 210) to: Display one or more views (301, 302, 303, 304, 305, 306, 307, 308, 309, 310, 11, 312); execute one or more software elements, software elements being associated Each with a Particular view (301, 302, 303, 304, 305, 306, 307, 308, 309, 310, 311, 312); associate a multi-touch or flag an exclusive touch flag With Each view (301, 302, 303, 304, 305, 306, 307, 308, 309, 310, 311, 312), said multi-touch flag Indicating whether a Particular view is allowed to receive multiple simultaneous touches and said exclusive Indicating whether a flag touch Particular view Allows other views to receive touch events while the view is Particular receive a touch event; receive one or more touches at the one or more views (301, 302, 303, 304, 305, 306, 307, 308, 309, 310, 311, 312), and selectively send one or more touch events, Each touch event-describing a received touch to one or more of the software elements associated with the one or more views (301, 302, 303, 304, 305, 306, 307, 308, 309, 310, 311, 312) at All which was a touch received based on the values of the multi-touch and touch exclusive flags. 22. The multi-touch enabled device (200, 210) or claim 21, wherein the multi-touch enabled device (200, 210) is a mobile telephone. 23. The multi-touch enabled device (200, 210) or claim 21, wherein the multi-touch enabled device (200, 210) is a digital media player. 2.8. The undisputed Dutch translation of EP 948's conclusions: 1. Method for handling touch events on a multi-touch device (200, 210) comprising: displaying one or more images (301, 302, 303, 304, 305,306, 307, 308, 309, 310, 311, 312); performing one or more software elements, each software element associated with a specific image (301, 302, 303, 304, 305,306, 307, 308, 309, 310, 311, 312); associating a multi-touch tag or mark each with an exclusive touch image (301, 302, 303, 304, 305,306, 307, 308, 309, 310, 311, 312), said Multi-touch flag indicates whether a particular image multiple simultaneous touches can 396957 / KG ZA 11-730 and 396959 / KG ZA 11-731 August 24, 2011 12 received this exclusive touch screen or a specific marker indicating the for other images allows to receive touch events while Specific events will receive a touch screen; receiving one or more touches to one or more images (301, 302, 303, 304, 305,306, 307, 308, 309, 310, 311, 312), and selectively send one or more touch events, each touch event received a touch describing to one or more of the software elements associated with one or more images (301, 302, 303, 304, 305,306, 307, 308, 309, 310, 311, 312) a touch which was received based on the values of the multi-touch and exclusive touch marks. 2. Process according to claim 1, further comprising: as a multi-touch marker is associated with a specific image, allowing the simultaneous other manifestations of touch with a touch event received on a specific image to be sent to the software elements associated with other images. 3. Process according to claim 1, wherein a multi-touch marker is associated with en2 specific image, the multi-touch flag indicates whether the software element associated the particular image multiple simultaneous touches can process in that picture are located. 4. Process according to claim 1, wherein the exclusive touch that prevents marker Touch events are sent to the software elements associated with other images than an image with a confirmed exclusive touch, while marking a touch is received at the image me3 mark the confirmed exclusive touch. 5. Process according to claim 1, wherein the multi-touch device (200, 210) a mobile phone. 6. Process according to claim 1, wherein the multi-touch device (200, 210) a digital media player. 7. Process according to claim 1, comprising: associating a multi-touch mark with a first image; receiving a first touch in the first picture, with the first image of a The one or more images is; sending a touch event which describes the first contact to 1 / 1 software element, the first software element of a one or more software elements and is associated with the first image; determining whether the multi-touch marker associated with the first image indicates that the first image is a multi-touch screen, and as the first image has no multi-touch screen, blocking all touch events to Other touches describe localized in the first frame to the first touch is not longer present. Meant 2 will be "one" 3 will be designed "with" 396957 / KG ZA 11-730 and 396959 / KG ZA 11-731 August 24, 2011 13 8. Process according to claim 7, further comprising associating a mark with exclusive touch each of the one or more images; determining whether the touchscreen exclusive marker associated with the first image indicates The first image is an exclusive touch-screen, and as the first picture an exclusive touch screen is blocking all touch events Translated.
One more reason I will never buy an Apple product. "When you can't compete, Sue!" -Apple
snowboarda42 said: One more reason I will never buy an Apple product. "When you can't compete, Sue!" -Apple Click to expand... Click to collapse can't compete? meanwhile back in reality apple is seeing growth from it's already dominating position.
detusueno said: can't compete? meanwhile back in reality apple is seeing growth from it's already dominating position. Click to expand... Click to collapse It is not.. http://www.neowin.net/news/millennial-android-usage-on-the-rise-ios-continues-to-fall
Rejinderi said: It is not.. http://www.neowin.net/news/millennial-android-usage-on-the-rise-ios-continues-to-fall Click to expand... Click to collapse you fail at interpreting. iOS and Android both have seen growth, Android has grown more and has taken more total share from new users but both HAVE grown including iOS. the real world difference is that apple kills all other oems and makes a heck of a lot more profit than any of them. htc doesn't give a damn about samsung, they are competitors just as much apple is.
From a practical standpoint I think it simply means that Samsumg would pay royalties to Apple for all the instances of patent infringement as opposed to actually banning a device. It's actually really smart for Apple to do this simply because it means more revenue for them. james
Ah, the nowadays typical "Apple makes more profits!!" line. So cliched. Yeah, they have high profit margins. So? That doesn't change the fact that they're losing market share. And they're damn afraid of it. Ok, that last one is not exactly a fact, but it is a very reasonable assumption. They're also total hypocrites and that one is a fact. Another fact is that this is actually a loss for Apple. Their community designs have been invalidated. The judge said that one of their patents (the unlock swipe) will be invalidated too. @atypical1: No, Apple is not out for cross-licensing. They really *do* want a ban. But they're not getting it, because the one patent that was upheld can easily be circumvented and won't affect Samsung sales at all.
Gusar321 said: Ah, the nowadays typical "Apple makes more profits!!" line. So cliched. Yeah, they have high profit margins. So? That doesn't change the fact that they're losing market share. And they're damn afraid of it. Ok, that last one is not exactly a fact, but it is a very reasonable assumption. They're also total hypocrites and that one is a fact. Another fact is that this is actually a loss for Apple. Their community designs have been invalidated. The judge said that one of their patents (the unlock swipe) will be invalidated too. @atypical1: No, Apple is not out for cross-licensing. They really *do* want a ban. But they're not getting it, because the one patent that was upheld can easily be circumvented and won't affect Samsung sales at all. Click to expand... Click to collapse Apple has higher profit margins because they have convinced their followers that they are getting 'more' for a laptop that costs $1200 but should be $700. Also, the confirmation that the iPhone 5 is going to be on Sprint and the idea that there may soon be a "cheaper iPhone"...combined with the literally new lawsuit every hour...seems to show how scared they really are.
Who cares Apple just lost this lawsuit they're really ****ting bricks now. Sent from my Nexus S 4G using XDA Premium App
DirtyShroomz said: Who cares Apple just lost this lawsuit they're really ****ting bricks now. Sent from my Nexus S 4G using XDA Premium App Click to expand... Click to collapse http://mashable.com/2011/08/24/samsung-galaxy-phones-netherlands-ban/ Samsung does say that this will not affect sales. The problem with this sort of thing is it sets a precedent.
mattykinsx said: Apple has higher profit margins because they have convinced their followers that they are getting 'more' for a laptop that costs $1200 but should be $700. Click to expand... Click to collapse Name a consumer laptop that is as good as a 15"+ Macbook Pro in design, build quality, support, and performance. Over the last 2 months I returned FOUR (DV6T, XPS 15Z, XPS 17, Envy 17 3D) laptops that are supposed to be some of the best consumer PC laptops at a reasonable price range, and none of them hold a candle to the balance of the Macbook Pro. I paid an average of $1200-$1500 for each of them, they had about equal specs but at the end of the day the $2200-$2400 17" Macbook Pro I'm ordering just offers more.
Award Tour said: Name a consumer laptop that is as good as a 15"+ Macbook Pro in design, build quality, support, and performance. Over the last 2 months I returned FOUR (DV6T, XPS 15Z, XPS 17, Envy 17 3D) laptops that are supposed to be some of the best consumer PC laptops at a reasonable price range, and none of them hold a candle to the balance of the Macbook Pro. I paid an average of $1200-$1500 for each of them, they had about equal specs but at the end of the day the $2200-$2400 17" Macbook Pro I'm ordering just offers more. Click to expand... Click to collapse "design" -- personal preference / opinion "build quality" -- Meh. I know a person who's Macbook screen failed on her[I mentioned that before, I don't know a lot of people with Macbooks]. I've never had a "build quality" issue with any laptop I've ever used. Acer, Dell, Gateway, or Toshiba. "support" -- ? "performance" -- Never had any issues with performance with the Acer laptop I use. However, I know multiple people who's iMacs were complete garbage.
mattykinsx said: "design" -- personal preference / opinion "build quality" -- Meh. I know a person who's Macbook screen failed on her[I mentioned that before]. I've never had a "build quality" with any laptop I've ever used. Acer, Dell, Gateway, or Toshiba. "support" -- ? "performance" -- Never had any issues with performance with the Acer laptop I use. However, I know multiple people who's iMacs were complete garbage. Click to expand... Click to collapse I like the part where you didn't name a single laptop. I spent 2-3 months looking for a Macbook Pro equal and there is none. The closest ones were workstations and for that price you might as well pay for the better design with the Macbook Pro.
1GB free space on Dropbox!
If you complete the dropquest2012 you automatically earn 1GB of extra storage for your dropbox account. Above you can find the answers for all chapters. If you don't have a dropbox account, click here and you'll get 2GB plus 500mb extra storage. Ps: I'm not the one who wrote this tutorial, I just made some improvements and shared it with you guys. If you want to say thanks to someone, say to this guy, all credits for him: http://forum.xda-developers.com/member.php?u=2919411 Answers: Chapter 1 46637 64529 38645 Chapter 2 Go to https://www.dropbox.com/about With each hint, move to a new person like how a chess knight would. ChenLi Wang -> Ramsey H. - > Allison Louie -> Naveen Agrawal -> Emily Zhao https://www.dropbox.com/dropquest2012/crane Chapter 3 SMUDGES Chapter 4 SOMA Chapter 5 MAD LIB Chapter 6 Invert the colours, look at the ones that don't match their text descriptions. Use the M/D/Y and use that date for https://www.dropbox.com/events. Should be one of the following: https://www.dropbox.com/events?ns=false&n=0&d=1-7-2003 https://www.dropbox.com/events?ns=false&n=0&d=3-21-2005 https://www.dropbox.com/events?ns=fa...0&d=11-28-2001 Chapter 7 The letters are in the soundcloud comments, use the legend to figure out the order by converting it to numbers. https://www.dropbox.com/dropquest2012/LEADING https://www.dropbox.com/dropquest2012/DEALING https://www.dropbox.com/dropquest2012/ALIGNED Chapter 8 Triumphant Chapter 9 Rearrange file names: Your next destination is the last page of the tour. Go to https://www.dropbox.com/tour/6 Send an invite to [email protected], [email protected] or [email protected] via https://www.dropbox.com/referrals Chapter 10 Mexico, Argentina or Korea Chapter 11 Southpole Chapter 12 Restore Chapter12.txt to its previous version via https://www.dropbox.com/revisions/Dropquest 2012/Captain's Logs/Chapter 12.txt. Then go to https://www.dropbox.com/help and click on the shield icon of "Security and Privacy". Chapter 14 Re-arrange the slider puzzle according to the highlighted part of the sudoku puzzle (once you solve it). Sudoku solution Use this to help you: http://analogbit.com/software/puzzletools Chapter 15 Share a folder with the email listed on the page (should be the same as in the one you invited in Chapter 9). Then go to https://www.dropbox.com/share and click on the larger rainbow icon next to "Sharing". Chapter 17 Shanghai Chapter 18 Go to https://www.dropbox.com/home/Dropquest 2012/Spring Cleaning Put 1, 3, 6, 8, 9 (.jpg) into Category 1 and 2, 4, 5, 7, 10 into Category 2. If you did this via the desktop app, use the Repair Dropquest Folder link on the lower left corner of the clue page. Chapter 19 For each column, subtract the smaller card value from the larger one http://db.tt/94J964 http://db.tt/72j933 http://db.tt/Q2J9J4 Chapter 20 Ocean's Eleven X-Men: First Class Twenty-One Super 8 28 days later Sixth Sense (just click this link) https://www.dropbox.com/dropquest2012/apollo13 Chapter 21 Abusively Chapter 22: FACED or MACAU or BADGE or BASED or ADAGE chapter 23: machu picchu Endgame: colosseum (just type the word at the end of the page) Try this google docs if you're stuck: https://docs.google.com/document/d/1...sle=true&pli=1 __________________
Re-arrange the slider puzzle according to the highlighted part of the sudoku puzzle (once you solve it). seriously man, i know i am being spoon fed but i am not able to figure out this line...cant even understand what it means and it is there is every tut!! what should i do ---------- Post added 19th May 2012 at 12:11 AM ---------- Previous post was 18th May 2012 at 11:36 PM ---------- for anyone after me: just click on the number adjacent to the box below the sudoko and the blank box moves. i hope you have solved your sudoko. now match the box below by moving the numbers to match the highlighted sudoko box.
i used this for the sudoku part: http://www.sudoku-solutions.com/ ---------- Post added at 04:59 PM ---------- Previous post was at 04:35 PM ---------- also: http://www.dropboxguide.com/bonusspace/dropquest/detailedsolution