Monitor mode for Broadcom WiFi Chipsets - for CM9 - AT&T Samsung Galaxy S II Skyrocket SGH-I727

Anyone read about this today?
http://bcmon.blogspot.com.au/2012/09/working-monitor-mode-on-nexus-one.html?m=1
Cyanogen 9 & GS2 (I9100)
Download the zip: http://bcmon.googlecode.com/svn/trunk/bundles/gs2_bundle.zip
Extract the zip on your device (your sdcard will do fine)
Run 'sh setup.sh' on some terminal (adb ssh, terminal emulator, ...)
Now you have a wifi interface named wlan0 in monitor mode
Now run 'iwconfig wlan0' and check that you get an output similar to the one above
With all the i9100/i727 differences, I'll keep you posted on my install! If anyone else feels brave, or is cool with wipe/davlik, with CM9, keep us posted on details.

any progress on this? this looks like it could be alot of fun but, i have no idea what i'm doing

I get permission denied errors...I'm assuming its trying to write to /mnt?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

I rebuilt the kernel module for a CM9 nightly, but it doesn't work. Basically there is a bug in the firmware code where they are accidentally freeing a packet twice (which doesn't happen on the International version of the SGS2, that they officially released for), and the card crashes. Here is the response I got from them:
I checked in the firmware and the address 0x80e308 is the function pktfree so I guess we have a double free bug. My problem is that I can't reproduce the bug since my phone is the nexus one and all my friends have the international gs2 version.
Sorry
Click to expand...
Click to collapse
They don't seem willing to help until they get the packet injection working. Kind of sucks...

Related

Android Wired Tether is patched and working for Evo

This post is now irrelevant, Alex put these commands into the main program. See second post for links.
I figured out how to get it fully working. Big thank you to tonyb486 and canteenboy for figuring out that you need to disable adb and usb mass storage for tethering to work. That only left the problem of disk mounting not working after you are tethering. Here are two scripts to get the whole thing running smoothly and without a problem.
First, if you haven't already, install android-wired-tether. Next install GScript Lite (on the Market) which will let us automate toggling the USB function switch.
Create a new script with SU enabled and use this as the code.
Code:
echo 0 > /sys/devices/platform/msm_hsusb/usb_function_switch
That command shuts off usb_mass_storage and adb so everything is disabled and ready for Wired Tether to come in and do its job. Your usb_function_switch will look like this after running the command.
usb_mass_storage:disable
adb:disable
diag:disable
serial:disable
ether:disable
modem:disable
nmea:disable
When you are done tethering, use this command to re-enable adb and usb_mass_storage:
Code:
echo 3 > /sys/devices/platform/msm_hsusb/usb_function_switch
If for some reason you don't use USB debugging (adb), you can use this command to turn on usb_mass_storage by itself.
Code:
echo 1 > /sys/devices/platform/msm_hsusb/usb_function_switch
For those of you new to GScript, you can place shortcuts to scripts on your home screen. To simplify my life, I put them in a folder with Wired Tether so I have everything in one place. It's not an elegant solution, but you won't need to reboot your phone to get SD card mounting to work again. Perhaps someone with more knowledge of GScript can write some code that will automate running the first script, starting Wired Tether, and then running the last script after it notices that tethering has stopped. (Or better yet, get these commands into the actual program itself.)
(Optional)
For completeness, if you use any of the other usb functions listed above, you can use other 'echo #' commands to find the right combination. They don't toggle individual settings, but rather represent entire combinations of settings. I think around 32-33 it cycles back to 0 (everything off), I didn't have time to figure out if there is a pattern. You can find out what each number does by using another script to read out the switches.
Code:
cat /sys/devices/platform/msm_hsusb/usb_function_switch
Huge thank you to Alex C. Hofbauer. He implemented these commands into the program. Now the program works flawlessly (or I assume, I haven't tested it yet).
Attached to this post:
http://forum.xda-developers.com/showthread.php?t=706602
http://code.google.com/p/android-wired-tether/issues/detail?id=21
Thanks! I'd like to add that the scripts and the patched app are both working great on my Incredible.
O Whoa, Wired Tether works on my stock Eris now Thank You
Saturn2K said:
Huge thank you to Alex C. Hofbauer. He implemented these commands into the program. Now the program works flawlessly (or I assume, I haven't tested it yet).
Attached to this post:
http://forum.xda-developers.com/showthread.php?t=706602
http://code.google.com/p/android-wired-tether/issues/detail?id=21
Click to expand...
Click to collapse
Do you have the link to the exact program that has the commands built in? Perused both links and couldn't find the link to the fixed one for the Evo.
jerdog said:
Do you have the link to the exact program that has the commands built in? Perused both links and couldn't find the link to the fixed one for the Evo.
Click to expand...
Click to collapse
Same. I was going to try the app on the Eris because the same manual fix works :\
jerdog said:
Do you have the link to the exact program that has the commands built in? Perused both links and couldn't find the link to the fixed one for the Evo.
Click to expand...
Click to collapse
yeah me too cant find it
Wow, I thought nobody gave a **** about this. Here it is, all compiled and ready to go.
Thanks duder, works like a charm...
Sent from my phone.
THANKS!!!!
Has anyone figured out how to get this to work on Froyo? I get a kernel unsupported error when trying to run it.
dalstrs said:
Has anyone figured out how to get this to work on Froyo? I get a kernel unsupported error when trying to run it.
Click to expand...
Click to collapse
Same here, I'm using netarchy's 4.0.3a kernel and SteelH's stock Froyo RevE.1 ROM.
I have stock froyo on my evo and use easythether, it works perfect, all you have to do is set it to debug mode in the settings, install the app on your computer and when connected set it to charge only.
Sent from my Evo using XDA App
striker012 said:
I have stock froyo on my evo and use easythether, it works perfect, all you have to do is set it to debug mode in the settings, install the app on your computer and when connected set it to charge only.
Sent from my Evo using XDA App
Click to expand...
Click to collapse
The problem with that is having to install stuff on the computer. With wired tether you don't have to install anything on the computer.
XevoX said:
Same here, I'm using netarchy's 4.0.3a kernel and SteelH's stock Froyo RevE.1 ROM.
Click to expand...
Click to collapse
I'm running the same kernel on evio rom and it's working fine for me...
Sent from my phone.
I've been able to make this work on my stock kernel, rooted FroYo Evo, so this is indeed possible and I've narrowed it down to what is necessary. Please star/follow issue 23 in the Google Code tracker for updates.
Unsupported Kernel message...
Hello, all. I'm running Fresh Evo 3.1.0.1 and King's latest kernel and I get the unsupported kernel message. When I try to ignore as is suggested in post 24 on the Google code page for the wired tether, I get a FC once I click to start tethering. Any ideas? Thanks in advance. -E
Hello, all. I'm running Fresh Evo 3.1.0.1 and King's latest kernel and I get the unsupported kernel message. When I try to ignore as is suggested in post 24 on the Google code page for the wired tether, I get a FC once I click to start tethering. Any ideas? Thanks in advance. -E
Click to expand...
Click to collapse
Hi EindhovenOne, I responded to you on the issue tracker for Wired Tether, but I'll respond here just for some others to know the situation.
I found a fix that worked for me on my stock, rooted FroYo Evo and I coded the change and sent Harald a patch. He incorporated the patch and did the build for Wired Tether for me to test, which I have done (and it does indeed work for me, but does currently have the unsupported kernel dialog*). At the same time, though, it is listed in the downloads (you have to select all and then search), but this is in beta state for the changes (hence the deprecated tag I believe).
* I have fixed the unsupported kernel message and sent Harald a patch on this as well, so when he finds time to build it, that should be corrected, too.
So back to the "it's not working" portion, since I'm not running anything but stock (ROM and kernel), my system won't be the same as everyone's. I have no problem with other variations of ROMs and kernels (Evo's and non-Evo's) trying the 1.3 APK, giving feedback, and I'll try to do what I can (and someone else can step in if more suited than me even).
If you do run into issues, you can tag them in the issue tracker, which I try to follow frequently right now. Also, most importantly, if you can provide as much information as possible (what ROM and kernel you're using, a LogCat run just after the error occurs, any other pertinent information we can use to diagnose the problem, etc.), that helps tremendously in tracking down the problem and identifying a fix.
Saturn2K said:
Huge thank you to Alex C. Hofbauer. He implemented these commands into the program. Now the program works flawlessly (or I assume, I haven't tested it yet).
Attached to this post:
http://forum.xda-developers.com/showthread.php?t=706602
http://code.google.com/p/android-wired-tether/issues/detail?id=21
Click to expand...
Click to collapse
Is there a way we can find this patched version of android-tether? It is no longer attached to the first post. Also, the version I download from google still says incompatible kernel. It would be awesome to get wired tether working for the EVO
superevilllama said:
Is there a way we can find this patched version of android-tether? It is no longer attached to the first post. Also, the version I download from google still says incompatible kernel. It would be awesome to get wired tether working for the EVO
Click to expand...
Click to collapse
The beta-in-progress version 1.3 is located here. It still warns about the kernel currently but you can ignore it (simple lapse in patching that as well at the time). It works perfectly for me (starting and stopping), but there are a couple of issues outstanding right now that I'm working through with the users.
If you do run into a problem, though, just let me/us know through the issue tracker preferably, but you can also contact me directly (here, or my email via the issue tracker).
PS: I have patched the kernel message already, but I don't have write access to the project yet and I don't have the build system in place to handle the native code just yet, so I have been handing builds off to Harald who graciously has done the 1.3 so far for me. When he has time to do the one including the kernel warning fix, I'll post again with an update on that.

Kernel for Xoom with 3.2.2 and 4g sim installed.

I just got my xoom back after getting the 4G LTE sim installed and the 3.2.2 version of Honeycomb.
I have rooted it again and restored my apps and data, but am stuck on a lot of things work related since there is no kernel that provides tun.ko and keeps 4g working.
Is there a kernel being built that provides tun and 4g or maybe possibly a Moray type rom that has 4g support? (That would be super sweet).
Dude the only one was in the universal root thread. If you changed kernals I think your stuck till we can get the img.
Sent from my Xoom using xda premium
I used the Universal Xoom Root process available in Development. It gave me back root access and superuser, but the kernel is still stock and lacking write access to the microsd card and tun.ko in the kernel so that IPSEC VPN connections work.
Was just searching around to see if a kernel with 4g support was in the works. Was going to use the Rogue kernel, but there is a post about waiting until it can be updated to handle 4g access.
I will just sit back and monitor the forum for an update.
The Tachi kernel is working for a few people so far. I don't live in a 4G area (VZW says it will be here next month), only work in one so I can't test the LTE yet, though the 3G works fine from my home.
I've identified a few minor annoyances and work arounds as compared to running the kernel (and Moray ROM) prior to 3.2.2 HLK75D as listed in this post:
PengLord said:
Interesting... I installed File Manager HD, enabled Root Explorer (in the settings menu) and it prompted for Root permissions. It works great. The next step in resolving this is going to be remounting the external1 device on boot to enable global write support. As I'm not so well versed in Android architecture to do that, I'll use MicroSD Mounter manually on boot.
The final step to getting this all sorted will be for me to figure out how to mount usbOTG devices, If anybody has experience with that on this kernel with a 4G Xoom, I'd very much appreciate it.
I figured out my problem with usbOTG support... I needed to added the "usbOTG" folder in the "mnt" directory using Root Explorer and then install a mount manager such as USB Mass Storage Watcher OTG
Click to expand...
Click to collapse
This will get you set up with R/W support for the external1 folder and usbOTG, VPN support may be in there as well since the kernel supports it, I however haven't tried it nor have I read about it being tested as functional on the HLK75D build.
Sadly solarnz announced he will not be working on a 4G Tiamat ROM due to life getting in the way, this means we will likely need to wait until another dev gets caught up or until ICS gets released to us by Motorola (fingers crossed for next month) before it gets any easier.
EtchG said:
I used the Universal Xoom Root process available in Development. It gave me back root access and superuser, but the kernel is still stock and lacking write access to the microsd card and tun.ko in the kernel so that IPSEC VPN connections work.
Was just searching around to see if a kernel with 4g support was in the works. Was going to use the Rogue kernel, but there is a post about waiting until it can be updated to handle 4g access.
I will just sit back and monitor the forum for an update.
Click to expand...
Click to collapse
See the arcturus kernel thread over on xoomforums... there is now an open beta for a postupgrade kernel if you want to try it
Hi Etchg,
I had a similar issue. I sent my Xoom in for the 4g update. When it came back I rooted it. Trying to vpn into work (ipsec) I found that my new kernel 2.6.36.3-g6963abe has no tun.ko file. I found some instructions online and compiled one myself. Attached is my tun.ko (You will need to unzip and put in the systems/lib/modules directory. If your kernel is exactly the same as mine then it should work. BTW, with the new tun, I have successfully VPN'd into my work.
-Jared
I just came back to this thread and saw the tun.zip you uploaded. I tried to open it, but it tells me it is corrupt.
Can you either upload it again or use dropbox and send me the link?
I was able to extract the module and load it on my Xoom. I have the same kernel, but I keep getting an authorization error when I try to connect. Darnit all to heck!
I fixed the authentication issue I was having. Thanks for the module...works like a charm.
Thanks for compiling the tun.ko. It works correctly with Cisco AnyConnect for Rooted Devices.
Glad to help
Hi Guys,
Been absent for the week. Glad to hear that you got it downloaded and working!
-Jared
This always comes back as corrupt for me. I've tried everything I can think of, but I can't extract the tun.ko out of the zip. I haven't been able to create my own either, so I'd really appreciate someone posting this.

[ROM] Androot-N7p-rom for Nextbook 7 Premium

Welcome to Androot-N7p-ROM for the NextBook 7 Premium *ONLY.
I decided to change up some of the apps and generalize the rom in terms of its boot-animation screen. It runs on LauncherPro (just choose it as the "always"/default upon first instance of it. The Launcher that comes with the device isn't so great, but I left it there just in case.
It's based on the first known rooted ROM for this device: 'DocHoppy's ROM'. Credit for most of this ROM goes to him and to 'Wendal' for his toolset for packing the ROM (into cramfs) for the Nextbook 7 Premium device.
As such, it is a beta/ work-in-progress.
Androot-N7p-ROM v0.2
[ 146 MB ]
download here
Instructions:
*WARNING: FLASHING THIS DEVICE WILL ERASE YOUR DATA AND APPS!!!!*
Download image.
Rename file to update.img
copy file to root of SD card.
Follow on screen prompt asking if you want to run update image.
Disclaimer:
I am not responsible for bricked devices.
Here's my changes..
removed:
-youtube player <- the real youtube app is better
-explorer <- redundant
-slide me app market <- redundant now that Google's Market is installed
-quick search box <- Google Search widget is better IMO
kept/added:
-Market <- the real Google one
-root explorer - an alternative & capable file explorer
-astro file manager <- we all know it well
-quickpic 1.5.2 - a much lighter & more efficient photo organizer/viewer
-3D gallery <- some love it, some hate it
-brightness level 1.0.0 - quicker brightness changes
-ConnectBot 1.6.2 <- for those that need a SSH tool
-Officesuite full <- may as well keep it
-Titanium Backup 4.6.7 <- has some very handy tools aside from backups
-LauncherPro 0.8.6 <- may be old, but it's smooth and capable
-superuser <- because this rom is rooted
-has some of the Google Apps (go ahead and add as you see fit)
-has a custom boot animation.
Click to expand...
Click to collapse
Known Issue:
Apps2sd reports SU Binary out of date. Attemps to update this via superuser fails due to cramfs file system.
It's not perfect, but it does work well and I run it as my daily driver on my N7P.
Please give feedback or suggestions! I trust the pro devs could easily help me out with the little things!
-------------------
here are other threads related to the Nextbook 7
http://forum.xda-developers.com/showthread.php?t=1410862 (dochoppy's rom)
http://forum.xda-developers.com/showthread.php?t=1190990 (rooting talk? )
Since I'm new to modifying/cooking ROMs, here's my
Questions I have for the devs that cook ROMs all the time...
(lol)
Where do I edit the items that show in 'settings > about' in the device?
How do I change the default shortcuts that LauncherPro puts on the dock?
How do I change what icons are default on the home screen?
Where do I put custom wallpapers as part of the rom?
How do I modify Android UI colours?
Can the dialer be removes without losing "contacts"?
How do I create a shortcut to "contacts" without the phone/dialer?
(more to come I'm sure)
Hello, first of all, thanks for your work!
I am having trouble loading this rom. it says there's an invalid image file in my sd card and if I want to delete.
Now, I don't know if my tablet is a never or older version of what you guys have...
Next7p
2.3.1
kernel: 2.6.32.27
build: v2.0.7.....
my serial is also different from alot..it starts with YF0511
any help or tips?
In Dochoppy's original rom/post he mentions that the device will need to have a serial number starting with YF1011. That stands the same for this rom, as it's derived from his.
Having an invalid update.img firmware file could be due to a number of things, but the one I have here works on my device.
I wish I had more of an answer, but by all means try out the tools for repacking the rom.
So after messing around compiling a ROM, I forgot to add a launcher, and now I am stuck in a bootloop. After the girl in the dress is there for awhile, I get a black screen, then reboot. Anyone now how to fix this? I have been searching Google, but can not find anything yet.
Any help would be great!
xxProphecyxx said:
So after messing around compiling a ROM, I forgot to add a launcher, and now I am stuck in a bootloop. After the girl in the dress is there for awhile, I get a black screen, then reboot. Anyone now how to fix this? I have been searching Google, but can not find anything yet.
Any help would be great!
Click to expand...
Click to collapse
I had mine half dead for a short bit until i found i could go into a low level bootloader mode and recover it. I am working on getting a the tool/images i used to recover mine uploaded and such.
Download and extract n7p_rescue_kit.zip
Reboot device using paper clip then quickly press and hold reset until you get black screen with usb plugged in
When windows wants driver give it the respective folder for your os (32bit or 64bit) from Drivers folder from the download
Run RK29update.exe if it says "Found RKAndroid Loader Rock Usb" on bottom you are good but if it shows "No Found RKAndroid rock usb" repeat last step.
Either flash all of the default selected items or do just system (since bootloop is in system)
Hope this helps
P.S. If you pack then unpack your custom one you can flash JUST system using the tool but be sure to use the offsets that are pre-loaded.
use a pin to push the reset button on the back to break out of the boot loop.
If after this your rom still bootloops, try putting a different update.img rom to flash, on to the sd card. Then boot into safe mode by holding all 4 front buttons after boot. the update should be found and installed after that.
Thanks!
I registered just to thank DocHoppy for all his efforts. I have a Nextbook Premium 7 I got for Christmas from Hastings, which fell into the YF09111XXXX batch. I used Wendal Chen's RK29xxImageTools_v2.1 to unpack the firmware upgrade from the nextbookusa site. I then put the Google apks, SuperUser, Rootexplorer, and re-packed it with a custom bootanimation. Because of my serial # I couldn't use DocHoppy rom without getting that "Invalid Update" error, but using their firmware seems to work.
My next goal is to find a way to get the "Accounts & Sync" into the settings! One of my apps is getting an "Error 42" which is an Android Market authentication error... however, other apps have worked without any problems so it's difficult to tell if that's the issue I'm having.
aberrantjots said:
I registered just to thank DocHoppy for all his efforts. I have a Nextbook Premium 7 I got for Christmas from Hastings, which fell into the YF09111XXXX batch. I used Wendal Chen's RK29xxImageTools_v2.1 to unpack the firmware upgrade from the nextbookusa site. I then put the Google apks, SuperUser, Rootexplorer, and re-packed it with a custom bootanimation. Because of my serial # I couldn't use DocHoppy rom without getting that "Invalid Update" error, but using their firmware seems to work.
My next goal is to find a way to get the "Accounts & Sync" into the settings! One of my apps is getting an "Error 42" which is an Android Market authentication error... however, other apps have worked without any problems so it's difficult to tell if that's the issue I'm having.
Click to expand...
Click to collapse
Install "Quick Sync Settings" to get to the hidden settings view.
Also did you use this guide for market? That one worked great for me.
Thanks
Working great for me so far. Thanks sharing your work.
Nice!!!
I have the image as well... Can you tell me how to open it or point me in the direction of a tutorial? I've been looking for weeks and couldnt find any info until this thread I have a yf091... as well. Thanks in advance for any help.
lost enigma 208 said:
I have the image as well... Can you tell me how to open it or point me in the direction of a tutorial? I've been looking for weeks and couldnt find any info until this thread I have a yf091... as well. Thanks in advance for any help.
Click to expand...
Click to collapse
Not sure if this rom will work for you, just guessing by your serial number. If it is to work changing between roms on these tablets is very easy. Just download the image onto the root of your sdcard, rename it update.zip (not update.zip.zip) your tablet will recognize it as an update and ask if you want to proceed. If you say yes then follow the prompts and your in business!
Sent from my NXM726HN using XDA App
Just go this to day and was plesantly suprised to find this rooted rom. Just wanted toy let you know that my S/N is YF12112xxxx and this rom work prefect for me (so far) Thanks for all the work you guys have done here. Also is there anyway to over clock the processor in out tabs?
Thanks for the comments thus far!
I would like to overclock this thing too, but that might be further down the road, as priority is on getting a different file-system for the /system volume.
Version 0.4 is coming next.
FYI:
There will be a larger span of time between updates on this particular rom for the N7p, because I will be using more stable conjumbles of things from other roms for this device. This rom is more of a remix or derivative than an entirely different rom.
Again thanks for all the hard work. I have a few requests. first since we cant change the Adhoc ( using wifi from another android device) on the fly with out RW access can you please add the ability to connect to adhoc wifi in the next build? Also i love google currents app but we cant use is on our device because we don't have map's installed. can that be added as well?
fireproof34 said:
Again thanks for all the hard work. I have a few requests. first since we cant change the Adhoc ( using wifi from another android device) on the fly with out RW access can you please add the ability to connect to adhoc wifi in the next build? Also i love google currents app but we cant use is on our device because we don't have map's installed. can that be added as well?
Click to expand...
Click to collapse
Most of the N7P roms out there now have Market installed and working. Why not just install these apps yourself?
I only suggest so because for the time being, the device is limited to its minimal capacity for apps without full-on apps2SD. Besides, for a tablet like this, you want to keep the system apps to a minimum and de-bloated for performance whenever possible.
sgtfoo said:
Most of the N7P roms out there now have Market installed and working. Why not just install these apps yourself?
I only suggest so because for the time being, the device is limited to its minimal capacity for apps without full-on apps2SD. Besides, for a tablet like this, you want to keep the system apps to a minimum and de-bloated for performance whenever possible.
Click to expand...
Click to collapse
As far air know they can not be installed with out write access. I f they can please let me know how and I will be more then ecstatic to get them both installed.thanks.
Sent from my NXM726HN using XDA App
fireproof34 said:
As far air know they can not be installed with out write access. I f they can please let me know how and I will be more then ecstatic to get them both installed.thanks.
Sent from my NXM726HN using XDA App
Click to expand...
Click to collapse
Oh I was talking about currents and maps. Both of those can be installed via market. I have them both on my tablet.
The ad-hoc networking is something worth putting in a later release though.
good mention.
Runs great
Works great on my
NextBook Premium 7
Serial: YF121121263
Manufactured: Dec 2011
I just joined and know very little about tablets
but this image is better than the rest. I'm 63 retired and would like to learn how to do what you do.
Again, thanks for your hard work.
lrmahon
Welcome. Lots of searching and trial and error ,but this is a great place to start!
lrmahon said:
Works great on my
NextBook Premium 7
Serial: YF121121263
Manufactured: Dec 2011
I just joined and know very little about tablets
but this image is better than the rest. I'm 63 retired and would like to learn how to do what you do.
Again, thanks for your hard work.
lrmahon
Click to expand...
Click to collapse
Sent from my NXM726HN using XDA App

[APP] GooManager Beta official thread

The official app of Goo.im
We have spent a lot of time getting the server side changes in place to automatically parse our developer's rom files to grab data to make a functional OTA update system without the need for editing manifest files, or other tedious tasks. This is our attempt at creating a way for Android developers to simply publish material, and distribute it to the masses without any hassle.
This app is and will always be FREE!
General Features:
Ability to browse and search all of the files we have on our site, and download directly to your mobile device.
Receive OTA style updates from your favorite rom developers that we have hosted here.
CyanogenMod nightly build update support
Incremental (differential) rom updates for sequential builds
Flashing roms & installing recoveries
Update gApps packages
If you would like to sideload the app on your phone and avoid the market, we distribute the APK by itself, and also as a prebuilt repo maintained by solarnz(github.com/solarnz)
Are you a rom developer wanting to publish your work with our updating system?
To get your rom compatible with our updating system, you should make the appropriate changes to your build.props. For more information on this system, see the link below (sorry it's not clickable but i need 8 posts!)
goo.im/howto-rom-updating-via-our-app (For developers who are curious about how to modify their build prop file for compatibility with GooManager)
GooManager download page (To download the actual app)
KNOWN ISSUES:
DownloadManager API is buggy on Gingerbread
Installing OpenRecoveryScript on devices that do not support flash_image and do not have a /cache/recovery/command supported recovery will fail
FEATURE REQUESTS
Feel free to post them in this thread, but as my time is limited and Goo.im/GooManager's code is just something I do in my free time, there are simply not enough hours in the day to address them all
SHOUT OUTS
Chris Solarnz (For his java advice and contributions)
Mike Wielgosz (For contributing to the rom reordering and listing code)
Dees_Troy for all of his amazing work on OpenRecoveryScript and TWRP
eyeballer (For countless nights of helping test stuff, and awesome suggestions)
Shift (For the market icon)
Drmacinyasha (For all the testing / anal retentive bug reporting)
toastcfh (For helping bounce lots of ideas around)
EVERYONE ELSE I PROBABLY LEFT OUT!
FREQUENTLY ASKED QUESTIONS:
Why is _________ phone/tablet not supported?
In order to offer us flexibility without compromising other software such as rom manager premium, etc we did not want to rely on /cache/recovery/extendedcommands. At the time of developing the flash automation features, extended commands were licensed to RM only and it would have been illegal to use them. Since then, the license has changed, but we still feel it is the best direction to have our own since we can change it to fit our needs.
Why does this not work with my recovery i downloaded from Rom Manager?
CWM and CWM touch builds distributed by rom manager ONLY WORK WITH ROM MANAGER SO STOP ASKING!!!! #@$#@$#
Why are incremental updates only available for some roms?
Incremental updates are enabled on a per rom-device basis. Not all builds are even capable of this, since wipe can be required. It is at the discretion of the developer to toggle this as needed.
If you are a developer and would like to sign up: goo.im/signup
If you are a recognized developer, chances are you will get approved. (Note not all buildbox applicants are approved, and you may get only hosting)
Awesome. Used it to put TWRP2.1.2 easily on my ATT Galaxy Note.
It's Goo time! Been using this to distribute my unofficial cm9 nightlies for the touchpad and nook color for a while now and we've had nothing but positive feedback from users. Encourage your favorite rom developers to sign up
Not only is GooManager a great app, the whole ecosystem is, I believe, second to none.
A fantastic, simple system for developers to upload their ROMs and specify what device that ROM is for.
Easy for device users to find the ROMs that work with their devices.
Notifications of ROM updates for the ROM that you're using.
Easy download and installation of ROMs for devices with a supported recovery.
Differential updates - only flashes the files that have changed from one version to the next - smaller download, less wear and tear on your device, and quicker updates.
Thanks for this free app!
People don't have to donate to automatically check if there is an update to a CM nightly now.
for those of us who are not update-happy (although it is addicting) is there anyway to know from either this app or from Goo notifications in general whether an update requires a full wipe and then the requisite re-setting up of one's device?
I get a notification everyday for the new Gapps and for an update of my ROM (AOKP milestone 5 for Kindle Fire). I've ignored them because I'm just too lazy to spend an hour or two getting everything back up and running.
I've tried repeatedly to download CM9 nightlies and gapps via the latest market version of the app (2.06 I believe) and I always get a "download failed" message no matter if I'm on wifi or 3g. I've tried uninstalling and reinstalling, clearing cache, and clearing app data, and nothing seems to work. Is the download manager problem referenced in the OP a problem with ICS as well as GB? I have a Galaxy Nexus (toro) using BAMF Paradigm 1.25 in case that info makes a difference.
Sent from my Galaxy Nexus using Tapatalk 2
lanceman5000 said:
I've tried repeatedly to download CM9 nightlies and gapps via the latest market version of the app (2.06 I believe) and I always get a "download failed" message no matter if I'm on wifi or 3g. I've tried uninstalling and reinstalling, clearing cache, and clearing app data, and nothing seems to work. Is the download manager problem referenced in the OP a problem with ICS as well as GB? I have a Galaxy Nexus (toro) using BAMF Paradigm 1.25 in case that info makes a difference.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Please get a logcat. It will give you a reason why the download failed. If you are on linux, adb logcat | grep GOO
There seems to be issues with some people or devices that I have yet to narrow down. If you can replicate this bug consistently please contact me on freenode IRC in the #goo-inside.me channel and i'll try to look into it. My time is limited these days hunting a bug i can't reproduce so despite the needs of the community -- work and life comes first!
peters4n6 said:
for those of us who are not update-happy (although it is addicting) is there anyway to know from either this app or from Goo notifications in general whether an update requires a full wipe and then the requisite re-setting up of one's device?
I get a notification everyday for the new Gapps and for an update of my ROM (AOKP milestone 5 for Kindle Fire). I've ignored them because I'm just too lazy to spend an hour or two getting everything back up and running.
Click to expand...
Click to collapse
It is up to the developer to state whether it requires a wipe in their changelog. Generally nightly builds will not require a full wipe though
thereals0up said:
Please get a logcat. It will give you a reason why the download failed. If you are on linux, adb logcat | grep GOO
There seems to be issues with some people or devices that I have yet to narrow down. If you can replicate this bug consistently please contact me on freenode IRC in the #goo-inside.me channel and i'll try to look into it. My time is limited these days hunting a bug i can't reproduce so despite the needs of the community -- work and life comes first!
Click to expand...
Click to collapse
I have no clue what I'm looking at, but here is the logcat of a download attempt. At least I hope this is what you meant.
http://db.tt/bpWD2LWo
Sent from my Galaxy Nexus using Tapatalk 2
Anybody can explain how to use with Galaxy note CM9?
I'd li ke to flash nightly in diff mode. First of all do I need to unistall cwm and install the open recovery?
Somebody has already tried?
Inviato dal mio GT-N7000 con Tapatalk 2
I like this app man, Good work...
Great job, it's nice to see such a useful app for no cost.
Raistlin82 said:
Anybody can explain how to use with Galaxy note CM9?
I'd li ke to flash nightly in diff mode. First of all do I need to unistall cwm and install the open recovery?
Somebody has already tried?
Inviato dal mio GT-N7000 con Tapatalk 2
Click to expand...
Click to collapse
You simply install goomanager, hit menu -> install openrecoveryscript which will DD over the image to your recovery partition for twrp 2.0.
As far as differential patches go, the feature is still being enabled on a per-rom basis while I make sure there are no bugs CM nightlies in general do not have it enabled yet but some devs do.. the list will improve but i don't want to make any big changes until I am 100% positive the incremental system is perfect
I'm having quite a few failed downloads recently via goomanager, anybody else?
Not sure if this is device related issue or they app/appserver etc.
Using GTAB P1000 btw.
This thing is a piece of crap if you are trying to download on 3g.
superstargoddess said:
This thing is a piece of crap if you are trying to download on 3g.
Click to expand...
Click to collapse
Please keep this conversation constructive. If you have anything relevant to resolving the issue go ahead and post it but complaints are not helpful. If you have a failed download, paste a logcat or simply the line which gives a numerical code for why the download failed. The tag will be "GOO"
We are aware of downloading issues but since this is just a project we do strictly on free time for no profit, we can only get what we can afford which is why we are on all used hardware and frequently have hiccups with our distribution boxes. We're looking into getting more in the rotation to lower the load on the servers but there are not enough hours in the day or dollars in the bank account to handle it right away. We're looking into financing some sexy new servers from dell if we can get approved
thereals0up said:
You simply install goomanager, hit menu -> install openrecoveryscript which will DD over the image to your recovery partition for twrp 2.0.
As far as differential patches go, the feature is still being enabled on a per-rom basis while I make sure there are no bugs CM nightlies in general do not have it enabled yet but some devs do.. the list will improve but i don't want to make any big changes until I am 100% positive the incremental system is perfect
Click to expand...
Click to collapse
Ok so I prefer to wait...I have no rush.
But it is safe to install the openrecovery? I mean 0% of brick over n7000 running CM9
Inviato dal mio GT-N7000 con Tapatalk 2
thereals0up said:
Please keep this conversation constructive. If you have anything relevant to resolving the issue go ahead and post it but complaints are not helpful. If you have a failed download, paste a logcat or simply the line which gives a numerical code for why the download failed. The tag will be "GOO"
We are aware of downloading issues but since this is just a project we do strictly on free time for no profit, we can only get what we can afford which is why we are on all used hardware and frequently have hiccups with our distribution boxes. We're looking into getting more in the rotation to lower the load on the servers but there are not enough hours in the day or dollars in the bank account to handle it right away. We're looking into financing some sexy new servers from dell if we can get approved
Click to expand...
Click to collapse
Sorry, was just being honest! ^^
Edit: I'd totally donate if it were reliable on 3g!
superstargoddess said:
This thing is a piece of crap if you are trying to download on 3g.
Click to expand...
Click to collapse
Then complain to your 3G provider dumbass.

[Q] Someone want to create a thread for a Lollipop ROM?

I have created a mostly-functional build of OmniRom 5.1 (Lollipop) for the T959V
However, I don't have enough posts to post in the development section or to put in links. Does somebody want to do this for me? If so, let me know.
The current status of it is:
What works
Taking pictures (very laggy switching between FFC and rear)
RIL
SMS
Data
Recovery
Bluetooth
Wifi
Vibration
Powered-off charging animation
Flash from BML
What is definitely not working
App to SD - not working on i9000 either, complains about insufficient space fixed in git
Tv-out as Omni's aries-common has removed it
Video recording - only captures fuzz fixed in git
What is untested
Everything else
What is probably not working
Microphone mute option doesn't work during calls - not working on i9000
GPS - I actually have a T959P, not a T959V... It was released by Telus in Canada. It is a very similar device (I can run ROMs for the T959V with limited problems - ie sometimes I get wakelocks and the gps never works), it has a different GPS chipset (hence why I have no clue on the status of the GPS) and also uses different cell bands (but I can still use your guys modems but I lose access to the 850Mhz band). I have created a build specifically for the T959V as best as I can guess from teamacid and others' device trees.
Selinux is set to permissive as I don't know how to create the proper policies for the GPS.
For a download and more information, see drive.google.com*open?id=0B7vXjzo0Hj-ifm1KQWNYam9FYWdnaFlXZU5LVnVVSzJxYVU3eHlWZGR1VVNZUWk1V1QzOUk (replace "*" with "/")
Source code can be seen under my github account (username is xc-racer99 there as well) under the android-5.1 and android-5.1-t959v branches
Ooooomg ...im wait ....is amazing the new proyect .....thanks thanks
Quick update:
I've got the video record to work properly now as well as being able to move apps to the SD card.
Selinux is left!
Should I upload a build?
Sure...I have a spare phone somewhere that I can test it. Do you have a Gapps package to go along with the ROM? As far as GPS is concerned, back when Beanstalk 4.4.2 was being worked on, a patch was developed to make GPS work...I'll have to root around in my files and see if I can dig it up...I think the developer deleted all the Beanstalk threads for some reason or another.
Yeah, I took the GPS files from CM-11.0 but I can't test if they work. With regards to the Selinux portion of things, only some parts of it were being enforced in KitKat while everything is now being enforced in Lollipop. GPS was not enforced in KitKat so the policies for it were not in place.
I haven't tried any gapps on it yet but I would recommend trying any of the three from the Omni i9000 thread
forum.xda-developers.com*galaxy-s-i9000/i9000-development/rom-t3054101 (again, replace "*" with "/")
I'll upload a new build as soon as I can verify that it boots - it fixes several issues such as apps2sd and camera that weren't working in the one I already have uploaded.
Also, I'm curious as to what the command "cat /sys/class/sec/gps/hwrev" shows. In CM11, one of the GPS files check this and depending on what it shows it loads a different file. Does this mean that there are two hardware variants of the SGS4G?
Alright, new build uploaded. Follow the "link" from my first post, the build is under the Galaxy S 4G (T959V) folder. Selinux is still disabled, no extra policies have been implemented. Apps2sd and video camera should work.
For flash instructions, just do a data wipe beforehand. You should be able to flash from any CWM 5.0+ or TWRP, regardless of BML/MTD status
Been looking at the gps a bit more, seems that TeamAcid's CM11 did it slightly differently than most other KitKat roms in that it has both a gpsd and a samsung-gpsd. Do you know what beanstalk used? It would be so much easier if it didn't have the samsung-gpsd... However, we still have the funky init.d gps script which checks the hardware revision....
xc-racer99 said:
Alright, new build uploaded. Follow the "link" from my first post, the build is under the Galaxy S 4G (T959V) folder. Selinux is still disabled, no extra policies have been implemented. Apps2sd and video camera should work.
For flash instructions, just do a data wipe beforehand. You should be able to flash from any CWM 5.0+ or TWRP, regardless of BML/MTD status
Been looking at the gps a bit more, seems that TeamAcid's CM11 did it slightly differently than most other KitKat roms in that it has both a gpsd and a samsung-gpsd. Do you know what beanstalk used? It would be so much easier if it didn't have the samsung-gpsd... However, we still have the funky init.d gps script which checks the hardware revision....
Click to expand...
Click to collapse
Link shows Not Found Error 404
Sammpls said:
Link shows Not Found Error 404
Click to expand...
Click to collapse
Sorry about that, I guess i screwed it up somehow.
Try this link:
drive.google.com*open?id=0B7vXjzo0Hj-ifm1KQWNYam9FYWdnaFlXZU5LVnVVSzJxYVU3eHlWZGR1VVNZUWk1V1QzOUk replacing the "*" with a "/"
Seeing as this is my 10th post, I think I'll probably try to open an actual thread for this project. If I do, I'll post a link to it here.
Doesn't work... Why use google drive when there are others better for uploading your files.
xc-racer99 said:
Sorry about that, I guess i screwed it up somehow.
Try this link:
drive.google.com*open?id=0B7vXjzo0Hj-ifm1KQWNYam9FYWdnaFlXZU5LVnVVSzJxYVU3eHlWZGR1VVNZUWk1V1QzOUk replacing the "*" with a "/"
Seeing as this is my 10th post, I think I'll probably try to open an actual thread for this project. If I do, I'll post a link to it here.
Click to expand...
Click to collapse
Sammpls said:
Doesn't work... Why use google drive when there are others better for uploading your files.
Click to expand...
Click to collapse
I was using Google Drive as its something I have an account for already and has plenty of space on. Do you have a suggestion of a site I should use? In the meantime, a direct link to the file is https://drive.google.com/file/d/0B7vXjzo0Hj-iZ0YtQTdoTG5KVW8/view?usp=sharing Hopefully this works...
Google Drive isn't bad at all. I was suggesting that you use another cloud service for uploading the files if it didn't work. (which i didin't do a really good job telling you that)
Thanks, that link works!
Alright, I have opened a devDB thread at http://forum.xda-developers.com/gal...official-omnirom-5-1-galaxy-s-4g-sgh-t3146611
Please post anything there and do not use this thread as I will not be monitoring it.
Google drive is at least better than Mega(especially if you use non top-end devices).

Categories

Resources