Database Users

TV out

Something that is missing from the Tytn II is the TV out. Is there a way - maybe use an accessory - to be able to conect and see the screen on a TV /projector?

Would be perfect for doing Powerpoint presentations on the road.

Somebody post this on the main Kaiser forum just yesterday:
http://www.mobiliparts.com/product_info.php?cPath=109&products_id=464&language=en

blue_94_trooper said:
Would be perfect for doing Powerpoint presentations on the road.
Click to expand...
Click to collapse
You can use the Showmate
http://www.expansys.com/a.aspx?i=151713&atype=Projectors

Third said:
Somebody post this on the main Kaiser forum just yesterday:
http://www.mobiliparts.com/product_info.php?cPath=109&products_id=464&language=en
Click to expand...
Click to collapse
That's amazing...

I like that alot...http://www.expansys.com/a.aspx?i=151713&atype=Projectors

what's 109.99 euro in american $?

""[email protected] what's 109.99 euro in american $? ""
Talk about lazy. Dude, do a simple search.
http://coinmill.com/EUR_USD.html#EUR=109.99

Yeah Spectec's always doing some crazy sh*t.
Now the real question is, what's the difficulty of changing the device's output resolution when an external display is in use? Not much good of having a projection system all rigged up if it can't display at least 1024x768...

kimtyson said:
""[email protected] what's 109.99 euro in american $? ""
Talk about lazy. Dude, do a simple search.
http://coinmill.com/EUR_USD.html#EUR=109.99
Click to expand...
Click to collapse
I know I know

[Q] Good game development engines?

Does any one know any good game development engines for android. Im not new but not an expert

I like this, android friendly too
xsxbluexsx said:
Does any one know any good game development engines for android. Im not new but not an expert
Click to expand...
Click to collapse
h t t p : / / w w w DOT unity3d DOT com

Unity
Did you pay for android licence (1500$)

http://www.jpct.net/jpct-ae/ free java engine

yah, right!
Orion_uk said:
h t t p : / / w w w DOT unity3d DOT com
Click to expand...
Click to collapse
Lol, noOoo..
I used the student/Indie version for ages but then upgraded to the 30 day full trial of Unity 3. Sadly Im back in student/Indie `mode` now
Cant afford full version on my income

Orion_uk said:
Lol, noOoo..
I used the student/Indie version for ages but then upgraded to the 30 day full trial of Unity 3. Sadly Im back in student/Indie `mode` now
Cant afford full version on my income
Click to expand...
Click to collapse
Can you pm me how to make it work with android?

there is AndEngine. This is huge, and free. And quite good. But I dont have the time to learn it as im at university.
e3droid is a 2D game engine that I definitly plan to look into more. Its only about 2 months old so its feature set is limited but for its age it looks impressive. I cant wait for e3droid to improve.

Flynny75 said:
there is AndEngine. This is huge, and free. And quite good. But I dont have the time to learn it as im at university.
e3droid is a 2D game engine that I definitly plan to look into more. Its only about 2 months old so its feature set is limited but for its age it looks impressive. I cant wait for e3droid to improve.
Click to expand...
Click to collapse
Do you mind sharing the project's page?

http://www.andengine.org/forums/
http://www.e3roid.com/

[MOD/Source] Display "H" icon in status bar on Froyo roms.

Hey everyone,
I posted this last night in the Vibrant forums (and confirmed that it works on the vibrant 2.2 roms) so I figured I'd cross-post here for anyone that wants to try it out on the captivate too.
Anyway I just figured out how to display the "H" icon in the status bar properly. And by that I mean, no renaming or duplicating drawable files in framework-res.apk, and the icon will show all data states now:
GSM, GPRS, Edge, 3G, HSDPA
I've only tested it for myself on the Vibrant running 2.2 roms.
Anyway, decompile services.jar, and open /com/android/server/status/StatusBarPolicy.smali
Then search for ".method private final updateDataNetType(I)V" in and replace the entire method with this:
Code:
.method private final updateDataNetType(I)V
.registers 3
.parameter "net"
.prologue
.line 1381
packed-switch p1, :pswitch_data_30
.line 1409
sget-object v0, Lcom/android/server/status/StatusBarPolicy;->sDataNetType_g:[I
iput-object v0, p0, Lcom/android/server/status/StatusBarPolicy;->mDataIconList:[I
.line 1412
:goto_7
return-void
.line 1383
:pswitch_8
sget-object v0, Lcom/android/server/status/StatusBarPolicy;->sDataNetType_e:[I
iput-object v0, p0, Lcom/android/server/status/StatusBarPolicy;->mDataIconList:[I
goto :goto_7
.line 1386
:pswitch_d
sget-object v0, Lcom/android/server/status/StatusBarPolicy;->sDataNetType_3g:[I
iput-object v0, p0, Lcom/android/server/status/StatusBarPolicy;->mDataIconList:[I
goto :goto_7
.line 1391
:pswitch_12
iget-boolean v0, p0, Lcom/android/server/status/StatusBarPolicy;->mHspaDataDistinguishable:Z
if-eqz v0, :cond_1b
.line 1392
sget-object v0, Lcom/android/server/status/StatusBarPolicy;->sDataNetType_h:[I
iput-object v0, p0, Lcom/android/server/status/StatusBarPolicy;->mDataIconList:[I
goto :goto_7
.line 1394
:cond_1b
sget-object v0, Lcom/android/server/status/StatusBarPolicy;->sDataNetType_3g:[I
iput-object v0, p0, Lcom/android/server/status/StatusBarPolicy;->mDataIconList:[I
goto :goto_7
.line 1399
:pswitch_20
sget-object v0, Lcom/android/server/status/StatusBarPolicy;->sDataNetType_1x:[I
iput-object v0, p0, Lcom/android/server/status/StatusBarPolicy;->mDataIconList:[I
goto :goto_7
.line 1402
:pswitch_25
sget-object v0, Lcom/android/server/status/StatusBarPolicy;->sDataNetType_1x:[I
iput-object v0, p0, Lcom/android/server/status/StatusBarPolicy;->mDataIconList:[I
goto :goto_7
.line 1406
:pswitch_2a
sget-object v0, Lcom/android/server/status/StatusBarPolicy;->sDataNetType_3g:[I
iput-object v0, p0, Lcom/android/server/status/StatusBarPolicy;->mDataIconList:[I
goto :goto_7
.line 1381
nop
:pswitch_data_30
.packed-switch 0x2
:pswitch_8
:pswitch_d
:pswitch_20
:pswitch_2a
:pswitch_2a
:pswitch_25
:pswitch_12
:pswitch_12
:pswitch_12
.end packed-switch
.end method
And if you haven't noticed by now, I HATE this samsung bs and would kill for an AOSP or CM rom, lol.
Cheers, =)

s0niqu3 said:
Anyway I just figured out how to display the "H" icon in the status bar properly. And by that I mean, no renaming or duplicating drawable files in framework-res.apk, and the icon will show all data states now:
GSM, GPRS, Edge, 3G, HSDPA
Click to expand...
Click to collapse
Interesting, though I've never had this issue. Is this for like the stock ROM? Because I was under the impression that the stock ROM never showed "H" because the modem didn't support it... But my current ROM (Serendipity 5.7) shows the "H" icon when necessary and switches over to 3G when it's on 3G. My area is so AT&T oriented, so I can't say the same for E, G, or any of the others, because my area is so densely populated with AT&T towers. I'm getting (legitimately, not false) HSDPA 99.999% of the time where I live.

Loggik said:
Interesting, though I've never had this issue. Is this for like the stock ROM? Because I was under the impression that the stock ROM never showed "H" because the modem didn't support it... But my current ROM (Serendipity 5.7) shows the "H" icon when necessary and switches over to 3G when it's on 3G. My area is so AT&T oriented, so I can't say the same for E, G, or any of the others, because my area is so densely populated with AT&T towers. I'm getting (legitimately, not false) HSDPA 99.999% of the time where I live.
Click to expand...
Click to collapse
Stock ROM supports HSDPA but not HSUPA, so it would show the "H" icon with this mod when getting that signal I assume.

Thank you very much!
Thank you very much, s0niqu3, I was looking for this to mod a JI6 rom.
Much appreciated ^^!!!.

I'm confused... if your phone is on the Edge network, wouldn't you want to know it? Why would you want your task bar to show an "H" in that scenario?

olo567 said:
Stock ROM supports HSDPA but not HSUPA, so it would show the "H" icon with this mod when getting that signal I assume.
Click to expand...
Click to collapse
Oh, that's interesting... I didn't know that! I thought I was getting just 3G for the first few days I had my phone.
jsmith8858 said:
I'm confused... if your phone is on the Edge network, wouldn't you want to know it? Why would you want your task bar to show an "H" in that scenario?
Click to expand...
Click to collapse
It won't. With this mod, the icon will be shown properly (if you're on Edge, it'll show "E").

jsmith8858 said:
I'm confused... if your phone is on the Edge network, wouldn't you want to know it? Why would you want your task bar to show an "H" in that scenario?
Click to expand...
Click to collapse
You didn't understand it.
Stock JI6 on the Captivate, for example, doesn't show the H icon when you have HSPA (by flashing a custom kernel and a HSPA capable modem). With this mod the H icon will be displayed.

Loggik said:
Oh, that's interesting... I didn't know that! I thought I was getting just 3G for the first few days I had my phone.
Click to expand...
Click to collapse
AT&T calls both UMTS and HSDPA "3G." My old phone had a "3G+" icon for HSDPA.

Confirmed!
Confirmed working on Captivate JI6.
You rock!.
Thank you very much .

CM7 Waiting Room/Discussion Thread ** UPDATED 07/13 - READ THE OP!!!! **

Thanks to Andmer MMS is now working. JT has used Andmer's MMS fix for the MIUI ROM and got it to work for CM7. So it is now safe for everyone to bask in the CM7 goodness
I'm putting this right up at the top of the OP so everyone can find it. If you are trying to flash the CM7 test 5 and you are getting the status 7 get.prop errors you have to unzip the ROM and go to META-INF/com/google/android/updater-script and delete the first 4 lines. By unzipping that doesn't mean right click and chose extract here. It means if you have 7 zip or winrar, just double click on the ROM file, double click on META-INF, double click on com, double click on google, double click on android, double click on updater-script, you will get a pop up window asking what program you want to open it with, choose notepad then follow nemesis2all's instructions here:
nemesis2all said:
These lines need to be removed from top of updater-script if you have issues with asserts on installation.
assert(getprop("ro.product.device") == "aries" || getprop("ro.build.product") == "aries" || getprop("ro.product.board") == "aries" ||
getprop("ro.product.device") == "fascinate" || getprop("ro.build.product") == "fascinate" || getprop("ro.product.board") == "fascinate" ||
getprop("ro.product.device") == "fascinatemtd" || getprop("ro.build.product") == "fascinatemtd" || getprop("ro.product.board") == "fascinatemtd" ||
getprop("ro.product.device") == "SCH-I500" || getprop("ro.build.product") == "SCH-I500" || getprop("ro.product.board") == "SCH-I500");
Then next line would be ui_print("Checking state of BML/MTD..."); everything from that line down stays.
Click to expand...
Click to collapse
After you do that, save and update the notepad file, close the notepad file and you should get a pop up from winrar or 7 zip asking if you want to save the changes to the updater-script file, click yes. You can double click on the updater-script file and open with notepad just to make sure the changes saved. Close up the winrar or 7 zip window and you can now move the modified ROM zip to your sd card and flash with no problems.
- CM7 test builds 7 and newer and the accompanying recoveries attached in the OP have corrected the problem with the asserts, so you won't need to do the above with test build 7 as long as you use the attached recovery. Both links are the same recovery, the tar file is flashed through ODIN and the zip file is flashed through CWM.
Well since it was my idea to start a General thread for all discussion, speculation, and chatter regarding CM7, only fitting I should be the one to do it. Jt has asked several times that thank you posts, X/Y/Z doesn't work posts, I'd flash this ROM if posts, and bug reports without logcats not be posted because they just clutter up the thread. There is a ton of excitement as jt, times_infinity, nemesis2all and everyone else working on it bring the Fascinate closer to a fully functioning CM7 build, and the thread is being overrun with posts either asking when it will be ready, or just posts expressing excitement over the pending release or progress toward that release. I read through the entire thread this morning, and since jt has joined his work into mainline CM7 this is where it stands:
Everything, yes everything INCLUDING MMS. That includes camera, camcorder, video codecs, bluetooth (although I remember it mentioned possibly not A2DP but I could be wrong), & sms. Times_infinity has mentioned it was a matter of getting the RIL to work. I'm sure many of you know what RIL stand for and what it does. I did not so I had to look it up, and for those of you who also don't know - http://en.wikipedia.org/wiki/Radio_Interface_Layer
So let's do jt and crew a favor and use this thread for all speculation, discussion, and chatter about CM7 for the Fascinate. I will do my best to update info as I hear it, but everyone else is free to do the same also. This is supposed to be for everyone's benefit, and since this is in the General Forum we can load this thread with as many posts as we want. If jt, times_infinity, or anyone else working on the CM7 build post an update in the CM7 thread in the Development section, repost the info here and we can discuss the update here. So feel free to post any news, rumors, speculation, discussion you want about CM7 for the Fascinate here.
And this doesn't have to be limited to jt's CM7 build either. Punk.kaos is also working on a CM7 build and this thread can also be a place for discussion about the differences between the two builds also. I would imagine there are people who prefer jt's build and never bother to keep track of kaos' build and vice versa. I'll see if I can work on putting together a comparative list of the two and post it later. But for now, let the discussion, speculation, and excitement begin..................
UPDATE 07/13
Jt1134 has released test build #10 here at XDA in his CM7 thread:
http://forum.xda-developers.com/showthread.php?t=1116424
You can view the changelog in that thread
Also nemesis2all has released his newest MTD OTB kernel, and it can be found here for those who want to manually undervolt and/or overclock the kernel:
http://forum.xda-developers.com/showthread.php?t=1119169
Copied from the OP in that thread:
Working:
Calls!!
SMS
3G data
GPS!!
Bluetooth!!
WiFi
Camera/Camcorder
USB mass storage / sdcard
Sensors!!
MMS! (thanks andmer!)
Not Working:
bugs I dunno
Now that all of that is working, jt1134 has said he is going to clean up his CM tree and submit this build for acceptance into mainline Cyanogen. That would mean we would be eligible to get nightly builds of CyanogenMod. This is extremely exciting and shows you how good the devs are that jt1134 seems likely to have a completely 100% working, functional Gingerbread ROM for our phones before samsung/verizon do.
Let's keep this thread going while everyone who wants to and can is testing this build. Times_infinity has asked we not post bug reports with logcats in the test build thread at this time. So let's keep the general chatter and what do you like/not like about it in this thread, along with discussion of bugs and problems. AND DON'T FORGET TO THANK THE MAN
Also don't forget times_infinity who has been working with jt1134 on this and nemesis2all for his kernel work. Lots of thanks and appreciation to be given to all these guys. Show them the love.
(Donations don't hurt either for those who can afford to. Plus seems like jt is doing some of his best work when he's drinking so I'm more than happy to try and keep his beer fund full.)

Reserved. Lol. Always wanted to do that.....
Sent from my SCH-I500 using XDA App

I have high hopes for it and am looking forward to it. the last alpha builds were great, but this whole new tree is going to be a major step forward in functionality when it hits.

I'd also suggest that JT post a new thread when the beta drops, keeping that one cleaner than the alpha thread that's gone haywire.

dnoyeb said:
I have high hopes for it and am looking forward to it. the last alpha builds were great, but this whole new tree is going to be a major step forward in functionality when it hits.
Click to expand...
Click to collapse
I'm thinking that if BT in call, camera, camcorder and hw/sw codecs all work then mms will as well. In the alpha builds the bugs were not specific to any one area (i.e. ril or just the camera area) Can't wait for the radio to reveal the moment of truth. I still can't figure how they have determined that sms/mms works without the radio. Thoughts?
Sent from my SCH-I500 using Tapatalk

kidserious said:
I'm thinking that if BT in call, camera, camcorder and hw/sw codecs all work then mms will as well. In the alpha builds the bugs were not specific to any one area (i.e. ril or just the camera area) Can't wait for the radio to reveal the moment of truth. I still can't figure how they have determined that sms/mms works without the radio. Thoughts?
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
I should have written that down when I saw it. Times_infinity said in irc how they were able to test those, but I can't remember. Sorry.
I did flash the new build on my second Fassy trying to help nemesis with something. Unfortunately I couldn't find any drivers that allowed my phone to be recognized by adb and I wasn't able to help. But the ROM itself is pretty sweet. No clutter, just bare bones Android goodness. Can't wait for this to drop so we can play with it.

mkarps said:
Reserved. Lol. Always wanted to do that.....
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Banned. LOL

the true beauty of CM when fully merged as JTs trying to do.. are the nightlies.
I would literally install a new rom every day when I was on my droid incredible... after I figured out what was causing the random reboots and fixed it on the AOSP roms like CM for the incredible, that thing became unreal.
I cannot wait to get back to nightly builds and all the awesome features that come with them.

So then would all the nightlies be available in a database so you could flash an older one you liked better? Or once you flashed a new nightly was the previous one gone for good?

I personally just want the camera to work.... don't care about the radio's... LOL... just the camera.

landshark68 said:
I should have written that down when I saw it. Times_infinity said in irc how they were able to test those, but I can't remember. Sorry.
I did flash the new build on my second Fassy trying to help nemesis with something. Unfortunately I couldn't find any drivers that allowed my phone to be recognized by adb and I wasn't able to help. But the ROM itself is pretty sweet. No clutter, just bare bones Android goodness. Can't wait for this to drop so we can play with it.
Click to expand...
Click to collapse
Yea, I was in irc when you and Bryan were testing that. So it has been confirmed that mms works?
Sent from my SCH-I500 using Tapatalk

As for the nightlies, are the phone specific? Or when everything gets merged for the fassy, cm7 is cm7 regardless of the phone?
Swyped via Tapatalk

kidserious said:
Yea, I was in irc when you and Bryan were testing that. So it has been confirmed that mms works?
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
I'm pretty sure I remember seeing that mentioned in irc, but with trying to retain info from work, personal life, AC, XDA, and irc I may be at full capacity and starting to not retain stuff
Basically I'm pretty sure I saw mms was working, just not 100% positive.

landshark68 said:
I'm pretty sure I remember seeing that mentioned in irc, but with trying to retain info from work, personal life, AC, XDA, and irc I may be at full capacity and starting to not retain stuff
Basically I'm pretty sure I saw mms was working, just not 100% positive.
Click to expand...
Click to collapse
Ok thanks man.
Sent from my SCH-I500 using Tapatalk

Hey shark, thanks for putting this together. I think it's a great idea and should be fun!

Headcase8911 said:
Hey shark, thanks for putting this together. I think it's a great idea and should be fun!
Click to expand...
Click to collapse
Welcome. It will be great once CM7 gets finished. I can wait as I'm doing just fine on KangBang, so jt and crew can take their time and make it awesome. And anytime they get it finished will be a hell of a lot sooner than when we will even get a whiff of GB from verizon.

landshark68 said:
Welcome. It will be great once CM7 gets finished. I can wait as I'm doing just fine on KangBang, so jt and crew can take their time and make it awesome. And anytime they get it finished will be a hell of a lot sooner than when we will even get a whiff of GB from verizon.
Click to expand...
Click to collapse
And this is going to GB the way it's supposed to be with the. 35 kernel. I'm running cm7 and loving it but I do miss the mms, camera and camcorder and you tube.
Sent from my SCH-I500 using Tapatalk

landshark68 said:
anytime they get it finished will be a hell of a lot sooner than when we will even get a whiff of GB from verizon.
Click to expand...
Click to collapse
+1 to that, I wonder how many people got their Fascinates within the last few months and what there feeling is though. I got mine on 9/13 and was initially pretty impressed, as time move on though the software side started to make the phone feel like it had been outgrown.

I just picked up a DINC, what waiting?
Definitely holding onto my Fascinate though. Although Sense 3.0 might have me hooked on HTC once it's stable.

Wait, so sms and mms are working? I thought a working RIL was needed for sms/mms to function.
Edit: so I read that wiki, and I'm assuming ril affects phone calls only?

[HOW TO] Create your own Android Launcher (Video Series) [VIDEO ADDED 8/18/15]

I have started a series on how to make your own Android Launcher and thought I would share. FYI: You will need to know moderate programming skills in order to understand this series. Tell me what you all think. Enjoy!
Below are all the parts of the series I have created so far. I will update this list each time I add a new part.
PART 1
PART 2
PART 3-1
PART 3-2
PART 4-1
PART 4-2
PART 5
PART 6
PART 7-1
PART 7-2
PART 8
PART 9-1
PART 9-2
PART 10
PART 11
PART 12-1
PART 12-2
PART 13-1
PART 13-2
PART 14-1
PART 14-2
PART 14-3
PART 15

Just added part 6

Loving this tutorial, I've been trying to make a launcher from scratch for a while now. Can't wait to see what else you have to offer us.

TroJaN SniPeR85 said:
Loving this tutorial, I've been trying to make a launcher from scratch for a while now. Can't wait to see what else you have to offer us.
Click to expand...
Click to collapse
Thanks for the support my friend. Glad you are enjoying it!
Sent from my Amazon Kindle Fire2 using Tapatalk 2

I have found one problem. I have changed the script a so it is loading a new frame instead of the sliding drawer, but the launcher crashes when I click on certain apps on my phone (e.g Camera, Call Log, Phone).
I have looked everywhere in the code, but I can't figure out what it is that is causing the problem. The project files for my launcher are here if you would like to look at them.
Thanks in advance.

TroJaN SniPeR85 said:
I have found one problem. I have changed the script a so it is loading a new frame instead of the sliding drawer, but the launcher crashes when I click on certain apps on my phone (e.g Camera, Call Log, Phone).
I have looked everywhere in the code, but I can't figure out what it is that is causing the problem. The project files for my launcher are here if you would like to look at them.
Thanks in advance.
Click to expand...
Click to collapse
Will take a look at it
Sent from my Amazon Kindle Fire2 using Tapatalk 2

TroJaN SniPeR85 said:
I have found one problem. I have changed the script a so it is loading a new frame instead of the sliding drawer, but the launcher crashes when I click on certain apps on my phone (e.g Camera, Call Log, Phone).
I have looked everywhere in the code, but I can't figure out what it is that is causing the problem. The project files for my launcher are here if you would like to look at them.
Thanks in advance.
Click to expand...
Click to collapse
Also you could add a try catch statement when launching activity and log the error
Sent from my Amazon Kindle Fire2 using Tapatalk 2

TroJaN SniPeR85 said:
I have found one problem. I have changed the script a so it is loading a new frame instead of the sliding drawer, but the launcher crashes when I click on certain apps on my phone (e.g Camera, Call Log, Phone).
I have looked everywhere in the code, but I can't figure out what it is that is causing the problem. The project files for my launcher are here if you would like to look at them.
Thanks in advance.
Click to expand...
Click to collapse
I opened your project but it cannot find ActionBarActivity when you extend it. Are you using eclipse. Their is no actionbaractivity class in what u sent me
Sent from my Amazon Kindle Fire2 using Tapatalk 2

powerpoint45 said:
I opened your project but it cannot find ActionBarActivity when you extend it. Are you using eclipse. Their is no actionbaractivity class in what u sent me
Sent from my Amazon Kindle Fire2 using Tapatalk 2
Click to expand...
Click to collapse
Sorry I forgot to say that I added ActionBar to my Launcher using this guide.

TroJaN SniPeR85 said:
Sorry I forgot to say that I added ActionBar to my Launcher using this guide.
Click to expand...
Click to collapse
Sent from my Amazon Kindle Fire2 using Tapatalk 2
I tried the apk in the bin dir of the project u gave me. Good looking launcher btw.The app never forced closed on any apps I opened. My suggestion is add a try catch to startactivity.
Ex
try { ...
Startactivity...etc
} catch (Exception e)
Log.e("MYAPP", "exception", e); }
if startactivity is the problem the app will not fc but log error to logcar.
From terminal type adb logcat to capture error messages.

Thanks for this guide
THANKS MY FRIEND FOR THE GUIDE AND AWESOME WORK :good:
BUT I HAVE A SILLY QUESTION WHAT THE NAME OF PROGRAM YOU USE AND PLEASE THE DOWNLOAD LINK
AND THANKS :good:

Egyptionman said:
THANKS MY FRIEND FOR THE GUIDE AND AWESOME WORK :good:
BUT I HAVE A SILLY QUESTION WHAT THE NAME OF PROGRAM YOU USE AND PLEASE THE DOWNLOAD LINK
AND THANKS :good:
Click to expand...
Click to collapse
I suggest you follow this guys series https://www.youtube.com/watch?v=SUOWNXGRc6g
Hope it helps

powerpoint45 said:
Sent from my Amazon Kindle Fire2 using Tapatalk 2
I tried the apk in the bin dir of the project u gave me. Good looking launcher btw.The app never forced closed on any apps I opened. My suggestion is add a try catch to startactivity.
Ex
try { ...
Startactivity...etc
} catch (Exception e)
Log.e("MYAPP", "exception", e); }
if startactivity is the problem the app will not fc but log error to logcar.
From terminal type adb logcat to capture error messages.
Click to expand...
Click to collapse
Well I have managed to get this log
Code:
12-29 15:44:21.882: E/MYAPP(15021): exception
12-29 15:44:21.882: E/MYAPP(15021): android.content.ActivityNotFoundException: Unable to find explicit activity class {com.android.camera/com.android.internal.app.ResolverActivity}; have you declared this activity in your AndroidManifest.xml?
12-29 15:44:21.882: E/MYAPP(15021): at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:1405)
12-29 15:44:21.882: E/MYAPP(15021): at android.app.Instrumentation.execStartActivity(Instrumentation.java:1379)
12-29 15:44:21.882: E/MYAPP(15021): at android.app.Activity.startActivityForResult(Activity.java:2830)
12-29 15:44:21.882: E/MYAPP(15021): at android.support.v4.app.FragmentActivity.startActivityForResult(FragmentActivity.java:839)
12-29 15:44:21.882: E/MYAPP(15021): at android.app.Activity.startActivity(Activity.java:2936)
12-29 15:44:21.882: E/MYAPP(15021): at com.amh.launcher.DrawerClickListener.onItemClick(DrawerClickListener.java:28)
12-29 15:44:21.882: E/MYAPP(15021): at android.widget.AdapterView.performItemClick(AdapterView.java:284)
12-29 15:44:21.882: E/MYAPP(15021): at android.widget.AbsListView$PerformClick.run(AbsListView.java:1812)
12-29 15:44:21.882: E/MYAPP(15021): at android.os.Handler.handleCallback(Handler.java:587)
12-29 15:44:21.882: E/MYAPP(15021): at android.os.Handler.dispatchMessage(Handler.java:92)
12-29 15:44:21.882: E/MYAPP(15021): at android.os.Looper.loop(Looper.java:130)
12-29 15:44:21.882: E/MYAPP(15021): at android.app.ActivityThread.main(ActivityThread.java:3706)
12-29 15:44:21.882: E/MYAPP(15021): at java.lang.reflect.Method.invokeNative(Native Method)
12-29 15:44:21.882: E/MYAPP(15021): at java.lang.reflect.Method.invoke(Method.java:507)
12-29 15:44:21.882: E/MYAPP(15021): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
12-29 15:44:21.882: E/MYAPP(15021): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
12-29 15:44:21.882: E/MYAPP(15021): at dalvik.system.NativeStart.main(Native Method)
But not exactly sure on what I would need to do to help it.

TroJaN SniPeR85 said:
Well I have managed to get this log
Code:
12-29 15:44:21.882: E/MYAPP(15021): exception
12-29 15:44:21.882: E/MYAPP(15021): android.content.ActivityNotFoundException: Unable to find explicit activity class {com.android.camera/com.android.internal.app.ResolverActivity}; have you declared this activity in your AndroidManifest.xml?
12-29 15:44:21.882: E/MYAPP(15021): at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:1405)
12-29 15:44:21.882: E/MYAPP(15021): at android.app.Instrumentation.execStartActivity(Instrumentation.java:1379)
12-29 15:44:21.882: E/MYAPP(15021): at android.app.Activity.startActivityForResult(Activity.java:2830)
12-29 15:44:21.882: E/MYAPP(15021): at android.support.v4.app.FragmentActivity.startActivityForResult(FragmentActivity.java:839)
12-29 15:44:21.882: E/MYAPP(15021): at android.app.Activity.startActivity(Activity.java:2936)
12-29 15:44:21.882: E/MYAPP(15021): at com.amh.launcher.DrawerClickListener.onItemClick(DrawerClickListener.java:28)
12-29 15:44:21.882: E/MYAPP(15021): at android.widget.AdapterView.performItemClick(AdapterView.java:284)
12-29 15:44:21.882: E/MYAPP(15021): at android.widget.AbsListView$PerformClick.run(AbsListView.java:1812)
12-29 15:44:21.882: E/MYAPP(15021): at android.os.Handler.handleCallback(Handler.java:587)
12-29 15:44:21.882: E/MYAPP(15021): at android.os.Handler.dispatchMessage(Handler.java:92)
12-29 15:44:21.882: E/MYAPP(15021): at android.os.Looper.loop(Looper.java:130)
12-29 15:44:21.882: E/MYAPP(15021): at android.app.ActivityThread.main(ActivityThread.java:3706)
12-29 15:44:21.882: E/MYAPP(15021): at java.lang.reflect.Method.invokeNative(Native Method)
12-29 15:44:21.882: E/MYAPP(15021): at java.lang.reflect.Method.invoke(Method.java:507)
12-29 15:44:21.882: E/MYAPP(15021): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
12-29 15:44:21.882: E/MYAPP(15021): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
12-29 15:44:21.882: E/MYAPP(15021): at dalvik.system.NativeStart.main(Native Method)
But not exactly sure on what I would need to do to help it.
Click to expand...
Click to collapse
You should System.println(PACSFORADAPTER[LOC].name);
Not on comp so I think u do that
But then you can make sure it is a legit activity
Sent from my Amazon Kindle Fire2 using Tapatalk 2

Very nice, thanks!
I'll be doing this soon!
JJE990

JJE990 said:
Very nice, thanks!
I'll be doing this soon!
JJE990
Click to expand...
Click to collapse
Just ask if you need any help
Sent from my LG-L38C using Tapatalk 2

Sorry sir but i can't find the video link please provide the one...
Thanx

vaibhav_alice said:
Sorry sir but i can't find the video link please provide the one...
Thanx
Click to expand...
Click to collapse
you mean like part 1... https://www.youtube.com/watch?v=vlGEAqlBSzc

Anyone know why this thread is getting so much activity today?

Great Stuff
Thanks for sharing, the videos are very helpful and easy to understand. I hope you continue make more of these videos in the future.