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.
Related
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.
**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
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.
To the Moderators:
This is a try at lowering the rate of repeated questions in the CyanogenMod 10.1 official nightlies // discussion thread. I am aware that this thread would probably belong in the "Q&A" section, but I fear that it will get buried and forgotten there. I beg you to consider the idea of this thread and leave it in the "General" section.
Have you flashed a CyanogenMod 10.1 official nightly? Do you have questions and problems? This post is here to help you!
Please read the entirety of this post before asking questions in the CyanogenMod 10.1 official nightlies // discussion thread!
It is assumed that you have read the first post of the CM10.1 thread (called "the OP" in the following).
If you were not able to find your information by yourself, or would not have been able to without this thread, you should reconsider flashing a CM10.1 NIGHTLY.
I will not answer Questions in this thread.
I get a "status 7" message when flashing with CWM!
It seems you are running PhilZ Kernel or a derivative of it. This kernel seems to be broken and unable to flash. Flash Siyah, Dorimanx or any other Kernel via CWM or ODIN, boot to Recovery and try again.
My phone asks for a PIN or some other code which I don't have!
You have a SIM.Locked Phone which was unlocked via an exploit. Samsungs kernel-update fixes a few issues, including those exploits. Use GalaxSim Unlock to re-unlock your phone.
Youtube/Market/GMail crashes!
You need to flash the corresponding 4.2.1 GApps, currently 20121212.
The Clock app (or any other app) crashes!
Go to Settings -> Apps -> All -> Clock (or whatever it was) and delete it's data.
Are there any other kernels supporting CM10.1?
As far as I know, all Siyah-based Kernels should work. Remember that you are not supposed to post on the CyanogenMod 10.1 official nightlies // discussion thread when using a different kernel.
I have flashed [insert any kernel here], now my phone won't boot!
The kernel obviously does not support CM10.1/Android 4.2.1. Reflash the ROM to get the stock kernel back.
Where are the developer and performance options?
Google has hidden them. With good reason. You can render your phone unbootable if you use those incorrectly. To quote Codeworkx: "bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed."
If you apsolutely need to use them, tap Build Number until you are a developer (about 7 times).
I unlocked the Developer Options and tried to use "Simulate Screens". Now my screen is black and won't turn on again!
That is why one does not simply mess around with the dev options. Reboot your phone and press vol. down while it's booting. This will boot it to Secure Mode, where you can go and untick "Simulate Screens". Fixed.
I cannot find Photosphere! Will it be added?
No. Photosphere is not open source and therefore only available for Nexus devices.
Charging speed is very slow!
Due to hardware limitations, there are only three possible charging speeds, one of which is never used. The others are 450mA on USB and 650mA on the charger. Your phone is either draining power while being charged (media scanner?) or has a problem with the USB connector. Try cleaning it CAREFULLY or find the app responsable for the drain with BetterBetteryStats.
I want to disable the Lockscreen Widgets
Use Lockscreen Policy from the Play Store
The weather Icon of Chronus does not show on the lockscreen!
You can maximize widgets in the Lockscreen Settings. All your Lockscreen widgets will be maximized after turining the screen on. If you want to know why there's no better Option read this.
Sometimes I get freezes when scrolling through long lists!
I have never experienced this. People suggest that ticking "Force GPU Rendering" in Developer Options solves this. Other People suggest that forcing GPU rendering breaks other things, e.g. the keyboarld leaves a black space in WhatsApp. I have never experienced this, neither.
My Car Stereo/Handsfree/other Bluetooth device does not work correvtly!
All AOSP 4.2.1 ROMs including the Nexus 4 seem to have problems with Bluetooth, or more specifically A2DP. Rumour has it that it will be fixed in 4.2.2.
I get "Out of storage" messages and can no longer install Apps!
Viber and Lucky pacher are known to trigger this. Try to move them to your external SD card. If that doesn't do the trick, search /data/apps for .odex files and delete them.
I get tons of dumpstate_ril_RESET_BY_CP_SILENTRESET.log files at /data/log !
These are logs of RIL crashes. Do NOT use GetRIL to fix this. Use this instead. These zips flash modem, RIL and a few other related files. They are much more reliable than GetRIL. You can also try to Flash XXLS8 without RIL and hen reflash CM, it comes with XXLS8 RIL.
The rotation- and the acceleration sensor do not work anymore!
Deactivating tilt to scroll in Chrome should help.
Real Racing 3/Simpsons/other games crash after a very short time!
Blamesung. This is a problem with the current mali driver (mali is the graphics chip). Do not expect it to be fixed. There is a possibility to flash older drivers and fix the gaming issues (see siyah kernel), but that will bring the graphical glitches in the UI and keyboard back.
UPDATE: It seems to me that it's not the mali driver, but the audio HAL acting up. I have sudden loss of audio and a game crash a few seconds after, most prominently in World of Goo, and some people report that disabling all things audio via in-game controls fixes the crashing.
I still have a problem that was not discussed here!
Reflash the ROM and wipe cache and dalvik cache in Recovery. Reboot. Delete the data of the app that is misbehaving. Search the CyanogenMod 10.1 official nightlies // discussion thread to see if anyone has had this problem before you, and if there is a fix. If all of this fails, ask in that thread and someone will hopefully try to help you.
IMPORTANT INFORMATION
I have moved on to a Sony Xperia Z. I will not trouble myself with keeping myself, the OP or the thread up to date. If you have very common problems and a solution, PM me and I'll update the OP. If you want to take over the management of this thread, PM me and we'll find a solution.
Happy flashing and bye!
this thread s completely useless... when we have a discussion thread and one development thread in original forum what was the necessity of this'd thread.. does q & a or discussion means different? think before starting a new thread..
I have been considering CM10.1 and aren't too bothered about some of the bugs but the GPS one does concern me. I use my phone as my everyday satnav, does this GPS bug mean that the navigation app is currently useless on CM10.1?
Prashanthme said:
this thread s completely useless... when we have a discussion thread and one development thread in original forum what was the necessity of this'd thread.. does q & a or discussion means different? think before starting a new thread..
Click to expand...
Click to collapse
True, All of the above answers are completely useless, because they have been answered countless times alerady. But still people ask them, sometimes the same question twice in the same thread page. But instead of flaming the questioners, yelling at them, i try to answer them in one, easy to find place. It is an experiment to see if maybe the original thread gets cleaner with this, and more efficient at solving the real problems as well as discussing issues and solutions. In my oppinion, telling people to tap the build number 7 times does not count as discussion...
Coirpre said:
True, All of the above answers are completely useless, because they have been answered countless times alerady. But still people ask them, sometimes the same question twice in the same thread page. But instead of flaming the questioners, yelling at them, i try to answer them in one, easy to find place. It is an experiment to see if maybe the original thread gets cleaner with this, and more efficient at solving the real problems as well as discussing issues and solutions. In my oppinion, telling people to tap the build number 7 times does not count as discussion...
Click to expand...
Click to collapse
I like the experiment an totally agree to the spirit of not flaming.:good:
But I am afraid it will not really help. Too much users who prefer to just ask instead of doing some honest searching.
Prashanthme said:
this thread s completely useless... when we have a discussion thread and one development thread in original forum what was the necessity of this'd thread.. does q & a or discussion means different? think before starting a new thread..
Click to expand...
Click to collapse
If it is not useful, why are you here and commenting on it.
There are people who appreciates others efforts
I think its useful for the people who will be first time flashing CM10.1
Guys what's the difference between stable releases and nightlies? Which one is better?
Sent from my GT-I9100 using xda premium
Kenrokks said:
Guys what's the difference between stable releases and nightlies? Which one is better?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
nightlies have small update day by day. Stable are versions are like milestones. I use cm10.1 nightlies.
Sent from my GT-I9100 using xda premium
Maybe someone can help me with this:
I experience very slow charging with the standard samsung charger and CM 10.1, never saw this before.
tr1cky1 said:
Maybe someone can help me with this:
I experience very slow charging with the standard samsung charger and CM 10.1, never saw this before.
Click to expand...
Click to collapse
updated OP with the answer.
How to get Root access of ADB on this CM 10.1 version?
How to get Root access of ADB on this CM 10.1 version?
On earlier CM version 10 there was "Developer options" in settings were I could simply change that, in "Root access" section.
My problem is that i get this: (shell has been denied superuser permissions) on my Samsung galaxy tab2 7.0 when trying to install app's wirelessly from my computer using "APK Batch Installer" that I found on the internet, ow and on the tab I use adbWireless app.
Typing "su" in terminal emulator and getting access to it doesn't work.
I am trying to solve this for few days and I just now found out that on CM 10 version everything would work if i would get ADB access, so I ended here asking for help. :fingers-crossed:
P.S. Sorry.. Writing this i didn't notice that this treat is for specifically one phone, that's because I googled this But any help would be appreciated.
@Coirpre
Maybe you could ask the mods or TS in this thread to merge, add or link your OP.
It'll help that thread by just pointing queries to the OP.
Good job collecting those info btw.
GT-i9100 | CM10.1 Nightly Stock
voltsb333 said:
@Coirpre
Maybe you could ask the mods or TS in this thread to merge, add or link your OP.
It'll help that thread by just pointing queries to the OP.
Good job collecting those info btw.
GT-i9100 | CM10.1 Nightly Stock
Click to expand...
Click to collapse
I asked Codeworkx to add something similar to the OP of the cm10 thread, but he refused. I will ask as soon as i have the time (25. dec.) and nobody reads the op anyways...
I get a "status 7" message when flashing with CWM![/B]
It seems you are running PhilZ Kernel. This kernel seems to be broken and unable to flash. Flash Siyah or Dorimanx Kernel via ODIN, boot to Recovery and try again.
Click to expand...
Click to collapse
If you get problems installing cm10.1 using the leaked version of Samsung jelly beans insecure kernel. You don't have to flash a kernel using odin.. If you flash sky fires dream kernel.. Reboot recovery and install cm10.1 from this kernel.. Everything works great.
Dream kernel found here:
http://forum.xda-developers.com/showthread.php?p=29129084
Sent from my GT-I9100 using Tapatalk 2
Removed
With all the issues I see I think I will keep my CM9 for long.
At least one of the mentioned problems has already been fixed:
My GPS-tracking shows 2 Km instead of the few hundred meters which i actually run. My average Speed is 100Km/h!
Click to expand...
Click to collapse
Prashanthme said:
this thread s completely useless... when we have a discussion thread and one development thread in original forum what was the necessity of this'd thread.. does q & a or discussion means different? think before starting a new thread..
Click to expand...
Click to collapse
I totally disagree. This thread not only save my time searching countless pages looking for my answer, it also prevented me spamming noob questions in the discussion/development thread. Thanks for the OP's effort for creating this thread. :good::good::good:
Legisy said:
How to get Root access of ADB on this CM 10.1 version?
On earlier CM version 10 there was "Developer options" in settings were I could simply change that, in "Root access" section.
My problem is that i get this: (shell has been denied superuser permissions) on my Samsung galaxy tab2 7.0 when trying to install app's wirelessly from my computer using "APK Batch Installer" that I found on the internet, ow and on the tab I use adbWireless app.
Typing "su" in terminal emulator and getting access to it doesn't work.
I am trying to solve this for few days and I just now found out that on CM 10 version everything would work if i would get ADB access, so I ended here asking for help. :fingers-crossed:
P.S. Sorry.. Writing this i didn't notice that this treat is for specifically one phone, that's because I googled this But any help would be appreciated.
Click to expand...
Click to collapse
Sorry for the late answers, however, i have prewarned in the OP.... Have you given Root access to ADB? it is in the developer options.
jcasares said:
With all the issues I see I think I will keep my CM9 for long.
Click to expand...
Click to collapse
It's not that bad. The only real problem atm is A2DP and bluetooth telephony. the ussues posted here are mostly unimportant or solvable.
TomBishop said:
I totally disagree. This thread not only save my time searching countless pages looking for my answer, it also prevented me spamming noob questions in the discussion/development thread. Thanks for the OP's effort for creating this thread. :good::good::good:
Click to expand...
Click to collapse
You are welcome!
:::::::... Kernels & Recoveries for || 4.4.x || KitKat Builds...::::::::
With:
TWRP Recovery
or
CWM Recovery
Devil Kernel
or
AOSP || CM Based Stock Kernel
...……………………………
...……………………………
Important...
DO NOT MIX
A 4.4.X Kernels to 4.3.x, 4.2.x, Etc. ROMs
...……………………………
...……………………………
from the hard work of Recognized Developer - DerTeufel1980
and those continuing to use his kernel mods
I have only put them into a standalone flashable .zip package ... Enjoy
I take no responsibility if it messes anything up,,,, these work for me or I dont post them ,,, ,,,, make backups,,,, nandroids,,, whatever you favorite choice is...
be prepared to potentially wipe, if it wont boot and you can get back into recovery,,, but worst case scenario you will have to ODIN back to stock EH03 and start fresh ...
:: If anyone needs a kernel I have not done up yet shoot me a reply or PM ::
Information and Compatibility
>>>>> >>>> >>>
Android 4.4.x
These Kernels/Recovery are interchangeable across AOSP/CM/OMNI/PA ROMs ,,, {{ So feel free to mix & match accordingly }}
General method of installation:
from Recovery:
Install Zip
Reboot
Enjoy
these zips allow a Rom to boot into chosen Recovery/Kernel combination - including all other Devil Kernel tweaks with programs like the ones below
With some ROMs offering nightly builds sometimes these may not work with the newer nightly ROM builds, just depends on what gets changed.
Just head the warnings and be prepared for possible incompatibility.
Tweaks --- Over Clocking and Kernel Control Programs --
>>>>> >>>> >>>
Devil Kernel Memory Tweak Options
-- 383mb -- Stock
-- 396mb -- XL -- No known issues
-- 408mb -- BigMem -- (Breaks only 720 Video Recording, 480p Video still works fine)
-- 439mb -- Max Ram -- No Camera [picture or video] at all -- [your memory may vary]
...........................................................
...........................................................
Some of the more popular programs if your included one lacks some features
>>>>> >>>> >>>
DevilTools by: DerTeufel
DevilTools-1.1.2.apk :: http://forum.xda-developers.com/attachment.php?attachmentid=2453825&d=1387010535
http://forum.xda-developers.com/showthread.php?t=2276036
Devil Kernel Manager
DevilAppSGS.apk
http://forum.xda-developers.com/showthread.php?t=2558082
https://play.google.com/store/apps/details?id=com.metalignus.devilappsgs&hl=en
Trickster MOD
https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod
ROM Toolbox Lite is excellent with the stuff available in it...
https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox&feature=search_result
I also found this nice Lulzactive controls app
specifically for the Lulzactive Governor and explains things nicely
https://play.google.com/store/apps/details?id=com.tegrak.lulzactive
>>>>> >>>> >>> >>>>> >>>> >>>
My Personal Favorite KitKat Devil settings are
100 Mhz CPU Min
1000 Mhz CPU Max
Zen - I/O Scheduler
Lulzactive - Governor || Smooth Ui = Off ||
Live O/C = 120% || OC Target Low = 1000 Mhz || OC Target High = 1000 Mhz ||
with that setting it it overclocks only the 1000 Mhz to = 1200 Mhz [ I still keep good battery life ]
[ Live OC has the benefit of also OCing the GPU, from 200 -> 240 Mhz @120%]
[ I also up the 1000 Mhz CPU Voltage setting +25 mV = 1300 mV, seems to help stability ]
396mb Memory
Zram 40%
Swappiness 80%
and SD read ahead 1024
Dirty Tweaks - Build Prop Mods::
PM Sleep Mode = 1 [Power Collapse (Best)
Wifi Scan Interval = 1500 [1st set to anything 15-420, then manually edit build prop]
dalvik.vm.heapstartsize = 12m [manually edit build prop]
......................................................................................................................
......................................................................................................................
I take no responsibility if it messes anything up,,,, these work for me or I dont post them,,, ,,,, make backups,,,, nandroids,,, whatever you favorite choice is...
be prepared to potentially wipe, if it wont boot and you can get back into recovery,,, but worst case scenario you will have to ODIN back to stock EH03 and start fresh ...
::KERNEL LINKS::
Fascinate - 4.4 Kernels
My 4.4 Kernels Link ~ thanks AndroidFileHost.com
~~~ clickable Link ~~~ https://www.androidfilehost.com/?a=show&w=files&flid=9626
--- New links show up in these first, before the "Direct Links" get posted
……………………………………
……………………………………
:: KERNEL Direct Links ::
:: :: 4.4 Kernel :: ::
Do not mix 4.4.x Kernels with 4.3.x and Earlier ROMs
2.1-cm11-4.4__TWRP_11-10-2013-fassy.zip
http://www.androidfilehost.com/?fid=23212708291679682
Made from:: [4.4] Unofficial CyanogenMod 11.0 || By: Unjustified Dev || http://forum.xda-developers.com/showthread.php?t=2521427
TWRP - Stock Kernel
3.0-kernel-Devil_TWRP_4.4.2_12-29-2013-fassy.zip
http://www.androidfilehost.com/?fid=23269279319202534
Made from:: DIRTY UNICORNS[4.4.2][v5.0][OFFICIAL][TWRP 2.6.3.0][12-29-13] || By: BDogg718 || http://forum.xda-developers.com/showthread.php?t=2591794.
TWRP - Devil Kernel
3.1-kernel-cm11_cwm_4.4.2_01-04-2014-fassy.zip
http://www.androidfilehost.com/?fid=23269279319202535
Made from:: [4.4.2] Unofficial CyanogenMod 11 [1/4/14] || By: times_infinity || http://forum.xda-developers.com/showthread.php?t=2598051
CWM - Stock Kernel
3.6-cm-11-unjust-kernel_cwm-6.0.4.9__06-04-2014-fassy.zip
http://www.androidfilehost.com/?fid=23501681358551286
Made from:: cm-11-20140604-UNOFFICIAL-fascinatemtd
CWM - didhiys kernel-by unjust
…………………………………………………
…………………………………………………
::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: :::::::::::::::::
Credits:
BDogg718, Dirty Unicorns, Unjustified Dev, DerTeufel1980, Notta, AOSPA, Mazda, Cyanogenmod, PacMan Rom, jt1134, AOSP, Omni Rom, LasVegasRomeo, times_infinity, other developers, users, supporters and anyone else that has helped out!
::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: :::::::::::::::::
.
@hhp_211. Can you marry a Devil kernel with a cwm 6046 to try on the cm11 1/09 ROM? Is it a big project or is it pretty easy?
kb8no said:
@hhp_211. Can you marry a Devil kernel with a cwm 6046 to try on the cm11 1/09 ROM? Is it a big project or is it pretty easy?
Click to expand...
Click to collapse
I hope in the near future to be able to these type of things,,, still learning it.
What issues are you having?
Switching the recovery portion out to be cwm with devil will have no effect on how a kernel portion operates.
They do work independent of each other but have to be installed together on the fascinate ( which is different from most every other phone)
.
hhp_211 said:
I hope in the near future to be able to these type of things,,, still learning it.
What issues are you having?
Switching the recovery portion out to be cwm with devil will have no effect on how a kernel portion operates.
They do work independent of each other but have to be installed together on the fascinate ( which is different from most every other phone)
Click to expand...
Click to collapse
It took me a long time to figure out how the kernel and recovery worked on this device and re-learned it several times til it sunk in but now I get it.
I got all those media errors with twrp/Devil. Maybe the SD card trick you proposed will fix that. Then I got some crashes and no sounds worked so I bailed.
My assumption was that it was twrp and not Devil. The dev in his OP is very particular about using cwm on his ROM. I don't know why they both shouldn't work as long as you have the right ones. Seems that is how it works in other ROMs. Dev called the recovery issue a "debacle" I believe and sounded frustrated. There should be a story here. Why wouldn't twrp flash ROM?
So that's why I'm thinking Devil/twrp is an issue. Have you tried it?
kb8no said:
It took me a long time to figure out how the kernel and recovery worked on this device and re-learned it several times til it sunk in but now I get it.
I got all those media errors with twrp/Devil. Maybe the SD card trick you proposed will fix that. Then I got some crashes and no sounds worked so I bailed.
My assumption was that it was twrp and not Devil. The dev in his OP is very particular about using cwm on his ROM. I don't know why they both shouldn't work as long as you have the right ones. Seems that is how it works in other ROMs. Dev called the recovery issue a "debacle" I believe and sounded frustrated. There should be a story here. Why wouldn't twrp flash ROM?
So that's why I'm thinking Devil/twrp is an issue. Have you tried it?
Click to expand...
Click to collapse
My understanding of the "recovery debacle" is the fact up having to go through the exact process is to get the partitioning set correctly.
Much of the the same reason why on @Unjustified Dev cm11 that you had to switch over to a certain TWRP recovery 1st, because he compiled his cm11 with the TWRP.
hhp_211 said:
My understanding of the "recovery debacle" is the fact up having to go through the exact process is to get the partitioning set correctly.
Much of the the same reason why on @Unjustified Dev cm11 that you had to switch over to a certain TWRP recovery 1st, because he compiled his cm11 with the TWRP.
Click to expand...
Click to collapse
I can get that. Are you saying first flash is about correct partitioning and not correct recovery? That's a reoccurring Fassy theme! So once it is flashed and partitioned correctly and then the ROM flashed, shouldn't we then be able to use any recovery, like a 4.4 compatible twrp?
hhp_211 said:
My understanding of the "recovery debacle" is the fact up having to go through the exact process is to get the partitioning set correctly.
Much of the the same reason why on @Unjustified Dev cm11 that you had to switch over to a certain TWRP recovery 1st, because he compiled his cm11 with the TWRP.
Click to expand...
Click to collapse
You can expect to to change recovery by flashing boot.img we don't have a recovery partition.
Boot image break down
Boot.img contains
* ramdisk
*zImage/Kernel
* recovery ramdisk
We load recovery from boot due to samsung old partition layout
Kernel is inside boot.img this isn't the issue
The issue is the ramdisk.
Some roms contain their own init.blahblah.rc and without it you will get soft-bricked due to certain things not getting initialized and not everything might work and two your ramdisk also contains your init files flashing an incompatible version will soft brick your device due to some things not correctly getting permission . This is the best I can explain it not really a kernel dev or what not so this is the best info I can provide from knowledge .
Newer phones layout
Recovery Partition is separate meaning you can load any recovery in theory without having to be forced to change the Kernel and all ramdisk files which is not good for this reason I always provided zips for my roms with the option to have twrp or cwm because we can't change recovery separately
Boot partition is separate boot.img and kernel never get touched by recovery which is great because you can have no recovery and it still will boot up.
In theory we can flash just recovery such as that twrp zip but it fails for some odd reason I can't understand . TWRP inject script should allow us to flash recovery ramdisk into boot.img so we can have any recovery we want. I may work on getting it to work but for now my fascinate is soft bricked. Also our boot partition is small twrp isn't always fitting in some roms for this reason I build cwm
Unjustified Dev said:
You can expect to to change recovery by flashing boot.img we don't have a recovery partition.
Boot image break down
Boot.img contains
* ramdisk
*zImage/Kernel
* recovery ramdisk
We load recovery from boot due to samsung old partition layout
Kernel is inside boot.img this isn't the issue
The issue is the ramdisk.
Some roms contain their own init.blahblah.rc and without it you will get soft-bricked due to certain things not getting initialized and not everything might work and two your ramdisk also contains your init files flashing an incompatible version will soft brick your device due to some things not correctly getting permission . This is the best I can explain it not really a kernel dev or what not so this is the best info I can provide from knowledge .
Newer phones layout
Recovery Partition is separate meaning you can load any recovery in theory without having to be forced to change the Kernel and all ramdisk files which is not good for this reason I always provided zips for my roms with the option to have twrp or cwm because we can't change recovery separately
Boot partition is separate boot.img and kernel never get touched by recovery which is great because you can have no recovery and it still will boot up.
In theory we can flash just recovery such as that twrp zip but it fails for some odd reason I can't understand . TWRP inject script should allow us to flash recovery ramdisk into boot.img so we can have any recovery we want. I may work on getting it to work but for now my fascinate is soft bricked. Also our boot partition is small twrp isn't always fitting in some roms for this reason I build cwm
Click to expand...
Click to collapse
Its so complicated. Thanks so much for taking the time to explain. So how do we get Devil kernel into 1/9 cm ROM with all that confusion? I like twrp but I want Devil so I can get some extra settings.
kb8no said:
Its so complicated. Thanks so much for taking the time to explain. So how do we get Devil kernel into 1/9 cm ROM with all that confusion? I like twrp but I want Devil so I can get some extra settings.
Click to expand...
Click to collapse
by flashing this:
3.0-kernel-Devil_TWRP_4.4.2_12-29-2013-fassy.zip
http://www.androidfilehost.com/?fid=23269279319202534
hhp_211 said:
by flashing this:
3.0-kernel-Devil_TWRP_4.4.2_12-29-2013-fassy.zip
http://www.androidfilehost.com/?fid=23269279319202534
Click to expand...
Click to collapse
I flashed it and as I said I had to revert as did the other guy. Have you used it yourself? Should I try again?
hhp_211 said:
by flashing this:
3.0-kernel-Devil_TWRP_4.4.2_12-29-2013-fassy.zip
http://www.androidfilehost.com/?fid=23269279319202534
Click to expand...
Click to collapse
the only problem with that kernel is getting twrp also. i think it'd be better to be able to flash the recovery/kernel separately, but like UDev said, the kernel/recovery/ramdisk makes it difficult because we don't have a separate recovery partition. unless we do more partitioning of the system/data/cache/datadata and create a separate recovery, but i don't think we can without some major work.. which sucks. we pretty much need to copy from another phone, if it's been done anyway. i know the Nexus s can flash recoveries separately, but i don't know how their partitions are laid out exactly.
kb8no said:
Its so complicated. Thanks so much for taking the time to explain. So how do we get Devil kernel into 1/9 cm ROM with all that confusion? I like twrp but I want Devil so I can get some extra settings.
Click to expand...
Click to collapse
It's only compatible for so long I mentioned why. These boot.img aren't really the the best solution due to changes that make it not compatible please guys go read on what a ramdisk is and what all this stuff is like init and stuff so you can understand why
Part of ramdisk is in system/core/rootdir in source code other parts come from your device tree . It's not like this code stays the same not even in the device tree it needs to be changed to fix things or give permission to new things or initialize things like sensors snd it runs more like wifi , bluetooth , etc. This boot.img was only made to allow you to get on 4.4 since recovery is in boot.img you had no choice due to recovery being incapable of installing new 4.4 since set permission is gone it's set metadata now . Compatibility with this boot.img is broken now and I wouldn't install it.
Sent from my SM-T210R using Tapatalk
---------- Post added at 12:47 AM ---------- Previous post was at 12:35 AM ----------
ztotherad said:
the only problem with that kernel is getting twrp also. i think it'd be better to be able to flash the recovery/kernel separately, but like UDev said, the kernel/recovery/ramdisk makes it difficult because we don't have a separate recovery partition. unless we do more partitioning of the system/data/cache/datadata and create a separate recovery, but i don't think we can without some major work.. which sucks. we pretty much need to copy from another phone, if it's been done anyway. i know the Nexus s can flash recoveries separately, but i don't know how their partitions are laid out exactly.
Click to expand...
Click to collapse
Actually we have one it's just not used due to how the device is made. I think it's a bootloader limitation based on how it was set up. I always imagined it was possible to load recovery there but I don't think the block is active or something to be used it just exists
Sent from my SM-T210R using Tapatalk
Unjustified Dev said:
It's only compatible for so long I mentioned why. These boot.img aren't really the the best solution due to changes that make it not compatible please guys go read on what a ramdisk is and what all this stuff is like init and stuff so you can understand why
Part of ramdisk is in system/core/rootdir in source code other parts come from your device tree . It's not like this code stays the same not even in the device tree it needs to be changed to fix things or give permission to new things or initialize things like sensors snd it runs more like wifi , bluetooth , etc. This boot.img was only made to allow you to get on 4.4 since recovery is in boot.img you had no choice due to recovery being incapable of installing new 4.4 since set permission is gone it's set metadata now . Compatibility with this boot.img is broken now and I wouldn't install it.
Sent from my SM-T210R using Tapatalk
---------- Post added at 12:47 AM ---------- Previous post was at 12:35 AM ----------
Actually we have one it's just not used due to how the device is made. I think it's a bootloader limitation based on how it was set up. I always imagined it was possible to load recovery there but I don't think the block is active or something to be used it just exists
Sent from my SM-T210R using Tapatalk
Click to expand...
Click to collapse
I wish there was a way to check to see if it's active without the possibility of bricking the phone. there's gotta be a workaround, but I don't know if that's even possible.
ztotherad said:
I wish there was a way to check to see if it's active without the possibility of bricking the phone. there's gotta be a workaround, but I don't know if that's even possible.
Click to expand...
Click to collapse
it's not made to be active this phone has a mtd partition I have no idea how it's set up but recovery is dead. Just kernel , cache , system , and datadata partitions are active.
Unjustified Dev said:
it's not made to be active this phone has a mtd partition I have no idea how it's set up but recovery is dead. Just kernel , cache , system , and datadata partitions are active.
Click to expand...
Click to collapse
so really that recovery is only activated within the boot.img
ztotherad said:
so really that recovery is only activated within the boot.img
Click to expand...
Click to collapse
Yep that's how it's read. Stock recover is different we had revovery .bin this was made to allow custom ones to work its how it loads it is different from stock. I think that was developed by kush. Brick your phone hard enough you will see cwm4 you installed on stock
Sent from my SM-T210R using Tapatalk
Unjustified Dev said:
Yep that's how it's read. Stock recover is different we had revovery .bin this was made to allow custom ones to work its how it loads it is different from stock. I think that was developed by kush. Brick your phone hard enough you will see cwm4 you installed on stock
Sent from my SM-T210R using Tapatalk
Click to expand...
Click to collapse
damn. that just goes with what Adam Outler created "the unbrickable mod" for the fassy. I'd love to do that with my phone and then try and flash a nexus s bootloader/kernel/etc and see if something loads. Hell, I'd even like to try it on my other fassy that is bricked/whatever to see if it fixes it. lol. I just don't know how to use a welder at all.
skepticmisfit said:
helly is still an amazing 4.2 rom. hell I'm running aokp ms6 (ics) right now and it seems to be the only thing that's fully satisfied me as of late.
Sent from my SCH-I500
Click to expand...
Click to collapse
Hey skepticmisfit and others too ,
I've seen you and a couple others prefer the aokp ics ms6 over other newer roms.
What do you feel it's doing that's hands down better?
Also...
What are its quirks?
What do you use your fassy for the most [surfing, gaming, music, mixture, other. ]
Can you list out what bugs you in newer Roms the most
I ask because I've been working hard on some tweaked settings in DU 4.4 that have reality improved the speed and stability for me and they should work for all the 4.4 Roms,,,
And I want to get some initial response to make sure I'm heading on the right path
Hopefully I'll have these tweaks in the next few days.
Whoever is ready or able to test let me know.
————— ————— —————
For me 4.4 has been good overall,,,
The hanging black screen on receiving a phone call has to be issue numero uno! drove me nuts!!!
and very slow at switching tasks ,
and slow looking up anything in the interweb,
Not to mention,, generally within a few hours from a fresh boot will cause a hang/reboot
[ or any semi heavy multi tasking it will happen faster]
So I've put a lot of hours into researching and finding out what certain settings effect and I've compared and made a spreadsheet if settings from ROM's that were popular or considered fast,,, and the results have been extremely positive
.
hhp_211 said:
Hey skepticmisfit and others too ,
I've seen you and a couple others prefer the aokp ics ms6 over other newer roms.
What do you feel it's doing that's hands down better?
Also...
What are its quirks?
What do you use your fassy for the most [surfing, gaming, music, mixture, other. ]
Can you list out what bugs you in newer Roms the most
I ask because I've been working hard on some tweaked settings in DU 4.4 that have reality improved the speed and stability for me and they should work for all the 4.4 Roms,,,
And I want to get some initial response to make sure I'm heading on the right path
Hopefully I'll have these tweaks in the next few days.
Whoever is ready or able to test let me know.
————— ————— —————
For me 4.4 has been good overall,,,
The hanging black screen on receiving a phone call has to be issue numero uno! drove me nuts!!!
and very slow at switching tasks ,
and slow looking up anything in the interweb,
Not to mention,, generally within a few hours from a fresh boot will cause a hang/reboot
[ or any semi heavy multi tasking it will happen faster]
So I've put a lot of hours into researching and finding out what certain settings effect and I've compared and made a spreadsheet if settings from ROM's that were popular or considered fast,,, and the results have been extremely positive
.
Click to expand...
Click to collapse
oh man.. well... specifically with AOKP, it's really stable and really fast a lot of the time. scrolling and opening apps is way faster than in JB and KK roms. gaming is also a bit better too. benchmarks, though they don't usually matter on phones, actually do better with an ICS rom than in JB.
some quirks with AOKP are that built in Wi-Fi tethering doesn't work and that only like two flashlight apps work (I use tiny flashlight). stock torch is broken.
Sent from my SCH-I500
skepticmisfit said:
oh man.. well... specifically with AOKP, it's really stable and really fast a lot of the time. scrolling and opening apps is way faster than in JB and KK roms. gaming is also a bit better too. benchmarks, though they don't usually matter on phones, actually do better with an ICS rom than in JB.
some quirks with AOKP are that built in Wi-Fi tethering doesn't work and that only like two flashlight apps work (I use tiny flashlight). stock torch is broken.
Sent from my SCH-I500
Click to expand...
Click to collapse
you can fix the wifi tethering issue by using Skunk works Glitch (0518 seems to be the only build still on the internet. if anyone has something newer PLEASE SHARE IT!) AOKP comes with IcyGlitch
Sent from my SCH-I500