Related
(Ergh. Link won't come through since I'm new. The tutorial to install Ubuntu on the Nexus One on the nexusonehacks website is the one i'm referring to)
Following this tutorial, Ubuntu installed perfectly on my Mez. No problems whatsoever! Just need to root the phone (I rooted with z4root if it matters).
Couldn't find any info on the MezBuntu combo, so I figured I'd post my experience with it here.. if it's already been known, sorry. Haha!
First post here btw
Post the link to this if you can or type it if you have problems as I would like to look at this thanks.
http://nexusonehacks.net/nexus-one-hacks/how-to-install-ubuntu-on-your-nexus-oneandroid/
-ignore, forum is being retarded-
I've spent a lot of time this evening getting some stuff added into this and tweaked tonight. I'm going to keep working a little more on this and then host my own copy so people don't have to jump through so many hoops to use it.
I can't post the link since I have less than 8 posts.. anyways, msullivan, I had no trouble with it at all. Didn't have to do any changes whatsoever. If you mean making it less complicated, then ignore me. Haha
Do you need adb to do it or can I just do it through android terminal?
Using my computers a pain lol
Sent from my SPH-D700 using XDA App
I'm assuming you need ADB, but it might work through the terminal.. I did it through ADB and had no problems whatsoever so I'd do it ADB just to be safe.
You don't need ADB, you can do most of it through a terminal emulator app. First enable WiFi and find out the WiFi IP address. Follow all the guide steps until you get to the part about finally seeing "[email protected]:/#"
Then issue the commands:
Code:
apt-get update
apt-get install openssh-server nano
service ssh start
passwd root
After that last command you'll be asked to set a password for the root account, do something simple to type on the android keyboard, like 'qwerty'.
Now go to a computer and SSH into your phone via PuTTY or whatever your favorite SSH client app is. Now it will be WAY easier to install things via apt, get the GUI running from the howto guide, etc etc. Also then you'll have a real file editor (nano) to work inside of, so you can edit the config files (such as 'bashrc' without having to do very complicated cat commands. This is how I performed my setup and it worked flawlessly. Note that if you set it up to create a VNC session for you automatically in the bashrc, you'll really feel the slowdown. In my tweaked version (which, like I said, I'll release on here soon), I have created a simple prompt on login that asks if you want to create a VNC session or not. That way if you are just there for command-line you don't have to eat the phone's RAM away.
msullivan said:
You don't need ADB, you can do most of it through a terminal emulator app. First enable WiFi and find out the WiFi IP address. Follow all the guide steps until you get to the part about finally seeing "[email protected]:/#"
Then issue the commands:
Code:
apt-get update
apt-get install openssh-server nano
service ssh start
passwd root
After that last command you'll be asked to set a password for the root account, do something simple to type on the android keyboard, like 'qwerty'.
Now go to a computer and SSH into your phone via PuTTY or whatever your favorite SSH client app is. Now it will be WAY easier to install things via apt, get the GUI running from the howto guide, etc etc. Also then you'll have a real file editor (nano) to work inside of, so you can edit the config files (such as 'bashrc' without having to do very complicated cat commands. This is how I performed my setup and it worked flawlessly. Note that if you set it up to create a VNC session for you automatically in the bashrc, you'll really feel the slowdown. In my tweaked version (which, like I said, I'll release on here soon), I have created a simple prompt on login that asks if you want to create a VNC session or not. That way if you are just there for command-line you don't have to eat the phone's RAM away.
Click to expand...
Click to collapse
What exactly did you do to get your tweaked version? Just wondering as I might give this a try
droidzach said:
What exactly did you do to get your tweaked version? Just wondering as I might give this a try
Click to expand...
Click to collapse
I didn't 'get' it, I just added some stuff like auto-starting SSH and a prompt asking whether or not you want a VNC service started. If you or others are still interested I can probably get it posted.
msullivan said:
I didn't 'get' it, I just added some stuff like auto-starting SSH and a prompt asking whether or not you want a VNC service started. If you or others are still interested I can probably get it posted.
Click to expand...
Click to collapse
Yeah that's what I meant. Ill see if I get around to getting ubuntu running and play with it then maybe I'll ask you what you did if I'm gonna actually use it. Thanks
Running a rooted G2 here, and I just installed the new US Bank app (com.usbank.mobilebanking). Upon initial launch, it requests root. If I deny the request, it looks like it would still work, but I'm concerned about what they would attempt to do with it if granted, and why they feel a need to do so. I haven't pulled logcat info yet, but I have a screenshot of the superuser request as proof.
Any thoughts? Here's mine:
Where did you download it from?
What permissions does it list?
LOL...
this had me cracking up...
I dont think I would be installing this one..
funny... nice catch
Most likely the same **** as the Blizzard Authenticator. With a rooted device, you can steal the applications /data and restore it onto another device, thus stealing *your* settings.
An application CAN refuse to run if it finds your device is rooted, whether you accept or deny the root request, and there is nothing stopping the application reporting back IMEI/IMSI and any other default stuff.
For clarification, this is the official app from US bank. I was informed about it from my bank when I logged in from the computer, and they provided a qr code pointing at com.usbank.mobilebanking on the market. I'm working on a cyanogenmod build machine, and I'm gonna look into figuring out a way to change the way superuser works to provide a third option to give the app a fakeroot style environment with a full transcript of commands run, and their output. I'm inclined to doubt my bank would pull anything really stupid with it, but then, you'd think sony would have been smarter than to rootkit peoples machines with audiocd's so many years ago too... At the least, there should be an easier way to answer the question "what is that app trying to do with a root shell?"
Ended up looking at it through dedexer. It seems a company called mcom created at least parts of the app, and their library has functions for detecting and logging to logcat rooted device status and weather the input method is custom or not. I suspect that these mcom functions are called based on policy from the bank in charge of a particular app, because I can't seem to get it to request root anymore. It appears that when it did, all it would have done is immediately destroyed the root shell and logged a warning to logcat.
fwiw, the way I was able to do it looked something like this:
$ java -jar ddx1.15.jar -d mobilebanking classes.dex
$ cd mobilebanking
$ grep -r \"su\" *
A custom su with fakeroot and logging via a third option would be neat though... I might still work on that.
acolwill said:
Most likely the same **** as the Blizzard Authenticator. With a rooted device, you can steal the applications /data and restore it onto another device, thus stealing *your* settings.
An application CAN refuse to run if it finds your device is rooted, whether you accept or deny the root request, and there is nothing stopping the application reporting back IMEI/IMSI and any other default stuff.
Click to expand...
Click to collapse
While I still have a method to figure out what an app would do with root fresh in my mind, I'm gonna take a look at that there Blizzard Authenticator... I've never used it, as Blizzard is on my do not trust list, and I think this might be interesting....
Blizzard's auth seems to do the same basic thing. It has a function called "isDeviceRooted" which seems to return true any time the su command can be run, though it nags the user for having root.
I started working on a custom su setup which allows you to log what programs try to do as root. So far, that entails recompiling the su binary, as well as busybox. It's in rough shape yet, so current "release" will just be a pastebin dump here:
http://pastebin.com/fiqQPeFq <- patch to su.c to use a logfile
http://pastebin.com/37NJyxQh <- new busybox config with support for the 'script' command used by my custom su, along with a few other small changes.
If you can compile it, you should be able to figure it out as well. Once I can make it a little cleaner (eg, logging as a checkbox on the accept/deny screen, instead of always being done), I'll make a more proper release, but maybe someone will find it useful here.
Hi all,
I've looked up as much as I can in pursuit of this, but alas have found nothing.
I'm a huge noob when it comes to code. In fact I don't know a single thing about writing code. So I might be completely off base here, but is it possible to use Tasker to run a shell command to start LiveWallpaper?
I have been using an app called EasyProfiles to do it. The app shows what appears to be a target that activates the LiveWallpaper when a certain condition is met (in my case, bluetooth or headphone connection). It looks like this:
LiveWallpaper:com.cyphercove.audioglow/ com.cyphercover.audioglow.LWSerive
[AudioGlow being the LWP]
So I'm wondering if it is possible using shell commands in Tasker to utilize this code (or whatever it may be) to activate the livewallpaper?
I'm aware I might be completely wrong here, but any help or advice is appreciated.
Thanks,
jldr
Evening bump
Anyone?
Hi.
I'm experimenting to write a personal app to help me get to know more songs. I want to catch the spotify intent that indicates when the track changes and use the data on my app.
I have been investigating how to do it and tried multiple lines of code like this (iF.addAction("com.android.music.metachanged"); ), but no luck yet. Everybody (stackoverflow) says there is no way to get that info. But the fact is that there is one app that is able to catch that info: musiXmatch. It is able to detect when the track on the spotify free radio changes and deliver the corresponding lyric.
So, I tried decompiling both the musicXmatch and spotify apks using apktool but wasn't able to find the way the apps comunicate with one another. I have yet to get deeper on smali but by what I see this far, the answer isn't there.
So, the next thing I was thinking I'd try was to make an AOSP rom with some extra logging habilities so that i can listen to the communication between the apps (namely, the broadcastreceiver).
My question: ¿Is there such an aosp distro? One that has extra sniffing/logging capabilities. Also, Anyone has an extra idea on how to accomplish my goal, or maybe some reason for which it will be impossible for me to do it (like for example the intent from spotify being explicit).
Thank you very much in advance for your time.
I solved it. I got the intent.
In case anyone wonders how I did it, here it is:
Rooted my phone (I have a Nexus 4 which lost root with one OTA update and never bothered to recover it)
Installed CydiaSubstrate. A wonderful piece of software by @saurik that allows you to literally modify any java or native C/C++ class during runtime seamlessly. It also does lots of other stuff I don't really understand.
Had to put SELinux to permissive on KitKat because it is on enforced by default since 4.3, in order for the Substrate to work
Got IntroSpy from git and wrote a Custom Hook for IntentReceiver startActivity() method
Enabled IntroSpy for musicXmatch app and it dumped all the app's intents to logcat
ztrange said:
I solved it. I got the intent.
In case anyone wonders how I did it, here it is:
Rooted my phone (I have a Nexus 4 which lost root with one OTA update and never bothered to recover it)
Installed CydiaSubstrate. A wonderful piece of software by @saurik that allows you to literally modify any java or native C/C++ class during runtime seamlessly. It also does lots of other stuff I don't really understand.
Had to put SELinux to permissive on KitKat because it is on enforced by default since 4.3, in order for the Substrate to work
Got IntroSpy from git and wrote a Custom Hook for IntentReceiver startActivity() method
Enabled IntroSpy for musicXmatch app and it dumped all the app's intents to logcat
Click to expand...
Click to collapse
Thanks, are you going to share said intents?
Nice work, but it would have been great with some more details...
Hi, please we need a follow up.
Hey guys, first of all, sorry if I post on the wrong section.
I have aquestion for devs. I'm a student developer and I'm learning to develop for Android. Do you guys think I'd necessarily need an Android device or the Android emulator would be enough(maybe for one year or more). I also like w10 mobile and I don't know what to do.
Thanks!!!!!!
Also another question, I'm a really beginner dev, but I'd like to get involved in community development, hacking etc, what do you guys recommend to me? Where should a beginner like me start from?
I am always running the apps on a real device if I can. This is definetly needed if the app uses for example something like networking because these functions will not be available on an emulator. The main reason however for using a real device is that it runs a lot smoother. The emulator can take a long time to boot up and it can be really laggy when running the app. Also when you are holding the phone on your hand you get to see how the app really looks and feels.
Emulator is ok though if there is nothing else available.
VilleI said:
I am always running the apps on a real device if I can. This is definetly needed if the app uses for example something like networking because these functions will not be available on an emulator. The main reason however for using a real device is that it runs a lot smoother. The emulator can take a long time to boot up and it can be really laggy when running the app. Also when you are holding the phone on your hand you get to see how the app really looks and feels.
Emulator is ok though if there is nothing else available.
Click to expand...
Click to collapse
Thanks for your reply. Well... the emulator is not really slow on latest versions of android studio... but it does start pretty slow. I'll finally use a real device.
On ADV, how can you test GPS, other sensors?
Do you guys think I'd necessarily need an Android device or the Android emulator would be enough(maybe for one year or more)
Click to expand...
Click to collapse
You can use Android Studio emulator and it will work in most cases. Couple recommendations:
1. Select Android version with Google APIs when creating device
2. Install Intel HAXM (you can find it in SDK manager also) - this will really speed up your emulator including loading time
3. Android Studio 2.0 will be released soon and looks like they will improve emulator performance and functionality there.
Of course you may face something wich is not currently works on emulator but you will face this on a real devices too - some features may work different on devices from different manufacturers. But the chance with facing this kind of troubles is very low when you work on common stuff. Also you can take a look to the 3rd party emulators, like Genymotion.
Anyway I prefer to use real device when developing because I can "feel" it
Where should a beginner like me start from?
Click to expand...
Click to collapse
Start with creating some app which will work with some Rest services, display some sort of lists, images, use database to store data. Just think about creating something useful and interesting for you.
---------- Post added at 04:54 PM ---------- Previous post was at 04:50 PM ----------
Cuong Phan said:
On ADV, how can you test GPS, other sensors?
Click to expand...
Click to collapse
You can test GPS using different apps which mocks your location (you can download apk from play store and install it on emulator) or using the terminal:
1. Connect to emulator with "telnet localhost 5554" command. Maybe you will need to change "5554" with another digits - just look at emulator's window title
2. Set location with "geo fix 12.345 67.89" command
What other sensors you need to test?
Used android emulators a lot, but mostly to test different unusual screen resolutions/dpi combinations.
They're ok speedwise, but you'll never get real feel of your app on AVD. And please, don't release anything, that just been tested only on AVD.
Also AVDs are quite good for recording videos of your app UI using screengrabbers on desktop (SSR - Simple Screen recorder is the best for me so far)
As for beginner's project - try to implement little game. I've started with simple rotating cube example from "Hello Android" book , and this little project ended with game with 3M downloads on play store
Android emulator will work when you begin a project.
If you need more tests or make a formal public apk, you can use real devices.
Best way is use both if you have device - use device. Another android versions, resolutions, sizes etc. test on the emulator.
If standard emulator is too slow, you can use genymotion.