**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
Related
Vanilla Flavored AOSP
Gtablet AOSP is a project for pure vanilla Android with the Gtablet. It aims to be barebones and as true to the AOSP code as possible. The Google AOSP code is modified as little as possible to provide functionality, and the ability to boot. It is stripped down for modification by the end user.
Using CyanogenMod device files, Pershoot's latest kernel (20110328, 2.6.32.36), and some cherry picked cyanogenmod/nv-tegra files, a functional 'rom' and a github repo for this project has been created. As functionality has been added since inception, more pieces from Cyanogen are making there way in (browser fix and tweaks, some under the hood stuff, internal storage fixes, etc) to improve overall experience. All variances from original AOSP code is visible via the public git.
Huge props to the Gtablet and the Cyanogen development community. Without your work, this wouldn't be possible.
Huge thanks to EJHart for his direct assistance with this project. Also, thanks to Bekit, Pershoot, GoJimi, Cyanogenmod team, Google... and I am probably missing others... This project would not be where it is without all of their work.
To use this rom, you will use ClockwordMod to flash the zip file as you would any other rom. I have only used ClockworkMod .8 in my testing.
DISCLAIMER: I cannot be held liable for anything you do to your GTablet. Make sure you are comfortable with recovery tools, such as nvflash, before proceeding. Though the rom is quite functional and stable in basic testing, this project is in early beta stages.
Download RC2 --http://www.mediafire.com/?t2rwxm9p9e4bcb7
MD5 -- fbb79ab9f4da245bb3ab2a320369f95b
*NOTE* GAPPS 20110307 for MDPI will not work.
Use the 20110120 MDPI GAPPS (for example, http://android.d3xt3r01.tk/cyanogen/gapps/gapps-gb-20110120-signed.zip).
Known Issues:
Most if not all the issues facing Cyanogen 7
Changes since RC1:
Latest Pershoot 20110328 kernel.
Browser crash loading google.com homepage is now fixed. This should resolve browser fc across the board.
Added User Agent, Fullscreen, Zoom controls, and Incognito to Browser.
Added Reboot to Power menu (intentionally excluding the recovery/bootloader options).
Fixed EMMC and basic information for Internal Storage in Settings->Storage.
Removed phone signal indicator, and tablified numerous text values.
Latest from AOSP Master (not much new since RC1).
Removal of extraneous junk, like speech recorder, voice dialer, and mms.
Retired changelog:
RC1 - Beta2:
My Apps now works in Market. Google Maps no longer force closes. -There is a downside to this-. The fix involves altering the LCD Density, which causes some apps to not scale properly.
Media on EMMC is now scanned and available in Music/Gallery/etc.
Live Wallpapers work.
Pershoot kernel 20110307
A bunch of under the hood stuff due to major changes upstream from AOSP.
Beta2 - Beta1:
AOSP is now pulling from master branch, making it version 2.3.3_r1.
Camera functions for still pictures. No mirroring or rotation issues. Video recording still not working.
Latest NVidia 3991 libs included (noticeable performance increase).
Pershoot kernel 20110301
Beta1 - Initial release:
Fixed EMMC.
Steamlined compile process.
Addition of Spare Parts/Dev Tools (possibly removed in future versions)
BUILD YOUR OWN:
GitHub -- https://github.com/aosp-gtablet
Use this project from github to create your own image:
repo init -u git://github.com/aosp-gtablet/gtablet-aosp.git
The process for CM7 will work. Run extract-files.sh, run envsetup.sh, lunch, make -j[X] bacon. Anything more is outside the scope of this post.
** Additional notes -- GoJimi's Soft Buttons are available in the source code, but are disabled in this release.
I am a minimalist, and I know there are others. I hope others enjoy, and help make this a better project
Please let me know what bugs you find so I can work on them! Thanks.
Sold! Will give this a try and report back. Nice writeup too. Is it true, development only available on linux?
Thanks.
I have done all my work in Linux, so I wouldn't know of any other way to create an image. Sorry.
Holy crap! This rom is whip fast! Have you installed gapps or monitored battery life on it yet?
jooky2000 said:
Holy crap! This rom is whip fast! Have you installed gapps or monitored battery life on it yet?
Click to expand...
Click to collapse
I have installed GAPPS, they work with the exception of the same Market/My Apps bug found in the CyanogenMod rom. I think it's fast too. I have not run battery test, or benchmarked it thoroughly. Someone has already recommended a possible fix for the 3d textures, that might help Quadrant run successfully. Without textures and all, I did get one run of Quadrant to complete (after numerous tries) and received a ~2100 score. Not the best, I know, but it still seems very snappy.
Not a quadrant user myself. Just the feel of it is impressive. I will report back with battery stats tomorrow.
Solid work getting this to the masses. Thanks.
What's with the weird Japanese keyboard and application that's included?
jooky2000 said:
What's with the weird Japanese keyboard and application that's included?
Click to expand...
Click to collapse
I assume you're asking about the Input Method options? I did not customize those, it's built with the full build of AOSP.
Please confirm what app you are talking about.
Has anyone tried MarketEnabler to see if it fixes the market issue?
just an FYI not sure what reports are coming in about it not working with 3.0.0.5 of CWM, but I was able to install it running 3.0.0.5.
-Josh
Excellent work, guys. Once everything works this will be my primary ROM.. since my wife also uses the tablet.
Yes Japanese IME keyboard and whatever that japanese character app is.. I don't read japanese (or Chinese) heck if I know.
Cell related services murdered my battery so swapped out for now. Fast ROM though thanks for sharing.
jooky2000 said:
Yes Japanese IME keyboard and whatever that japanese character app is.. I don't read japanese (or Chinese) heck if I know.
Cell related services murdered my battery so swapped out for now. Fast ROM though thanks for sharing.
Click to expand...
Click to collapse
Can you expand on what you removed? Just certain apks?
Would you send me a copy of your extract-files.sh? I'd like to see what you're pulling. Is the audio driver for the G Tablet open source? I'd be curious to see if we can't build a 2.3 driver.
gdanko said:
Would you send me a copy of your extract-files.sh? I'd like to see what you're pulling. Is the audio driver for the G Tablet open source? I'd be curious to see if we can't build a 2.3 driver.
Click to expand...
Click to collapse
The image is built using the device files from the CM7 repo, lightly modified and forked to it's own repo. This includes extract-files.sh, which is identical to that in CM7. I didn't see a point to re-invent the wheel on this step, as bekit & co. have done such an excellent job. It does not impact on the outcome of this being an AOSP image. Among other things (like defining hardware specifics in BoardConfig.mk), the device files bring in the core libraries already on your GTablet. This includes libaudio.so.
So ive installed this bad boy but ive seemed to have lost the market any ideas
jivy26 said:
So ive installed this bad boy but ive seemed to have lost the market any ideas
Click to expand...
Click to collapse
Same problem here. Market is not present.
You have to install google apps. Use the one for cm7/gingerbread found here http://goo-inside.me/gapps/ flash the zip as you would a rom in recovery.
can you please put screenshots?
If the rom is based on GB then screen shots at this point are not possible as ddms doesnt work with GB. It looks just like plain jane vanilla android.
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.
Many of us will use CyanogenMod 10 and Siyah kernel build by gokhanmoral, as it is maybe one of the best combinaison for a powerful and smooth device. My past experience with CM7 and Syiah Kernel show me some questions will hardnessly find a right place in the CyanogenMod 10 nightly builds | DISCUSSION THREAD neither in [KERNEL][ICS] SiyahKernel v3.0 thread. The issues you may experience could in fact be due to this specific combinaison, and when posting in CM10 thread you will be told to use only the custom Cyanogenmod Kernel, and when posting in Syiah thread you will be told your issue is CM10 relative and has nothing to do with the Kernel!!
Thus the idea to create an area dedicated to users running both Syiah kernel and CM10 ROM. They won't waste time posting and being flamed on both threads. I already can see some users jumping from one thread to another one.
When posting in this thread, you will lighten the main discussion threads, and browsing them will be easier.
Before you post, do a minimum of search in both threads to ensure there is not an easy and quick answer.
Then think twice, be as much as precise as you can when presenting your issue. We all will gain in efficiency and save our time.
Please keep this thread clean and useful in order to avoid "mass browsing". Refrain from flaming and adding to the crap ; do not offense, even in case of n00bish and stupid question; avoid any needless posts about your mood such as "Go Syiah", "Codeworkx, you are the best", "I love my phone" or any out of topic consideration.
learn a litle bit about BBC Code, and try to organise your post.
Be accurate and smart as much as you can. Answering will be easier and your post will help other users.
Both main threads are heavily busy, so I hope this one will help us in getting quick answers for both advanced users AND n00bs.
[color=#ooBFFF]It is up to you now to keep this place clean and convenient.[/color]
SEE POST 2 FOR LAST UPDATES AND POST 3 FOR BOOT TO GECKO
Unfortunately Mozilla decided to drop SGS2 development. I will still let the post in case Mozilla Dev team change their mind.
All credits are given to Teamhacksung, Cyanogenmod and Gokhan for their hard and clever work. Below are links to original work:
CM9 :
XDA Forum main discussion thread : http://forum.xda-developers.com/showthread.php?t=1419102
Cyanogenmod : http://www.cyanogenmod.com/
Teamhacksung : http://teamhacksung.org/
ROM download link : http://download.cyanogenmod.com/?device=galaxys2
You can download directly the nightly build to your device with Rom manager Premium.
Unless you are a flash addict, best is now to stick with official and stable CM9, currently 9.1
http://www.cyanogenmod.com/devices/samsung-galaxy-s2
CM10:
XDA Forum main discussion thread : http://forum.xda-developers.com/showthread.php?t=1794758
Modem + RIL installer : http://forum.xda-developers.com/showthread.php?p=31416701
CM10.1:
XDA Forum main discussion thread : http://forum.xda-developers.com/showthread.php?t=2036229
Still under development as Samsung code source is missing.
Syiah kernel :
XDA Forum Dev thread : http://forum.xda-developers.com/showthread.php?t=1555259
XDA Forum discussion thread : http://forum.xda-developers.com/showthread.php?t=1658647
Syiah Kernel for SGS2: http://www.gokhanmoral.com/
Kernel download link : http://www.gokhanmoral.com/
Extweaks thread by droidphile : http://forum.xda-developers.com/showthread.php?p=23616564#post23616564
Comprehensive and exhaustive list of Extweaks UV values by gecko95gek: http://forum.xda-developers.com/showpost.php?p=26755476&postcount=850
You can download directly the kernel to your device. Open your browser, go to gokhanmoral website. You will find an optimized version for device, with all listed kernels. Clic on it, the changelog will appeared as well as a download link.
Extweaks and Dual Booting FAQ by Droidphile
http://tinyurl.com/cvjcl52
http://forum.xda-developers.com/showpost.php?p=24233132&postcount=5
UNDERSTANDING ANDROID
Below is a link to a must read document about Android and how it works on your device. The pdf is quite big, 485 pages, but do not be afraid. All is very well explained, in a very clear english and academic fashion, so even n00bs can understand. There is a lot of pictures and very practical explainations.
http://tinyurl.com/dxr8dpx
All rights reserved www.hardkernel.com
Kernel cleaning scripts
Most often, custom Kernels create special directories and config files. If you want to switch from one custom Kernel to another one, it is not a bad idea to run this script before flashing the new Kernel. It will do some cleaning on your file system by removing all custom tweaks let by the Kernel.
http://forum.xda-developers.com/showthread.php?t=1363738
##My current configuration : [color=#ooBFFF]CM10-nightly-20121107[/color] + SyiahKernel [color=#ooBFFF]5.0.1[/color]##
##I am an Archlinux user, and some settings and way to operate are sometimes different from Ubuntu. So do not hesitate to ask here in case of any problem with Linux in general, and Arch in particular.##
Below is a list of major usage difference, known issues or tricks.
I will do my best to keep it up to date and exhaustive, according to my own usage of my SGS2 device and what I can read on the forum.
Noteworthy differences
Syiah Kernel use its own touch CWM. You can move around with touchscreen or screen buttons. When you backup, restore or install zip from sd card, use INTERNAL SDCARD instead of SDCARD (the opposite of CM9 practice).
Most kernel settings are done with an app called EXTWEAKS. This is a free app from Android Play. You need to give root access to Apps under Settings > Developper options > Root acess to allow EXTWEAKS to operate the changes. Settings from Extweaks will override the ones from CM9, like CPU govenor and clock speed.
Flashing Syiah kernel will install many .syiah folders and config files on your device. If you want to get rid of them when back to CM9 default kernel, flash syiah-resetdefaultprofile.zip (link to the file on his website under SiyahKernel v3.0beta3 section). It is NOT mandatory, as CM9 will be fully functional with these config files, but it is best to keep your system as clean as possible.
Using this kernel in the correct way, enjoying all the fine tunings, is not so easy and need a bit of knowledge. IF you have no idea about how work your CPU and GPU, stick to the default configuration. Wrong settings will cause malfunction, lags, glitches and make scrolling jerky.
Since version 3.1b1, dual booting is enabled. All settings are done in the Syiah custom CWM. It allows you to choose at boot time between two ROMs
[*]BLN IS WORKING NATIVELY SINCE KERNEL 3.2b4
GOOGLE NOW IS A HUGE BATTERY DRAINER ON CM10
2012/09/13
CM10 is now my first ROM. Flashed CM10-nightly 0913
flashed syiahkernel 4.1.5.
2012/09/13
Flashed CM10-nightly 0928
Battery is still draining very fast
some issues with superuser. Moved to SuperSu from chainfire (Play store)
2012/10/15
Flashed CM10-20121015-experimental-i9100-jbmalioshwc2-vsync_sysfs-changmin (link above under CM10)
Battery is better, memleak fixed.
Flashed Syiah-s2-v4.1.5-cm10-jbmali-vsync-sysfs
Flashed new gapps 20121011
2012/10/20
Flashed CM10-20121017-nightly
Flashed Syiah-s2-v5
2012/11/07
Flashed CM10-20121107-nightly
Flashed Syiah-s2-v5.0i
2012/12/09
You will find a 4.2.1 experimental CM10 ROM at this following link :
http://forum.xda-developers.com/showthread.php?t=2036229.
Teamhacksung has made a very hard work to port 4.2.1 to the SGS2, as they don't have any opensource drivers/kernel from Samsung.This build is still experimental.
2013/01/04
I am still on my old config with CM10 as I am not convinced CM and SyiahKernel are yet fully stable.
2013/02/28
I WILL NOT FOLLOW THIS THREAD ANYMORE .
CM 10.1 is totally broken on this device and there isn't even a stable release. Samsung broke things.
Gokham has some trouble building Kernels.
DUAL BOOT CM9/B2G : A QUICK & DIRTY HOW-TO
DEVELOPMENT ON SGS2 HAS BEEN STOPED. IT SEEMS WE WILL NEVER SEE THIS OS FULLY WORKING ON OUR DEVICES
B2G is Boot To Gecko, a Mozilla OS for device project. I have been following it since a while, and it is a very active and promising OS for your SGS2. It is in its very early stage, so do not expect to use it daily, but it is improving very fast.
When Gokham talked about dual boot, I immediatly think to B2G, as I am not interested in any other custom ROM than CM9. Thanks to its new 3.2.2 Kernel, it is now very easy to give it a try.
The work has been done by PULSER, building the B2G image, and GOKHAM, for dual boot capability. So a warm thanks to both of them, and of course to the B2G Team.
I will come back in the coming weeks with a more fine tuned How-To, as I did the install in the rush this morning.
How-To
I did everything on Ubuntu 11.10. Windows users will use Odin, and I am sure it works with other Linux distro.
I assume you have SyiahKernel v3.2.2. on your SGS2
I assume you have a working SGS2/Linux communication. It means a working ADB, USB and Heimdall. I used heimdall 1.3.1, and some users report issues with 1.3.2. Furthermore, I used Command Line, as the heimdall GUI front-end didn't work for me, and I didn't take time to investigate.
I assume B2G will be your second ROM.
Download the last two files of the list here (system and data image):
http://villainrom.co.uk/pulser/B2G/
Untar <Boot2GeckoDualBootsystem.tar> and rename it <hidden.img> if Pulser haven't changed the name (was mistakenly named <hiddenfs.img>)
Unzip <data.img.zip> and get a 2G <data.img>
Boot your device in CWM Recovery.
As mentionned on SyiahKernel website, Mounts and storage > format /secondrom_data and /secondrom_cache.
Reboot your device in Download Mode.
Plug your device
Run this command is to make sure heimdall is working
Code:
$ heimdall detect
Device detected
It shall return <detected>
Code:
$ heimdall flash --hidden <PATH/TO/HIDDEN.IMG>
---- you will see progress until 100%. It hangs a litle bit around 88%, just wait.
Reboot device on Android
Run this command on Linux:
Code:
$ adb push <PATH/TO/DATA.IMG> </sdcard/.secondrom/data.img>
File is big, so it takes a while (a few mn).
Reboot. On the dual boot screen, you have 3 sec to press your Home Button. Then you shall see :
Booting for the second ROM...
IF second ROM doesn't boot quickly (around 10-20 sec), then there is a mess somewhere.
Normally, you will quickly boot to B2G Lock Screen.
!!At this state, you will have nothing more than the lock screen. You need then to make-isntall Gaia!!
Let's make-install Gaia now
1-Dirty and quickest way-TRY THIS ONE FIRST
I did not yet tested this shortest way. It will save you a lot of time cloning unusefull stuff from Git.
You may have in this case an error with adb. Try to copy your own adb executable in the path where make gaia is supposed to find it.
Plug your device running the second ROM, B2G.
Then:
Code:
$mkdir ~/B2G
$ cd ~/B2G
$ git clone https://github.com/mozilla-b2g/gaia
$ mkdir /glue/gonk/out/host/linux-x86/bin
==> copy your adb executable in this directroy. Check permission
$cd gaia
$ make install-gaia
This is very minimal, but shall work.
2-Academic way
Code:
$mkdir ~/mozilla/gits/B2G
$ cd ~/mozilla/gits/B2G
$ git clone https://github.com/mozilla-b2g/B2G
$ cd B2G
$ make sync
Time for a beer...or two!! It takes long
Boot your device to second ROM, B2G now.
Plug your device to the computer.
Check if adb is fully working :
Code:
$ cd ~/mozilla/gits/B2G/
$ adb devices
List of devices attached
00194a183cd97e device
!!If you have no number and device, adb is not properly working on your system.!!
copy adb executable in /usr/bin
*EDIT : do not stress on adb, as in this case, when making gaia, an adb will be built.
Assuming you are still in the gaia folder
Code:
$cd ..
$ make install-gaia
ET VOILA.
You will soon see the gaia frontend.
useful links:
https://developer.mozilla.org/en/Mozilla/Boot_to_Gecko/Setting_Up_Boot_to_Gecko_Build_Environment
https://developer.mozilla.org/en/Mozilla/Boot_to_Gecko/Building_B2G_for_Samsung_Galaxy_S2
http://forum.xda-developers.com/showthread.php?t=1518467
https://www.villainrom.co.uk/forum/threads/introduction-to-dual-boot-of-boot2gecko-b2g.5436/
http://johnhammink.blogspot.ca/2012/05/part-3-updating-your-gingerbread.html
There is a very active B2G mailing list.
All credits to B2G dev, PULSER and Gokham.
On a serious note now first of all great posts you have made here. You have one way a right to be here so people can talk about the development issues that they are facing with the kernels but on the other hand this has nothing to do with development and you are actually not developing anything. Thus this thread should be moved to General Section and not here.
Plus there are threads of were people can talk about what they are facing on the perspective threads of the kernels that they are using. But anyway best of luck.
While the thinking and intention are good,I think this thread would best be put in the General or Q&A section,as it isn't development.
Anyway,the threads are already too cluttered,that's a fact...
Please, may a Mod move this thread to Samsung Galaxy S II I9100 > Galaxy S II General.
It has no reason to be under the development section.
Thank You
EDIT: Thread has been moved to a best place, as it is not mint to talk about development, but more of daily use.
This thread is a very good idea. Will be using it in the near future when I try cm9 again.
Sent from my GT-I9100 using XDA
That's a good idea.
But gokhanmoral him self change his mind twice a day regarding the support of CM9.
So I m afraid your thread would have no sucess until he clearly stand that:
1) Siyah will support CM9
2) Siyah wil NOT support CM9
That's a good idea.
But gokhanmoral him self change his mind twice a day regarding the support of CM9.
So I m afraid your thread would have no sucess until he clearly stand that:
1) Siyah will support CM9
2) Siyah wil NOT support CM9
Click to expand...
Click to collapse
No need for you negativity. If you don't think it will work. Don't use the thread.
There is a need. Because people are using siyah on cm9. Whether they will continue, another persons guess, but why do you have to point out the negatives. Is it to prove your knowledge to the contrary? Well done!
Just say nice thread, or even better, nothing if you don't agree and let people get on with it.
rice and pea(ce)
bleuxeon said:
That's a good idea.
But gokhanmoral him self change his mind twice a day regarding the support of CM9.
So I m afraid your thread would have no sucess until he clearly stand that:
1) Siyah will support CM9
2) Siyah wil NOT support CM9
Click to expand...
Click to collapse
1-I am not after sucess , just think there is a place for such a thread, being me or anyone else. If I am wrong, that's fine the thread will die by its lack of participation.
2-your post is exactly what I don't want here: unusefull from a practical standpoint. You are not helping anyone with your remark.
I was trying nightly 20120319 and siyah beta3 for a while and had no major issues.
In comparison to the kernel compiled by codeworkx, I had massive scrolling lags in trebuchet launcher with siyah.
more2come said:
I was trying nightly 20120319 and siyah beta3 for a while and had no major issues.
In comparison to the kernel compiled by codeworkx, I had massive scrolling lags in trebuchet launcher with siyah.
Click to expand...
Click to collapse
Which governor did you use?
Sent with Tapatalk from my GT- I9100
gabx said:
1-I am not after sucess , just think there is a place for such a thread, being me or anyone else. If I am wrong, that's fine the thread will die by its lack of participation.
2-your post is exactly what I don't want here: unusefull from a practical standpoint. You are not helping anyone with your remark.
Click to expand...
Click to collapse
I anderstand.
My main idea remains : how can you create a thread about a kernel while in the same time the father of that kernel say that he wont support CM9..or maybe he would?
It sounds crystal clear that your thread is like talking about Galaxy SIV when Galaxy SIII isnt here
well actually Gokhanmoral said so himself:
"kjetal advised me a nice and good build of cm9 and I hope to install it tomorrow. and I hope not to come back to a samsung rom in near future...
that's all for now. I have to go back to work"
And I'm pretty sure his signature says 'cm9 nightly' as well...
shr33kant said:
well actually Gokhanmoral said so himself:
"kjetal advised me a nice and good build of cm9 and I hope to install it tomorrow. and I hope not to come back to a samsung rom in near future...
that's all for now. I have to go back to work"
And I'm pretty sure his signature says 'cm9 nightly' as well...
Click to expand...
Click to collapse
great news!
I simply hope he will not change his mind again.
more2come said:
I was trying nightly 20120319 and siyah beta3 for a while and had no major issues.
In comparison to the kernel compiled by codeworkx, I had massive scrolling lags in trebuchet launcher with siyah.
Click to expand...
Click to collapse
Did you install Extweaks? If no, I would recommend.
Start to play a litle bit with CPU and GPU settings. Do not hesitate, it won't break your device. Just go step by step. You should quickly see some improvment.
I'm using b3 with the latest nightly and loving it . I don't need mtp when I've got airdroid!
Sent from inside a black hole.
bleuxeon said:
I anderstand.
My main idea remains : how can you create a thread about a kernel while in the same time the father of that kernel say that he wont support CM9..or maybe he would?
It sounds crystal clear that your thread is like talking about Galaxy SIV when Galaxy SIII isnt here
Click to expand...
Click to collapse
it is not quite true that I won't support CM9.
actually, I am thinking about using it as my primary rom.
but there are some facts now: I am using Samsung ROM, I cannot test anything about CM9 and I am very busy.
those facts make it impossible for me to support CM9 now.
when I install CM9, it will be harder to support Samsung ROM. that is why I want to finish dual-booting.
subscribed.
gokhanmoral said:
it is not quite true that I won't support CM9.
actually, I am thinking about using it as my primary rom.
but there are some facts now: I am using Samsung ROM, I cannot test anything about CM9 and I am very busy.
those facts make it impossible for me to support CM9 now.
when I install CM9, it will be harder to support Samsung ROM. that is why I want to finish dual-booting.
subscribed.
Click to expand...
Click to collapse
Many thanks Sir for this clarification.
PS : I just tried to make you a donation, but when I click "donation" then I go to PAYPAL in Turkish (or other that I dont know) and I can't anderstand it at all.
I have allready made you a donation but PAYPAL was in my own language this time.
Ramelov said:
Which governor did you use?
Sent with Tapatalk from my GT- I9100
Click to expand...
Click to collapse
I tried ondemand (default), interactive and smartassV2 .
All lead to the same result, very laggy scrolling.
Scrolling lags decreased with beta5, but performance still is worse than the CM9 kernel by codeworkx.
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.
For those that don't know what evervolv is, Evervolv is an AOSP (Android Open Source Project) rom. We're fully open sourced and encourage it with no restrictions. The work put into this rom is community driven and and Evervolv Project is made up of numerous members and contributors.
Right now the current source we are working on is KITKAT(Android 4.4.4).
Current version: 4.0.0p1
Current Items not working/Buggy
Updated 4-4-14
Bluetooth working --Still a WIP as some devices don't connect
Camera working --Still a WIP as the camcorder records in blue and a few minor issues
home key doesn't turn device on need to use power button--FIXED in the next nightly should be 4-5-2014
Battery draw around 50mA in sleep
Some experience SOD when hotword detect is active
Location service has stopped with Googles update looking into now
You tell me what you find.
4G Models are not currently supported
Click to expand...
Click to collapse
Evervolv Github: https://github.com/Evervolv
Evervolv Gerrit: http://review.evervolv.com/
Evervolv website: http://www.evervolv.com/
(New Site is up Check it out)
Evervolv Bug Tracker: http://bugs.evervolv.com/
(Please have discretion when reporting issues, and be descriptive / helpful. Also understand that we'll have some growing pains with this. So don't expect everything to be perfect.)
Twitter: https://www.twitter.com/wbellavance
IRC: #evervolv
Click to expand...
Click to collapse
[GPL Compliance]
Kernel Source
Click to expand...
Click to collapse
[Download]
If you already have evervolv installed you should see this build under testing if you refresh and can download that way.
No more nightlies Moved to 5.0 Lollipop
ev_tenderloin-1-23-15 Last and final for 4.0 -> Fix netflix
FLINTMAN-TWRP-touch-data_media-SELINUX-2.7.1.0-6-7-2014.zip
--This is a flashing TWRP recovery with data/media and SELINUX support. I have tested 100% of the features and everything is working great as far as i can tell. Soo
with that being said. Use at your own risk 8). Make sure you save a backup from your current recovery just in case. BACKUP BACKUP BACKUP
--Broke Vibration as i updated kernel.
Click to expand...
Click to collapse
NOTE: Recommend a clean install if moving from a previous version and or another ROM.
Flashing from cm or any other ROM will require a clean install, dirty flashes can cause random reboots and random errors
[Disclaimer]
I am not responsible for bricked devices, lost data, etc, etc. You all know the drill. BACKUP BACKUP BACKUP
Click to expand...
Click to collapse
[Special Thanks]
i would like to thank Flemmard, Jcsullins, Dorregaray, Invisiblek, Milaq, and anyone else that helped to make this happen. More great work to come.
Mitchbaria --for a 4g model to start in on this
Colchiro-- For a spare Touchpad WIFI to be able to test on one and develop at the same time
Click to expand...
Click to collapse
GAPPS
---These are the gapps i use. You should be able to use any that are KitKat compatible
http://forum.xda-developers.com/showthread.php?t=2397942
Grabbing logcats and dmesg along with last_klog.
These are helpful in figuring out what is going on
Install the sdk in you PC http://developer.android.com/sdk/index.html
Logcat
"adb shell logcat >logcat.txt"
This will run until unplugged or ctrl c and all the content will go into that file
dmesg
"adb shell cat proc/kmsg >dmesg.txt"
This will run until unplugged or ctrl c and all the content will go into that file
Last_klog
"adb shell cat proc/last_klog >lastklog.txt"
This is for if you have a reboot run this right after the device starts back up and it will get me the last dmesg from before it reboot and will help determine the cause of the reboot.
This will help me and everyone that uses this ROM as i can determine the cause of issues.
Thanks
Thank you for the continued HP Touchpad Development and support Flintman.
Cheers:highfive:
Touchpad Toolbox By Jcsullins
[ROM GUIDE]How to use the TouchPad Toolbox to install Android "The Super Easy Way"
[GAPPS][4.4.x/4.3.x] OFFICIAL 0-Day PA-GOOGLE APPS (Use Mini or Micro packages)
Thanks to both of you. For the roms and the video walk thru. I haven't tried art on the touchpad because it actually makes my Galaxy Nexus slower most of the time. And with some gapps it's even worse. Since it isn't listed as broken I am assuming you have tried it. If I may ask. What gapps did you use and what was performance like? It prevented my nexus from booting at times. Just wanna stick with what you have tried until I get use to the new data media and such. Thanks again.
Moody66 said:
Thanks to both of you. For the roms and the video walk thru. I haven't tried art on the touchpad because it actually makes my Galaxy Nexus slower most of the time. And with some gapps it's even worse. Since it isn't listed as broken I am assuming you have tried it. If I may ask. What gapps did you use and what was performance like? It prevented my nexus from booting at times. Just wanna stick with what you have tried until I get use to the new data media and such. Thanks again.
Click to expand...
Click to collapse
I haven't tested as its still a wip from Google. I do have it as broken in the op. But good to know that it boots 8)
Sent from my SCH-I545 using xda app-developers app
Added another build see OP for what was changed. I also adding in a touch recovery TWRP with data/media and SELINUX support. This will also allow you access to your webOS media folder which is know in the new build as external_sd. I have tested out all the features and everything is working great but please save a full backup from your previous recovery if you decide to use this recovery as it's still in an Alpha state.
Enjoy
flintman said:
Added another build see OP for what was changed. I also adding in a touch recovery TWRP with data/media and SELINUX support. This will also allow you access to your webOS media folder which is know in the new build as external_sd. I have tested out all the features and everything is working great but please save a full backup from your previous recovery if you decide to use this recovery as it's still in an Alpha state.
Enjoy
Click to expand...
Click to collapse
Thanks a lot for this amazing ROM and the recovery I had few bug with the reboot ... The recovery freezed and i have to manually reboot to unfreeze it ... A part from that great job Can't wait to see what you are going to bring next
And just one little request ... I love having the clock center on the status bar ... Do you think you can add it to the Evervolv project ? That's would be a great feature
Lyok0ne said:
Thanks a lot for this amazing ROM and the recovery I had few bug with the reboot ... The recovery freezed and i have to manually reboot to unfreeze it ... A part from that great job Can't wait to see what you are going to bring next
And just one little request ... I love having the clock center on the status bar ... Do you think you can add it to the Evervolv project ? That's would be a great feature
Click to expand...
Click to collapse
I have flashed with this recovery about 20 times now and only got the reboot to hang once. I'm looking into it.
Lyok0ne said:
Thanks a lot for this amazing ROM and the recovery I had few bug with the reboot ... The recovery freezed and i have to manually reboot to unfreeze it ... A part from that great job Can't wait to see what you are going to bring next
And just one little request ... I love having the clock center on the status bar ... Do you think you can add it to the Evervolv project ? That's would be a great feature
Click to expand...
Click to collapse
install xposed + gravitybox. it works like a charm and has this feature and many others.
Sent from my Nexus 4 using Tapatalk
Okay, I am doing something wrong. I have downloaded the recovery multiple times from multiple devices. I have tried installing via TWRP and manually extracting the image to /boot.
Each attempt, I get:
Checking uImage... Invalid Size
BOOT FAILED!
Please SELECT to continue
Any thoughts? I can still load my backup copy of TWRP without issue.
Update:
After purging the other copies of TWRP from /boot, the new version loads without issue. Thanks flintman!
Discovered that the TP 4G not compatible with the test 3.X Kernel yet
Hey Flintman just wanted to point out my findings after going crazy over the past couple weeks trying to figure what I was doing wrong when flashing the test Kit Kat ROMs w/3.X kernel.
Previously my TP 4G was working fine on shumash's SCHIZOID 4.2.2 ROM but I was extremely eager to try out the new 3.X kernels. I first tried out your non-data/media Evervolv 4.0.0p1 version and was unable to connect to WiFi despite repeated clean install methods and variations of cache wipes. I know that I had re-sized partitions with Tailor sufficiently for Kit Kat as warned so I then attempted to try out Invisblek's CM11 ROM. Not only was WiFi still not wanting to toggle on, but the rotation sensor was acting oppositely for landscape orientations and I was getting frequent crashing reboots just going through the UI. I then decided to try out JCSullins' updated CM10.1 ROM with his 3.0 kernel and then encountered the same behavior as Invisblek's CM11 ROM, but with even worse random touch driver issues that resulted in erratic automatic screen touches and ultimately soft-reboots.
Restoring a backup to SCHIZOID's 4.2.2 ROM worked fine to restore all functionality, but I couldn't help but think that I was still doing something wrong.
I got a hold of a normal TP (WiFi only model) and tried your latest 1-10-2014 Evervolv 4.0.0p1 ROM and was amazed to see that it was working great including WiFi (although 5GHz APs don't seem to scan as reliably as the past kernel) aside from the known issues. I tried the exact same install process on my TP 4G again just to see if anything changed, but unfortunately WiFi still wouldn't toggle and the orientation sensor behavior exhibited the same opposite landscape behavior as Invisiblek and JCSullins' ROMs.
I had thought that aside from the 3G HSPA modem in the TP 4G model chipset-wise it would be identical to the WiFi-only model so kernel 3.X developments would be complimentary across all TP devices. Unfortunately this doesn't appear to be the case and I hope with time you guys are able to work out any compatibility with the 4G model to benefit from the already terrific development that's going on with the 3.X kernel now.
I admire your guys' skills and look forward to all the improvements in store!
PS: I'd be more than happy to beta test anything you guys feel would address any compatibility issues on the TP 4G!
If we flash your twrp will it remove cwm or add another entry? I've never been able to have two recoveries working. I would much rather not have to use the power button and what not all the time in cwm but want to make sure I'm covered if something goes wrong. Thanks
Sent from my TouchPad using Tapatalk
Due to the limit of the boot directory it will remove all recoveries before installing this one.
Sent from my SCH-I545 using xda app-developers app
Sorry for the Nube question I've searched and I'm sure it's been answered already....
So I got my touchpad with ClockworkMod Recovery version 6.0.1.9 can I flash the TWRP SE data/media recovery from there? Trying with the acme installer 5ET has failed.
I do have the original 4.4 Evervolv up and running and my partitions have been updated.
Thanks
Steve
SteveoSupremo said:
Sorry for the Nube question I've searched and I'm sure it's been answered already....
So I got my touchpad with ClockworkMod Recovery version 6.0.1.9 can I flash the TWRP SE data/media recovery from there? Trying with the acme installer 5ET has failed.
I do have the original 4.4 Evervolv up and running and my partitions have been updated.
Thanks
Steve
Click to expand...
Click to collapse
So I replaced the ulimage in the boot directory and was able to install the 1/10/14 rom. So I guess I needed to search and just try a little more.
anyway -- I think it's a little slower than the first 4.4 version.... Maybe I need to reboot.... thoughts?
steve
Both using same cpu settings? Although with more things implemented it could seem slower.
---------- Post added at 01:11 AM ---------- Previous post was at 01:07 AM ----------
emph4tic said:
Hey Flintman just wanted to point out my findings after going crazy over the past couple weeks trying to figure what I was doing wrong when flashing the test Kit Kat ROMs w/3.X kernel.
Previously my TP 4G was working fine on shumash's SCHIZOID 4.2.2 ROM but I was extremely eager to try out the new 3.X kernels. I first tried out your non-data/media Evervolv 4.0.0p1 version and was unable to connect to WiFi despite repeated clean install methods and variations of cache wipes. I know that I had re-sized partitions with Tailor sufficiently for Kit Kat as warned so I then attempted to try out Invisblek's CM11 ROM. Not only was WiFi still not wanting to toggle on, but the rotation sensor was acting oppositely for landscape orientations and I was getting frequent crashing reboots just going through the UI. I then decided to try out JCSullins' updated CM10.1 ROM with his 3.0 kernel and then encountered the same behavior as Invisblek's CM11 ROM, but with even worse random touch driver issues that resulted in erratic automatic screen touches and ultimately soft-reboots.
Restoring a backup to SCHIZOID's 4.2.2 ROM worked fine to restore all functionality, but I couldn't help but think that I was still doing something wrong.
I got a hold of a normal TP (WiFi only model) and tried your latest 1-10-2014 Evervolv 4.0.0p1 ROM and was amazed to see that it was working great including WiFi (although 5GHz APs don't seem to scan as reliably as the past kernel) aside from the known issues. I tried the exact same install process on my TP 4G again just to see if anything changed, but unfortunately WiFi still wouldn't toggle and the orientation sensor behavior exhibited the same opposite landscape behavior as Invisiblek and JCSullins' ROMs.
I had thought that aside from the 3G HSPA modem in the TP 4G model chipset-wise it would be identical to the WiFi-only model so kernel 3.X developments would be complimentary across all TP devices. Unfortunately this doesn't appear to be the case and I hope with time you guys are able to work out any compatibility with the 4G model to benefit from the already terrific development that's going on with the 3.X kernel now.
I admire your guys' skills and look forward to all the improvements in store!
PS: I'd be more than happy to beta test anything you guys feel would address any compatibility issues on the TP 4G!
Click to expand...
Click to collapse
I am curious. Have you tried turning the 4g off. Like airplane mode then just turning wifi back on? Was thinking of getting one of these models to tinker with.
Moody66 said:
Both using same cpu settings? Although with more things implemented it could seem slower.
---------- Post added at 01:11 AM ---------- Previous post was at 01:07 AM ----------
Click to expand...
Click to collapse
I think it was because of sync.... it's running smooth now. after I loaded a different set of GAPPS.
Now I have to figure out the camera apk. it would help if I RTFM.... Thanks Flintman for the awesome update!
Which version of gapps is recommended for 01-10-14 version?
New Test build up which fixes vibration
emph4tic said:
Hey Flintman just wanted to point out my findings after going crazy over the past couple weeks trying to figure what I was doing wrong when flashing the test Kit Kat ROMs w/3.X kernel.
Previously my TP 4G was working fine on shumash's SCHIZOID 4.2.2 ROM but I was extremely eager to try out the new 3.X kernels. I first tried out your non-data/media Evervolv 4.0.0p1 version and was unable to connect to WiFi despite repeated clean install methods and variations of cache wipes. I know that I had re-sized partitions with Tailor sufficiently for Kit Kat as warned so I then attempted to try out Invisblek's CM11 ROM. Not only was WiFi still not wanting to toggle on, but the rotation sensor was acting oppositely for landscape orientations and I was getting frequent crashing reboots just going through the UI. I then decided to try out JCSullins' updated CM10.1 ROM with his 3.0 kernel and then encountered the same behavior as Invisblek's CM11 ROM, but with even worse random touch driver issues that resulted in erratic automatic screen touches and ultimately soft-reboots.
Restoring a backup to SCHIZOID's 4.2.2 ROM worked fine to restore all functionality, but I couldn't help but think that I was still doing something wrong.
I got a hold of a normal TP (WiFi only model) and tried your latest 1-10-2014 Evervolv 4.0.0p1 ROM and was amazed to see that it was working great including WiFi (although 5GHz APs don't seem to scan as reliably as the past kernel) aside from the known issues. I tried the exact same install process on my TP 4G again just to see if anything changed, but unfortunately WiFi still wouldn't toggle and the orientation sensor behavior exhibited the same opposite landscape behavior as Invisiblek and JCSullins' ROMs.
I had thought that aside from the 3G HSPA modem in the TP 4G model chipset-wise it would be identical to the WiFi-only model so kernel 3.X developments would be complimentary across all TP devices. Unfortunately this doesn't appear to be the case and I hope with time you guys are able to work out any compatibility with the 4G model to benefit from the already terrific development that's going on with the 3.X kernel now.
I admire your guys' skills and look forward to all the improvements in store!
PS: I'd be more than happy to beta test anything you guys feel would address any compatibility issues on the TP 4G!
Click to expand...
Click to collapse
Do you think you can get me some dmesg and logcats??