Database Users

[Q] responding to screen lock/sleep

Hi everyone
I have an irritating dilemma. Whenever the screen goes to sleep/locks, SOMETHING happens and then it crashes when you turn it on again.
let me clarify a bit.
My app is an opengl game. Textures are loaded on the game(logic) thread. the game thread is started by the main thread in the onCreate method.
However,
when the screen wakes up from sleep or 'unlocks' the main threads onCreate gets called again, and therefore textures are loaded again and this make the app run out of memory and crash.
and this ONLY happens when the screen locks, switching between applications works just fine.
----
my question is this:
what happens when the screen goes to sleep or locks? Why does onCreate get called multiple times, and why the hell is there like no information about this specific thing in the Android docs?
EDIT:
also, what happens to threads when the screen is off. Are they terminated or frozen or something?
THANKS!

I would assume your activity is being destroyed/torn down, threads continue to run but become eligible for GC AFAIK.
You should really plan for this in your life-cycle. Do cleanup in onPause, onStop and onDestroy. And check to see if threads/ textures exist in onCreate() onResume() and onStart()
This is actually a generally good habit to be in when writing methods. If you design them in such a way that if they get called multiple times your app will react correctly anyways.
hth

alostpacket said:
I would assume your activity is being destroyed/torn down, threads continue to run but become eligible for GC AFAIK.
You should really plan for this in your life-cycle. Do cleanup in onPause, onStop and onDestroy. And check to see if threads/ textures exist in onCreate() onResume() and onStart()
This is actually a generally good habit to be in when writing methods. If you design them in such a way that if they get called multiple times your app will react correctly anyways.
hth
Click to expand...
Click to collapse
definitely is a good practice to assume nothing and always check for pre-existing textures, values, threads and to either decide to destroy and recreate them or to use the pre-existing values. its a good way to minimize memory leakage and values without pointers, though the vm does a good job of cleanup.

[Q] Straight Answer on CIQ

I'm assuming that, for the most part, the apps on the Market that are designed to "discover" CIQ or traces of it are going to look for any small thing that might be left over from the removals, regardless of whether or not it's actually still part of our ROMs. That said, for all our devs who've put out ROMs that claim to not have CIQ on board, how do we know for sure that it's been removed?
Case in point - I'm currently running ACS ICS v5, and every ACS release that I've been on has claimed to have CIQ removed - yet, I ran 4 different CIQ discovery apps on a whim this morning, and they all claimed to find Carrier IQ on board. Is it just hype, or have we been missing something all along?
/and by "we," I mean, all the devs who work way harder on this stuff than me
//is basically just a ROM slut

From what I've read, the CIQ code is still baked into the kernel. BUT because the guts of CIQ were removed, the code has nothing to talk to.
That may be the culprit being detected. If you are getting other "false positives" then post screen shots of your output.

I am running SRF 1.2 still and from the OP for that ROM states that it is completely removed, not disabled or partitially removed.
"What's the secret sauce? Carrier IQ, the infamous Sprint spyware package, has been completely removed! More details in the second post - you won't believe what we found! Themers and other mod developers take note, many modifications were made to the system in order to achieve this exclusive feature."
When I run Voodoo CIQ app it says.
Carrier IQ has been found and is active
Detection score: 370
Test for: Android logcat debugging log
(LOGCAT, weight 100)
found: I/ActivityManager( 2840): Start proc android.iqd for broadcast android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver: pid=9960 uid=1000 gids={3003, 3002, 3001, 1015, 1006}
found: I/ActivityManager( 2840): Start proc android.iqd for broadcast android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver: pid=9960 uid=1000 gids={3003, 3002, 3001, 1015, 1006}
found: I/ActivityManager( 2840): Start proc android.iqd for broadcast android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver: pid=9960 uid=1000 gids={3003, 3002, 3001, 1015, 1006}
found: D/ ( 9960): onReceive Intent { act=com.sprint.android.SPRINTEXTENSION_STARTED cmp=android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver }
found: D/ ( 9960): onReceive Intent { act=com.sprint.android.SPRINTEXTENSION_STARTED cmp=android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver }
Test for: ROM binaries and daemons
(SYSTEM_BINARIES, weight 70)
found: /system/bin/iqmsd
found: /system/lib/libiq_client.so
Test for: Running processes
(RUNNING_PROCESSES, weight 200)
found: system 9960 2376 213724 14076 ffffffff 00000000 S android.iqd
Test for: Suspicious classes
(SUSPICIOUS_CLASSES, weight 0)
found: com.carrieriq.iqagent.service.receivers.BootCompletedReceiver

Yeah, I guess Voodoo is the one I hadn't run yet - according to that, I'm in the clear:
Voodoo Carrier IQ Detector report:
Build fingerprint:
sprint/SPH-D700/SPH-D700:2.3.5/GINGERBREAD/EI22:user/release-keys
Carrier IQ elements found
− however it seems inactive
Detection score: 170
Test for: Linux kernel interfaces
(KERNEL_INTERFACES, weight 50)
nothing found
Test for: Android logcat debugging log
(LOGCAT, weight 100)
found: I/ActivityManager( 285): Start proc android.iqd for broadcast android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver: pid=2073 uid=1000 gids={3002, 3001, 1015, 1006, 3003, 1001}
found: I/ActivityManager( 285): Start proc android.iqd for broadcast android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver: pid=2073 uid=1000 gids={3002, 3001, 1015, 1006, 3003, 1001}
found: I/ActivityManager( 285): Start proc android.iqd for broadcast android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver: pid=2073 uid=1000 gids={3002, 3001, 1015, 1006, 3003, 1001}
found: D/ ( 2073): onReceive Intent { act=com.sprint.android.SPRINTEXTENSION_STARTED cmp=android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver }
found: D/ ( 2073): onReceive Intent { act=com.sprint.android.SPRINTEXTENSION_STARTED cmp=android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver }
found: I/ActivityManager( 285): No longer want android.iqd (pid 2073): hidden #16
Test for: Linux kernel drivers
(KERNEL_DRIVERS, weight 50)
nothing found
Test for: System services
(SERVICES, weight 70)
nothing found
Test for: ROM binaries and daemons
(SYSTEM_BINARIES, weight 70)
found: /system/bin/iqmsd
found: /system/lib/libiq_service.so
found: /system/lib/libiq_client.so
Test for: ROM configs
(ETC_CONFIG, weight 0)
nothing found
Test for: Packages
(PACKAGES, weight 70)
nothing found
Test for: Running processes
(RUNNING_PROCESSES, weight 200)
nothing found
Test for: Suspicious classes
(SUSPICIOUS_CLASSES, weight 0)
found: com.carrieriq.iqagent.service.receivers.BootCompletedReceiver
Test for: Linux kernel dmesg log
(DMESG, weight 100)
nothing found

Mine had a score of 170 and then re-ran it to show someone that mine is inactive and then the score jumped to 370 and said active. I'm thinking wtf...

when creating the CIQ mod, k0nane had to leave certain directories in order for things to work. They're completely empty of the files that were in them, but their existence will register on the voodoo app until supercurio and k0nane fine tune the detection. CIQ is removed from your phone it you're running a CIQ-free rom. This is says the yellow warning that elements may still exist but CIQ may not be present.

The Root said:
when creating the CIQ mod, k0nane had to leave certain directories in order for things to work. They're completely empty of the files that were in them, but their existence will register on the voodoo app until supercurio and k0nane fine tune the detection. CIQ is removed from your phone it you're running a CIQ-free rom. This is says the yellow warning that elements may still exist but CIQ may not be present.
Click to expand...
Click to collapse
/thread 10char

I trust Konane a lot more than some random app. He is the one that warned us all about this and has made sevetal phones ciq free.
Sent from my Epic on Legend or my Galaxy Tab rooted (feels naked without a ROM)

lancelane said:
I trust Konane a lot more than some random app. He is the one that warned us all about this and has made sevetal phones ciq free.
Sent from my Epic on Legend or my Galaxy Tab rooted (feels naked without a ROM)
Click to expand...
Click to collapse
As do I, believe me. I'm new on the boards, but I've been lurking for at least a year now, and I've never had any reason to doubt our devs' fine work Like I said, I mostly tried out those detection apps on a whim, since I had no reason to believe that CIQ was still active on my ROMs (and obviously it's been a current event of sorts) and it just kind of threw me for a loop when I got the results that I did. Anyway, thanks to the community for such quick answers, hopefully I didn't come off as too hostile in my first post!

rekrdskratcher said:
As do I, believe me. I'm new on the boards, but I've been lurking for at least a year now, and I've never had any reason to doubt our devs' fine work Like I said, I mostly tried out those detection apps on a whim, since I had no reason to believe that CIQ was still active on my ROMs (and obviously it's been a current event of sorts) and it just kind of threw me for a loop when I got the results that I did. Anyway, thanks to the community for such quick answers, hopefully I didn't come off as too hostile in my first post!
Click to expand...
Click to collapse
You must not have read the disclaimer on the app. It says it may report false positives still.

Cautionary Tale: Always lock your Arrays in game development

Thought I would record my troubles with a game render loop and a logic engine given a particular bug has swallowed up about a week of my time. I am posting it incase anyone else happens to have the same problem/symptomns.
It originated when I wrote the LogicEngine which has an ArrayList of GameObjects and iterates through them deleting them as nessesary depending on the results of thier processStep.
The render thread would occasionally crash when something was deleted from the array while the list was being drawn but this happened quite rarely. No problem I thought, I'll just catch the out of bounds exception and it will get displayed on the next frame however many milliseconds later.
This all went well for 3 months of coding till I got to programming terrain where about 300 blocks were all displayed gradually scrolling down the screen. The blocks would flash intermittently but in sections not all at once.
At first I thought it was too many blocks for the LogicEngines collision detection so I doubled the size of the blocks. Then I thought it might be overhead allocating memory for the blocks and preloaded them in the constructor. Eventually in despair I disabled the deletion of blocks once they went offscreen and noticed the flashing stopped. This was the point I realised what was happening: The LogicEngine would delete a row of blocks because they went offscreen and the Renderer would be half way through drawing and instead of crashing it would just skip x blocks wherever it was in the for loop at the time that the LogicEngine removed them.
Wow I feel stupid, especially because of the lazy Exception catching solution I originally implemented which masked the problem for so long.
Code:
GameRender.java
//draw obstacles
theLogicEngine.objectsObstaclesLock.writeLock().lock();
for(int i=0 ; i<theLogicEngine.objectsObstacles.size();i++)
{
drawObject(theLogicEngine.objectsObstacles.get(i));
}
theLogicEngine.objectsObstaclesLock.writeLock().unlock();
LogicEngine.java
for(int i=0;i<objectsObstacles.size();i++)
if(objectsObstacles.get(i).processStep(this)) //we are to delete this object
{
objectsObstaclesLock.writeLock().lock();
//remove self if necessary
//move object returned true so delete object
GameObject toDelete = objectsObstacles.get(i);
objectsObstacles.remove(i);
toDelete.dispose();
i--;
objectsObstaclesLock.writeLock().unlock();
}
TLDR: If you have an ArrayList that can be edited by one thread, make sure you lock it rather than just catching the ArrayOutOfBoundsException

Glad you figured it out
I am still impressed that you can write Android games using these techniques. Is your game low-res or is Dalvik that powerful?
I mean, you are using Java, which is one thing, but then you use ArrayList and you delete objects as you go. I take this to mean that you do not recycle them in a pool.
Am I correct?

cyansmoker said:
Glad you figured it out
I am still impressed that you can write Android games using these techniques. Is your game low-res or is Dalvik that powerful?
I mean, you are using Java, which is one thing, but then you use ArrayList and you delete objects as you go. I take this to mean that you do not recycle them in a pool.
Am I correct?
Click to expand...
Click to collapse
ArrayList is self managing.
All of Java's garbage collection is done automatically. As a Java dev u can call System.gc but this only suggest the system attempt gc.
Dalvik is pretty good, but anything extensive I would go native...
Sent from my Galaxy Nexus using Tapatalk

jug6ernaut said:
ArrayList is self managing.
Click to expand...
Click to collapse
Right. But then there is the memory consumption issue. That's why I typically do things as described in this blog entry.
jug6ernaut said:
All of Java's garbage collection is done automatically. As a Java dev u can call System.gc but this only suggest the system attempt gc.
Click to expand...
Click to collapse
Although in System.gc()'s defense I've always observed that it was run immediately in Sun's ref. implementation. Not sure about Dalvik.
But overall I agree with your conclusion.

cyansmoker said:
I am still impressed that you can write Android games using these techniques. Is your game low-res or is Dalvik that powerful?
Click to expand...
Click to collapse
So far I have not been having any performance issues. The ArrayLists contain GameObjects which are quite lightweight memory wise as they do not contain Textures.
Textures are maintained in separate dictionary with a string key.
I did try recycling GameObjects in one location where I was spawning / destroying a lot but it didn't really seem to impact performance much.
I think my biggest area for optimisation at the moment is in collision direction. Currently there are about 5 different ArrayLists (Obstacles, Enemies, Players, Player Bullets, Enemy Bullets etc) only those that interact are tested for collision (Vector2d distance < objects collision radius). I think theres probably opportunity to split it further into quads.
I've yet to build in proper optimisation checking but it plays fine in 320x480 with ~100 enemies on screen and 4 player ships with maybe 20 bullets on screen at once with a turnover of 5/10 GameObjects a second. Even with this number though Texture memory usage is low with most enemies between 16x16 and 48x48.
I think libgdx and the behaviours library I use are pretty optimised.

[BETA] Twee - Keep track of your tv series

Hi!
I am pretty new to android/java-programming and has been developing an app for a while. The purpose of the app is to keep track of the tv series you follow. I would love it for you guys to download it and try it out, come up with new features and also find bugs
The app is now up on play store https://play.google.com/store/apps/...lt#?t=W251bGwsMSwxLDEsInNlLmphMTk4NC50d2VlIl0.
And some images: (these images are somewhat outdated, newer images are on play store)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks in advance!
//_b

Nice and first! Downloading now...Thanks

john9 said:
Nice and first! Downloading now...Thanks
Click to expand...
Click to collapse
Nice Any feedback?
//_booty

Nice app. Love the UI. Unfortunatly I get lots of FC when adding shows.
I would love to see a black theme.
Again really like this app.
I am running Galaxy S3 with Omega v10 and siyah 1.5beta
Keep up the good work. I can see a winner here
Sent from my GT-I9300 using XDA Premium HD app

iTrondsen said:
Nice app. Love the UI. Unfortunatly I get lots of FC when adding shows.
I would love to see a black theme.
Again really like this app.
I am running Galaxy S3 with Omega v10 and siyah 1.5beta
Keep up the good work. I can see a winner here
Sent from my GT-I9300 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for the feedback I think i know why it crashes when adding series, i will look in to it today
About the dark themes i will take a look at implementing holo dark and holo dark/Light as well as the holo Light that are default now.
By the way native english speaking people, men do one say show or series?
//_booty

_booty said:
Thanks for the feedback I think i know why it crashes when adding series, i will look in to it today
About the dark themes i will take a look at implementing holo dark and holo dark/Light as well as the holo Light that are default now.
By the way native english speaking people, men do one say show or series?
//_booty
Click to expand...
Click to collapse
You said there's a chance of 2.3.x version? I love the looks of this.

ryanstfl said:
You said there's a chance of 2.3.x version? I love the looks of this.
Click to expand...
Click to collapse
As I said I´m pretty new to android/java but i will defenetly look in to make it work for 2.3 and up!
//_booty

New version is up with a few bug fixes! I have updated OP!

i am currently using "TV show favs" app for the purpose. Anyone see significant difference between the two ? screenshots look identical

This is awesome! Thanks
I noticed two things:
1. When I mark series as watched it doesn't mark off all the episodes - Is it supposed to work like that or am I using the feature wrong?
2. The toast notification after marking the series as watched says "All episodes has been marked as watched" - It should probably say "All episodes have been marked as watched"
Now anyone have any recommendations for things to watch?

rohith_luffy said:
i am currently using "TV show favs" app for the purpose. Anyone see significant difference between the two ? screenshots look identical
Click to expand...
Click to collapse
As of now the shows favs are probably better, but I am improving this May I ask what the key features in TV shows.... are that make you choose that app? Maybe I can implement them as well
MdinizMobile said:
i like it !! :good:
Click to expand...
Click to collapse
Thanks!
theadb said:
This is awesome! Thanks
I noticed two things:
1. When I mark series as watched it doesn't mark off all the episodes - Is it supposed to work like that or am I using the feature wrong?
2. The toast notification after marking the series as watched says "All episodes has been marked as watched" - It should probably say "All episodes have been marked as watched"
Now anyone have any recommendations for things to watch?
Click to expand...
Click to collapse
1. No, it is supposed to work like that, i must have broken that feature, I'll look in to it!
2. I will fix the spelling error to the next version

I will be waiting for Android 2.2 version
Btw this supports complete Indian television schedule too?

varun.chitre15 said:
I will be waiting for Android 2.2 version
Btw this supports complete Indian television schedule too?
Click to expand...
Click to collapse
Seems to be only the action bar at the moment "holding me back" so I will see if a can use ActionBarSherlock insted..
Hmm, no not at the moment I'm afraid, only for Indian tv shows if anything
//_booty

Awesome app!!!!! Please publish on Play Store!

Is this project still alive? Looks good so far. Will be using it side by side with TV Show Favs

muzicfreako said:
Awesome app!!!!! Please publish on Play Store!
Click to expand...
Click to collapse
Kelvino9 said:
Is this project still alive? Looks good so far. Will be using it side by side with TV Show Favs
Click to expand...
Click to collapse
Thanks =) Totally forgot about this thread! =/ Twee is on play store now I hope you still find it nice ALOT has happend since i last wrote in this thread, to much to mention I'm afraid, but download it and check it out!
https://play.google.com/store/apps/details?id=se.ja1984.twee
//_booty

_booty said:
Thanks =) Totally forgot about this thread! =/ Twee is on play store now I hope you still find it nice ALOT has happend since i last wrote in this thread, to much to mention I'm afraid, but download it and check it out!
https://play.google.com/store/apps/details?id=se.ja1984.twee
//_booty
Click to expand...
Click to collapse
I downloaded the version in the OP earlier today and I really liked it but I had a few suggestions for improvements. When I came back to comment I saw your post about it being on the play store now and I am happy to say that the version on the Play Store seems to fix my issues.
If you are curious what they were, one was banner images being cut off on the right side causing some shows to show a banner with a cut off name or no name at all. I went to thetvdb.com to see if I could figure this out and I determined you'd either need to make the header smaller vertically in app or have the option to select from the many headers on that site. You seem to have made the banner smaller vertically which works great . Another was that if I tried to add multiple shows in a row it would force close and I'd have to reopen it but that seems to be fixed now as well.
My only recommendations to you are to update the OP with the link to the play store instead of the outdated apk and to implement a feature where you can select one of the banner images from thetvdb.com or possibly even add your own banner image. I really like your app, it looks good and it works well, keep up the great work!

Snargaflab said:
I downloaded the version in the OP earlier today and I really liked it but I had a few suggestions for improvements. When I came back to comment I saw your post about it being on the play store now and I am happy to say that the version on the Play Store seems to fix my issues.
If you are curious what they were, one was banner images being cut off on the right side causing some shows to show a banner with a cut off name or no name at all. I went to thetvdb.com to see if I could figure this out and I determined you'd either need to make the header smaller vertically in app or have the option to select from the many headers on that site. You seem to have made the banner smaller vertically which works great . Another was that if I tried to add multiple shows in a row it would force close and I'd have to reopen it but that seems to be fixed now as well.
My only recommendations to you are to update the OP with the link to the play store instead of the outdated apk and to implement a feature where you can select one of the banner images from thetvdb.com or possibly even add your own banner image. I really like your app, it looks good and it works well, keep up the great work!
Click to expand...
Click to collapse
Thanks for your kind words, these kind of comments triggers me to work even harder =) I will update the OP!
Yeah the apk in the OP is really buggy compared to what's live on the play store right now
I have actually thought about a function where you can choose which banner image to use but in the meantime the images are stored on the external storage in the Twee-folder, so you could replace the image with an image you like better!
//_booty

_booty said:
Thanks for your kind words, these kind of comments triggers me to work even harder =) I will update the OP!
Yeah the apk in the OP is really buggy compared to what's live on the play store right now
I have actually thought about a function where you can choose which banner image to use but in the meantime the images are stored on the external storage in the Twee-folder, so you could replace the image with an image you like better!
//_booty
Click to expand...
Click to collapse
I didn't realize that you had changed the location of the images from the data partition to the sdcard, another great improvement. My phone has a 2GB data partition so it didn't matter much to me but I'm sure that this will be essential to lots of people because many phones have data partitions as small as 150MB and when I had all my shows added the app data was 50MB. Its great that you're looking into the feature to choose a banner, in my opinion it will improve the quality of the app a lot, there is a lot of nice banners on that site. In the meantime grabbing them from the site manually and placing them in that folder is definitely an acceptable workaround
I have a few logcats of the app crashing that I'm going to post. I am running a Cyanogenmod 10 (AOSP 4.1.2) based rom on my Galaxy S2 I9100 so it may be version incompatibility as you do state that it only runs on Android 4.0 so it may be something to do with the different API. This may be app related or it may simply be due to incompatibilities with my operating system. I am only posting the messages related to the crash of the app, however I can recreate these crashes and I still have the entire logcat if you need more info.
Crash 1:
12-06 18:21:50.260 I/ActivityManager(2321): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 pkg=se.ja1984.twee cmp=se.ja1984.twee/.HomeActivity bnds=[384,25][480,143] u=0} from pid 3601
12-06 18:21:50.465 I/ActivityManager(2321): Displayed se.ja1984.twee/.HomeActivity: +138ms
12-06 18:22:02.785 I/ActivityManager(2321): START {cmp=se.ja1984.twee/.OverviewActivity (has extras) u=0} from pid 15231
12-06 18:22:03.375 E/AndroidRuntime(15231): at se.ja1984.twee.fragments.Summary.onCreateView(Summary.java:49)
12-06 18:22:03.380 W/ActivityManager(2321): Force finishing activity se.ja1984.twee/.OverviewActivity
12-06 18:22:03.385 W/ActivityManager(2321): Force finishing activity se.ja1984.twee/.HomeActivity
12-06 18:22:03.885 W/ActivityManager(2321): Activity pause timeout for ActivityRecord{41106dc8 se.ja1984.twee/.OverviewActivity}
12-06 18:22:05.165 W/InputDispatcher(2321): channel '41125f10 se.ja1984.twee/se.ja1984.twee.OverviewActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x9
12-06 18:22:05.165 E/InputDispatcher(2321): channel '41125f10 se.ja1984.twee/se.ja1984.twee.OverviewActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
12-06 18:22:05.165 I/WindowState(2321): WIN DEATH: Window{4101edb8 se.ja1984.twee/se.ja1984.twee.HomeActivity paused=true}
12-06 18:22:05.165 I/ActivityManager(2321): Process se.ja1984.twee (pid 15231) has died.
12-06 18:22:05.170 W/InputDispatcher(2321): Attempted to unregister already unregistered input channel '41125f10 se.ja1984.twee/se.ja1984.twee.OverviewActivity (server)'
12-06 18:22:05.170 I/WindowState(2321): WIN DEATH: Window{41125f10 se.ja1984.twee/se.ja1984.twee.OverviewActivity paused=false}
12-06 18:22:05.170 I/WindowManager(2321): WINDOW DIED Window{41125f10 se.ja1984.twee/se.ja1984.twee.OverviewActivity paused=false}
12-06 18:22:13.990 W/ActivityManager(2321): Activity destroy timeout for ActivityRecord{410297f0 se.ja1984.twee/.HomeActivity}
12-06 18:22:13.990 W/ActivityManager(2321): Activity destroy timeout for ActivityRecord{41106dc8 se.ja1984.twee/.OverviewActivity}
The crash that happens here is at:
se.ja1984.twee.fragments.Summary.onCreateView(Summary.java:49)
This one only happens when I try to open the show "Dragon Ball". I was going to use the app to track my progress in the show but it always immediately fails when I click the banner to get to the more detailed info such as episodes and show info.
Crash 2:
12-06 06:59:23.642 I/ActivityManager(2325): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 pkg=se.ja1984.twee cmp=se.ja1984.twee/.HomeActivity bnds=[384,25][480,143] u=0} from pid 2758
12-06 06:59:23.777 I/ActivityManager(2325): Start proc se.ja1984.twee for activity se.ja1984.twee/.HomeActivity: pid=14844 uid=10029 gids={3003, 1015, 1028}
12-06 06:59:24.367 I/ActivityManager(2325): Displayed se.ja1984.twee/.HomeActivity: +614ms
12-06 06:59:35.402 I/ActivityManager(2325): START {cmp=se.ja1984.twee/.OverviewActivity (has extras) u=0} from pid 14844
12-06 06:59:36.357 I/ActivityManager(2325): Displayed se.ja1984.twee/.OverviewActivity: +883ms
12-06 06:59:40.552 I/ActivityManager(2325): START {cmp=se.ja1984.twee/.OverviewActivity (has extras) u=0} from pid 14844
12-06 06:59:41.447 I/ActivityManager(2325): Displayed se.ja1984.twee/.OverviewActivity: +837ms
12-06 06:59:58.682 I/ActivityManager(2325): START {cmp=se.ja1984.twee/.OverviewActivity (has extras) u=0} from pid 14844
12-06 06:59:59.462 I/ActivityManager(2325): Displayed se.ja1984.twee/.OverviewActivity: +732ms
12-06 07:00:17.042 I/ActivityManager(2325): START {cmp=se.ja1984.twee/.OverviewActivity (has extras) u=0} from pid 14844
12-06 07:00:17.882 I/ActivityManager(2325): Displayed se.ja1984.twee/.OverviewActivity: +799ms
12-06 07:00:27.392 I/ActivityManager(2325): START {cmp=se.ja1984.twee/.OverviewActivity (has extras) u=0} from pid 14844
12-06 07:00:28.212 I/ActivityManager(2325): Displayed se.ja1984.twee/.OverviewActivity: +760ms
12-06 07:00:30.372 I/ActivityManager(2325): START {cmp=se.ja1984.twee/.OverviewActivity (has extras) u=0} from pid 14844
12-06 07:00:30.937 I/ActivityManager(2325): Displayed se.ja1984.twee/.OverviewActivity: +519ms
12-06 07:00:31.332 E/AndroidRuntime(14844): at se.ja1984.twee.utils.DatabaseHandler.GetEpisodes(DatabaseHandler.java:806)
12-06 07:00:31.332 E/AndroidRuntime(14844): at se.ja1984.twee.fragments.Episodes$GetEpisodesTask.doInBackground(Episodes.java:53)
12-06 07:00:31.332 E/AndroidRuntime(14844): at se.ja1984.twee.fragments.Episodes$GetEpisodesTask.doInBackground(Episodes.java:1)
12-06 07:00:31.352 W/ActivityManager(2325): Force finishing activity se.ja1984.twee/.OverviewActivity
12-06 07:00:35.417 I/WindowState(2325): WIN DEATH: Window{416ca1b8 se.ja1984.twee/se.ja1984.twee.HomeActivity paused=false}
12-06 07:00:35.417 I/ActivityManager(2325): Process se.ja1984.twee (pid 14844) has died.
12-06 07:00:35.417 W/ActivityManager(2325): Force removing ActivityRecord{41329468 se.ja1984.twee/.HomeActivity}: app died, no saved state
This one seems to happen at:
se.ja1984.twee.utils.DatabaseHandler.GetEpisodes(DatabaseHandler.java:806)
se.ja1984.twee.fragments.Episodes$GetEpisodesTask.doInBackground(Episodes.java:53)
se.ja1984.twee.fragments.Episodes$GetEpisodesTask.doInBackground(Episodes.java:1)
This one happens more frequently and it seems to have something to do with retrieving the episode list from the database. This will happen somewhat randomly in app but once all my episode lists have been loaded once (by viewing them) it seems to happen less frequently or not at all.
If you need anything else let me know! I'm happy to help with the development of such a great app. I rated it five stars on the play store and am planning on writing a good review for it soon. I will be recommending this to my friends who have Android phones as well, I know they'll like it.

Snargaflab said:
I didn't realize that you had changed the location of the images from the data partition to the sdcard, another great improvement. My phone has a 2GB data partition so it didn't matter much to me but I'm sure that this will be essential to lots of people because many phones have data partitions as small as 150MB and when I had all my shows added the app data was 50MB. Its great that you're looking into the feature to choose a banner, in my opinion it will improve the quality of the app a lot, there is a lot of nice banners on that site. In the meantime grabbing them from the site manually and placing them in that folder is definitely an acceptable workaround
I have a few logcats of the app crashing that I'm going to post. I am running a Cyanogenmod 10 (AOSP 4.1.2) based rom on my Galaxy S2 I9100 so it may be version incompatibility as you do state that it only runs on Android 4.0 so it may be something to do with the different API. This may be app related or it may simply be due to incompatibilities with my operating system. I am only posting the messages related to the crash of the app, however I can recreate these crashes and I still have the entire logcat if you need more info.
[...]
This one happens more frequently and it seems to have something to do with retrieving the episode list from the database. This will happen somewhat randomly in app but once all my episode lists have been loaded once (by viewing them) it seems to happen less frequently or not at all.
If you need anything else let me know! I'm happy to help with the development of such a great app. I rated it five stars on the play store and am planning on writing a good review for it soon. I will be recommending this to my friends who have Android phones as well, I know they'll like it.
Click to expand...
Click to collapse
The decision to move the images was actually a "double edged sword" part of it was that some might have small internal memory even thou most phones running 4.0+ are of the newer models But it was actually also so that your images are saved when you make a backup and part of it was so that the user would be able to changes images themselves
Thanks for the logs, it helps alot, the first FC with the dragon ball is due to the show not having any actors, i thought i had fixed this bug but apparently not
The other more random FCs I have to look into a bit further
And again, thanks for the help, the kind word and the good rating it really helps inspiring me to make the app even greater!
//_booty

TCP_NODELAY - send bytes without delay

I have next problem in developing app for android (Android studio, 4.0.3 kernel),
I communicate with my device over wifi. I need send from ever 20ms some bytes to my device. But I cannot send data more quickly like 100ms! When I use timer with 20ms period, system will send data in 100ms together. Setting timer to 200ms works, data sent ever 200ms. But In decreasing period to 20ms.
This is part of code:
// initialization of socket:
SocketAddress sockaddr = new InetSocketAddress(ip, parseInt(prt));
nsocket = new Socket();
//nsocket.setPerformancePreferences(0,1,2);
nsocket.setSendBufferSize(13);
nsocket.setTcpNoDelay(true);
// this is from timer, run every 20ms
nos = nsocket.getOutputStream();
nos.write(cmd);
nos.flush();
But android will send it with 100ms period! and together all bytes from every 30ms period of my timer
I think, it causes naggle algorithm. It's possible to switch it off. I found in documentation somethink about TCP_NODELAY, how can I use it? Is there any way how to send data to socket from android immediatelly?

I believe if you use SQlite and go into the database. You can add TCP_NODELAY, with a value of 1.