Database Develop

[kernel][testing]Unhelpful Kernel (from Captivate)

I'm trying to get the kernel I've been working on for Captivate working on Vibrant. This poses a bit of a problem, because while I have access to a Vibrant kernel and initramfs, and a known-working config for Vibrant, I lack access to a phone.
I've forked a test branch based on what I have so far. I would appreciate pretty much any of the following:
a volunteer to build this kernel or test a binary
a volunteer to help with Vibrant development
any other Vibrant-specific details that don't apply to Captivate or to SGS in general
I have already built a binary, but it is mostly untested. I want to make it very clear that this is a testing kernel. It should work, it should not break anything... but it might not boot, it might wipe data, I haven't heard of it happening to anybody yet but it's certainly not impossible that it might damage hardware. These are unlikely, except for not working, but are all possible outcomes of trying this kernel. If you want to test this, read the OP in the thread for the Captivate version, have backups of your data ready, preferably duplicated to a hard drive or an SD card that is removed before testing. Have Odin3 and a stock Vibrant kernel on hand, and have ClockworkMod recovery installed.
If it hangs starting up, wait a bit, then pull the battery and start in recovery without trying to start up normally. Then, start clockworkmod, mount /system, and use adb to pull /system/user.log - this should contain a log of what happened when the user init scripts ran, and may provide clues as to what went wrong. You can make sure it doesn't include anything you don't want to reveal, and just PM it to me or join #sgs_dev on freenode and talk to me or some other developers there - perhaps a dev with a Vibrant will have a better idea where to start.
In the long term, I would not mind somebody forking the github repository to work on any Vibrant-specific issues. I can then try to pull changes from a fork and do builds for both phones, if somebody doesn't want to do the Vibrant builds themselves.
Good luck, and thank you.

if no one volunteers by the time I finish installing openSUSE I'll give it a whirl. the binary that is.
Sent from my SGH-T959 using Tapatalk

ill be more than happy to test the binary

I too will be more than happy to give any sort of help possible. Should this be a start from a stock kernel and build deal, ie stock kernel stock rom just rooted with clockwork?
Sent from my Vibrant using tapatalk pro

If you're using a lagfix with the playlogos hack you should undo it first, or set up your user init script to run in the new early user init. Other than that anything that works with a stock kernel should still work.
Sent from my SAMSUNG-SGH-I897 using XDA App
EDIT: "lagfix", thx swype.

Unhelpful said:
If you're using a ladies with the playlogos hack you should undo it first, or set up your user init script to run in the new early user init. Other than that anything that works with a stock kernel should still work.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I'm about to build from your source i just forked to see whats diff then mine. They look though to be about the same except for nilFS
I will probably fork and maintain a vibrant tree with ivan who also has a Vibrant. That way we can get the best of both worlds. And being that we are in the same IRC we pretty much have identical mods to our kernels.
So most likely any changes you make to your captivate Kernel will end up in the vibrant branch as well and I also have the device to test with
See ya in IRC

anomalous3 said:
if no one volunteers by the time I finish installing openSUSE I'll give it a whirl. the binary that is.
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
haha if ur talking about the linux distro i know what u mean

Excellent news! I have some things in my tree I think you could use here, too, but it's much easier to have a developer with a Vibrant who can build them and test immediately.

What advantages does the captivate kernal have over the vibrant kernal, if any?
Sent from my SGH-T959 using Tapatalk

rei165 said:
What advantages does the captivate kernal have over the vibrant kernal, if any?
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
The stock captivate kernel doesn't have any "advantages" and wouldn't really work. Unhelpful, however, has added nilfs support to the captivate kernel as well as some other tweaks, and has now made these changes available to the Vibrant community. As I understand it, NILFS mounts, reads, writes, and unmounts faster on our devices than any of the other filesystems he tested, so there's hope for a permanent lagfix.

I tried this kernel, it does boot but my existing lagfix scripts don't work with it, so I lose all my data. No big deal to fix from recovery, just revert to stock before messing with it if you want to test it. As mentioned, no real advantage either way, but it's nice to have options.
If there is interest, I'll fix my lagfix scripts to run on this kernel. Reverting back to JAC OVv4 works without hassle via clockwork.

[HELP!]Need a kernel/ROM with DM_CRYPT/LOOPBACK

Hi again,
I need to find a kernel that has DM_CRYPT included/enabled. Is it possible to find that, just kernel and stay on stock GB? Or do i have to flash a custom rom, if so, which do have DM_CRYPT? Hope someone can assist me quickly, since this depends on wether if i'll keep the note or not...
Thanks!

it would be kernel related not rom related, you would have to see if a dev woudl put this into a kernmel for you but why do you need it?

Some apps need it. And i need them. I heard that all Honeycomb roms have it, so i guess ICS too. But i'm not gonna take risks since i might return it. And i don't have much time... How am i supposed to i "contact a dev" to request that? Is that a request board? If i'm alone to request it won't happen anyway.

Abyss kernel (v3.1) is compiled with CONFIG_DM_CRYPT=y . Since there is nothing about it in the changelog, I expect the latest version also has this option enabled.

Thanks! I'm gonna try it then. But what's difference between CW Touch & RedPill? I know CW Touch of course... But not RedPill. Anyway, if i flash this, Custom Rom Manager (from CF-Root) won't work anymore, eh? I can switch kernel, no risk? If anyone know other kernel with DM CRYPT , please post! ^^
PS: If it's just a line to edit "CONFIG_DM_CRYPT=y" then can't i just do it somehow on any kernel?
EDIT: I installed 4.2 and the app which required dmcrypt still refuse... If it was loaded, then should work directly, eh?

I'm sorry but i forgot a thing : "Loopback device" is required too, i guess this is some setting in the kernel..? Or is it something else? If so tell me what please Abyss doesn't work, i tested 3.5 too (can't test older since megaupload's dead... If you have links...) :X

Help with some concepts!!!

I'm having some problems to understand or find the difference between two concepts:
difference between kernel and firmware...
I really can't find the difference. Thanks for helping me
Sent from my SAMSUNG-SGH-I897 using xda app-developers app

Fersh0o said:
I'm having some problems to understand or find the difference between two concepts:
difference between kernel and firmware...
I really can't find the difference. Thanks for helping me
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
I'm still a noob myself, but this is what I think would explain this simply. The firmware is the ROM that you place onto your phone. This encompasses the user interface and overall function as seen by you, the user. The kernel is what tells the device what to do by allowing the hardware and software (firmware) communicate with each other. They're two separate items, but must be compatible in order for the device to function (and even boot) properly. For example, a kernel not meant for captivate firmware won't boot because it can't communicate the right messages to the hardware of the device to normally go through the start-up process. Kernel is also what allows many things to work right since it is hardware-related. Many custom kernels add functions like overclocking, underclocking, and many other tweaks that stock kernels can't. In turn, some beta kernels make the phone lose some functionality such as wifi, data, and video playback because it can't communicate with the phone's internals correctly. To sum it up, kernel is always present as a silent hero behind the firmware which you see and touch on the screen of your phone. The firmware bosses it around, but without a kernel, the firmware is nothing.
Hope this helped you a bit.

From noob to noob thanks a lot! Now I know more about this two concepts, this really helps me to understand better how they works, and at the same time has helped me to clarify and answer other questions that I had.... :laugh: Now I think I´m ready to start rooting my Cappy.
Once again THANKS! Belive me this helped me a lot... :good:

actually, firmware includes both the kernel and the various device drivers (example: graphics/touchscreen driver, modem that runs communications hardware for a specific phone on a specific network).
its the part of the phone's instructions that generally do not change regardless of which applications you install or remove from your phone via google play or other sources.
the rom flashing packages that folks develop and post on xda may include just a kernel, just a modem, or a complete rom that either matches, or differs, from the stock rom by Samsung/AT&T.
here's a link that may help
en.wikipedia.org/wiki/Firmware
Sent from my SAMSUNG-SGH-I897 using xda app-developers app

Rooted. Now what?

I was able to root my XT1068. What should I do now to 'enjoy the benefits' of a rooted Android? Someone please guide me. I am an absolute beginner.

if you dont know why you're rooting, why you're rooting?

Johnny_Queste said:
if you dont know why you're rooting, why you're rooting?
Click to expand...
Click to collapse
I know why I'm rooting. I know basic things about flashing ROMs and kernels. I flashed a CM13. I read that there is lot of other stuff that can be done, like increasing RAM and CPU and all that. But I couldn't find any specific guide anywhere. I don't want to mess up my phone, so asked. I tried to flash a (Halogen) kernel using some not-so-helpful guide and it had bugs. E.g. The WiFi wouldn't turn on. That's why it would be very helpful if someone told me properly what to do and how to.

hungryCharizard said:
I know why I'm rooting. I know basic things about flashing ROMs and kernels. I flashed a CM13. I read that there is lot of other stuff that can be done, like increasing RAM and CPU and all that. But I couldn't find any specific guide anywhere. I don't want to mess up my phone, so asked. I tried to flash a (Halogen) kernel using some not-so-helpful guide and it had bugs. E.g. The WiFi wouldn't turn on. That's why it would be very helpful if someone told me properly what to do and how to.
Click to expand...
Click to collapse
Technically you can't increase your RAM and CPU.
There are apps which say they do but I wouldn't do that if I were you.
Well if you fashed cm 13 then you know it's already rooted (in developer settings).
Flashing custom kernels is your choice.
Rooting is not that great, it does open up a whole new window of things but it comes at the cost of jeopardising the security of the system.
Do some research yourself, apps which you can use ,mods etc.
Everybody's uses are different so you won't get a proper answer but you will get tons of opinions.
And if you need help with anything then ask in the related thread and you will receive help.

Dim or switch off hardware buttons backlight on custom rom

What's up everybody?
I think I need some help.
I'm running a custom rom, apparently without any setting around the possibility to switch off or dim the hardware buttons backlight.
I'm wondering if it was possible to use a third party app, if it exists, or to modify any build.prop line or some more stuff like that, waiting for my rom developers to add this feature.
Please don't talk to me about xposed modules, I don't want to install xposed.

What custom rom are you using? Cause I'm using RR and I have this option right in the configurations part of settings.

se7ensde said:
What custom rom are you using? Cause I'm using RR and I have this option right in the configurations part of settings.
Click to expand...
Click to collapse
I know. I'm running Reaper OS (what was Broken OS up to few weeks ago). You can't find anything on XDA about it, that community doesn't want their rom to be discussed here.
I already asked in their community what was to be asked.
What I'm asking here, is a workaround on any android 7.1.1 custom rom. It can also help few other people with the same problem and not necessarily the same rom.

bigo72 said:
I know. I'm running Reaper OS (what was Broken OS up to few weeks ago). You can't find anything on XDA about it, that community doesn't want their rom to be discussed here.
I already asked in their community what was to be asked.
What I'm asking here, is a workaround on any android 7.1.1 custom rom. It can also help few other people with the same problem and not necessarily the same rom.
Click to expand...
Click to collapse
well if that's a feature you want I would say you should switch ROMs. I don't know of any workaround for this. Or you might try requesting it to be added in by the Dev.

@se7ensde I thank you very much for your time and efforts, but you are telling me obvious things.
This rom simply rocks on this device and, as I said, I'm already asked this feature on the right channels.
I'm asking a workaround, not another rom, I tried all of them already.