de en es fr
Let the machine help
Light teasing, exhibition, BDSM, sissyfication, watersports... with sounds and pictures


Post new topic Reply to topic  Page 1 of 2
  [ 17 posts ]  Go to page 1, 2  Next
  Print view Previous topic | Next topic 
Author Message
epton
 Bugs in the Android app
PostPosted: Mon Apr 11, 2016 1:27 pm 
Offline
Newcomer
There are many script that I can not download, it just gives an error
plus there are few scripts like 'eyes up here' where no .jpg was downloaded.

the camp drain gives me Functional Error when im trying to run it


thanks for your hard work :D
Top
 Profile Send private message 
 
doti
 Re: Bugs in the Android app
PostPosted: Mon Apr 11, 2016 3:19 pm 
Offline
Site Admin
User avatar
Thank you

What is the error - Do you know about quotas ?
What is your Android version please ?

Eyes'up there, and some other scripts : this is a problem about case sensitivity (searching for Default_main.jpg, default_main.jpg exists. I'll let a notice to Banjo.

Camp Drain : it won't work, it does some very special code that don't work in Android (uses the groovy.lang.GroovyClassLoader(), similar to Eval.me ). Perhaps we should add a "noandroid" tag that would exclude currently failing scripts.
Top
 Profile Send private message 
 
Dhccpmc
 Re: Bugs in the Android app
PostPosted: Thu Jun 09, 2016 2:04 am 
Offline
Newcomer
Everytime I start the app for the first time I get an error that goes something like
"Error
Java.lang.classcastexception:
Libcore.net.url.fileurlconnection
Cannot be cast to
Java.net.httpurlconnection"

Nothing I do seems to fix it
Top
 Profile Send private message 
 
doti
 Re: Bugs in the Android app
PostPosted: Thu Jun 09, 2016 5:57 pm 
Offline
Site Admin
User avatar
Ok, I'm on it
Top
 Profile Send private message 
 
doti
 Re: Bugs in the Android app
PostPosted: Fri Jun 17, 2016 10:10 am 
Offline
Site Admin
User avatar
What is your Android version please ?
When does this problem occurs ? When you start the app, before going to any menu ?
Is there any consequences on the behaviour of the application afterward ?
Top
 Profile Send private message 
 
doti
 Re: Bugs in the Android app
PostPosted: Mon Jan 02, 2017 12:16 pm 
Offline
Site Admin
User avatar
This error should no more occur now.

We couldn't find any error on Android 6 (emulator) ; perhaps on some real hardware there will be something to see.
Top
 Profile Send private message 
 
connact113
 Re: Bugs in the Android app
PostPosted: Fri Apr 07, 2017 10:08 pm 
Offline
Regular
Can you recommend a good logger that will work on a non rooted device. My phone running Marshmallow and the app crashes every time I open it. Phone is not rooted and don't plan on rooting it. Not sure where log files are stored or if they are acceesible. The app did work for awhile but stopped after a phone update.
Top
 Profile Send private message 
 
doti
 Re: Bugs in the Android app
PostPosted: Sat Apr 08, 2017 10:28 am 
Offline
Site Admin
User avatar
Which version of Android ?
Or do you have a PC (Linux, Windows, OS X) with a data USB cable ?

You can try this :
Quote:
If you want the user to give you debugging information, you can have them generate a bug report with power + volume down + volume up which includes the logs and lots of other data, and automatically brings up their e-mail app to sent it all (plus a screenshot). We were just discussing that we should have an easier way to generate these as well, I am going to look at adding something to the settings app.
Top
 Profile Send private message 
 
connact113
 Re: Bugs in the Android app
PostPosted: Sat Apr 08, 2017 2:12 pm 
Offline
Regular
Android version 7.0. S7 edge. I have a cable to connect phone to pc. The volume up/down power button doesn't do anything.
Top
 Profile Send private message 
 
doti
 Re: Bugs in the Android app
PostPosted: Sat Apr 08, 2017 2:26 pm 
Offline
Site Admin
User avatar
Still possible, if you want to give a try :

Commands to see log, in case of Android crash and not rooted

(strategy : running the tool "adb", from the Android SDK, with the option "logcat", on a PC plugged to the device)
  • Install android SDK on your PC (skip this if you already installed it with Android Studio)
  • Plug your device with an USB data cable (don't choose USB storage, if asked for)
  • Turn on developper mode and USB debugging on your device : details here ; its not as dangerous as rooting, far from it
  • (may be not needed) : install specific drivers on your PC, depending on your device, like here
  • Launch a command line, a terminal (for example on Windows : [window]+r, cmd[enter])
  • Inside the terminal, go to the directory of [SDK]/platform-tools with "cd", like "cd c:\users\me\android-sdk\platform-tools\"
  • Then run this command : > adb devices
  • If it shows your device, continue. If not, you needs drivers
  • Run > adb logcat
  • It shows you the log while its creation. You'll be able to find "ss.android" messages during the crash ; copy-paste them in SexScripts forum inside a "Code" tag.
Top
 Profile Send private message 
 
connact113
 Re: Bugs in the Android app
PostPosted: Mon Apr 10, 2017 11:55 pm 
Offline
Regular
I think this is the section that is relevant since the word groovy jumped out at me:

Code:
urfaceFlinger: id=233 Removed OovaLaunche (1/9)
04-10 17:52:56.617   713  5348 I SurfaceFlinger: id=233 Removed OovaLaunche (-2/9)
04-10 17:52:56.621  4417 16387 D ForegroundUtils: could not check pending caller
04-10 17:52:56.650 28083 28106 I System.out: HeyzapThreadPool calls detatch()
04-10 17:52:56.652 28083 28108 I System.out: HeyzapThreadPool calls detatch()
04-10 17:52:56.739 28083 28086 I art     : Do partial code cache collection, code=6KB, data=20KB
04-10 17:52:56.739 28083 28086 I art     : After code cache collection, code=6KB, data=20KB
04-10 17:52:56.739 28083 28086 I art     : Increasing code cache capacity to 128KB
04-10 17:52:56.741 28083 28086 I art     : Compiler allocated 8MB to compile groovyjarjarantlr.Token org.codehaus.groovy.antlr.parser.GroovyLexer.nextToken()
04-10 17:52:56.753  1558  2575 D MdnieScenarioControlService:  packageName : ss.android    className : ss.android.MainActivity
04-10 17:52:56.780 28083 28115 E AndroidRuntime: FATAL EXCEPTION: Thread-9
04-10 17:52:56.780 28083 28115 E AndroidRuntime: Process: ss.android, PID: 28083
04-10 17:52:56.780 28083 28115 E AndroidRuntime: BUG! exception in phase 'semantic analysis' in source unit 'script1491861176542275781711.groovy' throw with null exception
04-10 17:52:56.780 28083 28115 E AndroidRuntime:        at org.codehaus.groovy.control.CompilationUnit.applyToSourceUnits(CompilationUnit.java:935)
04-10 17:52:56.780 28083 28115 E AndroidRuntime:        at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:593)
04-10 17:52:56.780 28083 28115 E AndroidRuntime:        at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:542)
04-10 17:52:56.780 28083 28115 E AndroidRuntime:        at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298)
04-10 17:52:56.780 28083 28115 E AndroidRuntime:        at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268)
04-10 17:52:56.780 28083 28115 E AndroidRuntime:        at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:254)
04-10 17:52:56.780 28083 28115 E AndroidRuntime:        at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:211)
04-10 17:52:56.780 28083 28115 E AndroidRuntime:        at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:221)
04-10 17:52:56.780 28083 28115 E AndroidRuntime:        at ss.android.GrooidShell.evaluate(GrooidShell.java:93)
04-10 17:52:56.780 28083 28115 E AndroidRuntime:        at ss.android.MainActivity$18.run(MainActivity.java:759)
04-10 17:52:56.780 28083 28115 E AndroidRuntime: Caused by: java.lang.NullPointerException: throw with null exception
04-10 17:52:56.780 28083 28115 E AndroidRuntime:        at java.net.URLClassLoader.findClass(URLClassLoader.java:371)
04-10 17:52:56.780 28083 28115 E AndroidRuntime:        at java.lang.ClassLoader.loadClass(ClassLoader.java:380)
04-10 17:52:56.780 28083 28115 E AndroidRuntime:        at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:677)
04-10 17:52:56.780 28083 28115 E AndroidRuntime:        at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:545)
04-10 17:52:56.780 28083 28115 E AndroidRuntime:        at org.codehaus.groovy.control.ClassNodeResolver.tryAsLoaderClassOrScript(ClassNodeResolver.java:185)
04-10 17:52:56.780 28083 28115 E AndroidRuntime:        at org.codehaus.groovy.control.ClassNodeResolver.findClassNode(ClassNodeResolver.java:170)
04-10 17:52:56.780 28083 28115 E AndroidRuntime:        at org.codehaus.groovy.control.ClassNodeResolver.resolveName(ClassNodeResolver.java:126)
04-10 17:52:56.780 28083 28115 E AndroidRuntime:        at org.codehaus.groovy.control.ResolveVisitor.resolveToOuter(ResolveVisitor.java:676)
04-10 17:52:56.780 28083 28115 E AndroidRuntime:        at org.codehaus.groovy.control.ResolveVisitor.resolve(ResolveVisitor.java:308)
04-10 17:52:56.780 28083 28115 E AndroidRuntime:        at org.codehaus.groovy.control.ResolveVisitor.resolveFromDefaultImports(ResolveVisitor.java:454)
04-10 17:52:56.780 28083 28115 E AndroidRuntime:        at org.codehaus.groovy.control.ResolveVisitor.resolve(ResolveVisitor.java:308)
04-10 17:52:56.780 28083 28115 E AndroidRuntime:        at org.codehaus.groovy.control.ResolveVisitor.resolveFromStaticInnerClasses(ResolveVisitor.java:429)
04-10 17:52:56.780 28083 28115 E AndroidRuntime:        at org.codehaus.groovy.control.ResolveVisitor.resolve(ResolveVisitor.java:308)
04-10 17:52:56.780 28083 28115 E AndroidRuntime:        at org.codehaus.groovy.control.ResolveVisitor.resolveFromStaticInnerClasses(ResolveVisitor.java:429)
04-10 17:52:56.780 28083 28115 E AndroidRuntime:        at org.codehaus.groovy.control.ResolveVisitor.resolve(ResolveVisitor.java:308)
04-10 17:52:56.780 28083 28115 E AndroidRuntime:        at org.codehaus.groovy.control.ResolveVisitor.visitClass(ResolveVisitor.java:1218)
04-10 17:52:56.780 28083 28115 E AndroidRuntime:        at org.codehaus.groovy.control.ResolveVisitor.startResolving(ResolveVisitor.java:176)
04-10 17:52:56.780 28083 28115 E AndroidRuntime:        at org.codehaus.groovy.control.CompilationUnit$11.call(CompilationUnit.java:651)
04-10 17:52:56.780 28083 28115 E AndroidRuntime:        at org.codehaus.groovy.control.CompilationUnit.applyToSourceUnits(CompilationUnit.java:931)
04-10 17:52:56.780 28083 28115 E AndroidRuntime:        ... 9 more
04-10 17:52:56.781 28083 28086 I art     : Do partial code cache collection, code=48KB, data=61KB
4-10 17:52:56.781 28083 28086 I art     : Do partial code cache collection, code=48KB, data=61KB
04-10 17:52:56.781 28083 28086 I art     : After code cache collection, code=48KB, data=61KB
04-10 17:52:56.781 28083 28086 I art     : Increasing code cache capacity to 256KB
04-10 17:52:56.781  1558  1886 I WindowManager: Destroying surface Surface(name=Starting ss.android) called by com.android.server.wm.WindowStateAnimator.destroySurface:2838 com.android.server.wm.WindowStateAnimator.destroySurfaceLocked:1069 com.android.server.wm.WindowState.destroyOrSaveSurface:2534 com.android.server.wm.AppWindowToken.destroySurfaces:412 com.android.server.wm.AppWindowToken.destroySurfaces:376 com.android.server.wm.WindowStateAnimator.finishExit:654 com.android.server.wm.WindowStateAnimator.stepAnimationLocked:564 com.android.server.wm.WindowAnimator.updateWindowsLocked:431
04-10 17:52:56.782   713  5524 I SurfaceFlinger: id=235 Removed bndroid (4/8)
04-10 17:52:56.782  1558  3863 D Debug   : !@DumpState : SHIP
04-10 17:52:56.782  1558  3863 D Debug   : !@DumpState : debug level:0x4f4c
04-10 17:52:56.782  1558  3863 D Debug   : !@Dumpstate : Finally, system will skip dumpstate
04-10 17:52:56.785 28083 28101 I System.out: HeyzapThreadPool calls detatch()
04-10 17:52:56.789  3852  3852 D io_stats: !@   8,0 r 362190 18882360 w 53282 1060712 d 31477 2017128 f 18074 18071 iot 168190 134514 th 266512 0 0 pt 0 inp 0 0 2822.171
04-10 17:52:56.789   713  5524 I SurfaceFlinger: id=235 Removed bndroid (-2/8)
04-10 17:52:56.795  1558  3863 W ActivityManager:   Force finishing activity ss.android/.MainActivity
Top
 Profile Send private message 
 
connact113
 Re: Bugs in the Android app
PostPosted: Wed Apr 12, 2017 11:53 pm 
Offline
Regular
is this the applicable section? Any good info in here to help trouble shoot? It has to be related to some Android or ATT update as the program worked fine until it didn't, and uninstalling and reinstalling the apk has no results.
Top
 Profile Send private message 
 
doti
 Re: Bugs in the Android app
PostPosted: Thu Apr 13, 2017 8:29 am 
Offline
Site Admin
User avatar
I still couldn't check, I'll do in a few days.
Top
 Profile Send private message 
 
connact113
 Re: Bugs in the Android app
PostPosted: Fri May 12, 2017 10:31 pm 
Offline
Regular
following up on the bug. Still can't get it to work.
Top
 Profile Send private message 
 
doti
 Re: Bugs in the Android app
PostPosted: Sun May 14, 2017 11:40 am 
Offline
Site Admin
User avatar
I'm still trying to create a matching test bench. I have a lot of problem with nougat
Top
 Profile Send private message 
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  Page 1 of 2
  [ 17 posts ]  Go to page 1, 2  Next

Board index » Glitches

All times are UTC + 1 hour [ DST ]

Who is online

Users browsing this forum: No registered users and 4 guests

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  


Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group
Maroon Fusion theme created by Oxydo
Software, theme modifications, phpBB modification by Doti 2010 - 2020
This website uses session cookies only.