[APP][4.04+] OBackup - BUG FIXED, BACK ON PLAY STORE [07/21/2013]

Which Cloud network do you use / want to use?

  • Box.com

    Votes: 23 22.3%
  • SkyDrive

    Votes: 4 3.9%
  • Sugarsync

    Votes: 1 1.0%
  • Other? (post which one)

    Votes: 3 2.9%
  • I am Ok with Google Drive / Dropbox / FTP / FTPS

    Votes: 72 69.9%

  • Total voters
    103
  • Poll closed .
Search This thread

knääärz

Senior Member
Mar 17, 2012
242
231
Alpha Centauri
Thank you a lot knääärz for this protocol test.

Can you post a screenshot of the configuration?

I am wondering if I have correctly describe the fields.

Regards

So here is the screenshot of the the Configuration.

I found something else. When I configure FTP and touch a area outside of the configuration of FTP field, the field disappears and the Keyboard reamains active. This is really annoying because nothing helps in this situation. Even pressing back doesn't help.
 

Attachments

  • cpnfiguration.jpg
    cpnfiguration.jpg
    28.2 KB · Views: 115
  • Screenshot_2013-01-24-12-25-10.jpg
    Screenshot_2013-01-24-12-25-10.jpg
    32.5 KB · Views: 113
  • Screenshot_2013-01-24-12-25-29.jpg
    Screenshot_2013-01-24-12-25-29.jpg
    34 KB · Views: 107
Last edited:

snoopy33

Senior Member
Nov 27, 2005
1,497
2,633
I think he encountered the same 'issue' I did: if you enter the settings part (slide left to right, and press the back button, you'd expect to get back to the backup screen, but instead the program exits.

The suspected behavior of the back button would be to always go back one screen until you're in the main (backup) screen, and when pressing back in the main screen, then the program should close / exit.

---------- Post added at 12:37 PM ---------- Previous post was at 12:34 PM ----------

If you could implement a function that lets us restore data from backups, like Titanium Backup and AppExtractor, there would be another reason to ditch TB :)

Regarding the exit of the application it is a very interesting and complicated flow design issue.

I am using a side menu. In the first version I had a stack, so when you press back button you go to the screen you were before. But to exit, you may need lots of back button. Some says you should not go above 4 clicks on back button to exit.

But why 4. How th user can expect the behavior. So I have disabled the stack.

The confirm exit is known as a very bad pattern, and because the execution is totally unsynchronized with the application, the backup/zip/upload will continue even if you stop the application.

Regarding the second feature, I have always seen the nandroid as a block.

It should not be difficult to support TarBalls files. But I have read there are many formats, am I right?

If yes, it would take so much time to implement.

Let me know if you have some knowledge about the structure of the Nandorid files (best: existing code / library would help a lot).

Right now I am working on two feature which are eating all the time. So in anycase I will implement such big feature after everything else if I choose to implement it.

Regards
 

snoopy33

Senior Member
Nov 27, 2005
1,497
2,633
So here is the screenshot of the the Configuration.

I found something else. When I configure FTP and touch a area outside of the configuration of FTP field, the field disappears and the Keyboard reamains active. This is really annoying because nothing helps in this situation. Even pressing back doesn't help.

Can you try with slash at the beginning of the path?
Code:
/tralala/lala/lolila

Regards
 

snoopy33

Senior Member
Nov 27, 2005
1,497
2,633
So here is the screenshot of the the Configuration.

I found something else. When I configure FTP and touch a area outside of the configuration of FTP field, the field disappears and the Keyboard reamains active. This is really annoying because nothing helps in this situation. Even pressing back doesn't help.

About the second issue, easy to fix! I will do it tonight

Just a question, why your ROM display the button in black?? They should be white?

Is it a theme?

Regards
 
  • Like
Reactions: knääärz

knääärz

Senior Member
Mar 17, 2012
242
231
Alpha Centauri

beardymarrow

Senior Member
Oct 23, 2011
592
629
No.

I am implementing a WakeOnLan function.

A ping would help you think?

Hi snoopy,
No, definitely not. It's very bad practice as the ping might be blocked by the firewall on the server or some intermediate network device. If it had been pinging first to check, I'd have asked you to disable that :)

FWIW My personal experience of WOL is that it's an absolute pig to set-up and get working consistently. If I was you I wouldn't implement it, as you'll just get loads of problems that are nothing to do with your app, but are because of network set-up, incorrect MAC address being specified by the user, BIOS settings on servers etc. etc.

Beardy
 

snoopy33

Senior Member
Nov 27, 2005
1,497
2,633
Yes works so far. So it works with /dohiosd/doigjs and dhhsdog/doigjsiod

So ti is fixed?

Yes that's a theme. I like black :D

Mmmmhh it is bad that ROM dev destroy the UI created by dev of an application.

They modify the User experience but can't guaranty the final render.

If an application doesn't modify colors it will work as intended, but as soon as a part of the colors are overrided it will be an ugly UI.

Why do they not create their own black theme?

Since ICS (may be before) it is possible for manufacturers (and I suppose ROM modders) to add their theme and Keep Holo and Holo.light not modified.

The black buttons are not very beautiful ...

To fix that I ll need to override every colors.

Can you test this application on your ROM:
https://play.google.com/store/apps/...wsMSwxLDMsIm9yZy5ob2xvZXZlcnl3aGVyZS5kZW1vIl0.

And tell me if there are some black parts ?

Regards
 

beardymarrow

Senior Member
Oct 23, 2011
592
629
Sounds like it. Determined never to let little annoying technical problems beat me.

<snip>

Post the whole of the NETSTAT section if you want and I can pick out the relevant bits.

Beardy

So, as I discovered, you have to be really quick to flick from OB to Android Status to capture the failure, so that method doesn't help at all. Doh!

A better method is to use Shark for Root, which captures packets, so :-
Install Shark for Root
Run Shark
The parameters box will already say
Code:
-vv -s 0
You need to add to this
Code:
 host 192.168.0.100
(or whatever the IP of your FTP server is), to prevent it capturing absolutely everything that your phone is doing.

The parameters box will therefore say
Code:
-vv -s 0 host 192.168.0.100

Start the capture
Go into OB and Upload Last Backup
Stop the capture

PM me the resulting file (or attach it here) if it fails. Shark will have told you the filename. It'll end .pcap

If the upload is successful, don't send me the file for three reasons a) it'll contain your FTP password and your unencrypted nandroid, b) it won't help diagnose the problem and c) it'll be a huge file :)

Beardy
 
  • Like
Reactions: themadproducer

sgs9

Senior Member
Nov 10, 2010
749
186
Essen
garudalinux.org
what now

Yesterday all fine today my tab said "Client not connected"

Test with fileZillaServer, ok

Code:
(000002)24.01.2013 14:18:48 - (not logged in) (192.168.2.127)> Connected, sending welcome message...
(000002)24.01.2013 14:18:48 - (not logged in) (192.168.2.127)> 220-FileZilla Server version 0.9.41 beta
(000002)24.01.2013 14:18:48 - (not logged in) (192.168.2.127)> 220-written by Tim Kosse (Tim.Kosse@gmx.de)
(000002)24.01.2013 14:18:48 - (not logged in) (192.168.2.127)> 220 Please visit http://sourceforge.net/projects/filezilla/
(000002)24.01.2013 14:18:48 - (not logged in) (192.168.2.127)> USER Tab
(000002)24.01.2013 14:18:48 - (not logged in) (192.168.2.127)> 331 Password required for tab
(000002)24.01.2013 14:18:48 - (not logged in) (192.168.2.127)> PASS ******
(000002)24.01.2013 14:18:48 - tab (192.168.2.127)> 230 Logged on
(000002)24.01.2013 14:18:48 - tab (192.168.2.127)> FEAT
(000002)24.01.2013 14:18:48 - tab (192.168.2.127)> 211-Features:
(000002)24.01.2013 14:18:48 - tab (192.168.2.127)>  MDTM
(000002)24.01.2013 14:18:48 - tab (192.168.2.127)>  REST STREAM
(000002)24.01.2013 14:18:48 - tab (192.168.2.127)>  SIZE
(000002)24.01.2013 14:18:48 - tab (192.168.2.127)>  MLST type*;size*;modify*;
(000002)24.01.2013 14:18:48 - tab (192.168.2.127)>  MLSD
(000002)24.01.2013 14:18:48 - tab (192.168.2.127)>  UTF8
(000002)24.01.2013 14:18:48 - tab (192.168.2.127)>  CLNT
(000002)24.01.2013 14:18:48 - tab (192.168.2.127)>  MFMT
(000002)24.01.2013 14:18:48 - tab (192.168.2.127)> 211 End
(000002)24.01.2013 14:18:48 - tab (192.168.2.127)> OPTS UTF8 ON
(000002)24.01.2013 14:18:48 - tab (192.168.2.127)> 200 UTF8 mode enabled
(000002)24.01.2013 14:18:48 - tab (192.168.2.127)> CWD /
(000002)24.01.2013 14:18:48 - tab (192.168.2.127)> 250 CWD successful. "/" is current directory.
(000002)24.01.2013 14:18:48 - tab (192.168.2.127)> QUIT
(000002)24.01.2013 14:18:48 - tab (192.168.2.127)> 221 Goodbye
(000002)24.01.2013 14:18:48 - tab (192.168.2.127)> disconnected.
Code:
build.board: p3 build.bootloader: P7500XXLA1 build.brand: samsung build.cpu_abi: armeabi-v7a build.cpu_abi2: armeabi build.device: p4 build.display: cm_p4-userdebug 4.2.1 JOP40D eng..20130123.023850 test-keys build.fingerprint: samsung/GT-P7500/GT-P7500:4.0.4/IMM76D/XXLQ8:user/release-keys build.hardware: p3 build.host: cyanogenmod build.id: JOP40D build.manufacturer: samsung build.model: GT-P7500 build.product: GT-P7500 build.radio: unknown build.serial: xxxx build.tags: test-keys build.time: 1358937560000 build.type: userdebug build.user: unknown version.codename: REL version.incremental: eng..20130123.023850 version.release: 4.2.1 version.sdk_int: 17 01-23 18:52:49.000 I/PackageManager(442): Pruning dalvik file: data@app@com.pommedeterresautee.twoborange3-1.apk@classes.dex 01-23 18:53:11.530 W/PackageParser(442): No actions in intent filter at /data/app/com.pommedeterresautee.twoborange3-1.apk Binary XML file line #110 01-23 18:53:11.530 W/PackageParser(442): No actions in intent filter at /data/app/com.pommedeterresautee.twoborange3-1.apk Binary XML file line #128 01-23 18:53:11.570 I/PackageManager(442): Linking native library dir for /data/app/com.pommedeterresautee.twoborange3-1.apk 01-23 18:58:03.743 I/ActivityManager(442): Start proc com.pommedeterresautee.twoborange3 for broadcast com.pommedeterresautee.twoborange3/.Services.AlarmBootSetter: pid=2916 uid=10183 gids={50183, 3003, 1015, 1028} 01-23 18:58:13.423 I/ActivityManager(442): No longer want com.pommedeterresautee.twoborange3 (pid 2916): empty #17 01-24 12:03:49.982 I/ActivityManager(442): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.pommedeterresautee.twoborange3/.Activities.Main.MainActivity bnds=[227,436][323,532]} from pid 1156 01-24 12:03:50.042 I/ActivityManager(442): Start proc com.pommedeterresautee.twoborange3 for activity com.pommedeterresautee.twoborange3/.Activities.Main.MainActivity: pid=19943 uid=10183 gids={50183, 3003, 1015, 1028} 01-24 12:04:35.912 I/ActivityManager(442): START u0 {act=com.pommedeterresautee.twoborange3.BACKUP_KEEPER cmp=com.pommedeterresautee.twoborange3/.Activities.Other.Preference.BackupKeeper} from pid 19943 01-24 12:05:24.482 I/ActivityManager(442): START u0 {act=com.pommedeterresautee.twoborange3.BACKUP_STORAGE_CHOICE cmp=com.pommedeterresautee.twoborange3/.Activities.Other.Preference.ListStorageDialog} from pid 19943 01-24 12:17:15.312 D/su (20917): 10183 com.pommedeterresautee.twoborange3 executing 0 /system/bin/sh using shell /system/bin/sh : sh 01-24 12:17:16.022 D/su (20933): 10183 com.pommedeterresautee.twoborange3 executing 0 /system/bin/sh using shell /system/bin/sh : sh 01-24 12:17:16.902 D/su (20947): 10183 com.pommedeterresautee.twoborange3 executing 0 /system/bin/sh using shell /system/bin/sh : sh 01-24 12:17:21.952 D/su (21025): 10183 com.pommedeterresautee.twoborange3 executing 0 /system/bin/sh using shell /system/bin/sh : sh 01-24 12:17:22.692 D/su (21041): 10183 com.pommedeterresautee.twoborange3 executing 0 /system/bin/sh using shell /system/bin/sh : sh 01-24 12:17:23.482 D/su (21055): 10183 com.pommedeterresautee.twoborange3 executing 0 /system/bin/sh using shell /system/bin/sh : sh 01-24 12:17:24.242 D/su (21070): 10183 com.pommedeterresautee.twoborange3 executing 0 /system/bin/sh using shell /system/bin/sh : sh 01-24 12:17:27.372 D/su (21089): 10183 com.pommedeterresautee.twoborange3 executing 0 /system/bin/sh using shell /system/bin/sh : sh 01-24 12:32:37.172 D/su (25615): 10183 com.pommedeterresautee.twoborange3 executing 0 /system/bin/sh using shell /system/bin/sh : sh 01-24 12:32:40.242 D/su (25633): 10183 com.pommedeterresautee.twoborange3 executing 0 /system/bin/sh using shell /system/bin/sh : sh 01-24 13:58:48.542 I/ActivityManager(442): START u0 {flg=0x4000000 cmp=com.pommedeterresautee.twoborange3/.Activities.Main.MainActivity bnds=[48,76][528,189]} from pid -1 01-24 13:58:48.542 W/ActivityManager(442): startActivity called from non-Activity context; forcing Intent.FLAG_ACTIVITY_NEW_TASK for: Intent { flg=0x4000000 cmp=com.pommedeterresautee.twoborange3/.Activities.Main.MainActivity bnds=[48,76][528,189] } 01-24 14:12:50.422 I/ActivityManager(442): START u0 {flg=0x4000000 cmp=com.pommedeterresautee.twoborange3/.Activities.Main.MainActivity bnds=[48,76][528,189]} from pid -1 01-24 14:12:50.422 W/ActivityManager(442): startActivity called from non-Activity context; forcing Intent.FLAG_ACTIVITY_NEW_TASK for: Intent { flg=0x4000000 cmp=com.pommedeterresautee.twoborange3/.Activities.Main.MainActivity bnds=[48,76][528,189] } 01-24 14:13:31.112 I/ActivityManager(442): START u0 {flg=0x4000000 cmp=com.pommedeterresautee.twoborange3/.Activities.Main.MainActivity bnds=[48,76][528,189]} from pid -1 01-24 14:13:31.112 W/ActivityManager(442): startActivity called from non-Activity context; forcing Intent.FLAG_ACTIVITY_NEW_TASK for: Intent { flg=0x4000000 cmp=com.pommedeterresautee.twoborange3/.Activities.Main.MainActivity bnds=[48,76][528,189] } 01-24 14:14:18.442 I/ActivityManager(442): START u0 {act=com.pommedeterresautee.twoborange3.CLOUD_SELECTION cmp=com.pommedeterresautee.twoborange3/.Activities.Other.Preference.CloudSelection} from pid 19943 01-24 14:14:18.672 I/ActivityManager(442): Displayed com.pommedeterresautee.twoborange3/.Activities.Other.Preference.CloudSelection: +191ms 01-24 14:14:21.782 I/ActivityManager(442): START u0 {cmp=com.pommedeterresautee.twoborange3/.Activities.Other.Preference.ConfigureFTPDialog} from pid 19943 01-24 14:14:22.232 I/ActivityManager(442): Displayed com.pommedeterresautee.twoborange3/.Activities.Other.Preference.ConfigureFTPDialog: +438ms 01-24 14:14:50.802 E/WindowManager(19943): Activity com.pommedeterresautee.twoborange3.Activities.Other.Preference.ConfigureFTPDialog has leaked window com.android.internal.policy.impl.PhoneWindow$DecorView{412ff928 V.E..... R......D 0,0-580,335} that was originally added here 01-24 14:14:50.802 E/WindowManager(19943): android.view.WindowLeaked: Activity com.pommedeterresautee.twoborange3.Activities.Other.Preference.ConfigureFTPDialog has leaked window com.android.internal.policy.impl.PhoneWindow$DecorView{412ff928 V.E..... R......D 0,0-580,335} that was originally added here 01-24 14:14:50.802 E/WindowManager(19943): at com.pommedeterresautee.twoborange3.Activities.Other.Preference.ConfigureFTPDialog.a(SourceFile:150) 01-24 14:14:50.802 E/WindowManager(19943): at com.pommedeterresautee.twoborange3.Activities.Other.Preference.ConfigureFTPDialog.onCreate(SourceFile:48) 01-24 14:14:51.152 W/WindowManager(442): This window was lost: Window{415057e8 u0 com.pommedeterresautee.twoborange3/com.pommedeterresautee.twoborange3.Activities.Other.Preference.ConfigureFTPDialog} 01-24 14:14:51.152 W/WindowManager(442): mToken=AppWindowToken{41d931b0 token=Token{414f5dd8 ActivityRecord{411fbe70 u0 com.pommedeterresautee.twoborange3/.Activities.Other.Preference.ConfigureFTPDialog}}} 01-24 14:14:51.152 W/WindowManager(442): mRootToken=AppWindowToken{41d931b0 token=Token{414f5dd8 ActivityRecord{411fbe70 u0 com.pommedeterresautee.twoborange3/.Activities.Other.Preference.ConfigureFTPDialog}}} 01-24 14:14:51.152 W/WindowManager(442): mAppToken=AppWindowToken{41d931b0 token=Token{414f5dd8 ActivityRecord{411fbe70 u0 com.pommedeterresautee.twoborange3/.Activities.Other.Preference.ConfigureFTPDialog}}} 01-24 14:14:51.152 W/WindowManager(442): WindowStateAnimator{417a4fa8 com.pommedeterresautee.twoborange3/com.pommedeterresautee.twoborange3.Activities.Other.Preference.ConfigureFTPDialog}: 01-24 14:14:51.152 W/WindowManager(442): mSurface=Surface(name=com.pommedeterresautee.twoborange3/com.pommedeterresautee.twoborange3.Activities.Other.Preference.ConfigureFTPDialog, identity=266) 01-24 14:14:51.152 V/WindowManager(442): #13: Token{416da168 ActivityRecord{40f781f0 u0 com.pommedeterresautee.twoborange3/.Activities.Main.MainActivity}} 01-24 14:14:51.152 V/WindowManager(442): #7: Window{41581b80 u0 com.pommedeterresautee.twoborange3/com.pommedeterresautee.twoborange3.Activities.Main.MainActivity} 01-24 14:15:33.342 I/ActivityManager(442): START u0 {flg=0x4000000 cmp=com.pommedeterresautee.twoborange3/.Activities.Main.MainActivity bnds=[48,76][528,189]} from pid -1 01-24 14:15:33.342 W/ActivityManager(442): startActivity called from non-Activity context; forcing Intent.FLAG_ACTIVITY_NEW_TASK for: Intent { flg=0x4000000 cmp=com.pommedeterresautee.twoborange3/.Activities.Main.MainActivity bnds=[48,76][528,189] } 01-24 14:18:44.152 I/ActivityManager(442): START u0 {act=com.pommedeterresautee.twoborange3.CLOUD_SELECTION cmp=com.pommedeterresautee.twoborange3/.Activities.Other.Preference.CloudSelection} from pid 19943 01-24 14:18:44.382 I/ActivityManager(442): Displayed com.pommedeterresautee.twoborange3/.Activities.Other.Preference.CloudSelection: +200ms 01-24 14:18:46.952 I/ActivityManager(442): START u0 {cmp=com.pommedeterresautee.twoborange3/.Activities.Other.Preference.ConfigureFTPDialog} from pid 19943 01-24 14:18:47.222 I/ActivityManager(442): Displayed com.pommedeterresautee.twoborange3/.Activities.Other.Preference.ConfigureFTPDialog: +252ms 01-24 14:19:42.172 E/WindowManager(19943): Activity com.pommedeterresautee.twoborange3.Activities.Other.Preference.ConfigureFTPDialog has leaked window com.android.internal.policy.impl.PhoneWindow$DecorView{4116c6c0 V.E..... R......D 0,0-580,335} that was originally added here 01-24 14:19:42.172 E/WindowManager(19943): android.view.WindowLeaked: Activity com.pommedeterresautee.twoborange3.Activities.Other.Preference.ConfigureFTPDialog has leaked window com.android.internal.policy.impl.PhoneWindow$DecorView{4116c6c0 V.E..... R......D 0,0-580,335} that was originally added here 01-24 14:19:42.172 E/WindowManager(19943): at com.pommedeterresautee.twoborange3.Activities.Other.Preference.ConfigureFTPDialog.a(SourceFile:150) 01-24 14:19:42.172 E/WindowManager(19943): at com.pommedeterresautee.twoborange3.Activities.Other.Preference.ConfigureFTPDialog.onCreate(SourceFile:48) 01-24 14:19:42.562 W/WindowManager(442): This window was lost: Window{417364b0 u0 com.pommedeterresautee.twoborange3/com.pommedeterresautee.twoborange3.Activities.Other.Preference.ConfigureFTPDialog} 01-24 14:19:42.562 W/WindowManager(442): mToken=AppWindowToken{41d764a0 token=Token{41d730b0 ActivityRecord{41d73ca0 u0 com.pommedeterresautee.twoborange3/.Activities.Other.Preference.ConfigureFTPDialog}}} 01-24 14:19:42.562 W/WindowManager(442): mRootToken=AppWindowToken{41d764a0 token=Token{41d730b0 ActivityRecord{41d73ca0 u0 com.pommedeterresautee.twoborange3/.Activities.Other.Preference.ConfigureFTPDialog}}} 01-24 14:19:42.562 W/WindowManager(442): mAppToken=AppWindowToken{41d764a0 token=Token{41d730b0 ActivityRecord{41d73ca0 u0 com.pommedeterresautee.twoborange3/.Activities.Other.Preference.ConfigureFTPDialog}}} 01-24 14:19:42.562 W/WindowManager(442): WindowStateAnimator{41855f40 com.pommedeterresautee.twoborange3/com.pommedeterresautee.twoborange3.Activities.Other.Preference.ConfigureFTPDialog}: 01-24 14:19:42.562 W/WindowManager(442): mSurface=Surface(name=com.pommedeterresautee.twoborange3/com.pommedeterresautee.twoborange3.Activities.Other.Preference.ConfigureFTPDialog, identity=272) 01-24 14:19:42.562 V/WindowManager(442): #13: Token{416da168 ActivityRecord{40f781f0 u0 com.pommedeterresautee.twoborange3/.Activities.Main.MainActivity}} 01-24 14:19:42.562 V/WindowManager(442): #7: Window{41581b80 u0 com.pommedeterresautee.twoborange3/com.pommedeterresautee.twoborange3.Activities.Main.MainActivity}
logcat, on cm 10.1 , p4 give also in your "Your device" p3 as device board name "cm 10.1 nightly mistake ?"

"Wake On Lan" my favorit :D

XDA do not like two "CODE" ? or what I must do to show for Logcat.txt

---------- Post added at 04:57 PM ---------- Previous post was at 04:56 PM ----------

Code:
build.board: p3
build.bootloader: P7500XXLA1
build.brand: samsung
build.cpu_abi: armeabi-v7a
build.cpu_abi2: armeabi
build.device: p4
build.display: cm_p4-userdebug 4.2.1 JOP40D eng..20130123.023850 test-keys
build.fingerprint: samsung/GT-P7500/GT-P7500:4.0.4/IMM76D/XXLQ8:user/release-keys
build.hardware: p3
build.host: cyanogenmod
build.id: JOP40D
build.manufacturer: samsung
build.model: GT-P7500
build.product: GT-P7500
build.radio: unknown
build.serial: xxxx
build.tags: test-keys
build.time: 1358937560000
build.type: userdebug
build.user: unknown
version.codename: REL
version.incremental: eng..20130123.023850
version.release: 4.2.1
version.sdk_int: 17

01-23 18:52:49.000 I/PackageManager(442): Pruning dalvik file: data@app@com.pommedeterresautee.twoborange3-1.apk@classes.dex
01-23 18:53:11.530 W/PackageParser(442): No actions in intent filter at /data/app/com.pommedeterresautee.twoborange3-1.apk Binary XML file line #110
01-23 18:53:11.530 W/PackageParser(442): No actions in intent filter at /data/app/com.pommedeterresautee.twoborange3-1.apk Binary XML file line #128
01-23 18:53:11.570 I/PackageManager(442): Linking native library dir for /data/app/com.pommedeterresautee.twoborange3-1.apk
01-23 18:58:03.743 I/ActivityManager(442): Start proc com.pommedeterresautee.twoborange3 for broadcast com.pommedeterresautee.twoborange3/.Services.AlarmBootSetter: pid=2916 uid=10183 gids={50183, 3003, 1015, 1028}
01-23 18:58:13.423 I/ActivityManager(442): No longer want com.pommedeterresautee.twoborange3 (pid 2916): empty #17
01-24 12:03:49.982 I/ActivityManager(442): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.pommedeterresautee.twoborange3/.Activities.Main.MainActivity bnds=[227,436][323,532]} from pid 1156
01-24 12:03:50.042 I/ActivityManager(442): Start proc com.pommedeterresautee.twoborange3 for activity com.pommedeterresautee.twoborange3/.Activities.Main.MainActivity: pid=19943 uid=10183 gids={50183, 3003, 1015, 1028}
01-24 12:04:35.912 I/ActivityManager(442): START u0 {act=com.pommedeterresautee.twoborange3.BACKUP_KEEPER cmp=com.pommedeterresautee.twoborange3/.Activities.Other.Preference.BackupKeeper} from pid 19943
01-24 12:05:24.482 I/ActivityManager(442): START u0 {act=com.pommedeterresautee.twoborange3.BACKUP_STORAGE_CHOICE cmp=com.pommedeterresautee.twoborange3/.Activities.Other.Preference.ListStorageDialog} from pid 19943
01-24 12:17:15.312 D/su      (20917): 10183 com.pommedeterresautee.twoborange3 executing 0 /system/bin/sh using shell /system/bin/sh : sh
01-24 12:17:16.022 D/su      (20933): 10183 com.pommedeterresautee.twoborange3 executing 0 /system/bin/sh using shell /system/bin/sh : sh
01-24 12:17:16.902 D/su      (20947): 10183 com.pommedeterresautee.twoborange3 executing 0 /system/bin/sh using shell /system/bin/sh : sh
01-24 12:17:21.952 D/su      (21025): 10183 com.pommedeterresautee.twoborange3 executing 0 /system/bin/sh using shell /system/bin/sh : sh
01-24 12:17:22.692 D/su      (21041): 10183 com.pommedeterresautee.twoborange3 executing 0 /system/bin/sh using shell /system/bin/sh : sh
01-24 12:17:23.482 D/su      (21055): 10183 com.pommedeterresautee.twoborange3 executing 0 /system/bin/sh using shell /system/bin/sh : sh
01-24 12:17:24.242 D/su      (21070): 10183 com.pommedeterresautee.twoborange3 executing 0 /system/bin/sh using shell /system/bin/sh : sh
01-24 12:17:27.372 D/su      (21089): 10183 com.pommedeterresautee.twoborange3 executing 0 /system/bin/sh using shell /system/bin/sh : sh
01-24 12:32:37.172 D/su      (25615): 10183 com.pommedeterresautee.twoborange3 executing 0 /system/bin/sh using shell /system/bin/sh : sh
01-24 12:32:40.242 D/su      (25633): 10183 com.pommedeterresautee.twoborange3 executing 0 /system/bin/sh using shell /system/bin/sh : sh
01-24 13:58:48.542 I/ActivityManager(442): START u0 {flg=0x4000000 cmp=com.pommedeterresautee.twoborange3/.Activities.Main.MainActivity bnds=[48,76][528,189]} from pid -1
01-24 13:58:48.542 W/ActivityManager(442): startActivity called from non-Activity context; forcing Intent.FLAG_ACTIVITY_NEW_TASK for: Intent { flg=0x4000000 cmp=com.pommedeterresautee.twoborange3/.Activities.Main.MainActivity bnds=[48,76][528,189] }
01-24 14:12:50.422 I/ActivityManager(442): START u0 {flg=0x4000000 cmp=com.pommedeterresautee.twoborange3/.Activities.Main.MainActivity bnds=[48,76][528,189]} from pid -1
01-24 14:12:50.422 W/ActivityManager(442): startActivity called from non-Activity context; forcing Intent.FLAG_ACTIVITY_NEW_TASK for: Intent { flg=0x4000000 cmp=com.pommedeterresautee.twoborange3/.Activities.Main.MainActivity bnds=[48,76][528,189] }
01-24 14:13:31.112 I/ActivityManager(442): START u0 {flg=0x4000000 cmp=com.pommedeterresautee.twoborange3/.Activities.Main.MainActivity bnds=[48,76][528,189]} from pid -1
01-24 14:13:31.112 W/ActivityManager(442): startActivity called from non-Activity context; forcing Intent.FLAG_ACTIVITY_NEW_TASK for: Intent { flg=0x4000000 cmp=com.pommedeterresautee.twoborange3/.Activities.Main.MainActivity bnds=[48,76][528,189] }
01-24 14:14:18.442 I/ActivityManager(442): START u0 {act=com.pommedeterresautee.twoborange3.CLOUD_SELECTION cmp=com.pommedeterresautee.twoborange3/.Activities.Other.Preference.CloudSelection} from pid 19943
01-24 14:14:18.672 I/ActivityManager(442): Displayed com.pommedeterresautee.twoborange3/.Activities.Other.Preference.CloudSelection: +191ms
01-24 14:14:21.782 I/ActivityManager(442): START u0 {cmp=com.pommedeterresautee.twoborange3/.Activities.Other.Preference.ConfigureFTPDialog} from pid 19943
01-24 14:14:22.232 I/ActivityManager(442): Displayed com.pommedeterresautee.twoborange3/.Activities.Other.Preference.ConfigureFTPDialog: +438ms
01-24 14:14:50.802 E/WindowManager(19943): Activity com.pommedeterresautee.twoborange3.Activities.Other.Preference.ConfigureFTPDialog has leaked window com.android.internal.policy.impl.PhoneWindow$DecorView{412ff928 V.E..... R......D 0,0-580,335} that was originally added here
01-24 14:14:50.802 E/WindowManager(19943): android.view.WindowLeaked: Activity com.pommedeterresautee.twoborange3.Activities.Other.Preference.ConfigureFTPDialog has leaked window com.android.internal.policy.impl.PhoneWindow$DecorView{412ff928 V.E..... R......D 0,0-580,335} that was originally added here
01-24 14:14:50.802 E/WindowManager(19943):     at com.pommedeterresautee.twoborange3.Activities.Other.Preference.ConfigureFTPDialog.a(SourceFile:150)
01-24 14:14:50.802 E/WindowManager(19943):     at com.pommedeterresautee.twoborange3.Activities.Other.Preference.ConfigureFTPDialog.onCreate(SourceFile:48)
01-24 14:14:51.152 W/WindowManager(442): This window was lost: Window{415057e8 u0 com.pommedeterresautee.twoborange3/com.pommedeterresautee.twoborange3.Activities.Other.Preference.ConfigureFTPDialog}
01-24 14:14:51.152 W/WindowManager(442): mToken=AppWindowToken{41d931b0 token=Token{414f5dd8 ActivityRecord{411fbe70 u0 com.pommedeterresautee.twoborange3/.Activities.Other.Preference.ConfigureFTPDialog}}}
01-24 14:14:51.152 W/WindowManager(442): mRootToken=AppWindowToken{41d931b0 token=Token{414f5dd8 ActivityRecord{411fbe70 u0 com.pommedeterresautee.twoborange3/.Activities.Other.Preference.ConfigureFTPDialog}}}
01-24 14:14:51.152 W/WindowManager(442): mAppToken=AppWindowToken{41d931b0 token=Token{414f5dd8 ActivityRecord{411fbe70 u0 com.pommedeterresautee.twoborange3/.Activities.Other.Preference.ConfigureFTPDialog}}}
01-24 14:14:51.152 W/WindowManager(442): WindowStateAnimator{417a4fa8 com.pommedeterresautee.twoborange3/com.pommedeterresautee.twoborange3.Activities.Other.Preference.ConfigureFTPDialog}:
01-24 14:14:51.152 W/WindowManager(442):   mSurface=Surface(name=com.pommedeterresautee.twoborange3/com.pommedeterresautee.twoborange3.Activities.Other.Preference.ConfigureFTPDialog, identity=266)
01-24 14:14:51.152 V/WindowManager(442):   #13: Token{416da168 ActivityRecord{40f781f0 u0 com.pommedeterresautee.twoborange3/.Activities.Main.MainActivity}}
01-24 14:14:51.152 V/WindowManager(442):   #7: Window{41581b80 u0 com.pommedeterresautee.twoborange3/com.pommedeterresautee.twoborange3.Activities.Main.MainActivity}
01-24 14:15:33.342 I/ActivityManager(442): START u0 {flg=0x4000000 cmp=com.pommedeterresautee.twoborange3/.Activities.Main.MainActivity bnds=[48,76][528,189]} from pid -1
01-24 14:15:33.342 W/ActivityManager(442): startActivity called from non-Activity context; forcing Intent.FLAG_ACTIVITY_NEW_TASK for: Intent { flg=0x4000000 cmp=com.pommedeterresautee.twoborange3/.Activities.Main.MainActivity bnds=[48,76][528,189] }
01-24 14:18:44.152 I/ActivityManager(442): START u0 {act=com.pommedeterresautee.twoborange3.CLOUD_SELECTION cmp=com.pommedeterresautee.twoborange3/.Activities.Other.Preference.CloudSelection} from pid 19943
01-24 14:18:44.382 I/ActivityManager(442): Displayed com.pommedeterresautee.twoborange3/.Activities.Other.Preference.CloudSelection: +200ms
01-24 14:18:46.952 I/ActivityManager(442): START u0 {cmp=com.pommedeterresautee.twoborange3/.Activities.Other.Preference.ConfigureFTPDialog} from pid 19943
01-24 14:18:47.222 I/ActivityManager(442): Displayed com.pommedeterresautee.twoborange3/.Activities.Other.Preference.ConfigureFTPDialog: +252ms
01-24 14:19:42.172 E/WindowManager(19943): Activity com.pommedeterresautee.twoborange3.Activities.Other.Preference.ConfigureFTPDialog has leaked window com.android.internal.policy.impl.PhoneWindow$DecorView{4116c6c0 V.E..... R......D 0,0-580,335} that was originally added here
01-24 14:19:42.172 E/WindowManager(19943): android.view.WindowLeaked: Activity com.pommedeterresautee.twoborange3.Activities.Other.Preference.ConfigureFTPDialog has leaked window com.android.internal.policy.impl.PhoneWindow$DecorView{4116c6c0 V.E..... R......D 0,0-580,335} that was originally added here
01-24 14:19:42.172 E/WindowManager(19943):     at com.pommedeterresautee.twoborange3.Activities.Other.Preference.ConfigureFTPDialog.a(SourceFile:150)
01-24 14:19:42.172 E/WindowManager(19943):     at com.pommedeterresautee.twoborange3.Activities.Other.Preference.ConfigureFTPDialog.onCreate(SourceFile:48)
01-24 14:19:42.562 W/WindowManager(442): This window was lost: Window{417364b0 u0 com.pommedeterresautee.twoborange3/com.pommedeterresautee.twoborange3.Activities.Other.Preference.ConfigureFTPDialog}
01-24 14:19:42.562 W/WindowManager(442): mToken=AppWindowToken{41d764a0 token=Token{41d730b0 ActivityRecord{41d73ca0 u0 com.pommedeterresautee.twoborange3/.Activities.Other.Preference.ConfigureFTPDialog}}}
01-24 14:19:42.562 W/WindowManager(442): mRootToken=AppWindowToken{41d764a0 token=Token{41d730b0 ActivityRecord{41d73ca0 u0 com.pommedeterresautee.twoborange3/.Activities.Other.Preference.ConfigureFTPDialog}}}
01-24 14:19:42.562 W/WindowManager(442): mAppToken=AppWindowToken{41d764a0 token=Token{41d730b0 ActivityRecord{41d73ca0 u0 com.pommedeterresautee.twoborange3/.Activities.Other.Preference.ConfigureFTPDialog}}}
01-24 14:19:42.562 W/WindowManager(442): WindowStateAnimator{41855f40 com.pommedeterresautee.twoborange3/com.pommedeterresautee.twoborange3.Activities.Other.Preference.ConfigureFTPDialog}:
01-24 14:19:42.562 W/WindowManager(442):   mSurface=Surface(name=com.pommedeterresautee.twoborange3/com.pommedeterresautee.twoborange3.Activities.Other.Preference.ConfigureFTPDialog, identity=272)
01-24 14:19:42.562 V/WindowManager(442):   #13: Token{416da168 ActivityRecord{40f781f0 u0 com.pommedeterresautee.twoborange3/.Activities.Main.MainActivity}}
01-24 14:19:42.562 V/WindowManager(442):   #7: Window{41581b80 u0 com.pommedeterresautee.twoborange3/com.pommedeterresautee.twoborange3.Activities.Main.MainActivity}




Edit: Same on S3 Both 4.2.1 change S3 in Slim 3.1 (4.1.2) upload work :confused:
 
Last edited:

Android Cowboy

Senior Member
Jan 17, 2012
307
111
androidcowboy.com
md5sum error

I'm using this app for the first time. I have Samsung GS3 and choosing the TWRP option for backup. I'm saving to extSD card. When backup starts it run through okay with everything until the md5sum error which it says was not found in the path. How do you fix this. Thanks.
 

ameer1234567890

Inactive Recognized Developer
Mar 12, 2012
1,649
1,987
Thulhaadhoo
ameer.io
I'm using this app for the first time. I have Samsung GS3 and choosing the TWRP option for backup. I'm saving to extSD card. When backup starts it run through okay with everything until the md5sum error which it says was not found in the path. How do you fix this. Thanks.
Re-install busybox. Make sure all applets are ticked, while re-installing busybox.
 

knääärz

Senior Member
Mar 17, 2012
242
231
Alpha Centauri
Hi snoopy,
No, definitely not. It's very bad practice as the ping might be blocked by the firewall on the server or some intermediate network device. If it had been pinging first to check, I'd have asked you to disable that :)

FWIW My personal experience of WOL is that it's an absolute pig to set-up and get working consistently. If I was you I wouldn't implement it, as you'll just get loads of problems that are nothing to do with your app, but are because of network set-up, incorrect MAC address being specified by the user, BIOS settings on servers etc. etc.

Beardy

I know that WOL is a bit a hard to setup. I was asking for that feature. I'm not using the real WOL function (Magic Packet). I'm using pattern match. So my server starts even when I want to access with ftp, smb or anything else. The server starts when there is something that wants access.

The problem I have. When my server is sleeping and OB wants to upload the backup, it fails because my server needs ~15 seconds to be back on work. So I asked snoopy about the WOL stuff. And he said yes, I know how to implement.

But if it fails to implement there might be another solution I think (pattern match).
Before OB starts a upload-->test the ftp settings-->wait 15 seconds-->start upload. That will help me in my situation, because there is a bigger time range for starting server and upload it after that.



Mmmmhh it is bad that ROM dev destroy the UI created by dev of an application.

They modify the User experience but can't guaranty the final render.

If an application doesn't modify colors it will work as intended, but as soon as a part of the colors are overrided it will be an ugly UI.

Why do they not create their own black theme?

Since ICS (may be before) it is possible for manufacturers (and I suppose ROM modders) to add their theme and Keep Holo and Holo.light not modified.

The black buttons are not very beautiful ...

To fix that I ll need to override every colors.

Can you test this application on your ROM:
https://play.google.com/store/apps/...wsMSwxLDMsIm9yZy5ob2xvZXZlcnl3aGVyZS5kZW1vIl0.

And tell me if there are some black parts ?

Regards

I will test.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 329
    OBackup 1.35
    Backup your device to Cloud in one click


    BECAUSE OF AN ERROR WITH OUR SERVER I HAVE UNPUBLISHED THE APPLICATION FROM PLAY STORE

    THE ERROR IS NOW FIXED :)


    Application should came back on Play Store in the coming hours



    all_screens_together.png



    Overview

    :good: Make a backup, zip it and upload it on your Dropbox or Google Drive in ONE CLICK only !!! (upload is just a feature, you can make the backup and just keep it on your device)
    :good: Make it happen every night at 2AM or every two days at noon... or whatever you want
    :good: No need to restart your phone during the backup and miss some calls!
    :good: You can continue to use your device during the backup (may be laggy on slow device ;)).
    :good: CWM & TWRP support


    Download



    https://play.google.com/store/apps/details?id=com.pommedeterresautee.twoborange3


    Very clear explanation from Kantjer (original post here)

    Originally Posted by THE RED BLUR
    Im still a fan of the old trusted traditional way of backing up via cwm. But must admit I tried out Obackup recently and was impressed with it thanks to kantjers insistence :D

    On Samsung jb when using the app I never had to use a script so will need to look at that if its different for Aokp roms?

    Which one is better Online or OBackup?
    Answer from Kantjer:
    There basically 3 major developers involved in the world of online backup (online meaning no need to boot in recovery)

    1. ameer1234567890, who developed the "Online Nandroid Backup" script, this is the script making the actual online nandroid.
      The script can be run without any additional apps using a terminal emulator.
    2. snoopy33, he is the developer of "OBackup"
      OBackup is a frontend app that uses the Online Nandroid Backup script for the backup part. But offers a lot of additional features like like easy setup, scheduled backups and backup retention to name a few.
    3. H3R3T1C, is developing "Nandroid Manager"
      a dedicated app to manage all your backups and let you verify MD5 of backups, restore apps+data from nandroid backup and a whole lot of other nice things.

    So basically "Online Nandroid Backup"and "OBackup" should give you the same backup result, only if you want the nice extra options go for OB. Nandroid Manager is a great addition to compliment your set off backup tools.

    The good news for us as users is that the 3 developers are working closely together to ensure that everything is working nicely together and apps and script are compatible.

    A few tips for new users. I have seen a lot of people posting issues using "Online Nandroid" or "OBackup" and most off the time is due to only one off the following things.

    1. The user didn't install the correct device specific path, this is needed to tell the script where to find the boot and recovery partitions. You can find the patches here
    2. Don't start messing with selecting partitions to backup, leave that option disabled and OB will backup all the relevant partitions for you. Only use it if you need it and know what you are doing.
    3. Only use the SD-EXT option if you use apps like app2sd, link2sd, data2sd, etc... otherwise leave that option disabled.
    Good luck, and if you need any assistance place a port in the appropriate thread.
    Features

    * Easy Backup of your Device
    * Backup format: Nandroid (backup of absolutely ALL your data on your device)
    * Support CWM and TWRP (for beta tester only - Online Nandroid script version 7)
    * Automatic Zip of the Backup (with split zip option)
    * Automatic Upload to Dropbox OR Google Drive
    * Backup Planning every X days
    * Automatic Delete of old backups
    * Lots of advanced option (incremental backup, partition selection...)
    * Request patch file if not yet available
    * Uninstall any system application, not just freeze it
    * Kill any task (even system/hided one)
    * Elegant Interface
    * TASKER plugin
    * Nandroid Manager compatible

    Want to request a feature?
    http://goo.gl/mod/Dvmo
    Vote for one, or add a new one to the list!




    Bugs

    Did you find a bug? Please report it here!


    Reviews

    XDA Portal
    Reddit
    crewecustoms
    android-software.fr
    Tuto from tricksmash (I thought it was simple enough to not need a tuto)
    showmetech.com.br (unknown language)
    androidgalaxys.net (Italian)
    themobimag.com (Tutorial)
    blog.shift.it (Italian)
    landoftechnology.com
    dotekomanie.cz (unknown language)
    pocketables.com (first review)
    vnpda.com (Vietnamese)
    mojandroid.sk (Slovak)
    blog.toaninfo.com
    handheld.softpedia.com
    appzrev.com (very good review of the app)
    getandroidstuff.com (10 top new app of the week)
    blog.shift.it (Italian)
    folblog.it (Italian)
    addictivetips.com (very good review on a very good website)
    androidvzla.com (Italian)
    pocketables.com (second review)
    androidvenezuela.com (Spanish)
    perusmart.com (Spanish)
    droidtune.com (Russian)
    baixaki.com.br
    techtastico.com
    4tablet-pc.net
    actualidadg.com
    b4tea.com
    keddr.com
    kode-labs.blogspot.fr
    pocketables.com (comparison between several backup application)
    androidpipe.com
    dgtallika.com
    showmetech.com.br
    rewritetech
    androidsis
    hrjtricks
    newsgeek
    Video presentation in Italian
    OnlineNandroid script. :good:

    Big Thanks to everyone here, and in particular to Kantjer, Electricsheepdreamer, Knääärz and Ikjadoon for helping users since the beginning of this project and the many ideas they shared with me!!!


    Permission requested

    android.permission.ACCESS_COARSE_LOCATION -> Admob
    android.permission.ACCESS_FINE_LOCATION -> Admob
    android.permission.ACCESS_NETWORK_STATE -> upload to Dropbox
    android.permission.ACCESS_WIFI_STATE -> upload to Dropbox
    android.permission.GET_ACCOUNTS -> push notification (new option to come)
    android.permission.GET_TASKS -> task killer
    android.permission.INTERNET -> Device recognition / Upload
    android.permission.KILL_BACKGROUND_PROCESSES -> task killer
    android.permission.READ_EXTERNAL_STORAGE -> backup
    android.permission.READ_PHONE_STATE -> backup
    android.permission.RECEIVE_BOOT_COMPLETED -> Scheduler
    android.permission.VIBRATE -> backup
    android.permission.WAKE_LOCK -> backup / zip / upload
    android.permission.WRITE_EXTERNAL_STORAGE -> backup / zip
    35
    Ok I have missed an important email dated of last Friday from the Play Store notifying me that Orange asked to ban me because of the name "Orange Backup".

    Here is their request:

    This is a notification that your application, Orange Backup ★ Onandroid, with package ID com.pommedeterresautee.twoborange3, has been removed from the Google Play Store in the following jurisdictions: EU.
    REASON FOR REMOVAL: Alleged trademark infringement.
    Google has been notified that aspects of your application, Orange Backup ★ Onandroid, allegedly infringe upon the trademarks of others, and it has been removed from the Google Play Store due to a violation of the Content Policy.
    All violations are tracked. Serious or repeated violations of any nature will result in the termination of your developer account, and investigation and possible termination of related Google accounts.
    You may contact Orange Brand Services Limited at ***@orange.com. If Orange Brand Services Limited contacts us specifically authorizing your app to be re-published, and your app does not otherwise violate the Developer Distribution Agreement and Content Policy, we will reinstate the app.
    Please note that we have included a text copy of the Infringement Notice we received for your reference. If you have any further concerns about this issue, please address them directly to the complainant in the Infringement Notice provided below.
    The Google Play Team
    Text Copy of Infringement Notice:
    ***@orange.com


    to support-portal@google.com




    AutoDetectedBrowser: Firefox 1
    AutoDetectedOS: Windows 7
    IIILanguage: en
    IssueType: lr_trademark
    Language: en
    address: The Point, 37 North Wharf Road, London, W2 1AG
    agree1: checked
    android_app_developer_1: XDA Developers
    android_app_name_1: Orange Backup ★ root
    android_app_url_1:
    https://play.google.com/store/apps/...S5wb21tZWRldGVycmVzYXV0ZWUudHdvYm9yYW5nZTMiXQ
    companyname: Orange Brand Services Limited
    country_residence: GB
    form: trademark_complaint
    full_name: ***
    hidden_ctx:
    hidden_product: googleplay
    origin: helpcenter
    phone: ***
    signature: ***
    signature_date_day: 29
    signature_date_month: 4
    signature_date_year: 2013
    tm_good_faith: checked
    tm_infringement_explanation: The app is called "Orange Back-Up" which
    suggests it is a back-up service offered by Orange - the globally
    recognised telecommunications brand.

    Orange Brand Services Limited has extensive intellectual property rights
    including numerous trade marks protecting Orange as part of its global
    trade mark portfolio.



    The Developer has no rights to use Orange Brand Services Limited's "ORANGE"
    trade marks and there is no authorized use of Orange by the trade mark
    proprietor to the Developer.

    We are most concerned that this could cause confusion and our concerns are
    heightened as the description provided states that "this application is not
    linked in any way with Orange Telecom". This suggests there may have been
    confusion and the Developers are aware of this problem.

    Orange uses a similar colour palette (orange, white, black and grey) for
    its communications and apps so there is very little to distinguish this app
    (orange on a black background) from a genuine Orange app.

    Orange has its own apps and does not wish for there to be any confusion
    with Orange's own apps and this one.

    We should be grateful if you would remove this app before it damages
    Orange's reputation by causing customer confusion.
    tm_location_and_number: ORANGE - CTM registration number 8164758 in
    classes: 09, 16, 18, 25, 35, 36, 37, 38, 41 and 42.

    European Community together with a global trade mark portfolio protecting
    the word "ORANGE" and the orange colour (pantone 151) and square device/
    logo in a large number of countries throughout the world.
    tm_swear: checked
    tm_work: "ORANGE" word trade mark.
    your_title: Senior Legal Counsel





    And here is my answer:

    Hi ***,


    I am the developer of the Orange Backup application.


    I have just been notified that you have requested the removal of this

    application on the Play Store in every European Country in a claim to

    Google dated as of 29/04/2013.


    I am very surprised that you didn't take the time to contact me

    before asking to Google to remove my application.


    According to your claim, I understand that you have protected the word

    Orange and the squared Orange logo.


    "European Community together with a global trade mark portfolio protecting

    the word "ORANGE" and the orange color (pantone 151) and square device/

    logo in a large number of countries throughout the world. "


    You have based your claim on the CTM n 8164758:

    "tm_location_and_number: ORANGE -

    CTM registration number 8164758 in classes: 09, 16, 18, 25, 35, 36,

    37, 38, 41 and 42."


    I have attached to this email the Certified copy of the Registration

    Certificate with the registration number 8164758 as extracted from

    OHIM website.


    According to the attached certificate, the word mark "ORANGE" is

    protected for these classes *only*: 14, 18, 21, 26, 28, 30 ,35, 36,

    38, 39, 41 and 43.


    Interpretation of NICE classification can be found at this address:

    http://web2.wipo.int/nicepub/editio...lat&explanatory_notes=hide&basic_numbers=show (tenth edition)


    As described in the Play Store, the application "Orange Backup" is a

    software to make a "Nandroid" backup. Nandroid backup is a backup of

    all the device. It is needed to restore a software broken device

    because of some software low level modification (very common on

    android platform). It doesn't backup on a file per file basis but data

    as a whole (technically it backups the totality of a partition in a

    single image file), that's why when opening the application in an

    Android device, you will see that there is no option to select a

    specific file to backup.


    When using Orange Backup application, all software plus the data,

    the boot/recovery partition (needed to start any Android device),

    and other very low level data are backed up and can be restored as a

    whole in the future.


    To make it simple, it is like taking a picture of the state of the

    data of your Android device at a given time, and being able to go back to

    this exact state in the future.


    This application is clearly an Android device *recovery* application.


    Because of the main purpose of the application, it seems to me that it

    falls in the class 42 as it is defined in the NICE classification, and

    in particular in section "420175 - recovery of computer data".


    This class is cited in the claim you have sent to Google but is not

    listed in the Community Trade Mark with registration number 8164758.


    The second point that I have noticed is that the brand protected is

    "ORANGE" and not "Orange Backup". Moreover, a simple search of

    "orange" word on the Play Store

    (https://play.google.com/store/search?q=orange&c=apps) shows a huge

    number of application having Orange word in their name. All the one I

    tried are not banned in France. It doesn't match with the reasons you

    gave in your claim to Google (confusion in the mind of the user).

    "We should be grateful if you would remove this app before it damages

    Orange's reputation by causing customer confusion. "


    So it seems to me that "Orange Backup" name is not violating the

    Community Trade Mark 8164758 because the application is in class 42

    and the name is "Orange Backup". So I think that your claim to Google

    have no legal basis which is very unfortunate because you are causing

    me a real prejudice.


    However, even if I don't think I am violating your CTM, I want to

    close this case very rapidly and would agree to a deal.

    [REMOVED SENSITIVE DATA]


    So here is the deal I want to make with your company:

    I would agree to change immediately the name of the application from

    "Orange Backup" to "2BOrange". With this new name there is no risk to

    create any confusion between my application and "ORANGE" brand.

    Moreover, this new name is even farther from the domain protected by

    your CTM. In exchange I am asking you to notify to Google that my

    application is not infringing your brand anymore.


    For obvious reasons, I will keep the community following this

    application informed of what is happening, so they will understand why

    the application is not available anymore through the Play Store.


    Please, answer to this message *promptly* so I will know you are

    taking care of this case.

    Otherwise I will have to take a legal action against your company.



    Best regards,
    ***


    To make it simple, a brand is not protected for everything. You need to declare how you think to use it, and you need to use it the way you have described...

    Fortunately I think Orange's claim is not legally based, and so I have a chance to make a deal with them.

    Indeed, I don't think I am violating their brand because the ORANGE brand is not protected when it is used for a recovery software (you can protect a brand only for certain use).

    Even if I am happy that my case is strong, I am angry for two reasons, :
    - Orange didn't take the time to contact me first!
    - ...and Google didn't check the information provided by Orange, which are false (domain protected by the Brand in the claim does not match the domain protected by the brand as declared at the registration of the brand, it takes few minutes to check!).

    However, I want things to be fixed rapidly and I have asked them to remove their claim if I change the name of the application to "2BOrange".

    I keep you informed of the evolution. Tomorrow I hope to will get some news.

    It s really bad because I have wasted my day in writing the email, correct it and make legal search instead of programming...

    Thank you Google for protecting Indie dev against brand owner.


    Regards

    Edit: in case you care, I am not answering Orange email as a Lawyer but as the developer of an Android application, so I have not to respect the Lawyer French ethic code, and in particular the secret of correspondence.

    The Orange brand registration document (list the protected class):
    https://www.dropbox.com/s/fscxk0zn25t1qy1/I_TM_0007031593_0.pdf

    Edit2: updated my email with the last version... of the email!
    23
    Awesome news!!!

    Guess....


    Orange agreed on asking to Google to un ban us!

    Don't know how much time it takes, but that's great!!!!! :victory: :fingers-crossed: :good: :good: :good:

    Regards
    19
    Too much time lost on this legal stuff...

    Let s focus on real things.

    I rewrote the file rights part.

    Let me know if it improves things for you.

    Regards

    -> release v 1.29 beta 1
    18
    Just to continue to keep you informed, I have not yet sent the email, I use to prepare things and wait few hours before sending the stuff on the net.

    I did my jogging and realized that the use of maintenance software category to explain why Orange Backup should be classified in category 42 is weak. There are many way to understand maintenance software. You may say it is the service to keep software updated or something like that.

    So I searched something else, and here came a little miracle!!!

    I re read the NICE guideline, and found something really interesting. There is a category for recovery software in class 42.

    To make it short, they are not protecting the use of Orange word for Software in the class 42. I think it makes my case really strong.

    I am really happy of that finding!

    Moreover I have added an idea from this thread to the email: I have highlighted the fact that there are still tons of application having Orange in their name and not banned!


    Finally, I will write to some blogs what happened, because the system is not fair for indie dev.

    We all now the brand protection concept. There are some abuse, it s well know, and that's not what I want to speak about.

    The real issue here is how Google manage the thing:

    1/ They didn't check the claim from Orange because there is an obvious error inside it (the list of class protected in the claim don't match the real registration, it took me few minutes to check if what Orange was saying was true).
    2/ And the second big issue is that acording to the email from Google it is up to the owner of the brand (Orange) to decide if I will be un banned or not.

    My case is just an example of what can happen where the owner of a brand (big money able to pay to protect a word like the color Orange) abuse of its right.

    And even if Orange is right for some reasons I am not aware today, the system of Google letting the owner of the brand deciding of the future of the other application, it s just a break of the most basic justice rule, you can't be at the same time a judge and a party!

    Because I never read something about this matter, and I thing any dev should be aware of that, I will do my best to make some noise. It has to change!

    If some of you knows an Android blogger, let him know about this story. Anyone interested can contact me by PM if there is a need for more information.


    Regards