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.
Related
I have had the lurvely DHD for a week now, and I've recently noticed on OSMonitor a process that comes in pretty regularly and uses up between 60-80% ocp load.
Its called Customization Setup and its PID is 1552 and seems to be there hogging ocp everytime I check. Is this normal?
If so is there something I can set to prevent it coming?
Thanks
OK this thread is dedicated to developing a WORKING charging battery icon animation. The main problem is this: ASUS' code only allows for still images to be drawn when the battery is charging (specifically when the dock is connected). Applying existing techniques to allow for animation results in the following exception:
Code:
W/dalvikvm( 149): threadid=8: thread exiting with uncaught exception (group=0x401ab760)
E/AndroidRuntime( 149): *** FATAL EXCEPTION IN SYSTEM PROCESS: android.server.ServerThread
E/AndroidRuntime( 149): java.lang.RuntimeException: Error receiving broadcast Intent { act=android.intent.action.BATTERY_CHANGED flg=0x60000010 (has extras) } in [email protected]
E/AndroidRuntime( 149): at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:725)
E/AndroidRuntime( 149): at android.os.Handler.handleCallback(Handler.java:587)
E/AndroidRuntime( 149): at android.os.Handler.dispatchMessage(Handler.java:92)
E/AndroidRuntime( 149): at android.os.Looper.loop(Looper.java:132)
E/AndroidRuntime( 149): at com.android.server.ServerThread.run(SystemServer.java:608)
E/AndroidRuntime( 149): Caused by: java.lang.ClassCastException: android.graphics.drawable.AnimationDrawable cannot be cast to android.graphics.drawable.BitmapDrawable
E/AndroidRuntime( 149): at com.android.server.asus.DockManagerService.adjustStatusBarDockLocked(DockManagerService.java:371)
E/AndroidRuntime( 149): at com.android.server.asus.DockManagerService.updateLocked(DockManagerService.java:317)
E/AndroidRuntime( 149): at com.android.server.asus.DockManagerService.updateDockBatteryState(DockManagerService.java:309)
E/AndroidRuntime( 149): at com.android.server.asus.DockManagerService.access$300(DockManagerService.java:55)
E/AndroidRuntime( 149): at com.android.server.asus.DockManagerService$3.onReceive(DockManagerService.java:229)
E/AndroidRuntime( 149): at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:716)
E/AndroidRuntime( 149): ... 4 more
The line in question is the following: "Caused by: java.lang.ClassCastException: android.graphics.drawable.AnimationDrawable cannot be cast to android.graphics.drawable.BitmapDrawable", which is pretty much self-explanatory.
Anyways, I have dug into it more and traced the issue back to the source where I believe it is triggered from. First off, let me explain what I did:
Extracted 'classes.dex' from 'services.jar'
Decompiled 'classes.dex' using dex2jar
Was only able to view the source code with JD-GUI (don't know how to make edits)
Traced the issue to the file \com\android\server\asus\DockManagerService.class
In the 'DockManagerService.class', there are references to BitmapDrawable which I think need to be AnimatedDrawable, since that is what the logcat debug message says above (in the OP). I have no idea what to change it to exactly (let alone recompile it), but I believe this is where we need to look ('...' is edited-out code):
Code:
private void adjustStatusBarDockLocked()
...
...
localImageView.setImageResource(n);
int i1 = this.mDockBatteryLevel;
localImageView.setImageLevel(i1);
Bitmap localBitmap = ((BitmapDrawable)localImageView.getDrawable().getCurrent()).getBitmap();
localRemoteViews.setImageViewBitmap(16908985, localBitmap);
}
Also, near the top of 'DockManagerService.class', there is the following:
Code:
import android.graphics.Bitmap;
import android.graphics.drawable.BitmapDrawable;
import android.graphics.drawable.Drawable;
...not sure if we'd need to add something like 'android.graphics.drawable.AnimationDrawable;' in order to get animations supported?
Anyways, that's about as far as I can get with my current knowledge. If any other experienced dev is out there, it would be super great if they could give their thoughts, suggestions, ANYTHING!
Hopefully after we get to the bottom of this, we'll be able to have animated charging icons which support the ASUS dock.
OH, and forgot to mention that users of the OC kernel by Clemsyn (which is currently NOT built from source, since the 3.1 official ASUS source has not yet been released) do not suffer from this problem, since that OC kernel has broken support for the dock battery level/charging status. It currently only becomes an issue with the Stock 3.1 kernel which is able to correctly read the Dock Status.
Thanks in advance!
This may (or may not) help - but -
Can you locate the source for "BatteryService" and see if anything in there helps?
Also - did the Asus "limited release" for the Dock issues not contain a working Dock Status? If it did, someone may have the files kicking around from that which could have the parts you need in?
I use a widget called "bat stat" that uses animation, but it does not handle the dock (of course). It is small, has great animation and graphics, and is not well know yet it is in the market.
Was thinking to do my own tf version, will let you know if succeeds.
Hope this helps.
=======
UPDATE:
I finished the *graphics* to represent various tablet & dock and charging or discharging states.
I will look at some widget *codes* next.
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
Team venom will soon be supporting the desire z with the assistance of lms24
ViperZ is based on the other wvga viperRoms on the dhd, vivo, and vivow
We are looking for 5-10 beta testers who can run the rom for a few days prior to release to make sure there are no huge bugs that would prevent a release
Testers should meet following requirements:
Proficient with adb and logcats
Have run sense4 roms on this phone for at least a little while before
Are active forum members (ie didn't join a month ago and have very few posts-
Ethical (won't share beta links with anyone)
Please post here if interested !
Beta should be out this week
Let's do it
Sent from my HTC Vision using xda premium
I can participate too.
I'd be willing to try but I don't have much time in my hands. This is full sense, correct? Also would you prefer us not to use things such as PMR or ROM Cleaner?
I'm willing to participate. i have a spare desire z at home and i used the rom on dhd so i can compare if needer
crestofawave said:
I'd be willing to try but I don't have much time in my hands. This is full sense, correct? Also would you prefer us not to use things such as PMR or ROM Cleaner?
Click to expand...
Click to collapse
yes, please run the rom as close to stock as possible :fingers-crossed:
ok, guys check your inboxes....just run the rom for a day or two, and let me know if there are any serious bugs (bootlooping)
G2 users, you need to be on a Z Hboot
Have fun while you're testing the Rom, guys. Let's hope this runs as great on your phones as on my DZ.
Sent from my HTC Desire Z using xda app-developers app
Smooth installation with aroma. No errors. No bootloops. Also no reboots yet.
Lowmemorykiller works great, even tho there is 50-60 mb free ram, no stutters in games. Actually better gaming then aosp roms.
I went ahead and changed the phone ID from s710e to HTC Desire Z since it bothers me and i do it with every rom before installation. I hope its okay.
All in all great job with the rom.
Don't have time to flash it now will do so later tonight. Looks promising already loved it on dhd
Sent from my HTC Vision using Tapatalk 2
OC settings in venom tweaks not working. or i cant seem to save the new frequencies. they just go back to default when i close the app.
btrst said:
OC settings in venom tweaks not working. or i cant seem to save the new frequencies. they just go back to default when i close the app.
Click to expand...
Click to collapse
ah, i guess torxx didnt remove them before the latest update (i did in viperINC)
good catch, thanks
Something strange,
I tried to enable swap with swap_enabler script but it said swap was already enabled. So i checked with terminal and it shows 122 mb swap space enabled without me enabling it. Strange thing is, my sdcard partitioned for 256 mb swap space. I checked the init.d scripts and none of them has any lines indicating automatic swap enabling. Im really confused here.
Yo, OP send beta towards this way if you don't mind?
I'm off all week and have spare G2 and Always On my phone atleast 18hours of the day literally.
-thanks
Sent from my HTC Vision using xda premium
The PDF Reader app is FC'ing for me. Other than that and what btrst mentioned I haven't had any other issues. The only thing I did was disable CPU Rendering and use CPU Tuner for CPU freq management.
The ROM is between smooth and choppy for me, and has fairly decent performance, things to be expected as we're talking about Sense 4. Quite impressive as far as I'm concerned. I also like the very extensive customizations, especially the Sweep to Unlock.
I can imagine that getting rid of all redundant stuff using ROM Cleaner will increase the ROM's Performance. Thanks for the share
crestofawave said:
The PDF Reader app is FC'ing for me. Other than that and what btrst mentioned I haven't had any other issues. The only thing I did was disable CPU Rendering and use CPU Tuner for CPU freq management.
The ROM is between smooth and choppy for me, and has fairly decent performance, things to be expected as we're talking about Sense 4. Quite impressive as far as I'm concerned. I also like the very extensive customizations, especially the Sweep to Unlock.
I can imagine that getting rid of all redundant stuff using ROM Cleaner will increase the ROM's Performance. Thanks for the share
Click to expand...
Click to collapse
can you logcat the pdf reader fc?
Here you go. (Longer logcat here). I launched the app several times. The longer log is fudged up as I'm running adb from cmd. I managed to salvage a few lines that had to do with the app and make them easier to read. Hope it helps.
Code:
I/Adreno200-EGLSUB( 101): <CreateImage:893>: Android Image
I/Adreno200-EGLSUB( 101): <GetImageAttributes:1158>: RGBX_8888
I/ActivityManager( 184): Start proc com.htc.pdfviewer for activity com.htc.pdfviewer/.ActPDFReader: pid=9821 uid=10013 gids={2001, 3003, 1015, 1006, 5001}
W/ResourceType( 184): Skipping entry 0x7f04000c in package table 0 because it is not complex!
D/dalvikvm( 102): GC_EXPLICIT freed 38K, 27% free 2802K/3807K, paused 2ms+9ms
D/ConnectivityService( 184): onUidRulesChanged(uid=10013, uidRules=0)
D/dalvikvm( 102): GC_EXPLICIT freed <1K, 27% free 2802K/3807K, paused 3ms+2ms
D/dalvikvm( 102): GC_EXPLICIT freed <1K, 27% free 2802K/3807K, paused 2ms+2ms
I/ActivityThread( 9821): Pub com.htc.provider.pdfviewer: com.htc.pdfviewer.provider.PdfProvider
D/com.htc.pdfviewer.provider.PdfProvider( 9821): onCreate
D/com.htc.pdfviewer.provider.PdfProvider( 9821): AvailableDataDirectorySize 797159424
D/SqliteDatabaseCpp( 9821): Registering sqlite logging func: /data/data/com.htc.pdfviewer/databases/book.db
D/SqliteDatabaseCpp( 9821): DB info: open db, path = /data/data/com.htc.pdfviewer/databases , key = fkko, flag = 6, file size = 5120
D/SqliteDatabaseCpp( 9821): DB info: path = /data/data/com.htc.pdfviewer/databases , key = fkko, handle: 0x1fda9b0, type: w, r/w: (0,1), mode: truncate, disk free size: 760 M
I/ActivityThread( 9821): Pub com.htc.pdfviewer.PdfSuggestionProvider: com.htc.pdfviewer.PdfSuggestionProvider
W/dalvikvm( 9821): Exception Ljava/lang/UnsatisfiedLinkError; thrown while initializing Lcom/htc/pdfviewer/JNIHost;
D/AndroidRuntime( 9821): Shutting down VM
W/dalvikvm( 9821): threadid=1: thread exiting with uncaught exception (group=0x40aaf228)
E/EmbeddedLogger( 184): App crashed! Process: com.htc.pdfviewer
E/EmbeddedLogger( 184): App crashed! Package: com.htc.pdfviewer v400371055 (4.0.2215132855.371055.304684)
E/EmbeddedLogger( 184): Application Label: PDF Viewer
E/AndroidRuntime( 9821): FATAL EXCEPTION: main
E/AndroidRuntime( 9821): java.lang.ExceptionInInitializerError
E/AndroidRuntime( 9821): at com.htc.pdfviewer.ActPDFReader.<init>(ActPDFReader.java:577)
E/AndroidRuntime( 9821): at java.lang.Class.newInstanceImpl(Native Method)
E/AndroidRuntime( 9821): at java.lang.Class.newInstance(Class.java)
E/AndroidRuntime( 9821): at android.app.Instrumentation.newActivity(Instrumentation.java)
E/AndroidRuntime( 9821): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java)
E/AndroidRuntime( 9821): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java)
E/AndroidRuntime( 9821): at android.app.ActivityThread.access$600(ActivityThread.java)
E/AndroidRuntime( 9821): at android.app.ActivityThread$H.handleMessage(ActivityThread.java)
E/AndroidRuntime( 9821): at android.os.Handler.dispatchMessage(Handler.java)
E/AndroidRuntime( 9821): at android.os.Looper.loop(Looper.java)
E/AndroidRuntime( 9821): at android.app.ActivityThread.main(ActivityThread.java)
E/AndroidRuntime( 9821): at java.lang.reflect.Method.invokeNative(NativeMethod)
E/AndroidRuntime( 9821): at java.lang.reflect.Method.invoke(Method.java)
E/AndroidRuntime( 9821): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java)
E/AndroidRuntime( 9821): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java)
E/AndroidRuntime( 9821): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 9821): Caused by: java.lang.UnsatisfiedLinkError: Couldn't load pdfviewer: findLibrary returned null
E/AndroidRuntime( 9821): at java.lang.Runtime.loadLibrary(Runtime.java)
E/AndroidRuntime( 9821): at java.lang.System.loadLibrary(System.java)
E/AndroidRuntime( 9821): at com.htc.pdfviewer.JNIHost.<clinit>(JNIHost.java:768)
E/AndroidRuntime( 9821): ... 16 more
W/ActivityManager( 184): Force finishing activity com.htc.pdfviewer/.ActPDFReader
D/ViewRootImpl( 184): @@@- disable SystemServer HW acceleration
D/OpenGLRenderer( 587): Flushing caches (mode 1)
D/OpenGLRenderer( 587): Flushing caches (mode 0)
D/memalloc( 587): /dev/pmem: Unmapping buffer base:0x58dd8000 size:15052800 offset:13516800
D/memalloc( 587): /dev/pmem: Unmapping buffer base:0x56fbb000 size:4608000 offset:3072000
D/memalloc( 587): /dev/pmem: Unmapping buffer base:0x5a545000 size:6144000 offset:4608000
I/Adreno200-EGLSUB( 101): <CreateImage:893>: Android Image
I/Adreno200-EGLSUB( 101): <GetImageAttributes:1102>: RGBA_8888
W/ActivityManager( 184): Activity pause timeout for ActivityRecord{40daba60 com.htc.pdfviewer/.ActPDFReader}
thanks, seems to be missing the proper lib
im just gonna remove it from the rom, adobe reader is better (imo)
Just saw the new release for DZ, Thank you guys. I'm finishing downloading and i will share my experience with this rom after installation
desperately waiting for this rom keep up the good work thanks..
ahmedrzvi said:
desperately waiting for this rom keep up the good work thanks..
Click to expand...
Click to collapse
wait no longer! ITS BEEN OUT FOR TWO DAYS!
great for a full sense 4 ROM.
If you really want sense and all its features plus more, this is near perfect
I'm sorry for posting here, but since I haven't posted much to the forums in the past, I haven't hit 10 posts and can't post to the appropriate thread here: http://forum.xda-developers.com/showthread.php?t=1932826
Regardless, with that ROM, I'm seeing two issues:
1) My wifi password is not remembered, and hence has to be re-entered every time I reconnect.
2) My System process is eating the CPU, and probably not coincidentally, my logs are filled with sections like this, repeated forever:
Code:
rmt_storage( 3300): rmt_storage user app start
rmt_storage( 3300): rmt_storage open success
rmt_storage( 3300): rmt_storage shared memory ioctl success
rmt_storage( 3300): rmt_storage mmap addr = 40011000
rmt_storage( 3300): rmt_storage wait event ioctl failed
I can watch the logs and see this being repeated again and again while the ROM is running, but I can't trace it to a process that's causing the problem.
Finally, I hope this post is seen. It's extremely irritating to be forced to post to the wrong forum. Sorry about that.
Thanks a ton for any help!
Hmm, looks like the wifi thing at least is a known issue...
...and for what it matters, apparently others are seeing things like what I'm seeing in the logs, but with no resolution (and not necessarily only in this rom)
beanfootage said:
...and for what it matters, apparently others are seeing things like what I'm seeing in the logs, but with no resolution (and not necessarily only in this rom)
Click to expand...
Click to collapse
I finally had to revert to another ROM to address this. Strangely, I can't even tell what rmt_storage does. If anyone has any insight, let me know; in the meantime I'll keep googling, I guess.