Hello,
Introductions: I am a 15yr old Kernel Developer. Mainly for Samsung Devices. Hacking Kernels and programming is my hobby
I planned to maintain a Kernel for Galaxy NOTE N7000. However, I do not own the device and I want some BETA Testers who can help in testing out my initial Kernel builds.
Testers should-
-Know how to use adb, pull logcats
-And pull dmesg/kmsg logs for me
-Also, do some General Testing
You can have a look at my previous works by clicking links in my sig.
Interested testers, first post in the thread, then send me a PM :laugh:
Looking forward to maintaining some Good Kernels for this device :good:
Cheers, have a good day.
Dangerous lol do you know about the mmc_cap_erase bug for this device?
Tapatalking on my GT-N7000
Even more dangerous if you come to think of that the recovery on the Galaxy Note is baked into the kernel . So when your kernel is borked, your recovery will probably won't work too . Great!
I know about the eMMC bug, and that's the first thing I will get rid of before sending it to anyone for testing.
Edit: please stay on topic
Sent from my GT-I9003 using xda premium
Your gonna brick a lot of phones of people that volunteer you need to get your own note and JTAG unit for resurrecting the many hard bricks in your future... what you need is some donations to get setup and do this properly. I would look into obtaining the funds to do this. Hats off to u for using your skills to build a kernel
Sent from my SGH-I727 using xda app-developers app
TO make things more clear,
I am using Samsungs Update 4 sources(As per Entropy512, it is safe) + clearing eMMC bug to prevent a hard brick.
If anyone wants to test send me a PM.
I do not want to go offtopic anymore, if nobody is volunteering to test. I will close up the thread.
Thanks.
All known Gingerbread kernels for the Galaxy Note and other affected devices listed above
Kernels built from the GT-I9100 Update4 source code release - this includes XplodWILD's CM9 release and my DAFUQ release, hopefully more kernel choices will become available soon
Kernels with MMC_CAP_ERASE removed from mshci.c should be safe - look for it in the listed features of any kernel based off of N7000 Update3. (N7000 Update3 source code without this change made to render it safe is dangerous.)
Click to expand...
Click to collapse
A Sample commit of MMC_CAP_ERASE removed from my GT-I9103 KERNEL which uses same partitioning scheme.
[URL="https://github.com/franciscofranco/GT-N7000-ICS-3.0.y/commit/a1837cda4331d4822d8a3ba3caca8ff0d53f3b64"]Also, this commit by franco.
[/URL]
hey Adi, thanks for coming to our community-- much appreciated ! Developing kernels for the Note has been a challenge.
if you deem it proper release your work openly to our members,
you will know by the number of downloads, and feedback in the thread if your work has been appreciated/accepted/lauded...
i would come forth to test but im not an expert. just a request, be open to feedback - share your focus - safety, overclocking, root , battery or all
thanks again.
rraaka said:
hey Adi, thanks for coming to our community-- much appreciated ! Developing kernels for the Note has been a challenge.
if you deem it proper release your work openly to our members,
you will know by the number of downloads, and feedback in the thread if your work has been appreciated/accepted/lauded...
i would come forth to test but im not an expert. just a request, be open to feedback - share your focus - safety, overclocking, root , battery or all
thanks again.
Click to expand...
Click to collapse
I am always open to feedback! Now a couple of testers are ready to test.
My aim is to make a completely stable kernel, good and smooth , safe for daily use and make this device fly.
I have completely disabled the MMC Brick bug, will send the Kernel for testing to my BETA Testers, once it is good enough for a Release I will post this in the Android Dev. section. I thought of posting this here because I didn't want to pollute Android Dev. section.
Thanks!
make a thread in orignal development section maybe you get much more attention there..
Sent from my GT-N7000 using Tapatalk 2
No offence but you shouldn't have written that you are 15.
Sent from my GT-N7000 using xda app-developers app
SuperMane said:
No offence but you shouldn't have written that you are 15.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Yeah, makes me feel like a complete waste of space !:crying::crying:
Coz I'm 17 with absolutely no real contribution to XDA.
Related
So everybody knows, I have taken over as one of the Moderators for this forum.
Feel free to PM for questions,
Hit the report button if it's something you think I should take a look at.
Pax
EDIT FROM Moscow Desire,
Pax is now retired from FSM Duties. :crying:
MD
paxChristos said:
So everybody knows, I have taken over as one of the Moderators for this forum.
Feel free to PM for questions,
Hit the report button if it's something you think I should take a look at.
Pax
Click to expand...
Click to collapse
Welcome great job thanks for being a mod;-)
Welcome~!
welcome
http://forum.xda-developers.com/showthread.php?t=1711137
can u look at this thread and see if the thors kernel was ever present if it was fine if not can we get the thread reopened AOKP would be another good option for roms for the tablet.
Timelord83 said:
welcome
http://forum.xda-developers.com/showthread.php?t=1711137
can u look at this thread and see if the thors kernel was ever present if it was fine if not can we get the thread reopened AOKP would be another good option for roms for the tablet.
Click to expand...
Click to collapse
Why not just go get it from rootzwiki if you want it so bad?
bfranklin1986 said:
Why not just go get it from rootzwiki if you want it so bad?
Click to expand...
Click to collapse
I'll stick to XDA. Not everyone on here has social skills to participate in forum discussions but i find that this site has much more information and the groups of people are more eager to help troubleshoot. by unlocking the thread if its not thors kernel it opens it up to ALL of xda to help.
Timelord83 said:
I'll stick to XDA. Not everyone on here has social skills to participate in forum discussions but i find that this site has much more information and the groups of people are more eager to help troubleshoot. by unlocking the thread if its not thors kernel it opens it up to ALL of xda to help.
Click to expand...
Click to collapse
I'm not sure how many actually remember the events relating to this earlier this year... But it was a mess.
Thor decided to start developing a ICS rom providing (presumably under apache2) the device/vender tree to the build. Just two little tidbits were, how to say, off with his approach.
a) The device tree included his kernel still without the source code (so now we have some apache2 code.. nice but not required, and its poisoned with a closed source kernel)
b) he provided links to the github repo (now deleted and/or hidden) on XDA via adfly.
After this was reported, XDA closed the thread, Thor took down the git repo and tried to pan this off to his greater followers (probably successfully) as XDA not even allowing him in when him to work here even when his code is "open".
--
While the source was open blazingwolf, ProTekk, randomblame (and some others?) managed to get the repo and clone it (or parts of it) into their own projects.. Mostly with little or no credit, and not always properly removing all traces of Thors kernel (either the main kernel was replaced with blazingwolfs open kernel, but a second copy of Thors kernel in the repo was left, or they just used thors kernel as it existed in the device tree).
In addition to this there was a recovery that used blazingwolf's kernel but otherwise was a nearly unmodified thor recovery binary (simply a hex edit to change the title, and thus hide the upstream source)
--
AOKP is now using the CM9 base for the device and vender trees, so everything including the CM9 T20 kernel is open source. However I its up to the AOKP team to re-post here at this point and not someone just wanting a mirror with their own unrelated donate link.
Some locked threads to remember in relationship to this:
http://forum.xda-developers.com/showthread.php?t=1353252 - ProTekk bit of ICS locked
http://forum.xda-developers.com/showthread.php?t=1426617 - randomblame recovery - locked
http://forum.xda-developers.com/showthread.php?t=1524919 - original A500 AOPK thread - locked
Just to clear this up, roms are under Apache v2 license (which doesn't require source release) kernels are under GPL which does require source release.
Sent from my R800x using Tapatalk 2
ezterry said:
I'm not sure how many actually remember the events relating to this earlier this year... But it was a mess.
Thor decided to start developing a ICS rom providing (presumably under apache2) the device/vender tree to the build. Just two little tidbits were, how to say, off with his approach.
a) The device tree included his kernel still without the source code (so now we have some apache2 code.. nice but not required, and its poisoned with a closed source kernel)
b) he provided links to the github repo (now deleted and/or hidden) on XDA via adfly.
After this was reported, XDA closed the thread, Thor took down the git repo and tried to pan this off to his greater followers (probably successfully) as XDA not even allowing him in when him to work here even when his code is "open".
--
While the source was open blazingwolf, ProTekk, randomblame (and some others?) managed to get the repo and clone it (or parts of it) into their own projects.. Mostly with little or no credit, and not always properly removing all traces of Thors kernel (either the main kernel was replaced with blazingwolfs open kernel, but a second copy of Thors kernel in the repo was left, or they just used thors kernel as it existed in the device tree).
In addition to this there was a recovery that used blazingwolf's kernel but otherwise was a nearly unmodified thor recovery binary (simply a hex edit to change the title, and thus hide the upstream source)
--
AOKP is now using the CM9 base for the device and vender trees, so everything including the CM9 T20 kernel is open source. However I its up to the AOKP team to re-post here at this point and not someone just wanting a mirror with their own unrelated donate link.
Some locked threads to remember in relationship to this:
http://forum.xda-developers.com/showthread.php?t=1353252 - ProTekk bit of ICS locked
http://forum.xda-developers.com/showthread.php?t=1426617 - randomblame recovery - locked
http://forum.xda-developers.com/showthread.php?t=1524919 - original A500 AOPK thread - locked
Click to expand...
Click to collapse
sadly i do but the thread i linked is albeit messy with side stuff i made the assumption it was mod locked. after talking with the other people i have foudn out that the OP requested it be locked. i went and got the rom from AOKP website and as far as i can tell is Thor free and i run clockwork recovery and V8 ICS bootloader.
As for the motives for my request is i'd like to see more roms succeed for this tablet as it is "old" tech people are moving to the tegra 3 Tabs i am not ready to give up on my $567.87 less than year old purchase. I own the A501 ATT 4G LTE Variant i bought it from ATT without contract hence the price
Uhm... Hi paxChristos! Welcome to our slightly disfunctional family! I hope that you have a great time.:silly:
Timelord83 said:
As for the motives for my request is i'd like to see more roms succeed for this tablet as it is "old" tech people are moving to the tegra 3 Tabs i am not ready to give up on my $567.87 less than year old purchase. I own the A501 ATT 4G LTE Variant i bought it from ATT without contract hence the price
Click to expand...
Click to collapse
As do we all (want larger choices in roms).
But there-in lies the issue. We have an AOKP rom that has been through many hands, and at times, had some suspicious coding involved. Including getting closed on more than 1 occassion due to shady practices and non-GPL kernels. Might have been 3 seperate roms for all we know.
To post the rom now, would probably piss off quite a few people if enough credits were not given, even if the kernel proved to be legit. And even then, you would have several people claiming the rom was theirs and they were the original authors. That's the nature of these "KANG" roms and "MIUI" roms.
Well, we have polluted PaxChristo's welcome thread enough for now. I suggest we give it a rest, and probably open a new thread in the General Forum. I'll DL and install it, and see what's up with it. Post some results later.
MD
good job
paxChristos said:
So everybody knows, I have taken over as one of the Moderators for this forum.
Feel free to PM for questions,
Hit the report button if it's something you think I should take a look at.
Pax
Click to expand...
Click to collapse
t my a500wondering where to post question about how to root my tab. Sadly it is running 3.2 honey and I am very confused as what to do to get it rooted. I am in southern Louisiana, maybe there are folks close to me that could help.
Thanks everyone don
Hey thanks for being a mod' it is a lot of work I know. Listen I am knew as I just go
Hi XDians,
If any senoir member can write a step by step guide to convert (PORT) Galaxy SII rom to SII G version then it will be helpfull tohave a lot of different ROM's for the G version.
Please try to make it. We need futher more rom in G as it is picking up in mass and active members....
I would love that too but open in Q & A because all the members now wont answer and tell u wrong section
Sent from my GT-I9100G using xda premium
More and more roms is not a good idea... i like having each rom of different type.. like aokp, miui and now codename android... more roms ll not benefit...
Anyway there are no. Of porting guides which you can follow on xda already....
Please search a bit...
For eg. To port aosp rom cm is taken as base and app, font, framework, media folders are replaced by the rom to be ported.... and then in lib folder android_runtime.so is replaced and at last build.prop is edited... and if u r lucky then it ll boot
Other way is to compile from source Nd fuss is already in the process of completing the guide when he is free.... look up first before posting...
Creating a thread for a request should be the last idea and that also in Q/A section
Sent from my GT-I9100G using xda premium
Really helpful incarnation. The idea behind the forum is interaction and to learn - teach - learn.
We need a place to interact. This is not the matter of Q & A. This is more than that...
You said "if lucky then " it will work. We at XD don't depend on luck but we relay on effort....
anyhow thanks for the reply...
Looking forward for support and encouragement
Sent from my GT-I9100G using xda app-developers app
Thread moved
This absolutely does not belong in Development, it belongs in General, where it is now. If you didn't make it, it doesn't belong in Development.
gopzzz said:
Really helpful incarnation. The idea behind the forum is interaction and to learn - teach - learn.
We need a place to interact. This is not the matter of Q & A. This is more than that...
You said "if lucky then " it will work. We at XD don't depend on luck but we relay on effort....
anyhow thanks for the reply...
Looking forward for support and encouragement
Sent from my GT-I9100G using xda app-developers app
Click to expand...
Click to collapse
By being lucky i mean that all ROMS cannot be ported for any phone. One has to choose the phone (which is as close in terms of software and hardware) from which you want to port to your phone.
The method of replacing folders that i wrote is kinda for NOOBS, but heck who cares if it works i had tried to port slim jb(i9000), remics jb (i9000)and super nexus(i9100) and succeeded with nexus and remics jb.... the slim jb didnt boot unfortunately.
Whereas the method to compile from source is a better and an elegant way of doing this, and it requires some knowledge of git, linux
Fuss is busy in making a dualboot kernel for us but he confirmed completeing the thread that explains compiling aosp roms from source
If i helped hit the thanks button
Great help. Thank u for thus detailed explanation. Just now saw the work of fuss... let's cross fingers and wait
Waiting patiently for the update and a good guide
Sent from my GT-I9100G using xda app-developers app
I recently heard that FXP will stop developing for the whole Xperia 2011 series, when just around the corner, Android 4.2 was standing with a bag of goodies, for which FXP has a valid reason, that these devices lack ram to support features of 4.2. I decided to build 4.2 from source for 2011 devices, for those who'd want to try out the latest version of android. I can handle compiling ROM. But need some help with kernel. if you can help out, or if you wanna be a part of the project. Leave a comment at this thread or PM me. After public release, Dev's can submit their patches / fixes for the ROM to that thread....
I do this because i don't want us to be stuck with stock based ROMs forever and because 4.2 looks awesome . All in all, Thankyou FXP for your work.
one thing that our xperia 2011 devices (especially neo/v ) lack is kernel developers ,we dont have linux 3.0 kernel which which would have made the user experience of JB 4.1 or 4.2 better , linux 3.0 supports many advanced features of JB ,but due to lack of these kernels our user experience will be incomplete , building & testing out these kernels will take hell of time and patience.
i hope this doesn't disappoint's any user or dev just a suggestion
linux 3.0 kernels would be awesome on our phones
i wish you all the best for taking such a great project
vimjam said:
one thing that our xperia 2011 devices (especially neo/v ) lack is kernel developers ,we dont have linux 3.0 kernel which which would have made the user experience of JB 4.1 or 4.2 better , linux 3.0 supports many advanced features of JB ,but due to lack of these kernels our user experience will be incomplete , building & testing out these kernels will take hell of time and patience.
i hope this doesn't disappoint's any user or dev just a suggestion
linux 3.0 kernels would be awesome on our phones
i wish you all the best for taking such a great project
Click to expand...
Click to collapse
look here https://github.com/ExPeacer/CAF_android-msm-3.0/commits/master
progres stoped for 1 Month dont know what is problem , can you resume it ?
---------- Post added at 01:52 PM ---------- Previous post was at 01:46 PM ----------
emwno said:
I recently heard that FXP will stop developing for the whole Xperia 2011 series, when just around the corner, Android 4.2 was standing with a bag of goodies. I decided to build 4.2 from source for 2011 devices. I can handle compiling ROM. But need some help with kernel. if you can help out, or if you wanna be a part of the project. Leave a comment at this thread or PM me. After public release, Dev's can submit their patches / fixes for the ROM to that thread....
I do this because i don't want us to be stuck with stock based ROMs forever.
Click to expand...
Click to collapse
officaly thay will stop at january 2013
Guys atleast try to make the linux kernel
I can be the tester of any Rom/kernel
If you want!
Sent from my LT18i using xda app-developers app
XtremeSilencer said:
Guys atleast try to make the linux kernel
I can be the tester of any Rom/kernel
If you want!
Sent from my LT18i using xda app-developers app
Click to expand...
Click to collapse
all andoid kernel are linux (andoid is based on linux )
I want to participate in, I am not a dev but I can test all ROM fast and give ideas
n1kolaa said:
all andoid kernel are linux (andoid is based on linux )
Click to expand...
Click to collapse
I meant linux 3.0
Sent from my LT18i using xda app-developers app
I don't really need any testers if that's what your saying. I need people who can work, who can help me out.
emwno said:
I don't really need any testers if that's what your saying. I need people who can work, who can help me out.
Click to expand...
Click to collapse
then pm peaple like jader maxio fxp zackconsole pandemic ... i hope you accomplish this project!!
XtremeSilencer said:
then pm peaple like jader maxio fxp zackconsole pandemic ... i hope you accomplish this project!!
Click to expand...
Click to collapse
1. I'm not forcing any one to work on this
2. Jader, Maxio, pandemic are all greats devs but they build themes / stock, and I need help with kernel building
3. I was planning to ask FXP for some sources
4. Zack already has his hands full, look at his work.
+1
+1
emwno said:
1. I'm not forcing any one to work on this
2. Jader, Maxio, pandemic are all greats devs but they build themes / stock, and I need help with kernel building
3. I was planning to ask FXP for some sources
4. Zack already has his hands full, look at his work.
Click to expand...
Click to collapse
Hey. Why cant u ask nobodyatall. Aka naa. He has brought minicm10 to 2010 xperia Minis. Which is more stable than our cm10. I can help you with patches once you start compiling Rom. Cheers.
Sent from my MK16i using xda app-developers app
+1
+1
Sent from my Xperia Arc S using xda app-developers app
yeah the +1 counter thread
I would like to help, though I'm not of that much use YET.
Right now I'm mainly into developing apps, currently learning myself the basics of Kernel Development, I'm also capable of compiling Android.
Going to mess around a bit today, haven't compiled Android for my Xperia Pro yet.
Dympy.
Ok so.. Half way through compiling it failed, because of low storage or something. I read up online and found out that I need atleast 30gigs for compiling, where as I only have around 15-20 free on my laptop, lol unlucky I guess.. So project delayed - until I get more storage for my pc or if someone compiles for me if I give them the sources (if want 4.2 faster). And as for the kernel, instead of building a kernel (which may take long). I'll be modifying the current JB kernel for 4.2
~emwno
emwno said:
Ok so.. Half way through compiling it failed, because of low storage or something. I read up online and found out that I need atleast 30gigs for compiling, where as I only have around 15-20 free on my laptop, lol unlucky I guess.. So project delayed - until I get more storage for my pc or if someone compiles for me if I give them the sources (if want 4.2 faster). And as for the kernel, instead of building a kernel (which may take long). I'll be modifying the current JB kernel for 4.2
~emwno
Click to expand...
Click to collapse
I'm almost done with re-setting up my Linux Install, it got wiped when I installed Windows 8 on my laptop..
Anyway, I have about 800GB of storage left, if you sent me a PM with some directions and such, I'll try to compile when the install is done.
Dympy.
emwno first dev to go for 4.2
you rock
+1 pleease
Hello guys. I seen the new MIUI custom rom, which is very beautiful & full of modification along with numerous tweaks. I wonder all MIUI fan would love it. But this rom is presently developed only for sony Xperia S/SL but the developer assured me to make this one for our galaxy S3 too. But he need testers. So if anyone interested to enjoy this MIUI rom then please come & be the tester for our galaxy s3. So that he can start the new build for galaxy s3. Thanx in advance. Come soon
If most of you are ready to test this build then Required the following points by Dev....
How many you are presently porting ROMs for S3?
Which versions do you port?
Which the base and the port ROM that you opted for?
What are the Major Bugs in each of your versions?
What are the Major Bugs in your Official Release?
What are the Features that can still be improved?
Which are the Features that are Missing and Should be there?
How long would it take you to give me a very detailed testing report If I send you an experimental build?
Anything Else you would like to suggest or mention?
Anything else I should be aware of before starting working on it?
I want detailed answers on all these questions not just from you but from other users of your device who want me to start making ROMs for them. I hope you got the point what I am really trying to know here, As I don't have the device the only thing I could rely upon would be my testers.
See Rom :- http://en.miui.com/thread-7303-1-1.html
hey...I wanna be a tester
yonutz said:
hey...I wanna be a tester
Click to expand...
Click to collapse
If you are not noob. On what device you would test this rom, on galaxy nexus?
oohh no.. my signature won't edit.. i have a i9300 ..my galaxy nexus is sold.. d
Sent from my GT-I9300 using xda app-developers ap
I could test
me too...
yonutz said:
oohh no.. my signature won't edit.. i have a i9300 ..my galaxy nexus is sold.. d
Sent from my GT-I9300 using xda app-developers ap
Click to expand...
Click to collapse
Thats why i asked...
Thats greats who are ready to test this miui rom. But it is not meant to just download & get fun. It is meant to those who are expert & advanced users who can test the build properly to indentify any bugs,issue or any compatibility problem. So i request you only the well testers most wolcome here who can test this MIUI ROM.
I can test for you, tested almost every miui mintberry build. Pm me.
<=> minimal
Have anyone interested more to portting this rom for your s3?
I would like to test. I done lot of porting miui in my time. Not on s3. But the atrix.
I got friends in the miui community also which could be a big help too.
Sent from my GT-I9300 using xda premium
stevendeb25 said:
I would like to test. I done lot of porting miui in my time. Not on s3. But the atrix.
I got friends in the miui community also which could be a big help too.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Welldone. It would be great if u can try this new miui build on s3. As well as if you can bring more expert testers for miui from your community then plz tell me. So that we can provide the new miui rom for xda community. thanx
OK, so I am not a dev.
And iam completely newbie
I saw some people saying that if you have aosp on your device it's much easier to port omnirom for your device
So can I use CyanogenMod 10.2 that is available for the i9100
To build omni
And is there any detailed instruction on how to build it !!
Sent from my GT-I9100 using Tapatalk 4
I9100 needs some work because of its unified kernel, building it right now is pretty much useless if you don't know where to put your hands to solve some issues; I want to try it too but this project is in a early stage so I'll wait
Sent from my GT-I9100 using xda app-developers app
filllob said:
I9100 needs some work because of its unified kernel, building it right now is pretty much useless if you don't know where to put your hands to solve some issues; I want to try it too but this project is in a early stage so I'll wait
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Yup. There are two MAJOR blockers right now:
1) We haven't merged and tested the implementation of BOARD_SUPPRESS_EMMC_WIPE yet. So if someone were to build for a Superbrick-vulnerable device, they would have a a build that risks triggering Superbrick. While I normally don't like having moderators take down builds for something, if I see builds for Superbrick-vulnerable devices show up, I'm going to work with the mods to have them taken down until EMMC wipe suppression can be verified.
2) The build system needs some changes to permit TWRP to be built on userdebug builds. Right now, the only way you'll have a chance of working recovery is with an eng build.
Entropy512 said:
Yup. There are two MAJOR blockers right now:
1) We haven't merged and tested the implementation of BOARD_SUPPRESS_EMMC_WIPE yet. So if someone were to build for a Superbrick-vulnerable device, they would have a a build that risks triggering Superbrick. While I normally don't like having moderators take down builds for something, if I see builds for Superbrick-vulnerable devices show up, I'm going to work with the mods to have them taken down until EMMC wipe suppression can be verified.
2) The build system needs some changes to permit TWRP to be built on userdebug builds. Right now, the only way you'll have a chance of working recovery is with an eng build.
Click to expand...
Click to collapse
Can we not use cm10.2 smdk4412 kernel, @Entropy512? EMMC_WIPE is disabled there?
Also, would there be any problems if one were to remove Omni bootable project and replace it with cm10.2's?
chasmodo said:
Can we not use cm10.2 smdk4412 kernel, @Entropy512? EMMC_WIPE is disabled there?
Also, would there be any problems if one were to remove Omni bootable project and replace it with cm10.2's?
Click to expand...
Click to collapse
No, because it could still cause damage if flashing from an old "unsafe" kernel (see the first few CM10 builds as an example...). These are far rarer now than they used to be, but there are, believe it or not, occasionally people who are flashing stuff starting from TW ICS.
And CWM has tentacles throughout the CM source tree to get it to build. It requires too many hacks in too many places. TWRP is more standalone, the limitation being that on devices with standalone recovery, Dees_Troy always built using the "eng" variant instead of "userdebug".
There's a patch that allows for TWRP to build properly on userdebug using "make recoveryimage" but it fails to allow building of TWRP into unified-recovery devices like Sony pollux_windy/yuga. (Samsung requires even more hacks...)
Even the Sonys which are "sort of" working aren't ready for builds yet - for them to work they're dependent on the FOTAKernel trick Dees_Troy developed to allow for alternate recoveries to be put on a device.
Does the above apply also to the i9100g? It has an OMAP4 processor instead of Exynos so it should be easier to build for.
aidfarh said:
Does the above apply also to the i9100g? It has an OMAP4 processor instead of Exynos so it should be easier to build for.
Click to expand...
Click to collapse
I'm fairly certain the G has unified kernel/recovery just like most of the rest of the galaxys2 family (exception being the Qualcomm-based ones).
So it might build, but recovery will not function at all until the build system is fixed to properly support TWRP on devices with unified kernel/recovery.
It has nothing to do with Qualcomm vs. OMAP vs. Exynos, except that for whatever reason, Samsung actually allowed the recovery partition to serve its normal purpose on the Skyrocket and Hercules. Actually, the Straight Talk variant of the SGH-I777 might work, as that oddball device actually DID use its recovery partition.
Entropy512 said:
I'm fairly certain the G has unified kernel/recovery just like most of the rest of the galaxys2 family (exception being the Qualcomm-based ones).
So it might build, but recovery will not function at all until the build system is fixed to properly support TWRP on devices with unified kernel/recovery.
It has nothing to do with Qualcomm vs. OMAP vs. Exynos, except that for whatever reason, Samsung actually allowed the recovery partition to serve its normal purpose on the Skyrocket and Hercules. Actually, the Straight Talk variant of the SGH-I777 might work, as that oddball device actually DID use its recovery partition.
Click to expand...
Click to collapse
Is there anything I can do to help? Maybe if I can make it work on my device?
So the I9000 got a build of OmniRom, I thought it has also a unified kernel !!!
I was searching on Google today
and I suddenly found this
http://forum.xda-developers.com/showthread.php?t=2494127
that's an alpha build for I9100
it's using the CM10 kernel and it uses CWM not TWRP
Iam testing it right now
Jiangyi had some success getting i9100g working last night
I'm attempting to build for n7000 to see if it works at all... Who knows. Although I still need to merge in BOARD_SUPPRESS_EMMC_WIPE...
Entropy512 said:
Jiangyi had some success getting i9100g working last night
I'm attempting to build for n7000 to see if it works at all... Who knows. Although I still need to merge in BOARD_SUPPRESS_EMMC_WIPE...
Click to expand...
Click to collapse
I built it for Note already
http://forum.xda-developers.com/showthread.php?t=2495930
Sent from my GT-N7000 using Tapatalk
Yes @herna,you built it without a working recovery and without further testing. Nonetheless, it is running flawlessly, quicksand fluid with Raw kernel r3 and it's Cwm recovery.
Would you mind having a look at this commit.
http://review.cyanogenmod.org/#/c/50800/
Fixed the mobile data drop while calling. Thanks
GALAXY NOTE N7000 // OMNI ROM // JLS36I
AA1973 said:
Yes @herna,you built it without a working recovery and without further testing. Nonetheless, it is running flawlessly, quicksand fluid with Raw kernel r3 and it's Cwm recovery.
Would you mind having a look at this commit.
http://review.cyanogenmod.org/#/c/50800/
Fixed the mobile data drop while calling. Thanks
GALAXY NOTE N7000 // OMNI ROM // JLS36I
Click to expand...
Click to collapse
Yeah I know. Entropy and me are looking for the error, but is not beeing easy to fix. Okey, will add in a few hours and release new one. And I correct you, except the latest version, I tried all versions I released and some others I didn't release. I always do but that day I needed phone for important family things and couldn't test
Also I went to release with a prebuilt TWRP 3.0.101 kernel but XplodWilD say me that this will get Semi-Official maybe, and only compiled non-touched ROMs will be released.
Sent from my GT-N7000 using Tapatalk
@Entropy512 just wondering if your commit "i777 bringup" can be applied (obviously with some changes) to i9100
Sent from my GT-I9100 using xda app-developers app
filllob said:
@Entropy512 just wondering if your commit "i777 bringup" can be applied (obviously with some changes) to i9100
Click to expand...
Click to collapse
n7000 bringup would be easier, methinks.
filllob said:
@Entropy512 just wondering if your commit "i777 bringup" can be applied (obviously with some changes) to i9100
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Ask some DEV to try and see if works
Enviado desde mi GT-N7000 mediante Tapatalk
---------- Post added at 01:45 PM ---------- Previous post was at 01:44 PM ----------
chasmodo said:
n7000 bringup would be easier, methinks.
Click to expand...
Click to collapse
N7000 is gonna be up as soon as XplodWild get free and merge it and change something I said him. Idk why my Gerrit is not working. I am gonna install Ubunt 13.10 for clean and will set up all again for try if I can get Gerrit working again
Enviado desde mi GT-N7000 mediante Tapatalk
I'd like to try it myself, just want to know if it's legit or not
Sent from my GT-I9100 using xda app-developers app
filllob said:
I'd like to try it myself, just want to know if it's legit or not
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
If is legit what? I cannot understand you, sorry. You want to try, to compile...?
i am a noob to compiling etc, only followed cm instructions.
I want to know if the changes in the commit I mentioned can be applied to i9100 too, obviously with some adjustments, and if there is something more to do to compile omni for i9100
I hope I explained myself right( English is not my language)
Sent from my GT-I9100 using xda app-developers app