Database Users

[Updated 7/5][Kernel 1.2] LBS Honeycomb Kernel for the Viewsonic Gtablet

WARNING: TRYING TO CUSTOMIZE YOUR VIEWSONIC MAY LEAVE THE DEVICE IN A BRICKED STATE. PLEASE MAKE SURE YOU FULLY UNDERSTAND HOW TO USE NVFLASH BEFORE TRYING THIS INCASE SOMETHING GOES WRONG AND YOU NEED OR WANT TO GO BACK TO THE VIEWSONIC STOCK TNT ROM.
What we offer here is a new way to keep you in full control of your tablet. Our 1.8 Honeycomb Kernel offers Speed, Reliability, and new added features. This kernel is a spin off of the Pershoot Honeycomb Kernel Source Code & want to thank Pershoot for all his work on the kernel already. You do not have to Flash your device or even update to a different ROM to feel the benefits of the Linux Box Solution Honeycomb Kernel...
Updating to the Linux Box Solution Honeycomb Kernel couldn't be easier. No wiping of User/Data is necessary. If you are already running a Honeycomb ROM then your good to go. This kernel was designed for Tegra 2, Harmony Board based devices. The LBS 1.8 Honeycomb Kernel has only been tested on a Viewsonic Gtablet. If any other developers with the Specified Tegra 2 & Harmony Board based devices wants to give this Overclocked Powerhouse a try please give me your feedback once you have tested it out.
Features as of Version 3.2:
Increased Kernel Cache Sizes from 256kb to 512kb
Improved Stability
Overclocking (Kernel is Overclockable to 1.4Ghz)
USB Mass Storage ( If your favorite Honeycomb ROM doesn't offer USB Mass Storage drop this Kernel in and Full Support is there)
Improved Video Play (480P Plays, Not sure about 720P but 1080P Does Not Work)
Git Hub Source Location: https://github.com/linuxboxsolution/LBSGtab
Linus Torvald Repo: http://android.git.kernel.org/platform/kernel/tegra.git
Pershoot Repo: https://github.com/pershoot/gtab-2632.git
For anyone in doubt or wondering. This Kernel has been fully updated with Pershoot's source code from his 7/2 update. Next changes to the source code are taken from Linus Torvalds Repo Source to help merge Pershoot's and Torvalds Source to make a more efficiently running Kernel.
Download Link:
LBS 3.2 Honeycomb Kernel: http://linuxboxsolution.com/linux-b...tions-Viewsonic-Gtablet-Honeycomb-Kernel-3.2/(increased kernel cache size for improved stability)
LBS 1.9.2 Honeycomb Kernel: http://linuxboxsolution.com/linux-b...ons-Viewsonic-Gtablet-Honeycomb-Kernel-1.9.2/(Wifi configuration changes to help people with wifi connectivity issues)
LBS 1.8 Honeycomb Kernel: http://linuxboxsolution.com/linux-b...tions-Viewsonic-Gtablet-Honeycomb-Kernel-1.8/ Initial Release
1. Download the zip file for the Kernel Version you want to the Root of your SDCARD Partition.
2. Rename file to update.zip
3. Reboot Tablet into Recovery Mode (When Tablets Off hold 'Power' Button and 'Volume +' Button at Same time till Recovery Mode is Shown On Screen)
4. Using Volume -/+ to navigate the Clockwork Mod Menu go to apply /sdcard/update.zip
5. Once Installation of New Kernel is done Reboot the Tablet & Enjoy your newly found Feature Set and Performance Improvements

aww what the hell i'll give it a go...currently running BoS 6.0 and it's smooth...I'll post back with Quadrent scores for those who care about them.
Updated: well it might be me but the lockscreen seems more responsive, Video plays about the same but im in Rockplayer, Quadrant was 2677 using Quadrant Advanced. Kepp up the work guys.
Update: Ok well been playing with it and just found out No WIFI here. it won't pick up any signel...this might be just me but so far Reboot + turning wifi off and back on did not fix it i'm going to wipe cache and see if it resoves it.
Update: as of right now the Update did not fix the problem nor did wiping cache/data...Going back to my nandriod and i'll watch for updates.
Also i'm using a static setup with WEP Security if that helps...it shows my old connections but won't connect or find new ones.

Awesome please do but if you haven't yet try the updated version.

I had an exchange with you on slatedriod about "your" new kernel. You admitted that it is based on per shoots old GB codebase with your new wiz bang improvements. Why don't you say that here and say that this kernel is an L BS modified version of his kernel. You must just be looking for donations for the work of others?

you're going to continue updating illuminate with this right?

how have you improved playback of video in this kernel? is the improvement rom agnostic?

WiFI Issues
Well I was having intermittent WiFi problems with Illuminate until I flashed this Kernel, now I am just getting an error when I try to connect to WIFI.

jbrianj said:
Well I was having intermittent WiFi problems with Illuminate until I flashed this Kernel, now I am just getting an error when I try to connect to WIFI.
Click to expand...
Click to collapse
Try the latest pershoot GB kernel. And/or try the Flashback of BoS roms

Hi Everybody,
I need some help. I installed this rom into my malata zpad. First opening, there was no problem but after restarting, touchscreen was not worked.
I reinstalled, but same problem was occurred. My touchscreen is not working, only back and home button, which are physical button, are working.
What can I do?
I noticed this behavieur with the latest Version before I hadn´t any problems

I read today that this is Pershoot's latest + cm7 modules. No changelogs, no submissions to github. I read in the rules here something about "don't do anything to get us in trouble". To me this kernel looks like something that might do just that.

I loaded this kernal on top of illuminate yesterday. Couldn't determine if this was already part of the rom or another update to the kernal. In any event it did add some pep to it. Haven't figured out all the improvements yet. It did however mesh nicely with illuminate.

For the record I think this kernel is only compatible with illuminate and bos. Flashing this or clemsyns ver11 onto Flashback breaks the wifi.

ramerco said:
This thread has turned into a joke with no information other than a re-compiled version of pershoot's kernel.
Can it be closed please.
Click to expand...
Click to collapse
No, it is working well. Thanks dev we appreciate all your work. Been driving this one around for a few days to see what was different -- speed. Still investigating but don't stop because you are the only HC dev that works on the kernal and the rom itself we definitely need more like you. Looking forward to your next works!

Kernel source needs provided as per GPL. All this looks like is a rebranding of someone else's kernel - to dispel that belief please provide source and changes or else this will be removed as it would be in violation of the rules.

edirector said:
No, it is working well. Thanks dev we appreciate all your work. Been driving this one around for a few days to see what was different -- speed. Still investigating but don't stop because you are the only HC dev that works on the kernal and the rom itself we definitely need more like you. Looking forward to your next works!
Click to expand...
Click to collapse
He would need a 'first' work to have any 'next' works. Someone who actually took the time to research a little web history might find that the guy is merely a thief of others' ideas and work. They might find that the guy also has multiple usernames and accounts on various threads, in different forums, and actually "talks to himselves" in those threads. They also might find that the guy is also pretty much clueless, and would have exactly a 0.0% chance of developing his own kernel.
I'm not saying they would, I'm just saying they might.
I'd run stock on my Gtab before I ever TOUCHED this.
Just sayin.
By the way, 'eDirector'...In no way was I implying that you could be just another one of linuxboxsolution's 'NPC's.
Of Course I wasn't.

REMOVED my post, as it's off-topic and no longer relevant.

roebeet said:
When I posted in the other thread, I did mention that I didn't know the history - I suppose this is the "other" thread that some had mentioned?
Again, I haven't delved into this kernels and mods, and I do agree mostly with what tlbardelljr had written - "stealing" is a very gray area here. Most of my own ROMs are just mash-ups of other people's work that I tried to make into something more usable for me, and possibly the community.
But, I usually try to give credit also. If I'm using pershoot's ROM, I document that. If I'm using gojimi's framework changes for Brilliant Corners, I give him a nod. If I'm using the Adam HC base for BoS, I give them a nod as well. It's not only good manners, but it's also part of the rules here. If you're going to take, you should give credit. It's not rocket science.
I am not saying that's what's going on here - I haven't looked into these allegations, myself. But jerdog had commented two days ago and I think his comment is not only valid but it's something that needs to be responded to by the OP. That would certainly answer the question and put this to rest.
Click to expand...
Click to collapse
Hello Roebeet,
This may help but I am not sure for I am not a developer...Git Hub Source Location: https://github.com/linuxboxsolution/LBSGtab. Boy I wish I was for I would be on my way to Silicon Valley with my latest brainstorm for the Android platform that's why I respect what you guys can do so much. I can package your coding, sweetly I might add, but I am not a coder.

REMOVED my post, as it's off-topic and no longer relevant.

Offended by what's going here!
Comments removed as promised.

REMOVED my post, as it's off-topic and no longer relevant.

[Q] CM7 Nightly - Will these features be implemented?

I'm currently on CM7 Nightly #7 and was wondering if the following features would be implemented:
- Google Talk Video/Voice chat (stock MotoBlur GB update had this)
- 1% Battery Mod
- Overclocking
If none of those are set to be implemented, is it safe to install the above 3 using CWM like I normally would? Also, will Webtop work if I manually install it using CWM?
I'm assuming I can find the above 3 and Webtop lying around in forums?
Thanks.

Kaaji1359 said:
I'm currently on CM7 Nightly #7 and was wondering if the following features would be implemented:
- Google Talk Video/Voice chat (stock MotoBlur GB update had this)
- 1% Battery Mod
- Overclocking
If none of those are set to be implemented, is it safe to install the above 3 using CWM like I normally would? Also, will Webtop work if I manually install it using CWM?
I'm assuming I can find the above 3 and Webtop lying around in forums?
Thanks.
Click to expand...
Click to collapse
Umm...Ok. Google Talk, whether it be video/voice/otherwise is not installed or included with CM7 and as far as I KNOW, never will be. They keep the CM project clean of anything that doesn't come stock with Android, and Google Apps (a package that can be downloaded seperately and installed) are OPTIONAL, I don't think they would ever push it down our throats. Second, 1% battery mod IS included, just dependent on the theme you have whether or not it's showing you the % or not. There is actually a setting to change the battery icon now under Settings---Cyanogenmod Settings--Interface---Status Bar or something to that affect. Third, overclocking/underclocking/undervolting is all kernel dependent. The kernel that is currently being rolled out with the nightlies and the stable release is not capable of this. It runs at stock voltages and stock frequencies. Faux123 has several kernels that will work with these versions of CM7 however.

^the reason why google apps arent included is because google sent cyanogen a cease and desist letter because the apps arent open source. it almost completely killed CM development.

Phalanx7621 said:
Umm...Ok. Google Talk, whether it be video/voice/otherwise is not installed or included with CM7 and as far as I KNOW, never will be. They keep the CM project clean of anything that doesn't come stock with Android, and Google Apps (a package that can be downloaded seperately and installed) are OPTIONAL, I don't think they would ever push it down our throats. Second, 1% battery mod IS included, just dependent on the theme you have whether or not it's showing you the % or not. There is actually a setting to change the battery icon now under Settings---Cyanogenmod Settings--Interface---Status Bar or something to that affect. Third, overclocking/underclocking/undervolting is all kernel dependent. The kernel that is currently being rolled out with the nightlies and the stable release is not capable of this. It runs at stock voltages and stock frequencies. Faux123 has several kernels that will work with these versions of CM7 however.
Click to expand...
Click to collapse
Sorry I should've rephrased the Google Talk question; I guess I should've phrased it as will it ever come with the optional Google package that I installed via ROM Manager.
Anyway, thanks so much for your help! I found the battery option and I will get to installing the voice/video Google Chat and a new kernel soon.

Kaaji1359 said:
Sorry I should've rephrased the Google Talk question; I guess I should've phrased it as will it ever come with the optional Google package that I installed via ROM Manager.
Anyway, thanks so much for your help! I found the battery option and I will get to installing the voice/video Google Chat and a new kernel soon.
Click to expand...
Click to collapse
It's already included, just tick the video option when you install gapps from ROM Manager, or flash the 2nd "-newtalk" zip

turl1 said:
It's already included, just tick the video option when you install gapps from ROM Manager, or flash the 2nd "-newtalk" zip
Click to expand...
Click to collapse
^ This. I never download it or use it, but it should ALWAYS give the option as Turl said when downloading from Rom Manager.

[ROM][ICS][alpha1]ICYXMAS p5wifi ICS build for GTab 8.9 GT-7310

**Last update! This thread will (shortly) be locked, and a new one will be posted With Galaxian-Soup ICS Alpha 2
Check back in a few hours!
**Update, this tread will be retired and locked come this Thursday 1/5/2012
Read between the lines, and you will see that a brand new thread in its place will be posted, complete with a yummy new alpha of ICS for our dedicated fans to enjoy... We thank you for your patience, after this alpha goes out we believe tere will be more frequent releases and postings
Stay tuned, but from what I've seen so far we have many surprises in store for our next release, and you, is ICS nirvana just around the corner? Check back on thursday!
Please don't take this to mean we've fixed every outstanding bug, but we have made major core improvements, and fixed some of the big "items"
We are seaking anyone with expeirence working HAL's and drivers.. if you are interested please PM me.
TTFN!!
** Update ** Work around for voice search
It appears that voice search is broken in several AOSP roms, during my research I managed to get voice search working, however its the older version (prior to ICS). So far it seems to work fine!
So until Google fixes (or we do hah) do this to get voice search to work
Download
Voice_Search_2.1.4
Go to the location the this file was downloaded and from a terminal (linux/mac) or the command prompt (windows)
Code:
adb shell
su (if not root)
rm /system/app/VoiceSearch.apk
reboot
Then side load adb Voice_Search_2.1.4
Code:
adb install Voice_Search_2.1.4.apk
After the install click on the microphone icon near search at the top left of the home screen, accept the permissions (you have to do this a few times, 3 by my count), don't panic if it asks a few times, it does stick.
Enjoy!
** Update** Happy New Year XDA and esp our friends with the Galaxy Tab 8.9! is this the year of the droid? We shall see!
Hey everyone I wanted to give everyone an update and general goings on! Im sorry to inform you that there will not be a New Years alpha, but we will have something for you all very soon after.
Here is a taste of what early 2012 will bring to Alpha 2.
1. We have decided to use ASOP source rather than Cyanogen Mod, this is primarily why there hasn't been a new release since xmas. After reviewing some of the initial bugs, and reflecting on what we accomplished in under 4 days, we decided we wanted the focus of this rom to become "best in breed" optimized for the Galaxy Tab 8.9. Meaning we are going to cherry pick the best features of both to create the best possible experience, with the lightest footprint, and most importantly stock ICS launcher! NoWiz, no Trebuchet. So far it has yielded very positive results.
2. Moving to ASOP and stock launcher has fixed one of the big bugs, automatic home screen orientation. I know more than a few of you were hoping this would be resolved fast, well there.. happy now?
3. MTD
4. General cleanup and optimizations have resulted in improved launcher response, it feels more fluid and less laggy...
5. Our repo is nearly finished, we are just ironing out some manifest bugs, when alpha2 arrives, so will our git links!
6. We have chosen a team name! Galaxian-Soup!
Thanks for supporting us, and we look forward to celebrating a "Droid 2012".
In the spirit of openness, if you would like to use our rom in your work please credit us in your OP and release notes. Our git repo should be up soon.
***Update*** Xmas Dinner Edition ***
Updated links to a 1.1 version, I added the livewallpaper.apks and re-zipped, no other changes.
and a newer version of Google Apps, seems to be more stable, but I've only been using it an hour, let us know!
Good Morning and Merry Christmas!
Is there something in your stocking for your GT7310? Well Santa Clause (in the form of _Motely, nycbjr, poisike, termleech (still need a team name!)) is delivering the first public alpha!
This build has been tested on the 7310 (Gtab 8.9 wifi, no 3g), and 7300 with no 3g (3g is being looked at).
Standard YMMV tag: You are flashing this at your own risk, make a nandroid backup first! If this breaks your tab we are NOT responsible.. now go play and have fun!
ICYXMAS-p5wifi-alpha1.1-cwm
icyGapps V2
Alpha V1 - ICYXMAS!
ICS 4.0.3_r1 vanilla
Rooted, deodexed,
Includes motley kernel v2e beta (see his thread for git details)
WiFi, GPS, Bluetooth
Installation:
In CWM recovery, clear your data/factory reset
Clear the dalvik cache (under advanced, or under the wipe menu in overcome cwm)
Flash the provided zip using CWM recovery
Flash gapps from CWM recovery
Bootup and setup your Google account
Install cpu control of choice, and set to interactive governor (this is required!)
​*tested SetCPU, No-frills CPU control, and Antuantu.
Give it a chance, this is a deodexed ROM and will boot slow the first time and when you use apps the first time.
Doesn't work/Limitations:
WiFi-only, but 3G will be looked at for a future version (no ETA at the moment)
Camera doesn't work, don't know when or if it can be fixed.
Some video limitations, youtube HD vids not working. Some stuttering will occur until we get the kinks out.
Charger screen doesn't look correct when you plugin without booting up (charging status)
Voice search doesn't work - May have something to do with this error:
W/PackageManager(257): Failure retrieving resources forcom.google.android.voicesearch: Resource ID #0x0
Probably more that we haven't listed, this is an alpha - please let us know.
Team members:
nycbjr - project manager, dev (first working build), testing/troubleshooting
motley - lead dev, p5 device tree, final build, kernel development
poisike - pioneer testing with other tegra ICS ROMs, testing/troubleshooting
termleech - testing
Credits:
Google - for the releasing the OS
Cyanogen Mod Team - for their awesome git repo and developers. We used the p4 device tree as a starting point.
We would like to offer our p5 device if they are interested.
Samsung for the awesome device and kernel source (for HC 3.1 at least)
digetx - for pointing us in the right direction on the green frame buffer fix!
alterbridge - for his CWM Recovery port for 73xx.
JaeCar99 - for the sweet "Blue Hallway" bootanimation

I'm looking forward to a fully working ICS rom But a good thing takes time. Keep up the good work, guys!

great to see this development start
Sent from my HTC Incredible S using Tapatalk

Do you guys want some help? I'm currently working on a rom for the nexus with some other guys but could lend a hand here as well. What's the best way to get a hold of you guys?
Sent from my Full AOSP on Maguro using Tapatalk

termleech said:
Do you guys want some help? I'm currently working on a rom for the nexus with some other guys but could lend a hand here as well. What's the best way to get a hold of you guys?
Sent from my Full AOSP on Maguro using Tapatalk
Click to expand...
Click to collapse
I would never turn down any help, I'm very new at this (long time sysadmin, but only been a droid head since march hah).
Only caveat is you will need approval from motley before I can release anything to you, for now you can PM me and I will give you my aim/gchat and offline email, but I think we should setup an IRC, or aim/gmail chat to make this go faster.
As this is coming from CM9 sources I need to contact them too, I don't want to flub any licensing issues, etc, and maybe they will want to help, or us to help them!

Awesome! Thanks fellers!

great work

_motley said:
As far as WiFi, the P4 (Galaxy 10.1) uses a broadcom 4329 and we (the P5) uses the newer 4330. This is where the challenge will come it. When I get a better look at the Android code and have a flash up and running, hopefully it will become clear if something needs to be done on the kernel side or the Android side. If we start making good progress, we will need to get a git setup for our P5 stuff so we can share changes and files etc.
Click to expand...
Click to collapse
I don't know... I just flashed my P7300 with P7500 rom and wifi driver loads just fine. I only edited the build.prop and used a kernel from overcome rom, i didn't touch anything else. Also if you look in \system\etc\wifi you will see that both 7500 and 7510 roms have bcm4330 files there, so it looks to me that the wifi card is the same as our.
I also tried the kernel you sent me with 7500 rom and wifi driver still loads.

this is awesome guys.. after the posts yesterday and staying up till 3:Am , I got the sucker booting.. of course that was it though. Great to see this post today.. Sounds like it's not too far off.. at least for me wifi would be the only thing left that's important since I havent touched the camera app or bluetooth yet.

poisike said:
I don't know... I just flashed my P7300 with P7500 rom and wifi driver loads just fine. I only edited the build.prop and used a kernel from overcome rom, i didn't touch anything else. Also if you look in \system\etc\wifi you will see that both 7500 and 7510 roms have bcm4330 files there, so it looks to me that the wifi card is the same as our.
I also tried the kernel you sent me with 7500 rom and wifi driver still loads.
Click to expand...
Click to collapse
right, I'm going back over the source, and the board config, some wifi stuff seems commented out. I know I need to get on irc.. but work interjects lol..
for the record on linux to use broadcom it has to extract the firmware for the card, I don't think it has to for droid as in this case the firmware is provided to us. I should probably stop spinning my wheels and go back and read/learn more about how android treats these things.
I am all ears however, anyone with debugging exp can have the rom with permission to use the kernel from motly.

I don't think that the problem is in your build. I have tried 3 different builds and they all have the same error:
Code:
ERROR/WifiStateMachine(168): Failed to load driver!
ERROR/WifiStateMachine(168): DriverFailedState
So it looks to me that the problem is in kernel. Of course i could be wrong.
Also it looks to me that the bcm4330 driver source is posted on github (https://github.com/cyanogen/galaxy-2636/tree/ics/drivers/net/wireless/bcm4330), so i hope _motley finds time to take a look.

poisike said:
I don't think that the problem is in your build. I have tried 3 different builds and they all have the same error:
Code:
ERROR/WifiStateMachine(168): Failed to load driver!
ERROR/WifiStateMachine(168): DriverFailedState
So it looks to me that the problem is in kernel. Of course i could be wrong.
Also it looks to me that the bcm4330 driver source is posted on github (https://github.com/cyanogen/galaxy-2636/tree/ics/drivers/net/wireless/bcm4330), so i hope _motley finds time to take a look.
Click to expand...
Click to collapse
ok thanks I was looking at the source on my build system remotely, and the drive went oiffine, I think my ssd is going, so I'm going to get a new on on the way home. pisses me off!

Great work!
I'm seeing forward to try this out.
Gesendet von meinem GT-P7300 mit Tapatalk

poisike said:
I don't think that the problem is in your build. I have tried 3 different builds and they all have the same error:
Code:
ERROR/WifiStateMachine(168): Failed to load driver!
ERROR/WifiStateMachine(168): DriverFailedState
So it looks to me that the problem is in kernel. Of course i could be wrong.
Also it looks to me that the bcm4330 driver source is posted on github (https://github.com/cyanogen/galaxy-2636/tree/ics/drivers/net/wireless/bcm4330), so i hope _motley finds time to take a look.
Click to expand...
Click to collapse
Sorry, I misspoke, the 10.1 does indeed use the 4330 like us...been looking at Iconia, Xoom, and ASUS TF1 ROMs too much lately.

Well other than the green screen affect, wifi, camera,bluethooth this thing really runs well.
HC was a pig for memory, as I noted on my Acer when I ran ICS for a bit, memory mamagment is hugely improved over honeycomb, I never had more than 200mb free on a regular basis, with ICS its well over 400mb.
and the thing really cooks along, I snap in and out of screens really fast, and angry birds works! haha
I will spend some time tonight on wifi, and making a new build.
poisike I'll setup irc tonight, I may have to rebuild the macpro, who knew running an os other than apple would cause a problem lol..

_motley said:
Sorry, I misspoke, the 10.1 does indeed use the 4330 like us...been looking at Iconia, Xoom, and ASUS TF1 ROMs too much lately.
Click to expand...
Click to collapse
The otapackage build does spit out a file called "kernel" would that help you any?
I can drop it in my dropbox
actually there is a boot.img.cm9 in my alpha zip you have, but I can still upload just the file called kernel if yoi think it would help.
also once I have my macpro back in op I'm not against setting up accounts for you and poisike, or setting up our own git repo, would be beneficial to work against the same source once we zero in and attempt to create a working port for everyone.
oh and btw, your OC settings work, running ICS at 1.4ghz

This is great news!! Once the wifi is working, I'll be using this as my daily driver. Will this be a completely AOSP project or still based on TouchWiz. I wish I could have stock e-mail, calendar, etc.

Excellent news! I will be waiting patiently....

Asop only! "Don't wiz on my ICS"
Sent from my SGH-I777 using xda premium

nycbjr said:
The otapackage build does spit out a file called "kernel" would that help you any?
I can drop it in my dropbox
actually there is a boot.img.cm9 in my alpha zip you have, but I can still upload just the file called kernel if yoi think it would help.
also once I have my macpro back in op I'm not against setting up accounts for you and poisike, or setting up our own git repo, would be beneficial to work against the same source once we zero in and attempt to create a working port for everyone.
oh and btw, your OC settings work, running ICS at 1.4ghz
Click to expand...
Click to collapse
That sounds like it is just the zImage binary for their build, I think I remember seeing it there too. It won't do me any good. Sounds good about the repo. I can still browse the repos to look at code as necessary for the time being. Glad to hear that the OC is is still working good.
I just sent poisike a 3G kernel with the touchscreen fix so he can start working on that end.
"Don't wiz on my ICS!" haha

[POLL] PDroid Permission Management: do you want it?

UPDATE: PDROID NOW AVAILABLE VIA BOTBREW:
http://forum.xda-developers.com/showpost.php?p=26033156&postcount=10
First, for those who haven't heard about it:
PDroid
PDroid ICS Port
At this point, as far as I can tell, PDroid is only available as a patchset, not in any rom.
It looks like it is a lot more powerful than CM Permission Management.
The purpose of this poll is so Vibrant users can show interest in a rom with PDroid built in, hopefully motivating rom devs to add it.

I'll check this out tonight - looks interesting.

jellette said:
I'll check this out tonight - looks interesting.
Click to expand...
Click to collapse
I'm not set up to develop at present, but I'll try any CM or ICS open-source rom that has this built-in, or an open-source zip to hot-patch it into said roms.

Yeah pdroid looks awesome! I asked about this in slim forum and cm forum somewhere around here but got no love lol... its really awesome permission management and if they add a firewall it would be a must need app that I would love to buy... you can use it with droidwall but it has leaks and allows access before it loads up on reboot... pdroid could block that from the start if it had a firewall incorporated tho... I look forward to the development of this awesome app.

Looks like we might get a try ourselves with an ics patcher in the not so far off future
Sent from my SGH-T959 using XDA

An ICS patch does appear to be in the works.
As for CM, you're right, it will never have PDroid, and I'm really beginning to wonder if they will even bring any permission management into CM9. If you look at the PDroid patch, it's not a huge amount of code, meaning if Google wanted android to allow privacy, they would have added it long ago. But the frankly rather seedy business model of Google and many "free" app writers and Facebook is the harvesting and selling of personal information, and they apparently threatened to cut CM off from Market access if they added strong privacy.
Clearly the long-term solution is Google-free phones running Debian or Ubuntu, but until then, there's PDroid.

Pdroid Linux patcher ported and working for aokp and cm9
Sent from my SGH-T959 using XDA

c-pimp said:
Pdroid Linux patcher ported and working for aokp and cm9
Click to expand...
Click to collapse
Nice. Where?

Pdroid working for AOKP and CM9
PDroid is finally available for AOKP and CM9 on T959 Vibrant via botbrew. Follow instructions at http://forum.xda-developers.com/showpost.php?p=24934484&postcount=123 big thanks to mateorod for porting it over.

Hey guys-
UPDATE 6-5-12
I haven't had any requests for updated packages except for AOKP, so I can only confirm that AOKP Build 40 and CM7rc2 are currently supported! Any other ROMS are at your own risk! If you would like a ROM for vibrant or any other device to be supported, please post a request.
Okay, this is directions for PDroid support through Botbrew. Installing these packages over your nightlies will get PDroid working each time you flash, without having to patch every time. This way you can update your rom whenever you want.
Here is the XDA frontpage article about this exact process!
IMPORTANT: Eventually, the source code for these ROMs will change to a large enough degree that the packages won't work anymore! Just reflash the ROM and come report here at the thread. I will update the package as soon as possible (usually pretty damn soon, if I do say so myself...)
Directions
Install Botbrew from Google Play
Botbrew will bootstrap some packages necessary for its operation.
Install package repository-mateorod and press the refresh button.
There are three packages available at the moment for the Vibrant. Install the package that matches the ROM you are using.
android-framework-pdroid-cm9
For Cyanogen9 ROMs
android-framework-pdroid-aokp
For AOKP Milestone builds
android-framework-pdroid-aosp-gummy
For Team Gummy AOSP builds
New!
android-framework-pdroid-cm7.2final
For CM7.2 Final!
YOU MUST install the package that corresponds with your ROM, or it will result in bootloops!
Reboot!
Launch PDroid and configure.
That's it!
Note: You won't see any of the packages if you look while running CM7 due to an inconsistency in the cm7 build.prop.
If you have any questions about Botbrew or the process, here is a Q&A I have at the thread for my packages I host for the Nook Color.
If you have any questions about PDroid and the port to ICS, here is pastime1971's thread on the process. Thanks pastime!
Also thanks to c-pimp for the Team Gummy files! Also to svyat for PDroid and inportb for Botbrew!
cashmundy- could you maybe put a note in the OP about this being here? If you think I should start a new thread, I will. Thanks!

I confirm this is working with the 5-12 CM9 nightly. Thanks to mateorod and everyone he thanks in the post above!

Thanks, cashmundy. The problem was that cm9 has a weird naming convention for just your device, at least unique as far as I have seen.
I just changed the package to reflect your arch.conf.
So thanks very much for testing and finding the problem. I am pretty sure everything is OK now, but let me know!

Still on CM9. Did a reset, installed botbrew and your repo, and I now have no pdroid package.
As expected, botbrew fetched the CM9 props on install
, except that it down-cased the model to "sgh-t959".
arch.conf:
arch all 10
arch any 20
arch noarch 30
arch armeabi 100
arch armeabi-v7a 110
arch sgh-t959 120
build.props:
ro.product.model=SGH-T959
ro.product.brand=samsung
ro.product.name=SGH-T959
ro.product.device=SGH-T959
ro.product.board=aries
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi

Okay man. I took out the sgh-t959 package because I thought you said cm9 had vibranttmd as arch.
Are you saying that it changes whether or not you install cm9 as an update? Cause I don't see how that would be.
I am going to make it so Botbrew has cm9 packages for sgh-t959 and vibrantmtd. We'll sort it out for good later tonight when I have some time.
Thanks for your time and effort testing this stuff!

CM7 has vibrantmtd as ....device and SGH-T959 as ....model. CM9 has SGH-T959 as both model and device, as does AOKP. If you (or BotBrew) could use model instead of device, it might work well.
What happened before was I tried CM9 over CM7 without a reset. BotBrew didn't catch the upgrade, and so kept the conf from CM7. When I reset and then installed BotBrew, it found the new props and configured accordingly. A hook in BotBrew to check the current rom on startup and reconfigure itself on flashes would be a good thing.
I'm currently showing all three packages, version -9.
One minor note: somewhere you specify the BotBrew refresh button as being on the top right. On my phone it is always on the bottom left. Maybe more vibrant weirdness.
Final random thought: I'm not very impressed with CM9. It has some real drawbacks (the keyboard for example).
CM7 is still overall a lot better (to me) and if PDroid ever makes it there, I'll test it.

Well, I am still considering about cm7. Let me see.
Botbrew does has services you can turn on to configure at boot, as well as several ways it detects flashes, although most of those are centered around packages or the terminal.
But thanks for those tips, there is definitely some weirdness going on with the vibrant that I haven't seen elsewhere, but is good to know about because it could resurface in other devices.
But yeah, for instance, you could use light pad to turn your sdcard into a web server, and host websites off of it, so that's one of the services options.
There is honestly a world of stuff in the repo already, and he's about to add debian INSIDE android.
Crazy. Thanks, cashmundy. I will look into cm7.

Very cool.
I think I'll try AOKP again when a new build is out, and test the patch there.
One thing that would be useful would be a white-hat app which would request all permissions, gather all possible data, and display it. As it stands, we have to take it on faith that pdroid, droidwall etc actually work.
For the long term, I am very much hoping for Debian instead of android.

mateorod said:
Hey guys-
Most everyone in this thread I already know from the port thread. I was looking for a good place to put out this info. Glad I didn't start another thread already!
Okay, this is directions for PDroid support through Botbrew. Installing these packages over your nightlies will get PDroid working each time you flash, without having to patch every time. This way you can update your rom whenever you want.
Here is the XDA frontpage article about this exact process!
IMPORTANT: Eventually, the source code for these ROMs will change to a large enough degree that the packages won't work anymore! Just reflash the ROM and come report here at the thread. I will update the package as soon as possible (usually pretty damn soon, if I do say so myself...)
Directions
Install Botbrew from Google Play
Botbrew will bootstrap some packages necessary for its operation.
Install package repository-mateorod and press the refresh button at top right!
There are three packages available at the moment for the Vibrant. Install the package that matches the ROM you are using.
android-framework-pdroid-cm9
For Cyanogen9 ROMs
android-framework-pdroid-aokp
For AOKP Milestone builds
android-framework-pdroid-aosp-gummy
For Team Gummy AOSP builds
YOU MUST install the package that corresponds with your ROM, or it will result in bootloops!
Reboot!
Launch PDroid and configure.
That's it!
Note: You won't see any of the packages if you look while running CM7 due to an inconsistency in the cm7 build.prop.
If you have any questions about Botbrew or the process, here is a Q&A I have at the thread for my packages I host for the Nook Color.
If you have any questions about PDroid and the port to ICS, here is pastime1971's thread on the process. Thanks pastime!
Also thanks to c-pimp for the Team Gummy files! Also to svyat for PDroid and inportb for Botbrew!
cashmundy- could you maybe put a note in the OP about this being here? If you think I should start a new thread, I will. Thanks!
Click to expand...
Click to collapse
Ok, at the risk of annoying someone (due to my noobness) I wanted to ask if I could do the above for my kindle (which i just flashed with AOKP milestone 5) or is the above strictly for the sammy vib?

gaikokujinkyofusho said:
Ok, at the risk of annoying someone (due to my noobness) I wanted to ask if I could do the above for my kindle (which i just flashed with AOKP milestone 5) or is the above strictly for the sammy vib?
Click to expand...
Click to collapse
The Vibrant is I think the most recent device, and the BandN Nook is supported,
so I expect the Kindle will be someday.

gaikokujinkyofusho said:
Ok, at the risk of annoying someone (due to my noobness) I wanted to ask if I could do the above for my kindle (which i just flashed with AOKP milestone 5) or is the above strictly for the sammy vib?
Click to expand...
Click to collapse
If you run cm9 or aokp, I can take care of you.
Post your services, core, and services.jar plus build.prop at my packages thread so we keep this vibrant only.
Thanks for your interest.

[TOOL/SCRIPT] freecyngn - Removing proprietary userspace parts from CM10/11/12/12.1

Introduction
Though CyanogenMod always claimed to be open-source, there were only few versions that had an open userspace (Some drivers and firmware have always been proprietary, but it's not CMs fault).
The first CM version I ever installed on a device was CM7 and it contains koush's proprietary ROM Manager app. CyanogenMod 9 seemed to have no proprietary parts, but since CM10 they included Google Analytics Client library (libGoogleAnalyticsV2.jar) within cmstats in the settings app (so it's not even possible to disable it). In CyanogenMod 10.1 CMAccount was included. It relies heavily on Google's Cloud Messaging service and includes the proprietary Google Play Services Client library (google-play-services.jar).
There are some people here at xda (including myself) that installed CyanogenMod because it does not ship GAPPS and is a fully (except vendor files) open-source and free rom. Since i noticed it's not, i started building CM without these closed-source stuff, but it's a pity to do so. That's when the idea of freecyngn started.
What is freecyngn
freecyngn is a tool you can run from recovery, that removes some known proprietary things (or apps relying on proprietary extensions) from CyanogenMod. At the moment this is Google Analytics (from CMStats in CM10/11), CMAccount, LockClock, SetupWizard, Voice+, VoiceDialer and WhisperPush.
Installation Instructions
Copy or download the zip file to the sdcard of your android device
Boot your device into recovery.
If not already done, install CyanogenMod as usual from recovery - DO NOT REBOOT
Install freecyngn as if it was a rom, but DO NOT WIPE /system before
CyanogenMod 12/12.1The version for CyanogenMod 12 should not be used on nightlies before July 9, 2015!
Changelog
v1.0: First release for CM12
Downloads
Latest release (v1.0): https://github.com/mar-v-in/freecyngn/releases/download/v1.0/freecyngn-flashable-cm12.zip
All releases: https://github.com/mar-v-in/freecyngn/releases
Source: https://github.com/mar-v-in/freecyngn​
CyanogenMod 10/11
Changelog
v0.5: Latest fixes, better logs
v0.4.1: Remove LockClock (uses Google Play Services)
v0.4: Adapt to latest changes, remove VoiceDialer as well
v0.3.1: addon.d based auto repatching
v0.3: fixed logging
v0.2: Now creating logfile: /system/freecyngn/log
Downloads
Latest release (v0.5): https://github.com/mar-v-in/freecyngn/releases/download/v0.5/freecyngn-flashable-cm1011.zip
All releases: https://github.com/mar-v-in/freecyngn/releases
Source: https://github.com/mar-v-in/freecyngn
How it works (technical stuff)
freecyngn disassembles (using [bak]smali) the CyanogenMod settings app and removes the proprietary Google Analytics component. It then replaces it with NoAnalytics, so that existing bindings from cmstats do not break and reassembles the settings app.
FAQ
Q: My recovery hangs while flashing?
Q: Why is this script so slow?
A: freecyngn need plenty of time and is sometimes even slower than flashing the rom itself. This is bcause most recoverys underclock the cpu, which is no problem for just copying files from zip to partition or format a partition, but it is a problem for disassembling and reassembling, which are cpu intensive tasks.
Q: Do I need to apply the patch after every update?
A: Since v0.3.1 this is no longer needed. Patching is done automatically.
Q: What's about other custom ROMs?
A: AOKP is patchable with freecyngn as well. Paranoid contains Google Analytics in the proprietary ParanoidSettings app instead of the system settings and thus does not work with this patch. OmniROM does not contain Google Analytics. Note that some slimmed-down CM/AOKP-custom-builds will not work with freecyngn. If you use such, check the log file /system/freecyngn/log after flashing.
XDA:DevDB Information
freecyngn, Tool/Utility for the Android General
Contributors
MaR-V-iN
Source Code: https://github.com/mar-v-in/freecyngn
Version Information
Status: Stable
Current Stable Version: v1.0
Stable Release Date: 2014-08-07
Created 2013-12-01
Last Updated 2016-07-02

Its work in android 4.4 kitkat Ah?

Pretty interesting stuff, I didn't knew you could assemble/disassemble dex files on the device. Anyways, I wanted to tell you, you can just boot the cpu freq to make it faster.
just grep cpuinfo_max_freq and use that number for scaling_max_freq

This is really cool... definitely going to try this out,

Subscribed

Flashed on cm10.2 on evo3d. Only took about 3seconds for me. Thanks
Sent from my Evo 3D CDMA using XDA Premium 4 mobile app

MaR-V-iN said:
Introduction
What is freecyngn
freecyngn is a tool you can run from recovery, that removes some known proprietary things (or apps relying on proprietary extensions) from CyanogenMod. At the moment this is Google Analytics (from CMStats), CMAccount and Voice+.
Click to expand...
Click to collapse
I always remove CMAccount and Voice+ as they are system apps but isn't removing CMStats the same as disabling About Phone>CyanogenMod Statistics>Enable Reporting?

ela1103 said:
Its work in android 4.4 kitkat Ah?
Click to expand...
Click to collapse
I'm on beanstalk 4.4 and worked fine.
Sent from my GT-N7105 using Tapatalk 4

Thanks, will try this now!

jdstrydom
thank for u reply

Sir what is the use of it
I.mean by removing the google support what will we get
And how is this useful
Please tell me sir

ela1103 said:
Its work in android 4.4 kitkat Ah?
Click to expand...
Click to collapse
I tried it on the CM11 build for mako, so I highly assume it's working on all CM11 based roms.
broodplank1337 said:
just grep cpuinfo_max_freq and use that number for scaling_max_freq
Click to expand...
Click to collapse
I'm aware of this method, but I don't think it's a good idea in general, because on some overclocked kernels cpuinfo_max_freq could be really unstable.
jbonetwo said:
I always remove CMAccount and Voice+ as they are system apps but isn't removing CMStats the same as disabling About Phone>CyanogenMod Statistics>Enable Reporting?
Click to expand...
Click to collapse
It's not removing CMStats completely but only the Google Analytics part. Sending stats to stats.cyanogenmod.org will still work.
Moreover, you can't really say if Google Analytics is disabled. Due to it being proprietary code, it could do nearly anything and the class initializer code is called, even if CMStats is disabled. (I assume they're not doing this, but you can;t know and they always could add this in a future version)
aditya rathee said:
I.mean by removing the google support what will we get
And how is this useful
Click to expand...
Click to collapse
First: This does not remove Google Support in general. You could still install GAPPS afterwards, but it would be kind of senseless.
Second: Some people think, that Google is not this "don't be evil" company they're proposing to be. And some people like the idea of privacy and not getting totally tracked by Google, so they do not install GAPPS. If this is not the case for you, then this is just not targeting you. I'm not going to try to convince anyone that privacy is a good thing

MaR-V-iN said:
I tried it on the CM11 build for mako, so I highly assume it's working on all CM11 based roms.
I'm aware of this method, but I don't think it's a good idea in general, because on some overclocked kernels cpuinfo_max_freq could be really unstable.
It's not removing CMStats completely but only the Google Analytics part. Sending stats to stats.cyanogenmod.org will still work.
Moreover, you can't really say if Google Analytics is disabled. Due to it being proprietary code, it could do nearly anything and the class initializer code is called, even if CMStats is disabled. (I assume they're not doing this, but you can;t know and they always could add this in a future version)
First: This does not remove Google Support in general. You could still install GAPPS afterwards, but it would be kind of senseless.
Second: Some people think, that Google is not this "don't be evil" company they're proposing to be. And some people like the idea of privacy and not getting totally tracked by Google, so they do not install GAPPS. If this is not the case for you, then this is just not targeting you. I'm not going to try to convince anyone that privacy is a good thing
Click to expand...
Click to collapse
ok ok
now i am gonna flash it

MaR-V-iN said:
It's not removing CMStats completely but only the Google Analytics part. Sending stats to stats.cyanogenmod.org will still work.
Moreover, you can't really say if Google Analytics is disabled. Due to it being proprietary code, it could do nearly anything and the class initializer code is called, even if CMStats is disabled. (I assume they're not doing this, but you can;t know and they always could add this in a future version)
Click to expand...
Click to collapse
Thank you for the info. I would not have thought to look at the Settings app for undesirable activities.
Found the following activities for Settings in Sys Tuner:
UsageStats
Settings$AnonymousStatsActivity
DeviceInfo$StatsReportReceiver
cmstats.ReportingService
Will be flashing your zip for a 'cleaner' solution than sys tuner in the near future.
And yes google is evil . Their handling of adblock and similar apps shows they're motivated by money and I wouldn't give a corp like that free reign over my device. But that's just me...

Ran this script on my rooted stock KitKat ROM @ Nexus 4 & 7, so far no abnormal activity observed on my devices...

So if we run this app, can we still use gapps or is that considered one of the tracking apps that will be removed?

flashed it on my 4xHD, will see how it will behave
i had really quick install of the zip file, like i would install kernel
that is normal or ?
because in op you say that install will take some time

Do you know if this will work on all cm based roms or only actual cyanogen?
Sent from my SCH-I545 using XDA Premium 4 mobile app

pr0di9y said:
Ran this script on my rooted stock KitKat ROM @ Nexus 4 & 7, so far no abnormal activity observed on my devices...
Click to expand...
Click to collapse
rrrrrrredbelly said:
Do you know if this will work on all cm based roms or only actual cyanogen?
Click to expand...
Click to collapse
This is only for CM-based roms that contain CMStats. The Script does nothing useful on Nexus stock or not-CM-based ROMs, these do not include Google Analytics in the Settings app (yes that's right: CM+GAPPS does more Google tracking than Google's stock)
The new v0.2 release creates a log file in /system/freecyngn so you can make sure everything worked great.

MaR-V-iN said:
This is only for CM-based roms that contain CMStats. The Script does nothing useful on Nexus stock or not-CM-based ROMs, these do not include Google Analytics in the Settings app (yes that's right: CM+GAPPS does more Google tracking than Google's stock)
The new v0.2 release creates a log file in /system/freecyngn so you can make sure everything worked great.
Click to expand...
Click to collapse
Does this explain why they have these stats on hand?
developer.android.com/about/dashboards/index.html