Ok guys, alot of you have been making various requests on my Galaxy S threads, and I have a huge fork in the road I need to navigate. I have two theme routes to take, and if I take one, then the other must be abandoned without looking back, because there is just so much work involved in either one. I honestly wouldn't mind having someone help me with this, taking the other fork where I take the winning one from this poll. I have all the files you need & instructions, etc. I have a very well organized set up when it comes to these themes, and will make the work process as simple as possible
Ok, the two options I am facing revolve around a very minor difference, but impacts two completely different user bases.
First choice, is to make my current themes international, meaning they will have support for azerty, greek, and other languages.
Second choice, is to modify all the current themes I have to work with the voice input version of Swype (2.2.42.xxxxx). I will continue to fulfill requests as best as I can while maintaining a wide variety of usable, manageable, interchangeable (with Swype trail line colors) themes.
I'm not sure what you think, but my vote is on the Second option, mainly because Swype capability coupled with voice input is the perfect keyboard IMHO, but I am asking this because I DO have so much following wanting both, but I can only do one... I am just one guy
I am allowing 5 days for this poll, and the answer at the end of it will determine what I work on. So, let the voting begin!
I vote for the second as well. I think that it'd be a more efficient method. The first choice would still be on the table but that can be something in the future.
I vote second one also.
Sent from my SGH-T959 using XDA App
I also vote for the second!
Sent from Monnie's Vibrant.. oops, force close.
i can see which ones of you voted for what in the poll... that's what it's there for.
lets leave the thread clear of vote choices so a discussion can be had. this might also be a good place for me to find a partner or a few to help me build a huge Swype theme library, and hopefully in the future, implement it in some sort of convenient Android app-type library that we can distribute to the millions and millions and millions of Android users around the world, and possibly make a few bucks while we're at it.
I have been doing this for quite some time in relation to how long Swype has been available for Android users. Once I have established a solid base for Android, I expect to make a leap into other OS versions of the software, and even further extend my reach. I don't see why the most commonly used software on ANY phone shouldn't have the option to use a touch of some of mine or someone else's style with just the click of a button.
edit: unrelated, but I just noticed, I joined the XDA forums within a few days of the Swype official beta's release date for Android... Scary. My initial experiences with XDA were totally ROM and G1 functionality related, but around my 25th post, I started tinkering with Swype. Fate, anyone?
Hello wonderful comminuty,
The long and the veiny of it is, I want to upgrade the (full) ubuntu I have running and I can't. I realize that this would most likely break things like aiw, and the top notification bar. I don't care about the top bar, but would want to keep aiw for obvious reasons. I've gotten much better at working with linux over the last few months, but I'm still quite nib, so please don't hate on me for dreaming if this is impossible. I've looked all over the place and haven't seen anyone talking about it, so maybe it's just too much. Here's my questions anyway:
1) Would upgrading ubuntu make anything better, or even be worth the effort it will take?
2) Is there any possible way to upgrade the ubuntu version used on the dock? (Automatic update obviously doesn't work. I've read a lot about manually upgrading with CD's and such and can't find a place to stick a CD in my phone. Also, couldn't seem to find a way to mount an image like a disk, or a way that worked rather.)
Thanks in advance for anyone who can help, even with the differences in versions of ubuntu and what upgrading would change.
I haven't tried it myself but i've run over the links a few times. If you're on 4.1.52/26 then heres the link: http://forum.xda-developers.com/showthread.php?t=1000316
If thats too complicated, here's the EASY guide to it with a video showing it off: http://androlinux.com/android-ubuntu-development/how-to-install-ubuntu-on-android/
Thanks for the reply and the information, but not quite what I was looking for. I've already used Sogarth's webtop2sd and have full ubuntu running. I guess I should have been clearer. What I meant was that after gaining full access to ubuntu, and fixing apt-get, and installing a bunch of programs, I sit here thinking, hmmm what's next. So since this version of ubuntu is like 9.04 or something, we're using old repos and outdated software. I want to turn it into like ubuntu 10.04+
Anyone can help with that?
You'll need a lot of time/energy, but...
should be possible to do it. I was thinking of doing this myself, but am not sure I can make the time (18+ hr work days ) Motorola recently open sourced the web top code. Take a look at http://sourceforge.net/projects/motorola-webtop.motorola/files/WT-1.2.0-X/WT-1.2.0-110+WT-1.2.0-135/
The instructions are already outdated at the site - the rootstock command in the readme no longer builds rootfs since the jaunty repository is no longer available. I tried to build the natty rootfs but that has a couple of problems (which can be resolved - I ran out of time this weekend )
I will keep at it as time permits (might take ages, since time is tight right now). Let me know if you want to take the plunge and successfully build this (or if you need help).
Cheers
It is not easy to do because Moto has a bunch of hacked up stuff in /osh
You could try the approach here: http://forum.xda-developers.com/showthread.php?t=1093790
What this does is bring up the standard webtop, but then runs applications in a chrooted environment with a standard dist. I am not ceratain how "clean" it is because you have a bit of both environments running.
The ideal solution is to port the Moto changes (those that one cares about) into the newer distro, but that is more work.
EDIT: missed acerbix's post. I agree
Thanks for the information guys.
I did stray from the path today, and thought "hey, why not just run the debian chroot stuff INSIDE my full ubuntu, and then I'd basically have a window with an upgradeable distro..." Well, needless to say, I did get it to work, the only problem being that I couldn't run a GUI since my display was in use already by the first instance of xserver. I'm sure there's a way around that as well, and I'll surely keep looking into it.
That's not what I REALLY wanted though anyway... I'm going to look through those source code files and see if I can figure this all out. Since we can move the whole webtop environment to the sdcard now (thanks Sogarth), my idea of a perfect end result would be a completely independant distro with just aiw functional. That top bar is pretty useless and wastes my screen space...
Any help is always appreciated, I'll let you guys know if I come up with something.
>>>> 22Jan2012: linboothkvc v1.0 source released in my linboothkvc thread. It works successfully on Omap3 and Omap4 based devices including NookTab. And with minimal changes/love can work with any rooted arm based linux device <<<<
>>>> 17Jan2012: Kernel module SUCCEEDS on NookTab to reboot into NIRVANA - NO NEED to BREAK the default SECURE BOOT CHAIN and NOTE THAT EVEN THIS CAN WORK ON ANY ROOTED DEVICE and not just NT, with minimal love so ENJOY <<<<
>>>> 16Jan2012: My kernel module based path (linboothkvc) to running custom kernels and roms is almost done, except for a __small part__ to get it running on NT now - IF ONLY PEOPLE HAD WAITED ...., we could have reaped the potential benefit in future, Why not !!!! why not ....WHY NOT !?!?. NOTE that it can allow one to run custom kernel/roms WITH OUT MODIFYING ANY CRITICAL PARTITIONS provided one sets it up properly/appropriately. Source for beta version available in my linboothkvc thread, for the interested developers/experimenters for now ... <<<<
>>>> I may not respond to the posts on this thread currently, because I am trying to get a alternate option called linboothkvc using kernel modules up and running (which will occupy my free time), which AVOIDS the NEED for this flaw in the first place for most of the people out there (i.e Custom ROMS with different kernels). However over the weekends, I will go thro all the posts on this thread <<<<
>>>> 14Jan2012: Initial pre-alpha version of kernel module path based source code uploaded to my linboothkvc thread for those still interested to experiment
http://forum.xda-developers.com/showthread.php?t=1427610
<<<<
Hi All,
If you have been following my posts over the last few days
NOTE: To people frustrated with UART requirement - I understand the restrictions of UART access, but a lot of ROMS can be done with 2ndihkvc or equivalent methods and with out needing a Custom kernel. If someone is talking about Custom/New kernel for Android 4.0 (ICS). Then do note my statement (in NOP BYPASS thread) on POWER of KERNEL MODULES in Linux, IT CAN BE USED TO ACHIEVE what you want to achieve, only that it requires bit more effort, which I or some one else has not put currently... thats all. AND THAT By holding off now, we can _potentially_(Risk is always there) reap the benifit with next years NEXT GEN Nook Tab+ or what ever they call it.
a) I have implemented 2ndihkvc, which follows the same fundamental concept as 2nd-init, but achieves it in a simpler way (Needed because some of the calls used in original 2nd-init doesn't work on NookTab, or have unnecessary dependencies (in this given context, otherwise they are good in them selves) which can be avoided with my simpler method)
b) I have provided the NOP Bypass method of running a modified Ramdisk and also 90% a modified kernel, provided UART access is there.
c) There is still the power of linux KERNEL MODULES to EXPLOIT. (Haven't had time on that yet).
If you ask me, this should cover all category of people. Be it people who want to run custom Roms, or people who want to experiment with Kernel and or other low level stuff for the fun of it.
There is a 4th method which will allow one to achieve (b) above with out requiring UART access or even uSD (potentially . If one reads between the lines from all my posts till date, the answer is hidden in there. Only that I haven't spelt it out directly or in the face. The reason is because It is a fundament flaw (rather there are potentially two at two different levels - one relatively simple and one relatively bit more involved - One I know for sure, another I have to dig bit more) in the way things are done currently in the secure boot chain on this device as well as potentially other devices with same or similar SOC (and or different SOC but with similar boot chain s/w components.
SHOULD WE BE WASTING i.e providing a solution which uses it, when there is already 2ndihkvc and NOP Bypass over UART and also the Linux KERNLE MODULE ROUTE to cater to most peoples needs.
Because if we do, then even the Device manufacturers and their partners will come to know about it and can easily fix it in their Newer/NextGen devices. While if we withhold it for now, we may be able to get access to it on their Next generation Devices with hopefully Arm A15 core or .... (NOTE: Depending on the boot sequence ROOT access may or may not be required for this).
The reason I am asking now is because, few people are asking my help on certain things and the reality is I know that the concept for which they want my inputs/guidance, can be applied at a more fundamental level here (or even at the same level), but that I have not ventured into it because of my delimma above.
NOTE: People who wanted my inputs/guidance wrt uSD, you all know who you are, I know the flaw to achieve what you want to achieve, but it is more powerful than what you all are currently thinking of doing/ ristricting yourselves to (You all have one input/... in there wrt devices . Unless let me think thro further and see if something can be done differently, with out exposing the flaw I have in mind to help you achieve what you want, otherwise i.e if there is nothing else I can come up with, and in turn if you people experiment further and are able to come up with the solution on your own, I would suggest that hold off on it for few days, think thro all the implications keeping what I have mentioned in this thread, and then take a call one way or the other.
Please provide your thoughts on this after thinking thro the options already available on NookTab (root access, kernel modules, UART UBoot access and inturn 2ndihkvc and NOP Bypass or equivalents)
Based on all the feedbacks as well as bit more thinking from my side, I will take a call on this.
Forum moderators I know this is the development portion of the forum, but I wanted feedback from Developers also that is the reason why I have posted here. But beyond that I leave it to you, whether you want this to continue here or move it out.
UART access is not sufficient, as it is required during every reboot of the device if we wanted to have a custom kernel and ROM. This is simply an unacceptable state of affairs. (Say, my tablet turns off while on holiday, or at the airport. What then am I to do? Let is sit and wait off until I can get back home to my UART equipment in order to reboot?
The idea that the UART work around is sufficient is a nice one, however it is wrong.
---
Oh also, it's just a matter of time before they patch the u-boot in the Nook Tablet anyways... so it's not like this UART method is going to stick around forever anyways.
cfoesch said:
UART access is not sufficient, as it is required during every reboot of the device if we wanted to have a custom kernel and ROM. This is simply an unacceptable state of affairs. (Say, my tablet turns off while on holiday, or at the airport. What then am I to do? Let is sit and wait off until I can get back home to my UART equipment in order to reboot?
The idea that the UART work around is sufficient is a nice one, however it is wrong.
---
Oh also, it's just a matter of time before they patch the u-boot in the Nook Tablet anyways... so it's not like this UART method is going to stick around forever anyways.
Click to expand...
Click to collapse
Hi
I understand the restrictions of UART access, but a lot of ROMS can be done with 2ndihkvc or equivalent methods and with out needing a Custom kernel. If someone is talking about Custom/New kernel for Android 4.0 (ICS). Then note my statement (in NOP BYPASS thread) on POWER of KERNEL MODULES in Linux, IT CAN BE USED TO ACHIEVE what you want to achieve, only that it requires bit more effort, which I or some one else has not put currently... thats all.
By holding off now, we can potentially reap the benifit with next years Nook Tab+ or what ever they call it.
Im not a Developer but I've got a few questions. NOP requires to open up your device, so I think probably 95% won't open their device for ICS and I think since the device had a dual core CPU we should get ICS roms. Now my actual question how does your 2init work or how do you install it on our device? But great work so far keep on.
Sent from my SGH-T989
Just out the flaw now. Someone else might reveal it and you won't get the credit.
Don't you want a Wikipedia entry saying that you found this flaw? lol.
PM me about the flaw, I'll see if we should have it outed yet or not (sorry guys, but if it's a decent exploitable flaw and we have other methods, I'm pretty sure I'm with hkvc on it.)
xdahgary said:
Just out the flaw now. Someone else might reveal it and you won't get the credit.
Don't you want a Wikipedia entry saying that you found this flaw? lol.
Click to expand...
Click to collapse
Not worried for 2 reasons,
a) It doesn't bother if my name comes or not. I am exploring just for the fun of exploring.
AND MORE IMPORTANTLY,
b) Actually I have already revealed the flaw in my NOP Bypass thread, indirectly, if only, one reads carefully all my lines as well as between them. Only that I have just replaced one or two of the steps with a different steps thats all for now.
If someone else find the same flaw, he will realise the same, if he reads my posts once again with his new knowledge.
What an awesome idea, we can have a root for the Nook Tablet+ or whatever else in a years time!
...
So, um... what do I do now with my Nook Tablet? It's a piece of garbage now, I guess, so, I'll just return it since it's still within the Holiday return period? I suppose I'll just have to wait for the Nook Tablet+ to have a custom ROM running on my Nook... ("But you can UART hack it!" ... *sigh* I've already explain that that is not sufficient. The UART hack is a stop gap, and should only be stopped at if that is the absolute only option available.)
And I mean no disrespect to xIndirect, but why should he be the lone gatekeeper of what exploits and hacks are out there for the Nook Tablet? I would rather see this exploit before making a decision as well, but I don't think it fair that someone should have privileged access to the exploit. Either release it to everyone or DON'T SAY ANYTHING IN THE FIRST PLACE.
cfoesch, I have no plans to be using the exploit shown for myself. I am not going to be the "lone gatekeeper" I just want to know what it is before I give my full opinion. Chill.
Motorola Defy was locked bootloader too, may be to try and run port Defy bootmenu for Nook Tablet?
source: github.com/CyanogenDefy/android_external_bootmenu
Indirect said:
cfoesch, I have no plans to be using the exploit shown for myself. I am not going to be the "lone gatekeeper" I just want to know what it is before I give my full opinion. Chill.
Click to expand...
Click to collapse
If you buy a plot of land and the seller has accidentally left seeds there and isn't coming back for them, do you grow a garden on your current plot of land, or do you decide not to plant them and hope that the next time you buy a plot of land they might forget some seeds again?
I would rather tend the garden I own than hope for a better plot of land with seeds I may never have.
Cheers!
-M
XDA member since 2007
Sorry if my post is offtopic, I just want to help with development.
My SE Xperia x10 came worh a locked bootloader and devs figured out how to make a bootable recovery (xrecovery) based on CWM, may be with an adaptation for the NT we can get the world of custom roms, even with locked bootloader this crappy phone got cuatom kernels by bypassing the bootloader, hope this give little ligth to you guys the real Developers.
If this post is garbage mods please delate it.
Sent from my BNTV250 using xda premium
Hello, I beleive if there is a software way to get ICS + maybe overclocking it should be tried first as this IS what most people are waiting for. That's the big dream they got. If someone knows how to implement that, then please by all means do so ..
P.S. you said so much where to look for the flaw in your posts that if I was a programmer from B&N I'd know where to look like everybody else. Assuming they are not complete morons they can already figure it out too. Can they plug the hole or not? Is it oversight or permanent design flaw ? We'll see. Best way to keep a secret is to " keep it secret " , ie not talk about it at all. Especially if soft mod ICS, hw acceleration and overclocking already available.
Sent from my LG-P500 using Much Love
First of all hkvc +1 for your efforts.
I voted yes, the NT developers can read between the lines in your posts as well.
Whats life without risks once in a while
Hi All,
I understand very well that even BN devs will be looking and potentially can figure out and fix it. That is the risk, but at one level I don't mind taking the risk and see if it works out to my/our advantage (i.e the bug being still open in a new device (From BN or any other Vendor)) or disadvantage(the bug is either way fixed).
Also the flaw can affect ANY DEVICE (Not just NOOK TAB) using similar secure boot chain not just NookTab, that is also one reason why I am bit wary of releasing the info or a implementation which uses it just like that.
I will share my finding with few people on the forum/outside in few days time so that even If I loose interest in this, there will be few people with the required knowledge (i.e if they haven't already figured out on their own by then (and released something or not ...)).
Also I haven't taken a final call on this yet. I am in a delima, so getting all your opinions also before I decide.
Time permitting I will also attack/explore the KERNEL MODULE PATH in a few days time, so that people don't have to depend on this flaw in the first place, but use the wonderful world of Linux Kernel Modules to achieve what they want.
LexS007 said:
Motorola Defy was locked bootloader too, may be to try and run port Defy bootmenu for Nook Tablet?
source: github.com/CyanogenDefy/android_external_bootmenu
Click to expand...
Click to collapse
Hi,
With my modified 2nd-init (2ndihkvc), you can run bootmenu or any other user space mechanisms already on NookTab
absolutely YES, we r all xdaers, right hehehe. Thanks all devs especially hkvc for the efforts
hkvc said:
Hi,
With my modified 2nd-init (2ndihkvc), you can run bootmenu or any other user space mechanisms already on NookTab
Click to expand...
Click to collapse
It's very good. Thanks!!!
First off, not a dev but read religiously.
2nd, release it if the people who would take advantage of it agree. The rest of us say "great,woohoo!" But I must admit, I can't take advantage of it. But I certainly don't want to make a hardware uart to boot custom roms.
That being said, if its more complicated to install with a different method, that's fine. As long as it doesn't include a soldering iron.
But if it were easier to make a custom rom, or open up more capabilities of the kernal or whathaveyou, well that would attract more developers to make roms, etc. and so on and so forth.
Btw. Yes, exploit may exist if outedin a later tablet, but you found this one.... I have faith the next flaw will be found in the next one too.
A bird in the hand is worth two in the bush.
Posted from my B&N Nook Tablet... rooted of course!
jotekman said:
A bird in the hand is worth two in the bush.
Click to expand...
Click to collapse
I would say this summarizes everything I want to say on the topic.
Hi.
I've been a lurker on XDA for a while. This weekend I ordered a Galaxy Note to replace my Atrix 2, and I started going through the process of combing through the posts here to figure out how to root, flash roms, what roms to flash, etc. In the process I started learning a bunch of new terms that I'd never encountered before (ODIN specifically, but also "Fast Dormancy," APN, a few others). There's a lot of information here and it's a little dizzying.
Which brings me to the setup for my question(s). I am a technical writer, and have been for 19 years. I'm a pretty good one, and I have a knack for putting together pretty solid documentation. I thought it might be useful if I took a lot of these documents and put them together into an actual document, sort of an unofficial Galaxy Note manual for the i717, and turned it into a PDF that someone could download and use as a reference.
My questions are:
1. Is there any actual need or desire from the community for this? I figure a lot of you are probably more used to crawling through the forums for information than I am, so perhaps this is something that wouldn't provide much benefit.
2. Is there any legal concern for it? This is a little trickier. Essentially I'd be providing documentation that included how to root a phone, and as far as I know there's no reason it would be illegal (just, you know, warranty-voiding). I'm a little fuzzier on documenting ODIN, since it's apparently Samsung-provided software...
3. If I created this, where should I put it? I'd be tempted just to link to my own site, but I notice the common thing to do here is to post it on a cloud/file hosting account. Is there a specific reason I shouldn't put it up on my site, other than the bandwidth hit if it turned out to be ridiculously popular?
Anyway, those are my questions. Just trying to get feel for whether it would be worth the time to take on this project...
I've looked around and did a bit of digging regarding placing Ubuntu on our Jetstreams. I have a working version on my device, but this version is more a background application then a full replacement for Android.
I'm wondering what we can do to start working to get a replacement OS since HTC simply won't support us any longer.
Thoughts?
Announcement:
http://www.ubuntu.com/devices/tablet
Previous known method example:
http://www.xda-developers.com/android/ubuntu-10-10-on-android-the-slightly-less-difficult-way/
Also: If this needs to goto the General Section, then Mod's please move. Thanks!
this really caught my eye as well, but i'm guessing it won't include the pen support, so it kinda sucks for me.
the official versions for the nexus family should be released 2day. i'm guessing it would spread and get ported to more devices..when it would happen it will be easier to determine the easiest way to get it to the jetstream.
https://wiki.ubuntu.com/Touch/Install?action=show&redirect=TouchInstallProcess
i heard that in a few days porting instructions will come up
this is how it looks for those of you that haven't heard of it
http://www.omgubuntu.co.uk/2013/02/the-official-ubuntu-tablet-videos