Related
Hi,
Today I found this document on the german website www.heise.de
This document is a threat analysis of the Android Market.
On page 9 is an overview how many apps have which permissions and there are 9 apps that can brick your phone!!
Does anybody know such an app which can brick the phone?
You should read this: http://www.zdnet.com/blog/burnette/cnet-retracts-article-on-android-app-privacy-threat/1987 and realize its all a scam to get people to buy an iphone.
They where listing one of the option as brick, anybody know if there's such option. and what it does, I doubt it would brick the phone in the real meaning...
either way anything that has a direct connection to the internet and access to your record is a potential risk, it is goog to be aware of this but pointing Android because it list such option is quite ridiculous since other OS doesn't even warn you about the fact that program can read your data...
Link: http://developer.android.com/reference/android/Manifest.permission.html
android.permission.BRICK
Required to be able to disable the device (very dangerous!).
Good lord, WIPE I could see.... BRICK!?
klausdieter79 said:
Link: http://developer.android.com/reference/android/Manifest.permission.html
android.permission.BRICK
Required to be able to disable the device (very dangerous!).
Click to expand...
Click to collapse
I think it's there in the SDK only for testing on the emulator. I'm quite sure none of the actual hardware devices would support it.. or at least I hope not
rohandhruva said:
I think it's there in the SDK only for testing on the emulator. I'm quite sure none of the actual hardware devices would support it.. or at least I hope not
Click to expand...
Click to collapse
I think it should be there, at least I have one use for it, an application to remotely lock your phone (or wipe critical information) in case of stole or lost phone. Definitely user should confirm this permission and should only do that if they completely trust the author.
bohlool said:
I think it should be there, at least I have one use for it, an application to remotely lock your phone (or wipe critical information) in case of stole or lost phone. Definitely user should confirm this permission and should only do that if they completely trust the author.
Click to expand...
Click to collapse
Remote locking is different from bricking. It makes no sense to "remotely brick" a stolen device, because then, even if you do get it back, it's useless.
But when you install the app, it has to display the permission
This application has access to the following:
Hardware controls
Brick your phone
rohandhruva said:
I think it's there in the SDK only for testing on the emulator. I'm quite sure none of the actual hardware devices would support it.. or at least I hope not
Click to expand...
Click to collapse
I'm sure there's some kind of app that can potentially brick your phone. No doubt you have to be rooted for it to have access to that ability. Clockwork ROM manager could potentially brick you're phone if you do something stupid (battery pull).
Read the permissions. Don't install what seems suspect. If the app tries to do something it doesn't have permission to do, the OS won't allow it. It's not like another app store where you have to rely on a fallible person to safeguard you.
Oh, and don't freak out when that free game you're looking at asks for internet access and your GPS location. It needs that info to serve you ads so it stays free. Don't be paranoid, nobody really cares about you, never mind enough to stalk you.
ATnTdude said:
I'm sure there's some kind of app that can potentially brick your phone. No doubt you have to be rooted for it to have access to that ability. Clockwork ROM manager could potentially brick you're phone if you do something stupid (battery pull).
Read the permissions. Don't install what seems suspect. If the app tries to do something it doesn't have permission to do, the OS won't allow it. It's not like another app store where you have to rely on a fallible person to safeguard you.
Oh, and don't freak out when that free game you're looking at asks for internet access and your GPS location. It needs that info to serve you ads so it stays free. Don't be paranoid, nobody really cares about you, never mind enough to stalk you.
Click to expand...
Click to collapse
The Clockwork ROM Manager application itself can't brick the phone - or at least it won't advertise that it can. The bricking is caused if the flashing process is interrupted, which is (strictly speaking) outside the purview of the app.
Also, what the OP found is just an ability to advertise to the user that installing this app can brick the phone. There is no mechanism by which an apk, running inside the dalvik jvm sandbox, can cause irrevocable hardware damage to the phone - at least none has been found yet.
Your last paragraph about games staying free and paranoia is just off-topic.
rohandhruva said:
The Clockwork ROM Manager application itself can't brick the phone - or at least it won't advertise that it can. The bricking is caused if the flashing process is interrupted, which is (strictly speaking) outside the purview of the app.
Also, what the OP found is just an ability to advertise to the user that installing this app can brick the phone. There is no mechanism by which an apk, running inside the dalvik jvm sandbox, can cause irrevocable hardware damage to the phone - at least none has been found yet.
Click to expand...
Click to collapse
1) You're Splitting hairs. We don't know what criteria the company that produced this study was using. Given that the whole thing was a springboard for advertising the need for their product, they're probably being more loose with the facts than you or I would. I used Clockwork as an example of how they might be interpreting the market.
2) I wasn't arguing against you. I was using your post to segue into my own. So do not take anything I said as something against your position. I, in fact, agree with your statement. I highly doubt a stock Android handset will allow you permission to brick it. I even doubt there is a root-only app that will purposefully brick your phone. I think SMobile Systems is borderline LYING to sell their unneeded product.
Your last paragraph about games staying free and paranoia is just off-topic.
Click to expand...
Click to collapse
XDA attracts a lot more than experts, many of which are not even vaguely familiar with Android permissions are, what app services might need them, nevermind the economics of the Android market. As such, given that I had in the previous sentence advised people to be critical of the permissions that apps request (I don't think most people look at them closely enough), I went the other way and told them not to be so careful as to enter the realm of paranoia. It's balanced advice and is therefore relevant to the topic.
Hopefully, this clears up any confusion. Cheers and good night...err morning, whatever you call 4AM.
ATnTdude, I don't mean to be brandishing swords or arguing.. Sorry if it seemed that way I just realised that the OP started this topic out of that stupid SMobile article. Had I read that before, I wouldn't have 'split hairs'! My bad :-/
luffyz said:
but when you install the app, it has to display the permission
this application has access to the following:
hardware controls
brick your phone
Click to expand...
Click to collapse
ahhahaha +1
@klausdieter79 Thanks for the link
I also hope it is not included in the regular phone library, I can easilly imagine someone granting this by mistake
Let's wait for someone to upload a one button app named accelerate and the only permission requested will be brick...
P00r said:
@klausdieter79 Thanks for the link
I also hope it is not included in the regular phone library, I can easilly imagine someone granting this by mistake
Let's wait for someone to upload a one button app named accelerate and the only permission requested will be brick...
Click to expand...
Click to collapse
I'm pretty much 100% certain you would have to have a rooted ROM for that to work...in which case, you probably know better than to install an app that requests permission to brick your phone
rohandhruva said:
ATnTdude, I don't mean to be brandishing swords or arguing.. Sorry if it seemed that way I just realised that the OP started this topic out of that stupid SMobile article. Had I read that before, I wouldn't have 'split hairs'! My bad :-/
Click to expand...
Click to collapse
I figured as much. It's all good.
ATnTdude said:
Oh, and don't freak out when that free game you're looking at asks for internet access and your GPS location. It needs that info to serve you ads so it stays free. Don't be paranoid, nobody really cares about you, never mind enough to stalk you.
Click to expand...
Click to collapse
OT, but I would be a little pissed if a developer was wasting my battery with GPS just to serve up targeted ads. There's no reason they couldn't use the much more battery efficient network location for that.
I like to share a thought with everyone, but specially with the programmers.
How come all rom’s for this Smartphone, that looks like a computer, don't include a simple File Explorer?
It’s so basic, isn’t it?
Perhaps next roms can include this simple but so usefull feature....
MIUI has a file explorer, the philosophy for the Oxygen ROM is to make it as light as possible, and from the void. OP : "I hate ROMs out there which impose you their applications, keyboard, launchers and any other trash. No, it's my belief we have market for some reason, so use it."
AFAIK the CM7 got a file explorer... I usually install a new file explorer (the one from Stockwell's B160) when I use other ROMs than MIUI
MIUI is the Rom I just flashed and the explorer in it has 3 option (Navigate/SD Card/FTP) well non of this work with me, e.g., can't see any files.
I don’t have external SD card but we should be able to "navigate" on the phone directories.
The other, I understand and respect the philosophy of keeping things as light as possible, but it’s a file explorer, how heavy could this be?
Tried to use the internal sd card, and I understand your problem. Hopefully there is a fix for this, because the MIUI file explorer is relly nice
MIUI is only nice for the eyes.
Performance is 0 (Z...E....R....o....)
Pj77 said:
MIUI is only nice for the eyes.
Performance is 0 (Z...E....R....o....)
Click to expand...
Click to collapse
Your post isn't helping anyone, nor contributing to the topic.
Pj77 said:
MIUI is only nice for the eyes.
Performance is 0 (Z...E....R....o....)
Click to expand...
Click to collapse
I don't really think that MIUI is that useless.. I just underclocked my phone a bit(just 'coz MIUIs default clock freq. is 1018 and I wanted to compare to stock(806)) and quadrant averaged around 2000, which is approximately 500 points higher than an average stock-ROM would have given me..
Well, all stock-ROMs are still froyo, so maybe that is the biggest boost in performance, but in my experience, MIUI with franco-kernel and zram is quite good.
AND it's nice to the eye!
Oh, and I was running minmax, not performance..
Sent from my u8800 using XDA Premium App
Pj77 said:
[...] Performance is 0 (Z...E....R....o....)
Click to expand...
Click to collapse
I must totally disagree with you there. I find Stockwell's MIUI very fast, even when not overclocked. And with Franco.kernel and zram it is blazing fast.. Maby you didn't try the ROM long enough. At first after you flash it, it stutters in the launcher etc. But i think it just needs to build up cache or something, then after 1-3 minutes it is fast!
Actually android have a file manager by default. I don't understand why the rom creators don't include it.
This thread is pretty much useless...Just use the freaking Market and download Astro or FS File Manager...Is that so hard??
katu2006 said:
This thread is pretty much useless...Just use the freaking Market and download Astro or FS File Manager...Is that so hard??
Click to expand...
Click to collapse
Agreed, if that so hard, you shouldn't even choose android
Sent from my u8800 using XDA App
katu2006 said:
This thread is pretty much useless...Just use the freaking Market and download Astro or FS File Manager...Is that so hard??
Click to expand...
Click to collapse
Are you kidding me? In android, you can choose not the share your gmail account. I can understand you can trust google or you don't afraid anything from google. But this is people choices. You can at least respect their additude about that. Do you aware of the market don't work without gmail account? Maybe i don't want to use my any accounts on phone.
If you don't have a file manager, you can't install any application.
Well, this topic is not useless.
Please..
Özgürce said:
Are you kidding me? In android, you can choose not the share your gmail account. I can understand you can trust google or you don't afraid anything from google. But this is people choices. You can at least respect their additude about that. Do you aware of the market don't work without gmail account? Maybe i don't want to use my any accounts on phone.
If you don't have a file manager, you can't install any application.
Well, this topic is not useless.
Please..
Click to expand...
Click to collapse
) You're gotta be joking... This is a funny one )
You're saying that you don't want to use the Market at all? If that's the case, than you've made a mistake buying an Android phone or any smartphone for that matter.
I don't mean to offend anybody, but there is nothing to respect here, this attitude is actually childish... If you've installed a custom ROM, then you should know how to install a File Manager from CWM and stop winging about something silly things.
What is the difference with using or without it? I just don't get it the why people forced to use market or data connection. Thats all. Even if the people can use CWM that is not mean they can make update package. I mean update-script .. bla bla.. Filemanager is just 689KB file. I don't get the point removing it.
Whatever. Seems like i can't make myself clear to you.
Özgürce said:
What is the difference with using or without it? I just don't get it the why people forced to use market or data connection. Thats all. Even if the people can use CWM that is not mean they can make update package. I mean update-script .. bla bla.. Filemanager is just 689KB file. I don't get the point removing it.
Whatever. Seems like i can't make myself clear to you.
Click to expand...
Click to collapse
Market is meant to help you, nobody is forcing you to use it, but if it's there and it's free, why not use it?
I believe there are some licensing issues, as most application developers are not happy when their app is distributed with custom Roms (if the file manager is free, the app developer gets paid through the number of downloads each day and if everybody stops downloading, then developers are not going to be happy). That's why CM7 doesn't have the Google Market and other Roms are missing apps...
pls stop commenting on other people's preferences..
if u think a particular request is childish/stupid/useless/whatever, just ignore the whole thread!
whats the point of teasing/offending other's request and giving no help at all?
to prove that u r superior or what?!
this is indeed childish imho..
pls just stop dis-helping here.. please!
if you want/need a file manager why dont you download the apk of one and put it inside the zip of the rom? that way it will be there when it gets installed.
iamelton said:
pls stop commenting on other people's preferences..
if u think a particular request is childish/stupid/useless/whatever, just ignore the whole thread!
whats the point of teasing/offending other's request and giving no help at all?
to prove that u r superior or what?!
this is indeed childish imho..
pls just stop dis-helping here.. please!
Click to expand...
Click to collapse
I've explained why there is no File Manager (in Oxygen and CM7) and how to get get/install it...if this is "dis-helping" then you've big issues...
The point is: don't expect Developers to hold your hand with every everything you want to install on a CUSTOM rom, they've got better things to do.
katu2006 said:
I've explained why there is no File Manager (in Oxygen and CM7) and how to get get/install it...if this is "dis-helping" then you've big issues...
The point is: don't expect Developers to hold your hand with every everything you want to install on a CUSTOM rom, they've got better things to do.
Click to expand...
Click to collapse
Are you sure about that ? CM7 have it in official packages.
We are not kids. Watch your words. And i'm talking to rom developers not you anymore. If they have better things to do, they can talk and reject to make this you know?
katu2006 said:
I've explained why there is no File Manager (in Oxygen and CM7) and how to get get/install it...if this is "dis-helping" then you've big issues...
The point is: don't expect Developers to hold your hand with every everything you want to install on a CUSTOM rom, they've got better things to do.
Click to expand...
Click to collapse
u got me totally wrong (just as u usually did in other posts as well)..
i dont need a file explorer in this rom (or whatever rom).. i like to keep roms minimal and thats why i choose oxygen..
what im saying is that even if u and i dont need this, it doesnt mean those who want it childish..
and if the developers think this request is not to be entertained, its their decision..
what on earth gives u the authority to judge other's requests, and make comments such as "childish"?
this is what im against..
(anyway i dont know if u can read or comprehend others words properly..)
Hey
I've recently got my NST and, after TouchNootering it, I reverted it back to stock and manually rooted & installed stuff on it. I managed to install latest busybox too (1.19.1), even better than what TouchNooter installs.
Anyways, I've been wondering if anybody here is up to the challenge of making a ROM for this device. Modifying the actual ROM is nice... but it's buggy and it feels sloppy at times, not to mention it semi-works. Some features do, some don't.
I think, that if we make it possible to run a basic Eclair ROM, we can move to Froyo and maybe then, with enough experience and all, get GB or ICS installed on it. I think it's -very- possible... it just needs to be put some work on
Anyone?
Two issues: Drivers and memory. Unless drivers are available for the version of Android you want to build, you're going to have a tough time. Unless B&N releases a newer version of Android for the NST, this is probably unlikely. I suspect we're stuck on 2.1 eclair.
The NST only has 256M of memory, so a lot of what works on other devices is going to have to trimmed down.
This isn't to say that it can't be done, but by the time you're done, it may not be so much better than what we've got. Anything is possible, of course, but I'm not aware of anything along the lines of CyanogenMod in the works for the NST. I'd be happy to be wrong.
In the meantime, there's no reason improved software can't be written to run on what we've got. At least rooting makes that possible.
bobstro said:
Two issues: Drivers and memory. Unless drivers are available for the version of Android you want to build, you're going to have a tough time. Unless B&N releases a newer version of Android for the NST, this is probably unlikely. I suspect we're stuck on 2.1 eclair.
The NST only has 256M of memory, so a lot of what works on other devices is going to have to trimmed down.
This isn't to say that it can't be done, but by the time you're done, it may not be so much better than what we've got. Anything is possible, of course, but I'm not aware of anything along the lines of CyanogenMod in the works for the NST. I'd be happy to be wrong.
In the meantime, there's no reason improved software can't be written to run on what we've got. At least rooting makes that possible.
Click to expand...
Click to collapse
Hey
Well, yes, there's the issue with drivers. Thing is, and I might be wrong at this, that a driver can be kept in newer versions and still be used. For example, in HTC Magic, the video driver hasn't been updated in *ages*, and the little device can even run ICS now. Froyo, Donut & Gingerbread both use almost the same driver versions and it hasn't had any issues so far. I'm using my own experience as base on this though.
About the memory, again experience, HTC Magic has like 512 Mb ROM and 256 Mb RAM. The NST has 256 MB RAM and 2GB ROM. I find it very possible.
Thing is, I'm not very satisfied with "what we've got". See, I bought it planning to use it as a tablet instead, since... I rarely read, lol. So far so good, I can VNC/TeamView to computers at work and my computer at home, take notes and even browse the web (well, kiiiinda...), but it's buggy as hell. I mean, the rooters we have are pretty good at what they do, but the OS itself, the way B&N built it, it's broken.
See, LatinIME doesn't work correctly or is almost impossible to use with Dolphin (or any other browser) because they also broke WebCore =/. Not to mention the colors are a bit off since it's all B&W and some texts are in the same color as the background (thanks to their Framework.res theme) so...
Taking that into account, I wanted to give a go at a ROM instead, since there isn't any ROM for this device yet, and considering we have CWM working, I find it very possible to compile a ROM and use it, or hell, at least have a pure Android OS booting.
I've made some research here:
http://elinux.org/Android_on_OMAP
http://www.omappedia.org/wiki/Android_Getting_Started#Video_Tutorials
https://docs.google.com/document/d/19f7Z1rxJHa5grNlNFSkh7hQ0LmDOuPdKMQUg8HFiyzs/edit?hl=en_US
http://wiki.cyanogenmod.com/wiki/Barnes_&_Noble_Nook_Color:_Compile_CyanogenMod_(Linux)
And I think it's very possible to build a ROM, using the first two links + the tutorial at google docs. Also, it seems that some procedures, tools or code made for the Nook Color are also able to be used for the NST, since they share almost the same exact hardware.
However, I'm confused on how to start. This is my first time building an Android ROM after some few failed attempts at an HTC Magic ROM, though the instructions seem to be waaaay easier than HTC's. Right now I'm downloading Ubuntu Server 11.10 x64 so I can set up a simple OpenBox environment and start pulling code... but it's confusing
I'm up for the challenge, and I'm trying to work on it, but I'm no genius and I feel that if there's more than one person working on this, we can take a ROM out which would be better than the stock ROM and would have better and cooler stuff, like USB Host Mode already included or the refresh rate fixed/faster. Hell, I even restored it to factory defaults and then rooted it manually and installed BusyBox 1.19.1 in it, something which isn't mentioned in any tutorial that I've found yet.
darkguy2008 said:
Hey
Well, yes, there's the issue with drivers. Thing is, and I might be wrong at this, that a driver can be kept in newer versions and still be used. For example, in HTC Magic, the video driver hasn't been updated in *ages*, and the little device can even run ICS now. Froyo, Donut & Gingerbread both use almost the same driver versions and it hasn't had any issues so far. I'm using my own experience as base on this though.
Click to expand...
Click to collapse
The issue with drivers isn't so much it being old, it's getting a driver for the E-Ink screen. It's like video cards; you can put any driver you want on any computer, but unless it's the right one, you'll be stuck at 640x480 (or in the case of Android, no display).
darkguy2008 said:
About the memory, again experience, HTC Magic has like 512 Mb ROM and 256 Mb RAM. The NST has 256 MB RAM and 2GB ROM. I find it very possible.
Click to expand...
Click to collapse
It's not ROM, it's flash storage or whatever the correct term. ROM (read-only-memory) cannot be written to, and the flash storage is just storage space.
darkguy2008 said:
See, LatinIME doesn't work correctly or is almost impossible to use with Dolphin (or any other browser) because they also broke WebCore =/. Not to mention the colors are a bit off since it's all B&W and some texts are in the same color as the background (thanks to their Framework.res theme) so...
Click to expand...
Click to collapse
WebKit could probably be fixed eventually, and fixing the framework-res.apk shouldn't be too difficult, just unpack the thing with apktool and grab notepad++ or something.
darkguy2008 said:
Taking that into account, I wanted to give a go at a ROM instead, since there isn't any ROM for this device yet, and considering we have CWM working, I find it very possible to compile a ROM and use it, or hell, at least have a pure Android OS booting.
Click to expand...
Click to collapse
If we had CWM working, would this thread exist? Yes, it's working on the Nook Color, but getting it to work on the NST would require removing so many things and so much more, and even when it does happen it'd probably be a hollow shell of what it normally is.
darkguy2008 said:
I'm up for the challenge, and I'm trying to work on it, but I'm no genius and I feel that if there's more than one person working on this, we can take a ROM out which would be better than the stock ROM and would have better and cooler stuff, like USB Host Mode already included or the refresh rate fixed/faster. Hell, I even restored it to factory defaults and then rooted it manually and installed BusyBox 1.19.1 in it, something which isn't mentioned in any tutorial that I've found yet.
Click to expand...
Click to collapse
I didn't mean to put you down by all this or flame you, so hey, good luck!
Googie2149 said:
The issue with drivers isn't so much it being old, it's getting a driver for the E-Ink screen. It's like video cards; you can put any driver you want on any computer, but unless it's the right one, you'll be stuck at 640x480 (or in the case of Android, no display).
Click to expand...
Click to collapse
Hmm, you're right. I have the idea of using Eclair's drivers included in the B&N update files (1.1.2), I dunno how to use them but if the .so file exists, there must be a way to invoke their methods, no? It's just a theory, I kinda suck at this thing of kernel drivers 'n stuff.
Googie2149 said:
It's not ROM, it's flash storage or whatever the correct term. ROM (read-only-memory) cannot be written to, and the flash storage is just storage space.
Click to expand...
Click to collapse
Oh okay, then I can't seem to find any official specs of how much RAM does the NST have =/. Pretty weird.
Googie2149 said:
WebKit could probably be fixed eventually, and fixing the framework-res.apk shouldn't be too difficult, just unpack the thing with apktool and grab notepad++ or something.
Click to expand...
Click to collapse
Yeah, I have an idea of trying to fix that APK, but I wanted something more... Android-ish xD.
Googie2149 said:
f we had CWM working, would this thread exist? Yes, it's working on the Nook Color, but getting it to work on the NST would require removing so many things and so much more, and even when it does happen it'd probably be a hollow shell of what it normally is.
Click to expand...
Click to collapse
Actually, we -have- CWM working in the NST, just look here -> http://forum.xda-developers.com/showthread.php?t=1360994 . If a recovery was made possible in NST, which means some ROM (or whatever) compiling to display and use the hardware buttons, I'm very sure it is possible to build an Android ROM the same way o.o...
Googie2149 said:
I didn't mean to put you down by all this or flame you, so hey, good luck!
Click to expand...
Click to collapse
Hehe, it's okay, didn't take it as that, so, thanks
---
On another news, I followed this tutorial: http://www.omappedia.org/wiki/Android_Getting_Started up to the "repo sync" stage. It says it should take an hour and all, but it doesn't. It takes like 5 seconds, no output, nada. I don't know what could be wrong
Any help?
darkguy2008 said:
I can't seem to find any official specs of how much RAM does the NST have =/.
Click to expand...
Click to collapse
> adb shell
$ busybox free -m
Learn to love the command line.
darkguy2008 said:
Actually, we -have- CWM working in the NST, just look here -> http://forum.xda-developers.com/showthread.php?t=1360994 . If a recovery was made possible in NST, which means some ROM (or whatever) compiling to display and use the hardware buttons, I'm very sure it is possible to build an Android ROM the same way o.o...
Click to expand...
Click to collapse
Derp, I thought you were talking about Cyanogenmod for some reason.
notriddle said:
> adb shell
$ busybox free -m
Learn to love the command line.
Click to expand...
Click to collapse
Hey, I love the command line I -have- to ... Anyways, didn't thought of that first, so thanks
According to this:
Code:
total used free shared buffers
Mem: 227 212 14 0 8
-/+ buffers: 204 23
Swap: 0 0 0
The device only has 256 Mb RAM? I find it enough up to ICS. My previous HTC Magic could run ICS quite happily even without hardware acceleration, Froyo ran as fast as the stock 1.5 ROM and Gingerbread ran pretty okay. I didn't have the chance to work on optimizing it because my Magic got stolen, but I bet it could've been made to work as fast as the stock ROM if correctly optimized. Taking that into account, I'm sure this device can withstand a greater android version .
Googie2149 said:
Derp, I thought you were talking about Cyanogenmod for some reason.
Click to expand...
Click to collapse
Lol, nah XD. It it would be cool if it worked but nah, those guys prefer the most powerful devices :/ sucks though.
Okay, according to this wiki: http://wiki.samat.org/Nook ... NST's source code is here (for 1.1):
http://images.barnesandnoble.com/PResources/download/Nook/source-code/nook2_1-1.tgz
Anybody have an idea on how to compile it though? it doesn't seem complete to me.
Look here : http://forum.xda-developers.com/showthread.php?t=1290524
mdall said:
Look here : http://forum.xda-developers.com/showthread.php?t=1290524
Click to expand...
Click to collapse
That doesn't make any sense, that's for compiling a Kernel... this source code is for a whole ROM (it seems)... it has the kernel, u-boot, x-loader and some android source.
---
EDIT:
Actually... it makes sense now (after reading the whole thread, of course)... I'll see what I can do. Thanks for the link
I think radical changes of the Android version is too much to expect.
There's not a lot of ram on the Nook.
However, I just read that one of the big differences between 2.1 and 2.2
is that big changes were made to the Dalvik VM which sped it up 2X to 5X.
I think that that would be a worthy goal.
Renate NST said:
There's not a lot of ram on the Nook.
Click to expand...
Click to collapse
We won't know if nobody tries. Besides, GB has been ported to phones with less. (HTC Magic, as he already mentioned)
However, I just read that one of the big differences between 2.1 and 2.2
is that big changes were made to the Dalvik VM which sped it up 2X to 5X.
I think that that would be a worthy goal.
Click to expand...
Click to collapse
That would be awesome for stock users, but what about those apps that break under the hackish stock ROM? (ColorNote Sync, for example) Or things like NoRefresh that could take advantage of the underlying system's knowledge.
I think working around CM sources, like someone already has posted about trying, is a good idea.
CM9 might be a bit much, but CM7 is well in the device's range.
After all, it runs a CPU like my Motorola Defy, which runs CM9 without hassle (now with HWUI). It has 512MB ram though.
Look here: http://forum.xda-developers.com/showthread.php?t=1684782
imachine said:
I think working around CM sources, like someone already has posted about trying, is a good idea.
CM9 might be a bit much, but CM7 is well in the device's range.
After all, it runs a CPU like my Motorola Defy, which runs CM9 without hassle (now with HWUI). It has 512MB ram though.
Look here: http://forum.xda-developers.com/showthread.php?t=1684782
Click to expand...
Click to collapse
This thread is over a month old, and the thread specifically about CM7 is about 3 days old. But either way, I think that the NST can handle CM. The screen refresh may make it seem slow, but it actually is a little powerful (but seeing as it was my first Android device, and my only other one is a Nook Color, it might actually be as terrible as others say).
Wtf just look at attachments omg ... samsung
adrovic.ad said:
Wtf just look at attachments omg ... samsung
Click to expand...
Click to collapse
How does this belong in Q&A? Do you have a question about it? This is common knowledge. If it annoys you, de-bloat it using the many methods out there.
kingzain900 said:
How does this belong in Q&A? Do you have a question about it? This is common knowledge. If it annoys you, de-bloat it using the many methods out there.
Click to expand...
Click to collapse
I just want to know if someone else is haveing this I guess they do .. so what is the bloatware here ...touchwiz? and how can this be fixed
thats the question , sry
adrovic.ad said:
I just want to know if someone else is haveing this I guess they do .. so what is the bloatware here ...touchwiz? and how can this be fixed
thats the question , sry
Click to expand...
Click to collapse
It's all the extra apps that Samsung has got in there, plus all the extra ringtones, wallpapers, etc.
You can do a few things (all of which require rooting the phone).
The fastest and best method (IMO) would be to install a custom ROM and remove the bloatware that way. Look at Omega ROM
Alternatively, you can do it yourself using root explorer and apps like Root App Delete.
Or use this http://forum.xda-developers.com/showthread.php?t=2468596
Use any of these methods at your own risk. The first one is the safest and easiest.
Forget it, Samsung has "reserved" a certain amount of space, approx 7gb, for the system files whether its used or not.
You can't change it in any way unless you want to play around with the partition table - pit file... This is an extremely BAD idea...
ultramag69 said:
Forget it, Samsung has "reserved" a certain amount of space, approx 7gb, for the system files whether its used or not.
You can't change it in any way unless you want to play around with the partition table - pit file... This is an extremely BAD idea...
Click to expand...
Click to collapse
He can still free up a bunch of space by removing all of the non-essential Samsung apps.
kingzain900 said:
He can still free up a bunch of space by removing all of the non-essential Samsung apps.
Click to expand...
Click to collapse
Asa long as they aren't installed as part of the system. Otherwise there's no point as you may free up system memory but you still can't utilise it...
ultramag69 said:
Asa long as they aren't installed as part of the system. Otherwise there's no point as you may free up system memory but you still can't utilise it...
Click to expand...
Click to collapse
Thats right my friend I noticed exactly that but the taskmanager that samsung provides is bloatware?
Really omg I just cant believe what they are selling
Is there any way to remove completely the whole system memory and replace it with the google stock android while also being able to update the phone normaly.
If there isnt then im just going to swap it for an iphone 5 I made arrangements.
I dont trust all the moded firmware on this forum or anywhere else so is there any genuine 100% firmware from google stock android that I could use
Thank you
You could check out the developement part of the forum for a google rom.
There is no problem with most of what's done here as long as you read and are sure to follow the steps to flash. Most problems are people, and its not just noobs, jumping ahead and stuffing things up...
(May or may not be the right place to put this)
A place to discuss and attempt to implement Android app compatibility for Sailfish OS.
Now I'm not too knowledgeable about this kind of stuff, I'll need to do more research before I'll be able to help in any meaningful way.
vgrade said:
From a community standpoint I'd much prefer an open solution.
The way the Sailfish stack is designed it leads itself more to an open solution than previous attempts. It uses the android driver libs from original /system , runs an init just as in real android. For example surface flinger would run if you enabled it from init.rc. We can run the original dalvik. So all (and I know its a significant task) that is required is some plumbing to allow switching of surface flinger output to hwcomposer instead of lipstick (the sailfish compositor) and switching touch.
I'd invite anyone interested to join us at sailfishos-porters to discuss further
BR
vgrade
Click to expand...
Click to collapse
UPDATE 1:
I have been working on this lately, and can "boot" into CM11 and get to the setup screen, but the touchscreen, power button and potentially everything else doesn't work as it's still using the sailfish drivers. The only command needed to boot into CM11 is just starting surfaceflinger via "./surfaceflinger" after navigating to /system/bin/ . I did however modify the init.rc file to turn on the android specific services. which I've linked below.
UPDATE 2: using ssh via USB connection breaks when "booting" into CM but using ssh over WiFi does not.
Modified init.rc file
UPDATE 3: Quicksilver is a chromium client for sailfish, and if you build it with NaCl enabled (its currently disabled) then ARChon MAY work. The link to the git repo is below.
quicksilver repo link
UPDATE 4: It's getting close now. Chroot-ing into the android emulator image while also using it's renderer is almost seeing the light of day and we need your help. All info found in this thread.
Some extra posts for context...
The following post is what inspired the vgrade's post (see post 1 of this thread):
kageurufu said:
and Alien is ported over (I know it wont be official, someones gonna do it anyway) this could easily be a daily driver.
Click to expand...
Click to collapse
What makes you so sure of that, AlienDalvik's a proprietary solution, it's not an easy undertaking, IcedRobot really struggled to get anywhere.
I followed it & related/similar for years, but none of them got anywhere really...*
Jolla should be offering AD as a paid add-on via the store, not expecting the community to whisk a decent alternative into reality from thin air.
---------- Post added at 02:27 PM ---------- Previous post was at 02:24 PM ----------
vgrade said:
An open dalvik would be a huge step forwards and any help people can give please drop into #sailfishos-porters IRC
Click to expand...
Click to collapse
Surely a much better "step forward" would be to offer AD as a paid for add-on via the store...
Maybe longer-term you/we can aim for an open dalvik, but there's already too much you're/we're juggling over the next ~12mth.
*google IcedRobot & IcedRobot Dalvik, but here's 3 quick/dirty links:
https://wiki.debian.org/Java/DevJam...do=get&target=icedrobot-fosdem-2011-02-05.pdf
https://github.com/icedrobot
https://twitter.com/hashtag/icedrobot
The old project site doesn't even exist any more, just some junk fitness product:
http://www.icedrobot.org/
Click to expand...
Click to collapse
The next 2 posts below came after vrgrade's response (see post 1 of this thread):
jalyst said:
@vgrade
Interesting, I thought what would be required, is something akin to icedrobot i.e. a complete (openJDK compliant) replacement of dalvik.
Are you saying that something much simpler would be possible (& hence much less work), & would still work just as well?
Sorry for the OT post, last one, perhaps a sep. thread needs to be created here...
Click to expand...
Click to collapse
vgrade said:
Yes , something much simpler.
Please feel free to start a new thread , its there a general area on xda as this would be common to all Sailfish ports, N4, N5 , N7 , Galaxy Nexus etc
vgrade
Click to expand...
Click to collapse
Nice thread. I have not much knowledge about such things here but just to say it BlackBerry OS 10 has also support for Android apps and maybe someone could get done kind of inspiration off their implementation of Android. Just a thought of mine maybe it's completely nonsense what I said but maybe not so.
http://wiki.maemo.org/Apkenv
http://talk.maemo.org/showthread.php?t=87496
Have a look in here., trying to make sense of it myself.
You'd prolly want to get folks like: Mario Torre (IcedRobot), Carstun Munk (libhybris), Thomas Perl (apkenv) involved in one way or another.
Plus some Android guys who are well respected in this community, & who know dalvik/art inside out...
aironeous said:
http://wiki.maemo.org/Apkenv
http://talk.maemo.org/showthread.php?t=87496
Click to expand...
Click to collapse
https://openrepos.net/content/lightdot/apkenv
Yeah but, apkenv is far from being a solution, we need some of the relevant parties engaging here, not end-users.
ARC - App Runtime for Chrome OS, is promising, if anyone knows how to port it over . I can't find any source files, other than ARChon. Could it be this.
nh1402 said:
ARC - App Runtime for Chrome OS, is promising, if anyone knows how to port it over . I can't find any source files, other than ARChon. Could it be this.
Click to expand...
Click to collapse
https://chromium.googlesource.com/a...410.206.0/docs/getting-started-open-source.md
A small set of shared objects can be built which are part of ARC currently.
A fully running system cannot currently be built.
Click to expand...
Click to collapse
EnErGy[CSDX] said:
https://chromium.googlesource.com/a...410.206.0/docs/getting-started-open-source.md
Click to expand...
Click to collapse
I take it Archon works as it works through Chrome, which has similar stuff to Chrome OS.
EDIT: I mean theoretically you could install all the relevant repos to install chromium and then get archon working that way.
nh1402 said:
I take it Archon works as it works through Chrome, which has similar stuff to Chrome OS.
Click to expand...
Click to collapse
Archon is just repack of ARC extensition to make it work under desktop Chrome.
nh1402 said:
EDIT: I mean theoretically you could install all the relevant repos to install chromium and then get archon working that way.
Click to expand...
Click to collapse
installing chromuim to Sailfish os is no trivial task.
I was just stating theoretically speaking. I wasn't suggesting someone should do that, I understand that its not a trivial task. I guess we should wait till they release all the necessary files then, unless they don't plan to then we're back to square one.
I thought I would try and see what happens if I pause lipstick (kill -STOP 950) , and start surfaceflinger (./system/bin/surfaceflinger), and see what happens, turns out it shows that "static-y" image like when you're booting into sailfish.but since sailfish doesn't use surfaceflinger then nothing happens it just stays with that same screen. stop surfaceflinger, and then run (kill -CONT 950), and then start interacting with the screen again, everything goes back to normal.
If I can find out the bare minimum needed to install and run an apk, it could work, but probably won't.
If someone knows what services are needed in order to either boot into android, or to get an app to run, please say so.
EDIT: I can now get to the setup screen of cyanogenmod, but that is it, touchscreen doesn't work and ssh connection breaks. But its recognised as an unauthorised device in adb.
And how about https://github.com/vladikoff/chromeos-apk/ ?
sledges said:
And how about https://github.com/vladikoff/chromeos-apk/ ?
Click to expand...
Click to collapse
That works through Chrome/Chromium.
nh1402 said:
That works through Chrome/Chromium.
Click to expand...
Click to collapse
Chrome OS is a GNU/Linux distro, so would need crosscompiling to ARM and integration effort
sledges said:
Chrome OS is a GNU/Linux distro, so would need crosscompiling to ARM and integration effort
Click to expand...
Click to collapse
Checking the source code documentation still reads "A small set of shared objects can be built which are part of ARC currently. A fully running system cannot currently be built." They could provide an update and release the shared objects at Google I/O later this year but I wouldn't hold my breath.
Is Gentroid worth looking into? https://code.google.com/p/gentroid/
aironeous said:
Is Gentroid worth looking into? https://code.google.com/p/gentroid/
Click to expand...
Click to collapse
Nice find, I would say that it is.
Now there are 3 promising Android solutions
CM (if we can get touch working)
gentroid
quicksilver (if ARChon works on Chromium)