(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)
Related
Mod Edit: As stated by forum moderator jerdog in post 814:
FORUM RULES:
"Encouraging members to participate in forum activities on other phone related sites is prohibited."
The issue here is that directing traffic elsewhere is against XDA rules, and while there is no requirement to actively support your development efforts here at XDA, saying it probably won't be supported at XDA and that they can get support on your forum is kind of low and has been removed after requesting LBS do so - to which he did not after 2 days.
Click to expand...
Click to collapse
Thread closed.
will test this one. thanks
on v1.6
update 6.20.2011
~watching youtube on app and in browser are hit or miss, you should work on it to be more compatible
~so far so good though, thanks
update 6.21
~facebook FC's
will update this when i find more problems, when i find more time
ninditsu said:
will test this one. thanks
Click to expand...
Click to collapse
cool let me know what you think so far and if you let me know what the things are you missing the most and really need besides Flash. LOL but yeah I want to make this a Honeycomb that is a well rounded Android. So i want the advice of new features and such they have heard about.
Checked out the youtube video, looks pretty sweet. Will try it out tomorrow to see the improvements with hardware acceleration etc.
Edit: Let's see some benchmark comparisons between BoS and Illuminate.
Make sure you do the following
Unzip recover.zip and move recovery folder to /sdcard folder
The recover.zip file can be found in the Roebeets thread
http://forum.xda-developers.com/showthread.php?t=1078897
Regards,
Kenny N
Humm -- I got stuck with the boot loop . I am updating from 3588 stock recovery
Regards,
Kenny N
After half an hour struggling, I am able to load your HoneyComb edition. I am going to play around with it.
To make everyone's life easier.
Make sure you nvflash your device first using the following nvflash image
http://www.mediafire.com/?g7vorg66iiq29vm
1. Download the nvflash image above.
2. Download the recover.zip from (http://forum.xda-developers.com/attachment.php?attachmentid=596319&d=1305415712 ) and extract the recovery folder to SD root
3. Download this honeycomb image and rename it to update.zip and copy it to your SD root
4. nvflash the nvflash image
5. Reboot with Power + Volumn up. This should bring you to the new bootloader
6. Flash the SDCard external update.zip
7. Wipes
9. Restart
G'd luck . Thanks linuxboxsolution for his contribution. I will comment later.
Nice -- OpenGL is working perfectly. The benchmark from Quandrant is 1780. Not great but can't really complain
linuxboxsolution said:
Last Update 6/6/2011
NOTICE: Flash still not currently Working please see
Click to expand...
Click to collapse
That's funny, I could have sworn you claimed previously to have "fixed flash" too!
Does enabling OpenGL break the stock browser? Or have you done something to work around this issue?
Is the main difference from Roebeet's HCAdam and Vegacomb mashup that is Bottle of Smoke that you have enabled opengl?
This looks very promising, currently running BoS 3.3 and was about to jump to 4.1 but I might have to try this first. My apologies if this has already been covered but what exactly is the difference between this ROM and roe's BoS? How were you able to get hw acceleration on here while BoS lacks it?
Thanks alot for your contribution, and I'll be sure to post my findings later today.
just wondering
so if the opengl is fixed, how come flashed is still hasnt fixed?
i believ robeet said the opengl is what makes flash doesn't work
OpenGL is enabled but not working.. it lacks on driver and without flash no OPENGL.. note on that..
and one more thing.. BoS has HWaccel and working, like gingerbread... the only problem is video HWaccel HD playback..
BoS 3.3 or 4.0+ boot quickly too, smooth UI like that, so i can't really tell what's the difference between the two, except for bootanimation.. LOL
I, for one, appreciate your efforts
Going to start posting in XDA's GTAB forums, at least sporadically. I think enough time has passed and things have changed around here (ie a lot of 1.2 mods are popping up, which I think is a good thing). Plus I'm not really seeing the moderator "changes" that were heavily present in April. So maybe things are back to normal. Maybe.
With that in mind, I wanted to say that your efforts are much appreciated - the end goal is to get a good working HC ROM for the users out there and if you have the ear of some people to make that happen, then that's what counts. I already mentioned in Slatedroid that I plan to pull back a bit after this month with modding the GTAB, so any extra dev / modding work is ALWAYS appreciated, imo.
Thanks again.
Looks awesome, will flash once I get my new PC built >
Thanks roe
So first of all thank you for your work.
But this is different from bottle of smoke because it enables OpenGL right?
Any other changes?
I hate to be a Richard but, can we get some screenies fam?
cgingermany said:
I hate to be a Richard but, can we get some screenies fam?
Click to expand...
Click to collapse
Not quite sure what that means, but if you want to see what it looks like, you can watch the youtube preview. It's at the bottom of the OP or here.
cgingermany said:
I hate to be a Richard but, can we get some screenies fam?
Click to expand...
Click to collapse
Rich, there is an almost 9 minute video in the first post.
I received an onlive microconsole free from PAX solely for the reason of hacking (as did about 5000 others). My primary goal is to be able to put Google TV on it as it has very similar specs to some existing set top boxes. (Nixeus fusion xs, which also has sources available)
The source code for the consoles OS can be found here
http://opensource.onlive.com/
I poked around inside the zips and certainly contains all the drivers for generic linux. The interesting thing is they included the SoCs build folder giving instructions for android.
The kicker is, I have no idea how to build an OS from source and modify it nor do I know about getting it on to the machine. I took it apart and it has a block of 12 pins, which I presume are for nand reading and writing. I've glitched /jtagged a few 360s so I am familiar with the process of nand modifications, I just have no clue how to find out which pins to use on this board. The microconsole is keyboard and mouse compatible but I have not found a way to enter a terminal or bootloader.
The easiest thing to do is look for serial ports because with a serial connection you can most of the flash fw and stuff...
would help if you'd post some specs and pics
Reversedhex said:
The easiest thing to do is look for serial ports because with a serial connection you can most of the flash fw and stuff...
would help if you'd post some specs and pics
Click to expand...
Click to collapse
any news? I'am have one microconsole and can post here photo's. I'am found 3pin area but it's not a jtag perhaps.
suddo said:
any news? I'am have one microconsole and can post here photo's. I'am found 3pin area but it's not a jtag perhaps.
Click to expand...
Click to collapse
additional pictures
Update?
suddo said:
additional pictures
Click to expand...
Click to collapse
Has any progress been made on this?
Anyone ?
Any news to microconsole "hacking"?
Are there any ways to get toolchain to build OS sources?
Especially regarding to OnLive soon closure
Toshik23 said:
Any news to microconsole "hacking"?
Are there any ways to get toolchain to build OS sources?
Especially regarding to OnLive soon closure
Click to expand...
Click to collapse
I've got a HW engr. friend working on it ... Even just to get Shell
I DL the FULL open source proj. and I'd suggest you do the same before they take it down
opensource.onlive.com
Toshik23 said:
Any news to microconsole "hacking"?
Are there any ways to get toolchain to build OS sources?
Especially regarding to OnLive soon closure
Click to expand...
Click to collapse
ahze85283 said:
I've got a HW engr. friend working on it ... Even just to get Shell
I DL the FULL open source proj. and I'd suggest you do the same before they take it down
opensource.onlive.com
Click to expand...
Click to collapse
ahze85283 said:
I've got a HW engr. friend working on it ... Even just to get Shell
I DL the FULL open source proj. and I'd suggest you do the same before they take it down
opensource.onlive.com
Click to expand...
Click to collapse
upload this sdk to googledrive pls.
Try this nixeus.com/?p=171 .
Im also quite interested in what can become of this. Hell even drivers that would make the console version of the the controller work on a pc would be something.
GitHub
not My Github but I did Run across this
https// github.com/ samdmarshall/ Onlive-Source-Backup
better than any Google Drive Link I can Give
Still waiting on a few HW Tools from China [Needed a New UART adapter amount others]
I'll Keep you Updated ...
ahze85283 said:
not My Github but I did Run across this
https// github.com/ samdmarshall/ Onlive-Source-Backup
better than any Google Drive Link I can Give
Still waiting on a few HW Tools from China [Needed a New UART adapter amount others]
I'll Keep you Updated ...
Click to expand...
Click to collapse
Anything New man i really wanna find a use for this microconsole i dont like throwing Tech away
Has any more progress been made on this? I loved the OL service in it's prime and it'd be a shame to throw the microconsole away if there's any legitimate use for it.
I'm still digging to the code to verify what I can do with it but with 3 uart adapters not arriving I'm kind of at an impasse. I'm not done yet though I even bought an extra one off of ebay for $17 as an extra hardware in case I fry 1
+1 in hoping someone manages to get some other software running on it. would love to repurpose it as a Steam/shield streaming box
fingers crossed.
not enough people interested i guess, i mean it's no more than a thin client if im correct. either way if kodi + steamos could be installed great
So interseted in OnLive
keep the good work
i am also digging into the codes and have experience in GL low-level programming and high level
would be happy to share
snowwhiteln13 said:
keep the good work
i am also digging into the codes and have experience in GL low-level programming and high level
would be happy to share
Click to expand...
Click to collapse
Sure i'd love some help ... without a uart i cant figure out the trigger for sw/fw upgrade. I think i've got a passable image for an os ... in source. I don't know formt required.
Direct message me i'll connect on hangout or something
ahze85283 said:
Sure i'd love some help ... without a uart i cant figure out the trigger for sw/fw upgrade. I think i've got a passable image for an os ... in source. I don't know formt required.
Direct message me i'll connect on hangout or something
Click to expand...
Click to collapse
i had direct message you
Me and a few friends of mine are waiting to use microconsole again. It has super gamepad. It has built in DVR button and playback buttons that has many potential to use it on pc or via micro console.
Please keep us updating.
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).
This thread is purely for discussion on the Team EOS cornerstone builds.
A couple of notes.
1) These are completely unsupported. (Hence this thread being in the discussion forum)
2) Cornerstone builds are roms - not updates to a nightly build. Saying something like "I'm running Cornerstone wingray #17 with wingray nightly #90" is pointless. You only need to install cornerstone and then the google applications.
3) Always state what device and build # you're using - this thread is for 4 different types of Xoom on potentially different build numbers - AVOID CONFUSION. Not everyone knows what device you have.
4) You're welcome to say your experiences about the rom here including issues, however do not be insulted if I never reply to issues or bug reports. Remember these builds are unsupported.
5) Builds can be attained from http://goo.im/devs/teameos/roms/cornerstone
6) Please don't file bug reports for cornerstone.
7) If you're using cornerstone, please don't post in the official nightly build threads about your issues. This only confuses people.
Well stated sir.
I know they removed the switch between windows option because of a problem with Google. Would it be possible to go into their code and bring that feature back or to add it somehow?
double1 said:
I know they removed the switch between windows option because of a problem with Google. Would it be possible to go into their code and bring that feature back or to add it back?
Click to expand...
Click to collapse
Its very possible to add the code back. But keep in mind, it was likely taken out for good reason. They wouldn't take it out simply to upset users; at least I like to hope not.
Something to do with Diane Hackborn https://m.google.com/app/plus/mp/479/#~loop:aid=z13izns4pyiyj1opf04cc3owexetubjgzko0k&view=activity
If you could add that functionality back,..pretty please..
I'm still puzzled.
I'm from the Middle East using the Build H.6.1-38-9 for Retail Other International.
Which one from the link supplied should I use to retain my 3G connection?
And just to be sure, these are ICS builds, right?
Pretty thanks for the fantastic work!
Err didnt you guys build it into a rom tho? Or your source? Im confused....
Any anyone of your team using cornerstone or going to keep these updated?
Cheers
Sent from my mind control device
joshndroid said:
Err didnt you guys build it into a rom tho? Or your source? Im confused....
Any anyone of your team using cornerstone or going to keep these updated?
Cheers
Sent from my mind control device
Click to expand...
Click to collapse
I bring all the latest changes from our normal builds into the cornerstone builds.
I also keep cornerstone up to date.
Nothing has changed, I just would rather keep the normal build thread seperate from the cornerstone builds.
solarnz said:
I bring all the latest changes from our normal builds into the cornerstone builds.
I also keep cornerstone up to date.
Nothing has changed, I just would rather keep the normal build thread seperate from the cornerstone builds.
Click to expand...
Click to collapse
Cheers mate appreciate the hard work!
Sent from my Xoom using Tapatalk
solarnz said:
I bring all the latest changes from our normal builds into the cornerstone builds.
I also keep cornerstone up to date.
Nothing has changed, I just would rather keep the normal build thread seperate from the cornerstone builds.
Click to expand...
Click to collapse
Yes, I agree with above....cheers for working on this awesome project
Most important updates I feel are;
1) stock browser works awesome in small pane EXCEPT many times when typing right into URL bar then pressing enter it opens up A SEPARATE stock browser app in the main pane....def a glitch
2) Google talk does not show bottom inch or two of conversations
(^I think these are important because they're Google apps)
3) maybe get a COUPLE game apps working? Practical ones like cananbalt?
4) getting normal desktop layout back after closing cornerstone. It stays squished in
5) implementation of switching panes. The usefulness and functionality of this rom will never be realized without being able to bring things from background to foreground
6) folders/dock inside the little panes'app drawers
7) im having immense wallpaper problems if i try to set any that aren't the default "wallpapers"
Sent from my Xoom using XDA
This is unsupported... So you kinda have to state these problems mainly to dev of cornerstone... If there are problems directly related to a xoom build and you can differentiate the two you may be able to post in correct build thread however this may not be necessary as others usually have mentioned most problems already... So really this thread can be used for tips etc or sharing of problems between us but cornerstone side problems wont be fixed by eos team.. Hence the tag unsupported thats my understanding of it now
Sent from my mind control device
joshndroid said:
This is unsupported... So you kinda have to state these problems mainly to dev of cornerstone... If there are problems directly related to a xoom build and you can differentiate the two you may be able to post in correct build thread however this may not be necessary as others usually have mentioned most problems already... So really this thread can be used for tips etc or sharing of problems between us but cornerstone side problems wont be fixed by eos team.. Hence the tag unsupported thats my understanding of it now
Sent from my mind control device
Click to expand...
Click to collapse
Where do you think is then most appropriate to post technical issues/concerns? Isn't there a developer working to make a wingray/stingray cornerstone rom that's pretty regular now?
Sent from my Xoom using XDA
Damn.....was running stable for a day but now clock/wifi/battery indicator keeps freezing within 15 min of boot...
Sent from my Xoom using XDA
Dyelon said:
Yes, I agree with above....cheers for working on this awesome project
Most important updates I feel are;
Click to expand...
Click to collapse
Really? I thought the first post was pretty darn clear...
solarnz said:
1) These are completely unsupported. (Hence this thread being in the discussion forum)
4) You're welcome to say your experiences about the rom here including issues, however do not be insulted if I never reply to issues or bug reports. Remember these builds are unsupported.
6) Please don't file bug reports for cornerstone.
Click to expand...
Click to collapse
joshndroid said:
So you kinda have to state these problems mainly to dev of cornerstone... If there are problems directly related to a xoom build and you can differentiate the two you may be able to post in correct build thread however this may not be necessary as others usually have mentioned most problems already... So really this thread can be used for tips etc or sharing of problems between us but cornerstone side problems wont be fixed by eos team.. Hence the tag unsupported thats my understanding of it now
Sent from my mind control device
Click to expand...
Click to collapse
Well said...
bigrushdog said:
Its very possible to add the code back. But keep in mind, it was likely taken out for good reason. They wouldn't take it out simply to upset users; at least I like to hope not.
Click to expand...
Click to collapse
It is my understanding that it was removed because most applications are not written to Android standards that allow them to be dynamically resized as is required for swapping windows. The CornerStone Devs recognized that in order for this feature to work correctly the app designers would have to rewrite their code, and that won't likely happen. Leaving the feature in would result in Cornerstone being unstable when used with these apps.
Personally, I would like to see it added back even if it means I could only use the feature with selected apps.
Edit: this is supposedly true with resizing the main app when the side windows are collapsed or expanded and may result in changes to cornerstone to eliminate this feature. I think that would be a mistake.
otis_bartleh said:
Really? I thought the first post was pretty darn clear...
Well said...
Click to expand...
Click to collapse
Feel better?
Jesus this thread was created with intent to squander all the comments about the build to this unsupported rom, and then when I talk about it, I get mocked anyway...
This site can be really elitist and snarky oftentimes....its counter productive because not everyone who has interest and motivation to play with your toys will have the same acumen (im in pharmacy school and only delve into Modding for pure enjoyment)....I understand the build is not supported, im just venting about my feelings as there seems to be no relevant place to do so (not allowed on wingray forum, and the cornerstone rom board was moved to general and possibly into worthlessness
Seriously, its so taxing to interact with this site as a layman sometimes
Sent from my Xoom using XDA
REHolt218 said:
It is my understanding that it was removed because most applications are not written to Android standards that allow them to be dynamically resized as is required for swapping windows. The CornerStone Devs recognized that in order for this feature to work correctly the app designers would have to rewrite their code, and that won't likely happen. Leaving the feature in would result in Cornerstone being unstable when used with these apps.
Personally, I would like to see it added back even if it means I could only use the feature with selected apps.
Edit: this is supposedly true with resizing the main app when the side windows are collapsed or expanded and may result in changes to cornerstone to eliminate this feature. I think that would be a mistake.
Click to expand...
Click to collapse
I agree....even if switching could only be done by explicitly choosing ones you know work or only ones allowed by rom it'd be better than nothing....
What do you mean about main pane resizing? That it causes problems and may be taken out?
Sent from my Xoom using XDA
Dyelon said:
What do you mean about main pane resizing? That it causes problems and may be taken out?
Click to expand...
Click to collapse
That is what I read. Some apps have problems with the main panel resizing. The alternative would be to have the two side panels "overlap" the main panel when they are extended instead of resizing. Not sure how serious it is, but I would be very disappointed.
With the applications that I run I am having very few problems with CornerStone on Stingray. The biggest one I am not sure if it is an EOS Stingray problem or if it is induced by Cornerstone. Whenever I reboot I have problems with both wifi and 3g/4g locking up. I sometimes have to boot 3 or 4 times to get it working. Since I rarely reboot it doesn't cause me much grief, especially since once I get it working I have no further problems until I reboot again.
Dyelon said:
...
Click to expand...
Click to collapse
Whatever man, calm down. I wasn't mocking you, and I am far from elitist. But the worst problem on any forums IMO is lack of reading prior posts. Maybe I'm wrong, but I thought this thread was here for discussion as the first sentence of the thread says, not suggestions. ... deleted my own comments due to pointlessness ... All here enjoy this Cornerstone rom and Team Eos, so, lets just get back to it....
Back to your regularly scheduled program...
I've been having a bunch of issues keeping Cornerstone stable, but haven't done a clean install in a while, so am updating to the latest Cornerstone nightly and will go from there. Thanks to Solarnz for starting this thread!
otis_bartleh said:
Whatever man, calm down. I wasn't mocking you, and I am far from elitist. But the worst problem on any forums IMO is lack of reading prior posts. Maybe I'm wrong, but I thought this thread was here for discussion as the first sentence of the thread says, not suggestions. ... deleted my own comments due to pointlessness ... All here enjoy this Cornerstone rom and Team Eos, so, lets just get back to it....
Back to your regularly scheduled program...
I've been having a bunch of issues keeping Cornerstone stable, but haven't done a clean install in a while, so am updating to the latest Cornerstone nightly and will go from there. Thanks to Solarnz for starting this thread!
Click to expand...
Click to collapse
Try a full full wipe... Factory reset wipe cache n dalvik format system and only restore user apps without data if you can... I have had little to no real dramas doing it this way... I also set my home screen up on first boot so the alignment of apps are all good in the main window... Then i set cornerstone to not start on boot.. I just put the cornerstone app on home screen n launch when required.. I also set cpu to 1.5Ghz.. Try these steps and see how u go
Sent from my mind control device
We know there are work in progress to port CM 12 on T810 and T710 but none for T815 and T715
So those like me with T815 or T715 or ... that are looking for CM for their device can post their request in CyanogenMod Forum request page
http://forum.cyanogenmod.org/topic/116361-samsung-galaxy-tab-s2/
Yes; even without phone fuctions is ok for start. I see note 4 exynos got decent cm13 now; I hope no impossible to give it for tab s2 lte. Would be great
Hey, I'm new to this, but I want to give it a shot to try a port for the T715.
I think it should be no problem to make a build without modem support.
So my plan would be to use the source of the T710, if @CTXz allows me to use his sources.
Next I want to try to integrate the modem/ RIL sources, but don't expect too much! I'm completely new to android development and this will be my first project doing myself.
Just did some compilings and ports, but never to new unsupported devices. Maybe with some help it will be possible for me.
Greets, Phil!
Philippovitsch said:
Hey, I'm new to this, but I want to give it a shot to try a port for the T715.
I think it should be no problem to make a build without modem support.
So my plan would be to use the source of the T710, if @CTXz allows me to use his sources.
Next I want to try to integrate the modem/ RIL sources, but don't expect too much! I'm completely new to android development and this will be my first project doing myself.
Just did some compilings and ports, but never to new unsupported devices. Maybe with some help it will be possible for me.
Greets, Phil!
Click to expand...
Click to collapse
Hey, you really don't need to ask to use my sources A mention at the finished ROM would be all I need . However, if you plan to support it, I recommend joining my git group
CTXz said:
Hey, you really don't need to ask to use my sources A mention at the finished ROM would be all I need . However, if you plan to support it, I recommend joining my git group
Click to expand...
Click to collapse
Hey, ok great, thank you!
So let's try it!
A question:
What does one gain and lose by going from stock Samsung to CM12/13?
Thanks!
optionalmgrr.la said:
A question:
What does one gain and lose by going from stock Samsung to CM12/13?
Thanks!
Click to expand...
Click to collapse
That is a very tuff question to answer in just one post and depends on particular preferences. My advise is to Google: Cyanogenmod and TouchWiz.
Sent from my SM-T810 using Tapatalk
danyvw said:
That is a very tuff question to answer in just one post and depends on particular preferences. My advise is to Google: Cyanogenmod and TouchWiz.
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
It seems the main issue is battery and camera (quality).
i think i messed my t817v. i rooted using odin, and cannot figure out what to do next. it tries to install but gives error message, also my tab wont charge, and when hooked into odin it keeps "adding then removed" over and over again... now i have a tablet that does not work.
any help on this would be awesome.
@CTXz
Philippovitsch said:
Hey, I'm new to this, but I want to give it a shot to try a port for the T715.
I think it should be no problem to make a build without modem support.
So my plan would be to use the source of the T710, if @CTXz allows me to use his sources.
Next I want to try to integrate the modem/ RIL sources, but don't expect too much! I'm completely new to android development and this will be my first project doing myself.
Just did some compilings and ports, but never to new unsupported devices. Maybe with some help it will be possible for me.
Greets, Phil!
Click to expand...
Click to collapse
I would love that!
I also posted a device request at the CyanogenMod Forum.
What you always lose with CM is Bluetooth aptX support for higher quality Bluetooth audio, since they have no licence. And since now there is official MM for the S2 and it - with enough free storage and 3 GM of RAM and root available - really doesn't profit any more from a "slim" ROM than earlier devices did, can anybody point me to a real advantage of CM?
For me CM was never about storage, but about control. As far as possible (for I am no programmer) I want to decide about the rights apps have and don't. It starts with being able to delete them and goes on with being able to restrict their access rights. As far as I remember such privacy guard things are much more easier to accomplish with CM.
Pegaside said:
For me CM was never about storage, but about control. As far as possible (for I am no programmer) I want to decide about the rights apps have and don't. It starts with being able to delete them and goes on with being able to restrict their access rights. As far as I remember such privacy guard things are much more easier to accomplish with CM.
Click to expand...
Click to collapse
But stock MM offers these permission settings now, so what else?
saintsimon said:
But stock MM offers these permission settings now, so what else?
Click to expand...
Click to collapse
My TAB s2 is my first Samsung device.... ( other android devices being nexus 7, xperia z2 / z3, moto g 4G ) ...... I love the tablet but I must say the draw of a supported CM ROM would be the look / feel of stock android and the way the system behaves. Whilst with a rooted device you can remove bloatware, the system itself does not change. All of my other devices have been stock or only lightly skinned....and basically stock once you swap out the launcher.... so I have come to like that. I do find touchwiz to be a little in my face and I do notice the system intrusions a little...... a personal thing of course and I am not complaining as I made the decision to buy it knowing full well what Touchwiz was... but the hardware in the tablet and the price was the draw-card (got the WiFi version here in Aus the first month on sale for $540 ... in comparison, the Nexus 9 was circa $700 and the Ipad Air 2 64gb was $730). My nexus 7 2013 runs MM with less and smoother than the TAB s2 runs LP. I could only imagine what it could do with an ASOP ROM once the bugs were fixed.
Could it be due to a defect usb-port?
optionalmgrr.la said:
A question:
What does one gain and lose by going from stock Samsung to CM12/13?
Thanks!
Click to expand...
Click to collapse
Do u know the difference between WIndows Phone/iPhone and Android, that's the kind of comparison u can use between Stock and CM.
Stock is the cute "little" thing with mostly everything that u may need ready to go.
CM is the smaller in size, much faster and with options to do almost anything u could think in a device.
aaronadams74 said:
i think i messed my t817v. i rooted using odin, and cannot figure out what to do next. it tries to install but gives error message, also my tab wont charge, and when hooked into odin it keeps "adding then removed" over and over again... now i have a tablet that does not work.
any help on this would be awesome.
Click to expand...
Click to collapse
Was this ever fixed?
Why does the SM-T815 run in 32bit mode, even under CM13?