Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.java.programmer > #30101 > unrolled thread

Android Studio built-in samples okay but imports don't work

Back to article view | Back to comp.lang.java.programmer

Contents

  Android Studio built-in samples okay but imports don't work John Doe <always.look@message.header> - 2014-10-16 01:46 +0000
    Re: Android Studio built-in samples okay but imports don't work John Doe <always.look@message.header> - 2014-10-16 15:21 +0000
      Re: Android Studio built-in samples okay but imports don't work John Doe <always.look@message.header> - 2014-10-16 16:49 +0000
        Re: Android Studio built-in samples okay but imports don't work John Doe <always.look@message.header> - 2014-10-21 20:23 +0000
      Re: Android Studio built-in samples okay but imports don't work Joerg Meier <joergmmeier@arcor.de> - 2014-10-16 18:51 +0200
        Re: Android Studio built-in samples okay but imports don't work John Doe <always.look@message.header> - 2014-10-16 17:04 +0000
          Re: Android Studio built-in samples okay but imports don't work Andreas Leitgeb <avl@auth.logic.tuwien.ac.at> - 2014-10-16 22:04 +0000
        Re: Android Studio built-in samples okay but imports don't work John Doe <always.look@message.header> - 2014-10-24 15:59 +0000
          Re: Android Studio built-in samples okay but imports don't work Joerg Meier <joergmmeier@arcor.de> - 2014-10-24 18:20 +0200
            Re: Android Studio built-in samples okay but imports don't work John Doe <always.look@message.header> - 2014-10-24 18:13 +0000
              Re: Android Studio built-in samples okay but imports don't work Joerg Meier <joergmmeier@arcor.de> - 2014-10-25 10:30 +0200
    Re: Android Studio built-in samples okay but imports don't work John Doe <always.look@message.header> - 2014-10-18 02:42 +0000
    Re: Android Studio built-in samples okay but imports don't work John Doe <always.look@message.header> - 2014-10-21 03:17 +0000
      Re: Android Studio built-in samples okay but imports don't work John Doe <always.look@message.header> - 2014-10-21 03:20 +0000
    Re: Android Studio built-in samples okay but imports don't work John Doe <always.look@message.header> - 2014-10-21 20:49 +0000
    Re: Android Studio built-in samples okay but imports don't work John Doe <always.look@message.header> - 2014-10-23 19:06 +0000

#30101 — Android Studio built-in samples okay but imports don't work

Using the most recent Android Studio (0.8.9). I've been trying to 
import and run a sample project all day. This is very close... 

<http://adanware.blogspot.com/2014/10/android-importing-older-android-gradle.html> 

Thing is, the file (SlidingTabsBasicSample\build.gradle) is empty. 
So of course there is no way to edit any of the entries that are 
not there. 

I have a feeling that my Android SDK Manager selections are not 
right. 

If you want to run older projects, do you need older APIs? 

Or does that need for older stuff just apply to the Build Tools? 

I have tried downloading all of the newer stuff. I guess I will 
try installing all of the older stuff. 

Currently using (4.4.2) API because that's my device's Android
version. I thought that API would support older software even
though older hardware won't run newer API software. 

Thanks.

[toc] | [next] | [standalone]

#30103

I have downloaded everything in the Android SDK Manager. 

Whether or not that helped, now I can see text in the 
(SlidingTabsBasicSample\build.gradle) file. But when I made the 
recommended change, I got another error, and then another after 
that. 

Today I'm going to start by trying the method on this page... 

https://github.com/gdg-hudson-valley/android-samples 

Apparently they are showing how to use the Android samples in
Android Studio (0.8.9). 

[toc] | [prev] | [next] | [standalone]

#30104

From that page...

For making the Android online samples work in Android Studio 
(0.8.9)...

Edit the (build.gradle) file with text in it, the file that's in the 
subfolder. There is more than one (build.gradle) file.

change "0.9.+" to "0.12.2"

change "19.0.1" and "19.1.+" to "20.0.0"

change "plugin: 'android'" to "plugin: 'com.android.application'"

[toc] | [prev] | [next] | [standalone]

#30149

This is the original...

https://github.com/gdg-hudson-valley/android-samples

We imported and built Android Developers Samples to run on Android 
Studio (currently at v0.8.9). Doing this required the following 
changes after the relevant's project zipfile was downloaded from its 
specific page on the samples site.

First, in the build.gradle file,

    change classpath to'com.android.tools.build:gradle:0.12.2'
    change buildToolsVersion to "20.0.0"
    change plugin to 'com.android.application' (from 'android')
    change 'com.android.support:' dependencies to remove "+" 
versions (replace with 20.0.0)

Next,

    import the project into Android Studio (File->Import Project)
    rebuild it (automatically, or manually using Project->Rebuild).
    if build errors occur, try 'File->Invalidate Caches/Restart', 
then rebuild

Finally,

    verify project build by running the application in an emulator, 
or on a connected Android Device.

Optionally,

    Set ".gitignore" to prevent compile/build/IDE artifacts being 
stored needlessly in version control.
    For reference: This repo uses a .gitignore file based on this 
StackOverflow post.

[toc] | [prev] | [next] | [standalone]

#30105

On Thu, 16 Oct 2014 15:21:28 +0000 (UTC), John Doe wrote:

> Today I'm going to start by trying the method on this page... 

May I recommend trying #android-dev on the Freenode IRC network ? It might
be a more helpful place for that kind of stuff that needs a more immediate
response. It also has a lot more Android devs than this place ;)

Liebe Gruesse,
		Joerg

-- 
Ich lese meine Emails nicht, replies to Email bleiben also leider
ungelesen.

[toc] | [prev] | [next] | [standalone]

#30106

Joerg Meier <joergmmeier@arcor.de> wrote: 

> John Doe wrote: 
> 
>> Today I'm going to start by trying the method on this page... 
> 
> May I recommend trying #android-dev on the Freenode IRC network 
> ? It might be a more helpful place for that kind of stuff that 
> needs a more immediate response. It also has a lot more Android 
> devs than this place 

I must get used to messing with the IDE and stuff, so spinning my 
wheels is not a big deal now. And I use UseNet for notes. Is 
anything on IRC ever propagated to the Internet? I don't recall 
finding search results from IRC. After asking here on UseNet, I 
usually find my question when searching the Internet. 

I guess the only other Android related UseNet group is 
(comp.mobile.android) but that's user oriented. 

[toc] | [prev] | [next] | [standalone]

#30110

John Doe <always.look@message.header> wrote:
> Joerg Meier <joergmmeier@arcor.de> wrote: 
>> John Doe wrote: 
>>> Today I'm going to start by trying the method on this page... 
>> May I recommend trying #android-dev on the Freenode IRC network 
>> ? It might be a more helpful place for that kind of stuff that 
>> needs a more immediate response. It also has a lot more Android 
>> devs than this place 
> I must get used to messing with the IDE and stuff, so spinning my 
> wheels is not a big deal now. And I use UseNet for notes. Is 
> anything on IRC ever propagated to the Internet? I don't recall 
> finding search results from IRC. After asking here on UseNet, I 
> usually find my question when searching the Internet. 

If you get helped on the IRC, then surely nobody would complain,
if you posted the answer here in this thread, afterwards... ;-)

[toc] | [prev] | [next] | [standalone]

#30176

Joerg Meier <joergmmeier@arcor.de> wrote: 

> John Doe wrote: 
> 
>> Today I'm going to start by trying the method on this page... 
> 
> May I recommend trying #android-dev on the Freenode IRC network

"freenode group registration is currently suspended"

[toc] | [prev] | [next] | [standalone]

#30177

On Fri, 24 Oct 2014 15:59:36 +0000 (UTC), John Doe wrote:

> Joerg Meier <joergmmeier@arcor.de> wrote: 
>> John Doe wrote: 
>>> Today I'm going to start by trying the method on this page... 
>> May I recommend trying #android-dev on the Freenode IRC network
> "freenode group registration is currently suspended"

Why exactly are you trying to register a group, and why are you telling me
about it ? If you received that message trying to just chat on
#android-dev, you have somewhere taken a wrong turn.

Liebe Gruesse,
		Joerg

-- 
Ich lese meine Emails nicht, replies to Email bleiben also leider
ungelesen.

[toc] | [prev] | [next] | [standalone]

#30178

Joerg Meier <joergmmeier@arcor.de> wrote: 

> John Doe wrote: 
>> Joerg Meier <joergmmeier@arcor.de> wrote: 
>>> John Doe wrote: 

>>>> Today I'm going to start by trying the method on this page...

>>> May I recommend trying #android-dev on the Freenode IRC 
>>> network 

>> "freenode group registration is currently suspended" 
> 
> Why exactly are you trying to register a group, and why are you 
> telling me about it ? If you received that message trying to 
> just chat on #android-dev, you have somewhere taken a wrong 
> turn. 

Apparently. 

I was trying to use the web access. The instructions from their 
webpage are cryptic, given without explaining that presumably the 
commands for nickname registration are entered in their IRC 
program. In other words... They don't tell you that you need the 
IRC program to register a nickname before using the web access. 
I guess that by the format of their instruction for registering a 
nickname. 

[toc] | [prev] | [next] | [standalone]

#30181

On Fri, 24 Oct 2014 18:13:34 +0000 (UTC), John Doe wrote:

> Joerg Meier <joergmmeier@arcor.de> wrote: 
>> John Doe wrote: 
>>> Joerg Meier <joergmmeier@arcor.de> wrote: 
>>>> John Doe wrote: 
>>>>> Today I'm going to start by trying the method on this page...
>>>> May I recommend trying #android-dev on the Freenode IRC 
>>>> network 
>>> "freenode group registration is currently suspended" 
>> Why exactly are you trying to register a group, and why are you 
>> telling me about it ? If you received that message trying to 
>> just chat on #android-dev, you have somewhere taken a wrong 
>> turn. 
> Apparently. 

> I was trying to use the web access. The instructions from their 
> webpage are cryptic, given without explaining that presumably the 
> commands for nickname registration are entered in their IRC 
> program. In other words... They don't tell you that you need the 
> IRC program to register a nickname before using the web access. 
> I guess that by the format of their instruction for registering a 
> nickname.

I suspect you looked at the wrong help section. The correct one is:

<https://freenode.net/faq.shtml#nicksetup>

You only really need step 2, and you don't need a separate downloaded
client, the web client on their site is just fine.

Short summary:

Go to <http://webchat.freenode.net/> and connect

write

/msg NickServ REGISTER password youremail@example.com

obviously while filling in a password and your email, then confirm the
email you get. The next time you visit freenode, use

/msg NickServ IDENTIFY account password

to identify again.

I'm sorry you are having so much trouble, as IRC is a fantastically useful
resource if you can raise above the various trolls trying to get you into
arguments. But then, you have these everywhere, as evidenced by our own
annoying "[calls me a liar]" idiot.

Liebe Gruesse,
		Joerg

-- 
Ich lese meine Emails nicht, replies to Email bleiben also leider
ungelesen.

[toc] | [prev] | [next] | [standalone]

#30123

https://android.googlesource.com/

That's where to get the stock clock source code.

[toc] | [prev] | [next] | [standalone]

#30138

The DeskClock runs with zero errors using version (android-4.1.1_r6.1). 
Don't know why so many errors are produced with newer versions. Maybe 
it's an Android Studio beta problem. I have downloaded everything in 
the Android SDK Manager.

The source code is from here...

https://android.googlesource.com/platform/packages/apps/DeskClock/+refs

The method for testing the different versions, in Windows...

Move to your projects folder

Right-click on your projects folder > Git Bash

git clone https://android.googlesource.com/platform/packages/apps/DeskClock/

cd DeskClock/

Now start the process of testing revisions...

git checkout tags/<revision>, for example...

git checkout tags/android-cts-2.3_r12

Open Android Studio (forthe first time) and import the DeskClock project 
(will be done repeatedly). It will produce a different project for the 
new revision if all goes well.

Rebuild the project

Note the errors, close the project, no need to close Android Studio

If no joy, try repeating the process starting with (git checkout) 
above using a different version

Other versions might run, for example (android-cts-2.3_r12).

Looks like there might be a bunch of ready to go clock source code 
to play with.

Now give me some hacking room! 

[toc] | [prev] | [next] | [standalone]

#30139

Correction, the first one should read...

git checkout tags/android-4.1.1_r6.1

[toc] | [prev] | [next] | [standalone]

#30150

Trying to use a more recent version of DeskClock... 

Using DeskClock version (android-4.4.2_r2.0.1, that is apparently 
the most recent version for Android 4.4.2) was producing 63 
errors. Imported it anew, then changed the Android Studio produced
(app/build.gradle) file to the recommendations from the 
above-mentioned website. Now it produces 18 errors. 

That's what I thought. It's an IDE settings problem. Now... Figure
out which settings get rid of the remaining 18 errors. 

[toc] | [prev] | [next] | [standalone]

#30167

I now have the Android (4.4.2) version of DeskClock running with
no errors in Android Studio and on the USB connected Galaxy Tab 3.
Had to import another Google repository program... 

https://android.googlesource.com/platform/frameworks/opt/datetimepicker/

Like this...

Project Structure > Modules > +

New Module > Import Existing Project (name should be same as module)

ignore the error (in Windows 7) and Finish.

Project Structure > select your project > Dependencies > + (on right side)

select Module Dependency > newly added module

copy library project files to the newly created module directory (don't know what that's about)


I stopped before the second Project Structure instruction above,
rebuilt, and was prompted to import some stuff from the SDK
Manager. Then continued with the second Project Structure part. 


This is the standard (build.gradle) file...

apply plugin: 'com.android.application'
dependencies
{
  // Add the support lib that is appropriate for SDK
  compile "com.android.support:support-v4:20.0.0"
  compile "com.android.support:support-v13:20.0.0"
}
android
{
  compileSdkVersion 19
  buildToolsVersion "20.0.0"
  defaultConfig
  {
    applicationId "com.android.deskclock"
    minSdkVersion 19
    targetSdkVersion 19
    testApplicationId "com.android.deskclock.tests"
    testInstrumentationRunner "com.android.deskclock.DeskClockLaunchPerformance"
  }
  buildTypes
  {
    release
    {
      runProguard false
      proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.txt'
    }
  }
}

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.java.programmer

csiph-web