Related
This distro was created with all the tools needed for android development. After you install this os, you're ready to start developing for Android.
GreenRom Dev Kt is now available. It has Android SDK/NDK, Eclipse, ADB(from any location!), ThemerStudio, all required dependencies for compiling roms, repo init for pulling source code from github, and Gimp for theming/editing graphics.
Q:Why is this important?
A:Because all you need to do is install this OS, plug in your phone, and begin having fun as you dev. There's no need to try and download and install ANYTHING for Android development because it's all been done for you. Do you need to run ADB Logcat? Go ahead. Now there's no need to make sure you're in a certain directory because you can run ADB from anywhere.
Some common questions might be:
Q:Do I have to install GRPdevkit to my HDD?
A:No, you can run it from live mode and store your progress on a pen drive. Alternately, you can install it on a pen/usb drive and run it from that if your bios detects usb drives.
Q:Will I be able to install this alongside another OS?
A:Possibly, although LivLogik and I haven't had any luck with dual booting this nor Ubuntu.
Q:Will this screw up my computer?
A:As with any Linux OS that's experimental, the possibility is there, although LivLogik and I have been testing this OS extensively to ensure all the bugs have been work out before making it available to you. Nevertheless, we are in no way responsible for your actions!
Q:What if I don't want to dev and just want to use this for an every day system?
A:That's quite fine as this OS is built from Linux Mint 11 and has all the stuff you probably use such as Brasero, X-Chat, Transmission, Libre Office, Movie Player, Calculator, Pidgin, G-Thumb, and much more!
Q:What if I can't burn an installation disk?
A:As with the majority of mainstream Linux Distros, we will be offering an installation disk for a small fee + s&h. LivLogik and I have to come up with a design for the cd decal as I have access to a cd printer. We will post the availability when we come up with it.
Q:How do I use the tools that are in this?
A:There is a get started guide on the desktop that you can move to your home folder or delete that explains briefly how to use the tools, however, I didn't include instructions on Eclipse as I've never used it. For Eclipse just go to it's website here: http://eclipsetutorial.sourceforge.net/totalbeginner.html and learn how to use it. Eclipse is used to make programs for Android.
LivLogik will be making a video so that you can see it in action. Enjoy!!
Note: you may need to right click on the desktop and change the wallpaper mode setting from zoom to whatever fits your screen best. -Fixed in update
**EDIT** if you have problems signing in to gtalk on the messanger... go to software manager and in the search box type in gtalk and download that plugin and it should work and if you have problems with anymore accounts like facebook do the same and it should work fine -Fixed in update
CLICK HERE TO VIEW THE VIDEO !!!! (it shows a run through of it and also sorta where everything is and a little how to - livlogik
Video #2 Updates For v1.1
============> grpdevkit.iso - 2.0 GB <============
MIRROR >>>---------------> http://dev-host.org/fj1lh8zu4g60/grpdevkit.iso <-----------------<<<
Code:
[color=green]Change Log: [/color]
(07-22-11 v1.1) :
~Added Chrome Browser
~Added plugin for Gtalk
~Shortcut for SDK/NDK in home folder
~Added shortcut for GRP forum
~Added different wallpaper([color=blue]thanks LivLogik[/color])
(6-?-11 v1) :
~Linux Mint 11(Katya) as Distro base [URL=http://www.linuxmint.com/]Linux Mint11[/URL]
~Remastersys(for building the distro [url]http://remastersys.sourceforge.net/[/url])
~Added GRP custom default wallpaper([color=blue]thanks LivLogik[/color])
~Added Android NDK
~Added Android SDK
~Added all required dependencies for compiling Android OS as follows:
git-core, gnupg, flex bison, gperf, libsdl1.2-dev, libesd0-dev, libwxgtk2.6-dev, squashfs-tools, build-essential zip curl, libncurses5-dev, zlib1g-dev,
sun-java6-jdk, pngcrush, schedtool, lib32z1-dev, lib32ncurses5-dev, lib32readline5-dev
~Added ADB( thanks to Tahl:[URL=http://www.rootzwiki.com/showthread.php?589-Android-SDK-NDK-Eclipse-and-ADB-Auto-Installer-(Ubuntu-Linux-Mint)]Tahl's tread[/URL])
~Added Gimp
~Added ThemerStudio(thanks to CorCor67:[URL=http://corcor67.blogspot.com/p/themer-studio.html]CorCor's blog[/URL])
~Added Repo Init to home directory
[color=red]Testers:[/color]
LivLogik
SlashDW
whoever else has tested or is running the Dev Kit let me know so I can include you in the testers credits. ;-)
epic!? I think so.
Treken said:
This distro was created with all the tools needed for android development. After you install this os, you're ready to start developing for Android. Check it out here: http://greenromproject.com/showthread.php?188-GreenRom-Dev-Kit-is-here!!-64bit(updated-7-23-11)
And, of course, enjoy!
Click to expand...
Click to collapse
Nice! This should save a ton of setup time when I install a new distro
Sent from my ADR6300 using XDA App
AWESOME! Finally, I can run Linux simply. Expect ROM's from me!
EASY Set-up! Now to figure out how to do everything else..... :/
Smokeey said:
EASY Set-up! Now to figure out how to do everything else..... :/
Click to expand...
Click to collapse
If you need some help with anything just let me know.
Wow. downloaded.
vassskk said:
Wow. downloaded.
Click to expand...
Click to collapse
how was the download speed? The server will be getting a make-over tomorrow and should beef up the download speed.
I'm assuming I can make this into a persistent usb and take it anywhere and work on it? Regardless I'm going to give it a shot.
DL started at 700 and dropped 1kB/s every 2 seconds continuously, then dropped out. I thought it was an artifact of the averaging done by Google Chrome; except it was linear, 2 seconds every time.
bogwurm said:
I'm assuming I can make this into a persistent usb and take it anywhere and work on it? Regardless I'm going to give it a shot.
Click to expand...
Click to collapse
Please see #2
Q: Do I have to install GRPdevkit to my HDD?
A: No, you can run it from live mode and store your progress on a pen drive. Alternately, you can install it on a pen/usb drive and run it from that if your bios detects usb drives.
vassskk said:
Please see #2
Q: Do I have to install GRPdevkit to my HDD?
A: No, you can run it from live mode and store your progress on a pen drive. Alternately, you can install it on a pen/usb drive and run it from that if your bios detects usb drives.
Click to expand...
Click to collapse
And boom goes the dynamite
/Dinc
Very nice work. Thanks for this.
Sent from my ADR6300 using XDA App
vassskk said:
DL started at 700 and dropped 1kB/s every 2 seconds continuously, then dropped out. I thought it was an artifact of the averaging done by Google Chrome; except it was linear, 2 seconds every time.
Click to expand...
Click to collapse
The server went down for a little bit. They beefed up the server speeds so it should download faster now. It should be up and running now
Great.. now I have to stop & get more DVDs. My old laptop doesn't boot from usb. Looking forward to trying it out. Thanks!
OP,
You said you were having trouble paralleling it with other os's? Any ideas why? i was very much hoping to throw it alongside joulicloud (ubuntu based) on my ssd.
vassskk said:
OP,
You said you were having trouble paralleling it with other os's? Any ideas why? i was very much hoping to throw it alongside joulicloud (ubuntu based) on my ssd.
Click to expand...
Click to collapse
I wasn't having any luck dual booting Linux Mint or Ubuntu. I have Windows 7 Ultra that I wanted to dual boot but couldn't get it worked out and just gave up since I have to have Linux for most of the development I do.
beard0 said:
And boom goes the dynamite
/Dinc
Click to expand...
Click to collapse
Dino-mite? Faq said run live and store on usb. Assumption was run live from dvd. Second part of answer was run from usb if BIOS allowed it. That's why I assumed I could run a live usb with a dedicated partition on the same usb. If we didn't have questions then we wouldn't have Devs. But thanx for your input Mr Dynamite.
bogwurm said:
Dino-mite? Faq said run live and store on usb. Assumption was run live from dvd. Second part of answer was run from usb if BIOS allowed it. That's why I assumed I could run a live usb with a dedicated partition on the same usb. If we didn't have questions then we wouldn't have Devs. But thanx for your input Mr Dynamite.
Click to expand...
Click to collapse
You should be able to install on a usb pen drive and save your files on a dedicated partition. Just make sure you have enough room on your pen drive. Look here: Link and see the requirements for doing so. I've never actually installed on a pen drive myself but theoretically speaking it's plausible. Let me know if it works out for you.
Will do thanx for the reply. I know how to set up a persistent live distro but some of them are tricky. I like this idea because all I need is the flash drive to do work on any computer.
"Here and now, boys, here and now."-Aldous Huxley
Hi all,
I just got the ambient light sensor of the KF#1 working and posted some instructions on my small Kindle Fire Hardware Blog (no ads there, simply lazy to write it up again here for the forum): http://hack-a-fire.blogspot.de/.
All you need are either the original kernel sources from Amazon or the 3.0 kernel from Hashcode (I double-checked that the driver code is almost the same there, so it should also work with that one).
The driver code itself is not in best shape and we may want to clean it up, e.g. suspend doesn't seem to work properly for me.
Let me know if you need further help...
Best,
stylon
stylon said:
Hi all,
I just got the ambient light sensor of the KF#1 working and posted some instructions on my small Kindle Fire Hardware Blog (no ads there, simply lazy to write it up again here for the forum): http://hack-a-fire.blogspot.de/.
All you need are either the original kernel sources from Amazon or the 3.0 kernel from Hashcode (I double-checked that the driver code is almost the same there, so it should also work with that one).
The driver code itself is not in best shape and we may want to clean it up, e.g. suspend doesn't seem to work properly for me.
Let me know if you need further help...
Best,
stylon
Click to expand...
Click to collapse
Nice Blog.:laugh:
Thanks for this
Sent from my Amazon Kindle Fire using xda premium
this is awesome! nice find
Sent from my Nexus 4
Also works on hashcode's 3.0.50 kernel
FYI: I just got Hashcode's 3.0.50 kernel (recent pull from his repo) running and also tried out the ambient light sensor driver from there and it works, too.
Best,
STYLON
stylon said:
FYI: I just got Hashcode's 3.0.50 kernel (recent pull from his repo) running and also tried out the ambient light sensor driver from there and it works, too.
Best,
STYLON
Click to expand...
Click to collapse
A couple things. Do you know if hashcode will be putting your fix into his next update?
Also, I was not exactly able to follow all of your commands. I read and reread your blog, but I was not sure where to do the commands, or what exactly I need to make everything work.
Any help would be appreciated. Thank you, stylon.
Sent from my Amazon Kindle Fire using Tapatalk HD
jma9454 said:
A couple things. Do you know if hashcode will be putting your fix into his next update?
Also, I was not exactly able to follow all of your commands. I read and reread your blog, but I was not sure where to do the commands, or what exactly I need to make everything work.
Click to expand...
Click to collapse
Technically, all he has done is enable the light sensor such that its value (representing the ambient light level) can be measured as raw output. There would still need to be a bit of work done to have our Kindle Fires adjust brightness automatically based on this. But it's a darn good start!
jma9454 said:
A couple things. Do you know if hashcode will be putting your fix into his next update?
Also, I was not exactly able to follow all of your commands. I read and reread your blog, but I was not sure where to do the commands, or what exactly I need to make everything work.
Any help would be appreciated. Thank you, stylon.
Click to expand...
Click to collapse
Hashcode's 3.0.50 kernel source does include the driver and I think Hash's default config even compiles and links it in. However, the driver initialization is commented out in Hash's kernel source. So, on none of Hash's kernel's you will get the driver to say any word.
The driver code is in no good shape at all (suspend not working, awkward I2C initialization, global variables all over). I'm in the process of rewriting it and will send the rewritten driver to Hash for inspection once I'm finished.
What you can do to experiment with the sensor is the following:
1. compile your own kernel from Hash's config, take Hash's boot.img, extract the ramdisk and make a new boot image with your compiled kernel, then flash it to the boot partition via fastboot (keep the old boot.img as you most likely want to reflash to the original boot.img after finishing experiments)
2. follow my instructions on the blog, i.e. uncomment the driver initialization, do "echo 1 > /sys/.../enable" to enable the driver from the user space, and read the lux value and don't forget to shed some light on the sensor (I did the first time I tried )
But be warned: suspend is not working, that means your KF will either not suspend or even crash with a kernel panic if you try. That's why it's not a good idea to enable the driver in it's current state.
Best,
STYLON
Geko45 said:
Technically, all he has done is enable the light sensor such that its value (representing the ambient light level) can be measured as raw output. There would still need to be a bit of work done to have our Kindle Fires adjust brightness automatically based on this. But it's a darn good start!
Click to expand...
Click to collapse
Indeed, I haven't done much more yet than enabling the disabled driver. And I've not done anything to get it working in Android. So, the user-level code still needs to be written.
From the current state of the kernel-level driver I suspect that Amazon never got suspend working on the driver and therefore decided to exclude it from the product. Maybe the sensor was never high on their priority list anyway and that's why they also never spend much time to improve the quality of the driver. Also, the sensor looks a bit sensitive to me, but that could be fixed by simply averaging over time in a user-level driver.
My rewrite of the kernel-level driver will not change the current sysfs user-level API, so maybe someone wants to volunteer to start on the user-level implementation for Android already. Unfortunately, I don't know too much (yet) about the user-level drivers for Android. I know liblights, but that's for the LCD backlight. Is libsensors supposed to handle also ambient light sensors?
Best,
STYLON
I have a Android 4.2.2 ROM from twa_priv and I have a 3.0.63 Kernel, will this work? I have not found the driver on my kindle. I used the CM File Manager with Rooted Permissions.
Sent from my Nexus 7 using xda app-developers app
JRBX550 said:
I have a Android 4.2.2 ROM from twa_priv and I have a 3.0.63 Kernel, will this work? I have not found the driver on my kindle. I used the CM File Manager with Rooted Permissions.
Click to expand...
Click to collapse
I doubt that the driver will work on your configuration as is, as all KF kernel sources that I've seen so far contain the same disabled driver code. As I said, even if somebody who compiles a kernel enables the driver in the kernel config, it's still disabled in the code. So, although in principle part of the driver is then linked into the kernel, it's not visible via sysfs (/sys/...) and therefore there's no way to enable it lateron from user-space as I mentioned in my blog.
I think it's best to stay calm as a user for a couple of weeks until I've reworked the driver code. I'm working together with Hashcode and twa_priv already and can contribute directly to the kernel code since yesterday.
Best,
STYLON
Just added a first rewritten version of the driver to my github respository at https://github.com/stylon/kernel_omap_otter-common/ for people that want to play around with it.
The sysfs device has moved to /sys/devices/platform/lightsensor-level. You still need to enable it by "echo 1 > /sys/devices/platform/lightsensor-level/enable", but then it should also survive suspend/resume cycles now. lux values can either be read as ascii from /sys/devices/platform/lightsensor-level/lux or as continuous stream of binary values from /dev/input/event? (was 4 for me always). The stream is delta-thresholded (can be set via sysfs, too), meaning that it only outputs a new value if it's significantly different from the previous value.
One shortcoming: although I've rewritten the driver with care to load as modules, it's still a platform device driver in nature, meaning that it'll fail to load after the first insmod/rmmod cycle.
Best,
STYLON
Finless juste made a new rom (version 1.7) for these android stick:
Measy u2c / B12 / imito v2 (camera)
libstagefright inside
support and download here:
http://www.freaktab.com/showthread.php?4282-NEW-Measy-U2C-B12-Finless-ROM-1-7
my question.. Is he the only one who cook rom for android stick? cant find alternative here on xda...
anyway, a great Rom done by Bob!
Code:
Features in my Measy / B12 / Imito V2 ROM:
This is an entirely new system. This is not much from the original Measy/B12 ROM in this as fas as system goes.
Many features from my 1.6 ROM are of course in this along with new features.
BE SURE to check out the mouse wheel ZOOM function to enable google earth etc to zoom!!!!
Set it by going into settings>accessability> and turn on mouse zoom!
1) New "auto hide" status bar! To enable this go into settings>Display and turn it on.
Now anytime you run an APP it will automatically hide the status bar. Please note, some badly written APPs
can leave you in a stuck condition that you cannot exit the APP. You will need you keyoard exit key.
2) While you in settings>display there is another feature to force the settings menu icon in the status bar.
It is 3 dots vertically. NOw anytime you in a APP that has a settings capability, if you click that you get settings!
3) Lock screen is back friends! Now is settings>security you can
A) Disable the lock screen completely (default is slide)
b) Setup a pattern for lock screen
c) Setup a PIN for lock screen
d) Setup a password for lock screen
4) Sleep is back like a tablet!!!! Go into settings>display and you can turn on sleep!
Now understand how this works
a) If there is no wifi or ethernet connection, when it goes to sleep will power off.
b) If there is a connection, it will simple go into low power mode and turn the display off. Moving the mouse turns it back on again
5) I enabled location services. This is now in the settings menu. Tested and working with all APPs that use it.
remember to turn off GPS as we have no GPS.
6) New "grid" style launcher available as a choice of launcehrs.
Some people still want the Alternate launcher that comes with many TV sticks for EZ TV use.
I took this from the Neo X5 ROM as I liked it better than previous versions. This of course comes with the RK settings as well.
If you want to remove this just use ES File explorer and delete these files from /system/app
LauncherNEW.apk
AllApp.apk
RKSettings.apk
RKBasicsettings.apk
Now just reboot and all this will be gone.
7) Gameloft fix. This fixes Gameloft games from crashing to the desktop.
Many of them do not run and crash to the desktop. This is due to a license check based on the device.
Special thanks to Christian Troy for inventing this fix. I modded it for this ROM.
8) Build.prop edit to open up the Google Play store to APPs that normally say "not compatible".
I am spoofing a Samsung device that will show almost any APP as compatible.
YOur device will show up in google play as NOT a B12 device! Understand this please.
I also left the original buiild.prop in the ROM called build.orig.
If you want to go back, just use ES FIle Explorer or a root file explorer and rename build.prop to build.old
Then rename build.orig to build.prop.
Go into settings, apps, all and go into the Google Play app. Clear the cache and data.
Reboot! You should be back to showing up as a Minis Nexo X5.
9) Rockchip just released a updated libstagefright.so to try and fix HW decoding issues in XBMC.
Ihadd added this ot the ROM but have not fully tested it yet.
See info here regarding this new library.
http://forum.xbmc.org/showthread.php...756#pid1345756
10) As always, full init.d support! If you do not know what that is... ignore it. For geeks that want to use it. It is there!
11) RK Mirrioring is enabled. I have yet to figure it out or how to use it but if we ever do, its there.
I think we need a client on our tablets to use it. Hopefully more info will come from WiMo about this.
12) Remote Control using RK Remote APP is now fully supported!
In the ROM kit is a RKRemoteControl.apk.
You install this on your phone or tablet and now it can remotly control your TV player!
Just put the APK on sdcard or something and install it on your Android phone, tablet, etc.
ENJOY this one! I had a HARD TIME getting it to work!
13) I added a reboot APP that will allow optional reboot options like reboot to bootloader (flash mode).
14) As always I added the Xbox XPAD.KO module is now injected on boot. This was by request! Enjoy!
15) I added Xbox360 keylayout to fix some games and camera spin with xbox 360 controller. Per this post here:
http://forum.xda-developers.com/show....php?t=1792531
16) TUN.ko module is also added by request. (CIFS and MD4 are already in the latest kernel).
Be aware if you use another kernel other than whats in this ROM, you may have to manually insmod CIFS and MD4.
The files are in /system/lib/modules
This ROM has several options for you to choose from for flashing so please read carefully how to change these flash options.
I have provided 4 parameter files. These will increase APP space and decrease internal sdcard space.
1GB APP space (this is default setting for the flash tool).
2GB APP space.
4GB APP space.
6GB APP space! This is the max! This leave only 400MB of space for the internal SDcard.
___________________________
NOTE:
USB OTG port boot up:
Anytime the Measy/B12 is booted AND the OTG port is plugged into a PC, it will boot with USB storage turned on! What this means is on boot up you will not be able to see the internal SDcard or the External SDcard from within Android. On your PC you see the removable drives because on boot they are mounted to the PC not Android. Now you can this OFF once booted. Go into settings and USB. You will see PC connection is grayed out.
1) Click it and it will then put the check box in "conneted". Odd it is OFF by defualt even though it is really connected to the PC.
2) Now turn it off and it will unmount the SDcards from your PC and you can now see them in Android.
HOWEVER... Realize next reboot, it will be on again.
In my opinion this should not work this way but at least you can turn it off once booted.
The other work around is to always hook up the USB cable to the back micro USB port not the OTG port.
The back port ONLY powers the unit. There is no data connection on this port for PC.
This solves that issue. But remember the back port will NEVER connect to a PC or allow ROM flashes.
Only the OTG port allows that.
Can I install this ROM on MK809II?
ledzgio said:
Can I install this ROM on MK809II?
Click to expand...
Click to collapse
YES. And I think it's the best ROM for MK809 II. Try it and you'll see...
g.b.a. said:
YES. And I think it's the best ROM for MK809 II. Try it and you'll see...
Click to expand...
Click to collapse
Thank you! Is everything working with this ROM? even Wifi and bluetooth? I read that there are problems with them...
ledzgio said:
Thank you! Is everything working with this ROM? even Wifi and bluetooth? I read that there are problems with them...
Click to expand...
Click to collapse
Yes. They are working fine with this ROM...
Enjoy!
Hi I am looking for cmw flashable zip for mk808 will this work ?
g.b.a. said:
Yes. They are working fine with this ROM...
Enjoy!
Click to expand...
Click to collapse
I have heard that, with the MK809II because it doesn't have the reboot button, I have to open the device and do something inside...is it correct? do I have to do this operation even with this ROM?
thanks
ledzgio said:
I have heard that, with the MK809II because it doesn't have the reboot button, I have to open the device and do something inside...is it correct? do I have to do this operation even with this ROM?
thanks
Click to expand...
Click to collapse
Reboot?
If it is a normal reboot, you don't have to open the device.
There is a Reboot app included in the New Measy Finless 1.7 Rom.
Correct me if I am wrong but based on my understanding, you only have to open your device and do the "Shortcut" method when you are having
some problem in getting into recovery mode. or your small switch button is not working anymore...
Can I install this rom on my MK809III rk3188
are there some instructions/guide how to make rom for this little sticks on your own?
adiprince1 said:
Hi I am looking for cmw flashable zip for mk808 will this work ?
Click to expand...
Click to collapse
I would like to know this also.
Thanks
Sent from my SGH-T889 using xda premium
Hi all,
Thanks to the huge discount on Nook Simple Touch earlier this month in UK, hopefully the device will regain some popularity and draw more attention from the XDA community. Unfortunately all the new devices come with firmware v1.2.0 while most posts in the forum were for the outdated v1.1.x, including the brilliant multitouch mod from wheilitjohnny. I know there is a way to downgrade to v1.1.x but I still prefer v1.2.1 after I tried v1.1.0. So I decided to port wheilitjohnny's mod to v1.2.1. After one week's hard work as I'm a newbie to the Linux world, I finally built the kernel and saw no more boot loop. All the multitouch test tools from Market correctly reported up to 2 fingers.
Before put the kernel to your device, make sure it's already running 1.2.1 firmware and rooted. You can find the link to the official upgrade file in the forum and you can use Nook Manager to root your device which is also available in the forum.
Then please found the kernel attached as zip file. You need to unzip the file and follow arkusuma's post on how to install it.
http://forum.xda-developers.com/showthread.php?p=24168019#post24168019
All credits go to wheilitjohnny. It's all his work.
One lesson I learned for all the developers who may be interested in more mod development is, to make a bootable kernel you MUST use toolchain from "http://www.codesourcery.com/sgpp/lite/arm/portal/release1293". Select the IA32 GNU/Linux TAR one (MD5: c6930d14801b4fab6705d72df013e58b). Any other toolchains including Google's own or even another version from codesourcery won't work. The generated kernel built with any other toolchains will only cause boot loop.
[UPDATE] Oh forgot to say, you need to add one more line to your /etc/permissions/required_hardware.xml on your device. You should be able to find the first line already in the file, just add the second line.
<feature name="android.hardware.touchscreen" />
<feature name="android.hardware.touchscreen.multitouch" />
More info please check http://forum.xda-developers.com/showthread.php?t=1563645
Does this kernel work with NoRefresh (I assume debug2 version for FW 1.2.x)?
koltshin said:
Does this kernel work with NoRefresh (I assume debug2 version for FW 1.2.x)?
Click to expand...
Click to collapse
Yes. I have NoRefresh_Debug2 and Fast Mode mod running together with this kernel. No problem so far.
Thx. Does this kernel works for both Nook Simple Touch and the Glow light model?
Sent from my GT-N7100 using xda app-developers app
waynesi said:
Hi all,
One lesson I learned for all the developers who may be interested in more mod development is, to make a bootable kernel you MUST use toolchain from "http://www.codesourcery.com/sgpp/lite/arm/portal/release1293". Select the IA32 GNU/Linux TAR one (MD5: c6930d14801b4fab6705d72df013e58b). Any other toolchains including Google's own or even another version from codesourcery won't work. The generated kernel built with any other toolchains will only cause boot loop.
I've had good success with the toolchain on Ubuntu; just install the gcc-arm-linux-gnueabi packages, and add the Makefile and head.S changes that were in the fastmode2 patch; I've not tried building this touch mod, but it has let me build my own kernels with usb host and with TLS support.
Click to expand...
Click to collapse
I can confirm that this kernel works on a NST with Glowlight on FW. 1.2.1 Thanks for the hard work.
Can I use this kernel for 2 fingers zoom in? I tried it with aldiko, but do not work with pdf.
You need to unzip the file and follow arkusuma's post on how to install it.
http://forum.xda-developers.com/showthread.php?p=24168019#post24168019
Click to expand...
Click to collapse
Could somebody please help me installing this without adb over wifi? Because i have internet only over ethernet. I was thinking of CWM.
Thanks
Sagittarius0 said:
... without adb over wifi?
Click to expand...
Click to collapse
Well, how about ADB over USB?
Renate NST said:
Well, how about ADB over USB?
Click to expand...
Click to collapse
Can you please help me exactly how to do it? I have tried it once for some other reason and it didn't work... :crying: And after that I searched for it here and found a post which said that adb works only over wi-fi.
And I am quite new with android so please explain the process well.
waynesi said:
Yes. I have NoRefresh_Debug2 and Fast Mode mod running together with this kernel. No problem so far.
Click to expand...
Click to collapse
Fast Mode don't works on my NST fw 1.2.1. What app exactly are you using to activated the fastmode?
update: this kernel don't have / sys/devices/platform/omap3epfb.0/graphics/fb0/fmode so fastmode is not possible
tebra said:
Fast Mode don't works on my NST fw 1.2.1. What app exactly are you using to activated the fastmode?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=39529578&postcount=140
Step one, use noogie and do a full backup of your Nook.
It should be almost 2GB file size.
Using noogie, copy uRamdisk.
Use bootutil.exe (in signature):
Code:
bootutil /x /v uRamdisk init.rc
[i]edit init.rc[/i]
bootuil /r /v uRamdisk init.rc
The line you edit out (with a number sign) is
Code:
[color=red]#[/color] setprop service.adb.tcp.port 5555
(uncomment this line to go back to using WiFi ADB)
Copy uRamdisk back to the Nook.
Reboot your Nook.
Read up about getting the ADB drivers working on your desktop here:
http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Installing_ADB
This thread is old, I know, but hopefully someone will spot this. So I took the plunge and installed Multi-Touch (running FW 1.21 and rooted). I followed the instructions for the ADB wireless method and also changed the required_hardware.xml file, resetting the permissions of the edited file to match those of the original.
Nothing is different? My original hope was that the pinch-zoom function in Dolphin 10.2.6 might work with this mod. It doesn't seem to work on either Android or Desktop settings in that browser. I can't see that it works anywhere. Maybe I need to reinstall Opera Mobile and test it there?
...
O.K., I just reinstalled Opera Mobile. No effect at all that I can discern.
Hmm....I am underclocking with No-frills CPU Control to 300 MHz. Is that the problem? Nope....changed back to 800 MHz and no effect.
So...what am I missing? Is there something I can check to be sure I did the ADB thing correctly (after I'm done using the "shell" do I just close it down or is there some closing command I should have used?). Does this mod have to be used in conjunction with something else?
I usually jump out of an ADB shell with ^C
There's an interim release of UsbMode-1.7a.apk in the signature.
If you touch the left 3/4 of the screen it will report touch coordinates.
It will indicate multiple touches.
That's the easiest way to see how many simultaneous touches your device supports.
My Nook: 2, my Kyocera: 4, my ZTE: 5
I installed a multi-touch test app from the Market and it showed that two fingers were recognized (no more), although the recognition was somewhat spotty.
I've been fussing around with it and sure enough it has begun to work with Opera Mobile, both at 800 MHz and 300 MHz (no discernible difference there). It also works very well with Perfect Viewer. It does not work with Google News and Weather (which really needs it), at least not the version that came with NookManager rooting.
Alas, it does not work with Dolphin, which was my main impetus for trying this. I've got Dolphin to the point where it is much more reliable than Opera Mobile but the only way to zoom is via a gesture which requires going to a blank screen, drawing the gesture and then returning to the current page. It makes one want to draw gestures that are not found in children's books. Although Dolphin claims pinch-to-zoom, it doesn't seem to work with the NST, at least not this version of Dolphin. Maybe I need to delve back into the past versions (which will probably be less stable in other respects...).
Well, anyway it works. I'll have to see if it affects the battery life in any significant way (I read on my Nook, too!). If not, I may as well keep it although its utility to me is limited.
Now to look at "no-refresh"......
nmyshkin, what about Google Maps?
Yes, I forgot to mention Google Maps (I was using "Places" but it amounts to the same thing). That works with multi-touch as well. I also noticed that to some extent multi-touch zooming in Opera Mobile is web-site dependent. For example, it does not seem to work at all on Wikipedia but worked OK on some other sites I tried. I just wish it would work in Dolphin
I just tried it with Orion Viewer (which I like for PDFs) and it also works there. It seemed to want to work with Kingsoft Office on the same PDF file but then the app crashed. There are other ways to magnify in both, of course.
I finally tried NoRefresh, and while it worked, I was left wondering what it is for other than as a "we can do this" feature. Lots of flickering while it made up its mind as a white-listed app was launched and then the image degradation thing. After I exited the app my screen was such a mess I had to reboot. I guess I'm used to the way the e-ink display sort of tears when scrolling (or even zooming now, for that matter). The NoRefresh just doesn't seem to give me anything I want. I have not tried FastMode. As I currently underclock to 300 MHz I am reluctant to overclock the Nook just so it will (sort of) work like something it is not and run down the battery really fast.
Hey everyone. I bought this device specifically because I do a lot of work on linux in command line world and I though it would be the perfect device when combined with the Logitech Pro keyboard and Complete Linux Installer (it's an app on Google Play). It turned out to be quite a bit of work getting everything working because of Knox and SELinux. Eventually I got a custom kernel working that allows me to toggle SELinux between permissive and enforcing.
I attached an Odin flashable tar that works on the SM-P900 (wifi version). I am on the North American version, so I have no idea whether it will work in other regions. If you flash this kernel then there are a few things you need to know:
I'm assuming you already have root on your device.
When you boot it will still be in "Enforcing" mode. This change simply allows you to use the "setenforce" terminal command or any of the apps on Google Play that do this for you.
You might experience some wifi weirdness after you flash the kernel. You just need to open up /system/build.prop and change ro.securestorage.support from true to false and then reboot to resolve the issue.
If you have a different version of the device or want to compile it yourself for any reason I wrote an article describing how I compiled it here:
http://graemehill.ca/compiling-permissive-android-kernel/
I also did a few other things to fix the keyboard and get linux running properly, so if you're interested in that I described my setup in more detail here:
http://graemehill.ca/turning-a-galaxy-note-pro-into-a-linux-laptop/
Thank you for this!
Sent from my SM-P900 using Tapatalk
trying to build kernel
I'm trying to follow your guide to compile a kernel from source. I have installed (on my Win 8.1_64 PC) Android SDK/NDK. GnuWin32, JavaJRE, and downloaded SM-P900 kernel source.
I'm getting errors at "Apply Kernel Config" step.
here's the output: http://pastebin.com/yFqDrNY8
Thanks for your help
Don :good:
dodo99x said:
I'm trying to follow your guide to compile a kernel from source. I have installed (on my Win 8.1_64 PC) Android SDK/NDK. GnuWin32, JavaJRE, and downloaded SM-P900 kernel source.
I'm getting errors at "Apply Kernel Config" step.
here's the output: http://pastebin.com/yFqDrNY8
Thanks for your help
Don :good:
Click to expand...
Click to collapse
It looks like you're in Windows. To my knowledge it is not possible to compile a Linux kernel in windows. I would recommend downloading virtual box and installing some Linux distro in there. This is what I was talking about in the "environment" section at the top of the article.
For android development I find that you need access to a lot of tools where some are only available on Windows and others are only available on Linux so a Windows PC with a Linux VM is ideal in my opinion.
Oh ok, no problem. I just misread the guide. I've setup a build environment in a vm before to compile aosp for my Nexus 10. Shouldn't be too hard to do it again. I recently rebuilt my pc so the vm I had got nuked.
Sent from my SM-P900 using Tapatalk
ok I got my Ubuntu VM up and running using this guide
http://forum.xda-developers.com/showpost.php?p=50748836&postcount=25
installed android NDK to ~android/NDK, and unzipped the kernel source to ~android/kernel
followed your guide to build a SELinux permissive kernel but i'm getting some errors when trying to compile. here's the output:
http://pastebin.com/Npdu7J5h
EDIT: retried doing the EXPORT command and now it seems to be compiling
dodo99x said:
EDIT: retried doing the EXPORT command and now it seems to be compiling
Click to expand...
Click to collapse
When you export a variable in the terminal it only exists for that one session, so if you open a new terminal instance you need to run the command again. If you want to set it permanently normally you can just put the export command into ~/.bashrc
Oh I see. I'll give that a try. I was able to create a new boot.img following the rest of your guide. I have yet to try flashing it though. Will have to find some info about all the kernel options that can be set. Hopefully be able to integrate HMP to get all eight cores running at the same time.
Sent from my SM-P900 using Tapatalk
Cool, let us know how that goes. I wonder how much it would affect battery life.
Graeme H said:
Hey everyone. I bought this device specifically because I do a lot of work on linux in command line world and I though it would be the perfect device when combined with the Logitech Pro keyboard and Complete Linux Installer (it's an app on Google Play). It turned out to be quite a bit of work getting everything working because of Knox and SELinux. Eventually I got a custom kernel working that allows me to toggle SELinux between permissive and enforcing.
I attached an Odin flashable tar that works on the SM-P900 (wifi version). I am on the North American version, so I have no idea whether it will work in other regions. If you flash this kernel then there are a few things you need to know:
I'm assuming you already have root on your device.
When you boot it will still be in "Enforcing" mode. This change simply allows you to use the "setenforce" terminal command or any of the apps on Google Play that do this for you.
You might experience some wifi weirdness after you flash the kernel. You just need to open up /system/build.prop and change ro.securestorage.support from true to false and then reboot to resolve the issue.
If you have a different version of the device or want to compile it yourself for any reason I wrote an article describing how I compiled it here:
http://graemehill.ca/compiling-permissive-android-kernel/
I also did a few other things to fix the keyboard and get linux running properly, so if you're interested in that I described my setup in more detail here:
http://graemehill.ca/turning-a-galaxy-note-pro-into-a-linux-laptop/
Click to expand...
Click to collapse
I tried to install this using VBox Odin and I couldnt get it to work. Tried using BOOTLOADER and also PDA. Not sure the correct one but neither worked for me. Also, Moblie ODin hasnt yet worked but when it does, things will be much easier for me at least.
I have a newly rooted SM-900. I will have to find time someday to compile the kernel against what I have. Must be a slightly newer version than the one you posted. That is only thing I can think since I just got my 12.2. Thanks for the detailed info.
Camera?
Hey, thanks for the great kernel. It's working as expected to enable permissive mode, but I'm having one issue with it. When I use your kernel, the camera is disabled (says something like "Camera Failed"), and it won't work even when trying different software besides stock, like Google Camera. Anyway, clearing cache, etc. doesn't do anything, but the camera works again when I flash the stock kernel. Is this related to permissive mode or something else with the settings?
aarstar said:
Hey, thanks for the great kernel. It's working as expected to enable permissive mode, but I'm having one issue with it. When I use your kernel, the camera is disabled (says something like "Camera Failed"), and it won't work even when trying different software besides stock, like Google Camera. Anyway, clearing cache, etc. doesn't do anything, but the camera works again when I flash the stock kernel. Is this related to permissive mode or something else with the settings?
Click to expand...
Click to collapse
The camera fails for me too. I dumped a logcat and isolated the issue here:
W/ActivityManager( 2746): Permission Denial: get/set setting for user asks to run as user -2 but is calling from user 0; this requires android.permission.INTERACT_ACROSS_USERS_FULL
V/ApplicationPolicy( 2746): isApplicationStateBlocked userId 0 pkgname com.google.android.GoogleCamera
But... the camera is not a huge deal. It did, however, break wifi. I did not get a logcat of that yet, but I would assume it is also a permission issue.
Wifi works for me using the fix mentioned in the OP. Also, thanks for looking into the camera issue. I agree it's not a big deal, and it's easily fixed by flashing the stock kernel, until someone figures out a proper fix.
aarstar said:
Wifi works for me using the fix mentioned in the OP. Also, thanks for looking into the camera issue. I agree it's not a big deal, and it's easily fixed by flashing the stock kernel, until someone figures out a proper fix.
Click to expand...
Click to collapse
Wow, I totally missed that entire line in the OP... You literally just made my whole day. I fought this all day long, desperate to get ubuntu working. Thank you for pointing that out.
I get "xt_mark.h" is missing (no such file or directory) error. Any idea why that may be?
I'm using the source for p900 international hoping that I may sidestep the camera issue that way (by enabling permissive to the international kernel I mean), but as it stands it does not compile.
I've googled it but until now it was/is to no avail...
Graeme H said:
Hey everyone. I bought this device specifically because I do a lot of work on linux in command line world and I though it would be the perfect device when combined with the Logitech Pro keyboard and Complete Linux Installer (it's an app on Google Play).
Click to expand...
Click to collapse
Hey Graeme H,
we both have the same intention. I am downloading the international Kernel at the moment and will compile it again for you guys. The download takes a little longer as I am at vacations.
I am going this route: doviak.net/debian-kit/debian-kit_p00.html . In the future I would like to have arch linux running on this device but a customized debian would be okay for the beginning, too.
Eventually I will try to use framebuffer instead of vnc or something like that. I would love to use sublime-text and dwm on that device with that resolution
Good luck guys. I will try to update.
Edit: hehe I have dwm in front of me now and the resolution is so high that I am barely able to read
Compiled the kernel and flashed in on my device but my camera is still not working. Maybe we need to edit the config:
# Camera sensor devices
#
# CONFIG_VIDEO_OV7670 is not set
# CONFIG_VIDEO_VS6624 is not set
# CONFIG_VIDEO_MT9M032 is not set
# CONFIG_VIDEO_MT9P031 is not set
# CONFIG_VIDEO_MT9T001 is not set
# CONFIG_VIDEO_MT9V011 is not set
# CONFIG_VIDEO_MT9V032 is not set
# CONFIG_VIDEO_TCM825X is not set
# CONFIG_VIDEO_SR030PC30 is not set
# CONFIG_VIDEO_NOON010PC30 is not set
CONFIG_VIDEO_S5K6B2=y
# CONFIG_S5K6B2_CSI_C is not set
CONFIG_S5K6B2_CSI_D=y
CONFIG_S5K6B2_POSITION_FRONT=y
# CONFIG_S5K6B2_POSITION_REAR is not set
CONFIG_VISION_MODE=y
# CONFIG_VIDEO_M5MOLS is not set
# CONFIG_VIDEO_S5K6AA is not set
Click to expand...
Click to collapse
Rather than each people compiles its kernel, could someone put a link to download the international kernel compiled? I think this would allow more people to get this kernel. Thank
PHP:
smylion said:
Rather than each people compiles its kernel, could someone put a link to download the international kernel compiled? I think this would allow more people to get this kernel. Thank
Click to expand...
Click to collapse
Compiled from Kitkat source. [ur#l]erhan.es/upload/sm-p900-permissive-intl.tar[/url] (odin)
Thank you but the link does not work
smylion said:
Thank you but the link does not work
Click to expand...
Click to collapse
Sorry, it is erhan.es/upload/sm-p900-intl-permissive.tar