Related
Hi All,
Running rooted Hero with Modaco 2.5.1 rom ( thanks Paul )
Was hoping someone could ( simplistically ) answer a few question for me.
As I understand it - one of the things holding back development of Hero ROMS is that HTC haven't released the kernel for the Hero.
1) What exactly IS the kernel in the greater scheme of things?
2) When are HTC likely to release it?
3) When it is released, what new things will it allow developers to do?
4) Anything else relevant to it worth knowing?
TIA
Look at these:
1. The kernel is the Operating System for the phone, it runs everything.
2. That is the magic question...
3. It'll allow more development in terms of mods. we'll be able to change alot more and get more out of the phones.
I'm sure others will have more detailed explanations.
Regarding question 2:
I've gotten response from HTC support the other day that the release is planned but no sure date could be given.
Date: 5th of October
My question:
Hello there, I realize that this might not be the normal kind of request you guys get, but here goes. This is probably not your average request and might require escalation. I was wondering when the source code for the Hero kernel was gonna be available at developer.htc.com?
Click to expand...
Click to collapse
Answer:
Hello
This is quite a normal question we get here at HTC. The source code is something that will becoming soon. We have had contact with those far higher than my self or are planning on adding the source code as soon as possible. I have not been given a time scale but bases on the code for the two other handsets i should expect it in the next couple of weeks.
Hope this helps.
Click to expand...
Click to collapse
So, educated guess would be around the release of the Hero in the US.
Some if I have this right -
The kernel is the basic underlying OS of the phone, and a ROM sits on top of this end gives us the end user experience ( and Sense UI is within the ROM ).
Am I right in thinking the kernel is linux based?
And a big magic question - when the kernel is released, will people be able to modify it and get the bluetooth working properly?
Sorry if it's a bit basic - but interesting to me....
The Kernel is not the OS (As most people understand an OS to be) (OS meaning Operating System)
It's at the core of the OS but is not the OS. You can keep the same build of an OS but update the kernel and vica versa. It is (put simply) what converts the hardware calls from the OS into something the hardware understands.
So (using current issues as explanation) The OS tries to load the GPS and the kernel isn't configured with the right settings the GPS won't load. Similarly if you try and use the trackball and it's not setup in the kernel then it won't do anything.
The OS will still work fine with other things but until the kernel has the right settings put into it it just won't see the parts of the phone it's not set up to.
Here is a technical description of a Kernel.
http://www.linfo.org/kernel.html
I'm sure I've just made it as clear as dishwater but if not I hope it's helped.
J-Zeus said:
Some if I have this right -
The kernel is the basic underlying OS of the phone, and a ROM sits on top of this end gives us the end user experience ( and Sense UI is within the ROM ).
Click to expand...
Click to collapse
Not exactly. To add to what akirainblack has said already...ROM stands for Read Only Memory. In this context it is a bit different as it is the complete package that makes up the Kernel, the OS and anything that is pre-installed to the phone. When you run the RUU (Rom Update Utilitiy) on your PC is completely refreshes the system software in your phone - Kernel, OS and any pre-installed apps - just as if you had bought it from the shop like that.
J-Zeus said:
Am I right in thinking the kernel is linux based?
Click to expand...
Click to collapse
Yes.
Hmmm...
simple question... when the kernel is available... would we be able to get a white taskbar on the Hero?
//Nik
When the kernel source is available, we should be able to rebuild Android completely from the source code repositories and do practically whatever you want.
Regards,
Dave
foxmeister said:
When the kernel source is available, we should be able to rebuild Android completely from the source code repositories and do practically whatever you want.
Regards,
Dave
Click to expand...
Click to collapse
Including getting Bluetooth working?
J-Zeus said:
Including getting Bluetooth working?
Click to expand...
Click to collapse
In theory, yes. In practice, the situation is a little more complicated, but at the very least I'd imagine it would be possible to get BlueX, or something like it, working on rooted Heros fairly quickly.
Regards,
Dave
Given that this is a Linux kernel, aren't HTC required by the GPL to make the source available to all Hero owners?
This is covering the same ground, but is another way to look at things regarding the kernel and the OS. The kernel abstracts the specifics of the hardware from the Android system. For example, when the Android system requests that the bluetooth hardware be enabled, the kernel can translate that request so that it works with the particular hardware of the phone - as the bluetooth hardware of the Magic may be different from the bluetooth hardware of the Hero. So the kernel, is an interface that translates and Android call to the specific hardware level controls necessary. The kernel sits between the hardware and the Android system.
It also means that releasing the kernel will not allow us to make changes to the Hero Android user interfaces. If we want to change colours, icons and so on in the Hero ROM, we would need the source code for their "tweaked" Android and maybe to some degree their TouchFlo software. I doubt they would give that away. It would allows us however, to tweak the kernel, or transplant the driver code for specific hardware pieces in the Hero, to a newer version kernel.
I understand that the release of the hero kernel, could help me with my cause (getting 1.5/1.6 'clean' android on my hero without any htc apps/front ends).
Somebody suggested contacting HTC and asking for it to be released.
I have a few questions regarding that:
1) Has this happened before? That HTC released an android kernel?
2) Did this happen after the request?
3) Who should we contact to get it? (which HTC division)
4) Is there a possibility that they don't want to release it, because it would allow people to copy parts of the proprietary interface?
E2K said:
1) Has this happened before? That HTC released an android kernel?
Click to expand...
Click to collapse
Take a look at http://developer.htc.com/
The Dream and Magic sources are available.
E2K said:
4) Is there a possibility that they don't want to release it, because it would allow people to copy parts of the proprietary interface?
Click to expand...
Click to collapse
The HTC Sense UI won't be included in the kernel source.
They dont have to release the source of them.
New question
Is it possible to create a new donut kernel (2.6.29) with the changes they made to the 1.5 kernel (2.6.27)?
Looks like they send you the hole kernel, not just some patches and new drivers...
mopodo said:
Take a look at http://developer.htc.com/
The Dream and Magic sources are available.
Click to expand...
Click to collapse
So this means that we could compile or 'cook' a working vanilla android 1.5 for the HTC hero, with everything working fully?
HTC HAS to release the kernel source as required under the GPL license that the kernel was released under. It is indeed a linux kernel and it contains the necessary parts to work the hardware along with extra drivers and modules (stupid monolithic kernels).
Here's what I don't get (and hopefully somebody will clarify this for me). Why hasn't anybody tried building android with the current kernel available? Android has the ability to be built around a pre-compiled kernel (it does this if you do a straight make right after repo sync with the pre-compiled dream kernel). You'd only need to re-build the wlan.ko module for the new kernel and the gps module would be compiled against the specified kernel, so it should work.
If I had Hero, I'd test it (if you want to trade your Hero for my G1, hit me up ), but there's no reason it shouldn't work.
Up to now, I've only seen ports, and those are hard to make work because of the pre-compiled files, so that leads to loads of file-swapping and finger-crossing, but an AOSP make should still work. Anybody wanna try it (or post me a hero kernel and I'll compile you a stock donut build to test).
jubeh said:
HTC HAS to release the kernel source as required under the GPL license that the kernel was released under. It is indeed a linux kernel and it contains the necessary parts to work the hardware along with extra drivers and modules (stupid monolithic kernels).
Here's what I don't get (and hopefully somebody will clarify this for me). Why hasn't anybody tried building android with the current kernel available? Android has the ability to be built around a pre-compiled kernel (it does this if you do a straight make right after repo sync with the pre-compiled dream kernel). You'd only need to re-build the wlan.ko module for the new kernel and the gps module would be compiled against the specified kernel, so it should work.
If I had Hero, I'd test it (if you want to trade your Hero for my G1, hit me up ), but there's no reason it shouldn't work.
Up to now, I've only seen ports, and those are hard to make work because of the pre-compiled files, so that leads to loads of file-swapping and finger-crossing, but an AOSP make should still work. Anybody wanna try it (or post me a hero kernel and I'll compile you a stock donut build to test).
Click to expand...
Click to collapse
Hi, thank you for this information. You make it sound like it's possible
I tried searching for the Hero Kernel, but I could only find this:
http://developer.htc.com/
The hero is not listed (maybe it shares a lot with the magic kernel?).
edit: this post dating from september 10 stated that HTC would "release the kernel source soon".
This was more than a month ago though..
edit2: calling HTC Netherlands right now..
edit3: after explainig the need for the kernel, I've been on hold for 10 minutes now..
edit4: more than 18 minutes now
edit5: after 26 minutes I hang up
Well I have a Hero running Modaco 2.2. I could post this kernel (where?) Or it surely could be extracted from one of the ROMs available on this very site
SquiffSquiff said:
Well I have a Hero running Modaco 2.2. I could post this kernel (where?) Or it surely could be extracted from one of the ROMs available on this very site
Click to expand...
Click to collapse
I could be wrong, but I believe there is a difference between the 'kernel', and the 'kernel source'. The second one is needed when you want to compile the kernel.
Speaking as one who has compiled kernels in the past there are three components required here:
The kernel source- this is typically available from http://kernel.org/ If HTC have made any changes to the source of the kernel itself then these should be apparent in their distribution of the kernel source
The relevant configuration file '.config' which should accompany their distribution of the kernel source and permit you to compile any other kernel as a drop in replacement.
Source code and makefiles for any custom kernel modules ('drivers' in windows terminology) In Linux these have to be compiled together with the kernel.
To use a cookery analogy:
The kernel source is the raw ingredients. It can be set up for anything from a supercomputer to a DVD player depending on how you use it. The kernel config is the method which will allow you to bake the type of cake you intend. The modules sources are any of HTC’s own custom ingredients required for everything to work. THe kernel is the finished cake which you eat.
As you may know, HTC have just released the kernel source code, and i've been having a play.
Nothing massively exciting yet, but if you want your kernel to feature...
- Additional filesystems (EXT4, NFS, CramFS, SquashFS 4.0)
- Freshly compiled tun.ko module
- CompCache 0.5.4 support
- Required iptables functionality for DroidWall
...then you can install this package over the top of the latest MCR.
This is pretty much untested at the moment, so Nandroid backup first (of course), and i'm taking requests for future improvements. This is seperate from the main MCR thread for now simply because of it's untested nature!
I'd like to add...
- Port to 2.6.29 kernel
...but as I say this is just an early first-stab at a custom kernel. I thought i'd put it out there as I know many people like to run EXT4 on their A2SD partitions.
Download: MoDaCo
Enjoy!
P
Changelog
1.2
Added DroidWall support
1.1
Internal (non public) Test Release
1.0
Initial Release
Added source download.
P
We could look into Bluetooth OBEX file transfers now...
oblika said:
We could look into Bluetooth OBEX file transfers now...
Click to expand...
Click to collapse
http://code.google.com/p/androidobex/source/checkout
Version 1.2 up, added DroidWall support.
P
MCK 1.2 is now rolled into MCR 2.8. This thread will remain as the test bed / source code post.
P
good going Paul.
Good work Paul ,I apriciate your hard work. You are our HERO.
gangstaunitg said:
Good work Paul ,I apriciate your hard work. You are our HERO.
Click to expand...
Click to collapse
Bump - i second that!
MasterOfDesasters said:
Bump - i second that!
Click to expand...
Click to collapse
I have to third that.
modaco said:
As you may know, HTC have just released the kernel source code, and i've been having a play.
Nothing massively exciting yet, but if you want your kernel to feature...
- Additional filesystems (EXT4, NFS, CramFS, SquashFS 4.0)
- Freshly compiled tun.ko module
- CompCache 0.5.4 support
- Required iptables functionality for DroidWall
...then you can install this package over the top of the latest MCR.
This is pretty much untested at the moment, so Nandroid backup first (of course), and i'm taking requests for future improvements. This is seperate from the main MCR thread for now simply because of it's untested nature!
I'd like to add...
- Port to 2.6.29 kernel
...but as I say this is just an early first-stab at a custom kernel. I thought i'd put it out there as I know many people like to run EXT4 on their A2SD partitions.
Download: MoDaCo
Enjoy!
P
Click to expand...
Click to collapse
I'd love to help test this however I'm new to Android so when you say MCR I assume you mean the latest Modaco Rom? So I should install MCR then install this? Sorry and thanks, looking forward to giving it a go
will this have CDMA support by any chance for the CDMA hero?
jman069 said:
I'd love to help test this however I'm new to Android so when you say MCR I assume you mean the latest Modaco Rom? So I should install MCR then install this? Sorry and thanks, looking forward to giving it a go
will this have CDMA support by any chance for the CDMA hero?
Click to expand...
Click to collapse
The MCK kernel was added to the custom ROM in version 2.8, so if you want it all you have to do is install the MOdaco ROM 2.8
Well may be it is possible to make clean Android OS available for HTC Hero since kernel sources are released? With no Sense UI etc.
NoXXX said:
Well may be it is possible to make clean Android OS available for HTC Hero since kernel sources are released? With no Sense UI etc.
Click to expand...
Click to collapse
There seem to be more and more people expecting that
all our hopes r on the devs. only they can provide us something. good job guys. keep it up.
*sorry. double post*
No sense UI..................Slightly off topic
frandavid100 said:
There seem to be more and more people expecting that
Click to expand...
Click to collapse
I dont understand all the people not wanting sense UI
if you dont want it, go into settings--------manage applications-----find touch flo and clear defaults....
The next time you press the home button, just press launcher and make it your default home screen.
There you have it...
Sorry Paul for going slightly off topic
Some people do not want it because they find it heavy.
By using the clear defaults method you only visually disabling it, but in the background the sense ui processes are still running.
ZenorGR said:
Some people do not want it because they find it heavy.
By using the clear defaults method you only visually disabling it, but in the background the sense ui processes are still running.
Click to expand...
Click to collapse
Ever heard about Paul's Rosie remover? I think what people want is to get features of e.g. Cyanogens work in a ROM, and the ability to modify. In fact if you remove Rosie, add some vanilla android apps and change the Hero drawables in the framwork.apk you'll get a "vanilla" looking and working kind of ROM.
I'm pleased to present my MoDaCo Custom ROM for the Samsung Galaxy S! READ THIS WHOLE POST BEFORE YOU START! No, really, it contains everything you need to know. wink.gif
This ROM is the 'starting point' for my Galaxy S custom ROMs.
About MoDaCo Custom ROMs
MoDaCo Custom ROMs are based on official ROMs - either shipping or leaked. A MCR release is designed to feel as far as possible like a stock ROM, with optimisations, tweaks and complimentary additions that enhance the user experience. The aim of a MCR is to be ultra reliable for use on an everyday device.
Requirements
In order to use this ROM on your device, YOU MUST ALREADY BE RUNNING THE JFB ROM FROM HERE. Do NOT use this ROM with any other base, unpredictable things will happen, the most likely being you'll have to reflash your device via Odin.
Features Included
* Based on the JFB release
* Rooted with Superuser 2.1 by ChainsDD
* Built with the MCR build process which reduces the size and boosts the speed of the ROM
* busybox with Droid Explorer support
* Updated Google Maps
* MCR version displayed in 'About' screen
* Optional Google Voice Search
* Optional Google Voice Dialer
* Optional Fancy Widget
* Optional Beebplayer
* Optional baked in Wavesecure via the online kitchen (installed to system partition for maximum security)
Changelog
Please see 2 posts below this one for the changes in each release.
Installation
To install this ROM:
* Ensure you have the JFB ROM installed (linked above)
* Download the zip file of your choice from the links below (or the online kitchen) and copy to your SD card named 'update.zip'
* Restart your device in recovery mode by running 'adb reboot recovery' (download adb if you do not have it already, use adb-windows, adb-mac or adb-linux as appropriate)
* Select the option to apply an update zip, and select the zip file you copied to your memory card
Upgrading
No wipe is explicitly required in order to use this ROM, however if you do encounter issues of any kind, it is recommended that you wipe your device and reproduce the issue before raising it here.
Downloads
This ROM is currently only available in the online kitchen - prebakes to follow.
Thanks
It's impossible to mention everyone who contributes to the Android community by name, but to everyone out there who does great work and shares it with us all - you have my gratitude and respect.
And finally...
If you would like to show your appreciation for the ROM, please consider supporting MoDaCo by signing up for a MoDaCo Ad Free or MoDaCo Plus account, both of which also give you early access to Beta ROM releases and access to the the online kitchens.
Enjoy!
http://android.modaco.com/content/s...rom-for-samsung-galaxy-s-with-online-kitchen/
Does this ROM fix the ram issue so that all 512MB of ram is utilized?
Congrats on being the first custom rom here.
Congratulations! I don't have a phone yet but I am very pleased to see a custom rom already!
woohoo custom ROMs already. Guess I'll be getting myself the phone after all.
umm.. but in another thread people where saying that it wasn't gonna be possible because samsung encrypt their drivers etc. so this mean they did release they drivers? and there is gonna be alot of custom rooms for galaxy gravity?
Perrosky said:
umm.. but in another thread people where saying that it wasn't gonna be possible because samsung encrypt their drivers etc. so this mean they did release they drivers? and there is gonna be alot of custom rooms for galaxy gravity?
Click to expand...
Click to collapse
No I said it would be near impossible to get roms from other sources like Sense roms or Froyo on because of the driver issue. I never said you would never see custom roms. The only roms you are going to see are one's based off of Samsungs release.
Hold on, hold on. So even though Samsung released the Galaxy S' driver source code to the public, it's going to be "near impossible" to port Sense and FroYo to the phone? I may be ignorant but I'll just ask with ignorance, how do you figure?
Javalu said:
Hold on, hold on. So even though Samsung released the Galaxy S' driver source code to the public, it's going to be "near impossible" to port Sense and FroYo to the phone? I may be ignorant but I'll just ask with ignorance, how do you figure?
Click to expand...
Click to collapse
Download the source code..... ok now open it and go to GalaxyS_Kernel.tar.gz. Now in there just enter the first folder then go to modules. Go to Dpram. Open up any of those files in notepad. You should see written non-compiled code right? That is fine now go back to the module folders and go to S3cbc. Now open up s3cbc_module.o. Does that look like non-compiled code? No it doesn't. It's either already compiled or encrypted. That's what I mean
psychoace said:
No I said it would be near impossible to get roms from other sources like Sense roms or Froyo on because of the driver issue. I never said you would never see custom roms. The only roms you are going to see are one's based off of Samsungs release.
Click to expand...
Click to collapse
Quick question, does that mean any custom rom that is release will be based off the official rom they release which has Touchwiz backed in? If so, does that rule out a plain vanilla android rom for this device? Thanks for your help and appreciate the knowledge.
Papa_I said:
Quick question, does that mean any custom rom that is release will be based off the official rom they release which has Touchwiz backed in? If so, does that rule out a plain vanilla android rom for this device? Thanks for your help and appreciate the knowledge.
Click to expand...
Click to collapse
No it doesn't rule out plain vanilla android rom. Yes they will all be based on Samsung but rom makers can take out all the touchwiz garbage and throw in another launcher like adw or Launcherpro.
That's what I wanted to hear. Thanks for the help. Now if I only could decide if I should keep the Nexus One or purchase this phone..... Decisions, Decisions.
psychoace said:
Download the source code..... ok now open it and go to GalaxyS_Kernel.tar.gz. Now in there just enter the first folder then go to modules. Go to Dpram. Open up any of those files in notepad. You should see written non-compiled code right? That is fine now go back to the module folders and go to S3cbc. Now open up s3cbc_module.o. Does that look like non-compiled code? No it doesn't. It's either already compiled or encrypted. That's what I mean
Click to expand...
Click to collapse
How lame. Have other handsets had similar problems?
what are talking about .o files and unix compiled modules same on all versions of unix. o stands for object module.
Javalu said:
How lame. Have other handsets had similar problems?
Click to expand...
Click to collapse
Yes the Behold 2, the original Galaxy, and the Moment all made by Samsung have only had Samsung roms on them.
lgkahn said:
what are talking about .o files and unix compiled modules same on all versions of unix. o stands for object module.
Click to expand...
Click to collapse
So they can easily be decompiled? If it's source code why is it already compiled?
dont go too deep into specific things that we may not even need (we are not coders here) but the source code for basic hardware that we need to get things going are already there.. things like camera, wlan, etc. btw, do u know what s3cbc is for?
raspdeep said:
dont go too deep into specific things that we may not even need (we are not coders here) but the source code for basic hardware that we need to get things going are already there.. things like camera, wlan, etc. btw, do u know what s3cbc is for?
Click to expand...
Click to collapse
What about s3clcd? Here is a little copy and paste of some of the garble that was in the compiled file
screen width=%d height=%d va=0x%x pa=0x%x
I would go out on a limb and say those are video drivers. The one's that have been encrypted on all other samsung phones.
Also in s3cbc there is some code at the bottom
PVRSRV_PIXEL_FORMAT_YUY2 PVRSRV_ERROR_FIFO_SPACE char ui32ByteStride psDevInfo PVRSRV_PIXEL_FORMAT_PAL1 PVRSRV_PIXEL_FORMAT_PAL2 pfnOpenBCDevic
If you don't know the Galaxy's gpu is PowerVR SGX540 and YUY2 is a colol format for video screens
http://www.fourcc.org/yuv.php#YUY2 and Pal is of course a European video standard.
they are not encrypted, they are object codes in machine language for arm.. and why we need that again for custom roms?
Wanted to test modaco ROM but they are not free.. Any kind souls upload and share ?
well feedback on the R1 rom its clean and smooth, worked even better when i did the stall tweak posted here
http://android.modaco.com/content/s...298/got-the-stalling-problem-rooted-try-this/
the phone seriously got 2 times faster, opening apps playing game very quick .. happy as here
Ferdimage said:
well feedback on the R1 rom its clean and smooth, worked even better when i did the stall tweak posted here
http://android.modaco.com/content/s...298/got-the-stalling-problem-rooted-try-this/
the phone seriously got 2 times faster, opening apps playing game very quick .. happy as here
Click to expand...
Click to collapse
How much free ram have you got? Considering flashing and rooting, but not sure if it's worth it right now. Meh 10£ isn't that much think I'm gonna give it a try.
EDIT: Just flashed, but now I don't have root access(says access denied when I try to access the /data/data folder). Thought this included the rooted PDA file or do I have to flash that again with odin?
EDIT2: Scratch that I forgot to press the allow-button on my phone after sending the Super-user request..
.
.
.
sediROM - or why I created a new ROM based on the good old ("ancient") ICS
.
.
.
Long story short. The following list are my requirements to a custom ROM:
I need my phone everyday so I need to resist that it is working everyday (means rock stable).
I do NOT need the latest available Android version.
I WANT to have the other components (like Kernel etc) up to date.
I REALLY REALLY need headset profiles for my bluetooth devices (Jabra, Nokia and Plantronics)
I need root access, of course.
I want to get the best battery life possible.
GB is too old for me.
Stock ROM is "too stock" for me.
I have tried all available captivate ROMs starting from ICS over Jelly Bean to KitKat.
Android < v4.x are too old for my requirements. Several features missing and well it even LOOKS old..
Android >= v4.1 are working well with the Glide but there is 1 main killer function which is completely broken since Android 4.1: Bluetooth Headset Profiles
(The Bluetooth stack was completely re-developed in 4.1)
The version which is the best compromise of beeing fresh enough - but working like a charm is Android v4.0.4 (ICS)
The problem is.. there is no ICS based ROM out there which completely fullfill ALL my requirements.
So I thought it is time for me to create my own daily-use feature-complete and rock stable ROM for the Samsung Captivate Glide / SGH - I927..
IMO the best working and best battery saving ROM for the Glide is PACMAN ROM (used pac_i927-milestone.1.RC1.4.zip)!
The problem: the earliest version of it is based on Android 4.1 which is a No-Go for me because of Bluetooth HSP.
--> I recommend the mentioned version of PACman as your daily driver if you do NOT need BT HSP. I had it running several weeks without any problems but really great battery saving.
.. well that said I couldn't fork PACman ..
So I've downgraded to all available ICS based ROM again (which was VERY painful because of broken links to the apps because of different mount point names etc).
I have tried those all again (IcePOP, Cranium, Stock, DMans ICS, etc.) but no was "as good as" LiteROM (IMHO) - which I used several weeks before.
.. so +1 for forking LiteROM ...
The problem with LiteROM is that there are still issues and no further development is done on it.
Some of the major LiteROM issues for me (those are also the reasons why I first tried newer Android versions):
It looses the paired devices after a reboot ! (but that sounded to me like it can be fixed somehow)
The lags/waits when pressing the power button to switch the display on
Battery life is not the best
not the latest Kernel
many little things in the installer like it re-installs everything when only switching to another modem etc.
Nevertheless LiteROM is still the best base I can get (because it fits to my requirements best and is rock stable) and therefore I started in May 2014 the build of sediROM which is a fork of LiteROM v0.9.
UPDATE:
sediROM is officially available and have tons of fixes and enhancements inside. Check it out in the DEV thread:
--> http://forum.xda-developers.com/showthread.php?t=2789727
Best regards
xdajog :victory:
what kernel do you use? Stock or litekernel?
Replacing kernel is very easy.
No documentation for BT sound, I dont think anybody would fix it. I've tried to find dev to find alsa HAL ( that is for voip sound fix), and no luck, while fixing alsa much more easier then fix BT sound.
Somebody tried to port cm10, it has many issue, you can find that topic in dev forum.
The idea for sediROM is to have a very well tested setup of default settings (like which kernel, etc.) but the free choice to modify it later whenever you like it.
bubor said:
what kernel do you use? Stock or litekernel?
Click to expand...
Click to collapse
Well not 1 only ... there are 4 available atm (and more when I find them and find them good enough...) (while using LiteKernel v1.2.2 as default atm - but you have the free choice)
Stock Kernel
LiteKernel v4.0 OverClocked and without UnderVoltage
LiteKernel v1.2.2 GPU not OverClocked and with UnderVoltage
LiteKernel v1.2.2 GPU OverClocked and with UnderVoltage
I tried with the ardatdat 4.x Kernels,too but without success.
Replacing kernel is very easy.
Click to expand...
Click to collapse
Well yes and nowhere such comfortable as in sediROM You can choose one of the above within the aroma installer. The same for several Modems which coming with LiteROM already (nice for testing around).
No documentation for BT sound, I dont think anybody would fix it. I've tried to find dev to find alsa HAL ( that is for voip sound fix), and no luck, while fixing alsa much more easier then fix BT sound.
Somebody tried to port cm10, it has many issue, you can find that topic in dev forum.
Click to expand...
Click to collapse
BT sound? Do you have any issues here? For me BT sound itself is working great (using it daily in my car)?! But you talked about voip - is your problem skype related?
Regards
xdajog
xdajog said:
The idea for sediROM is to have a very well tested setup of default settings (like which kernel, etc.) but the free choice to modify it later whenever you like it.
Well not 1 only ... there are 4 available atm (and more when I find them and find them good enough...) (while using LiteKernel v1.2.2 as default atm - but you have the free choice)
Stock Kernel
LiteKernel v4.0 OverClocked and without UnderVoltage
LiteKernel v1.2.2 GPU not OverClocked and with UnderVoltage
LiteKernel v1.2.2 GPU OverClocked and with UnderVoltage
I tried with the ardatdat 4.x Kernels,too but without success.
Well yes and nowhere such comfortable as in sediROM You can choose one of the above within the aroma installer. The same for several Modems which coming with LiteROM already (nice for testing around).
BT sound? Do you have any issues here? For me BT sound itself is working great (using it daily in my car)?! But you talked about voip - is your problem skype related?
Regards
xdajog
Click to expand...
Click to collapse
would you point to sediROM? I couldnt find anything with google.
I dont know what is litekernel v4, I tought the last one was 2.x or less.
Litkernel has many power save improve, but it has many bugs too,
You have said already headset doesnt work, or does it work? I'm confused.
bubor said:
would you point to sediROM? I couldnt find anything with google.
Click to expand...
Click to collapse
It will be available soon - The first barrier was the post restriction which is ok now And now I need to find a place for uploading the 430 MB and then I will post it in the dev area..
I dont know what is litekernel v4, I tought the last one was 2.x or less.
Litkernel has many power save improve, but it has many bugs too,
Click to expand...
Click to collapse
--> http://goo.im/devs/thegreatergood/LiteKernel/ICS
You have said already headset doesnt work, or does it work? I'm confused.
Click to expand...
Click to collapse
Oh no I said Bluetooth is generally working fine in Android v4.0 and therefore in sediROM / LiteROM but not in other ROMs which are based on Android 4.1 or higher
--> The only thing which are not perfect in v4.0 (or especially in LiteROM) is that Bluetooth Pairing are lost after rebooting.
--> ... and that is fixed in sediROM
Smashing! :laugh: I have been roaming around for something like this! Bloody awesome! Let me know when you have the download link ready! I will be glad to test it, and if it is stable as stock ICS I will definitely keep it as my DD! Thanks in advance for this! If you say it is indeed a fork for LiteROM with no bugs it will be the s#$)!!! And of course a keeper. Same as you, I´ve tried almost every ROM available for our cappy, but never totally satisfied with none. :fingers-crossed: Hoping this ROM is what I have been looking for. What exactly did you fix, aside from the pairing issues? Any luck with the automatic toggles, Force close issues, deep sleep power button.... :fingers-crossed::fingers-crossed::fingers-crossed:
Man gimme more details! Freakin excited here :silly: jue jue jue jue
lasuazo said:
Smashing! :laugh: I have been roaming around for something like this! Bloody awesome! Let me know when you have the download link ready! I will be glad to test it, and if it is stable as stock ICS I will definitely keep it as my DD! Thanks in advance for this! If you say it is indeed a fork for LiteROM with no bugs it will be the s#$)!!! And of course a keeper. Same as you, I´ve tried almost every ROM available for our cappy, but never totally satisfied with none. :fingers-crossed: Hoping this ROM is what I have been looking for. What exactly did you fix, aside from the pairing issues? Any luck with the automatic toggles, Force close issues, deep sleep power button.... :fingers-crossed::fingers-crossed::fingers-crossed:
Man gimme more details! Freakin excited here :silly: jue jue jue jue
Click to expand...
Click to collapse
whooa keep calm my friend
as said I try to solve all the problems I saw in my case and that's what I fixed. If that fixes all yours.. - I don't know
The thing which sounds interesting to me is that you talk about automatic toggles and force closes.
I never seen automatic toggles and force closes but it may be because I use another Kernel. Well we will see when you have tried it .
I cannot promise it is bug free (in this early state of this ROM there is at least 1 known bug - to be honest) but I may can help to fix things..
Rest and details coming soon... :angel:
I'd definitely be interested in testing your ROM. Your idea is more or less what I wanted for my i927. Hope to be able to try it soon.
xdajog quick question mate, which Kernel have you been using so far? Stock Kernel, Litekernel (version)?
I remember lite kernel causes battery drain in ics
Sent from my SGH-I927 using XDA Premium 4 mobile app
Androide3 said:
I remember lite kernel causes battery drain in ics
Sent from my SGH-I927 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Exactly, that is why I would like to know which kernel would be recommended Never tried liteRoM with stock kernel
Will be fun to test out. I mostly stick to CM11 but I like to try out others often.
lasuazo said:
xdajog quick question mate, which Kernel have you been using so far? Stock Kernel, Litekernel (version)?
Click to expand...
Click to collapse
Androide3 said:
I remember lite kernel causes battery drain in ics
Click to expand...
Click to collapse
Well that point is not totally fixed yet. I'm currently using Litekernel 1.2.2 in the not-overclocked version but also played around with the others - even Stock of course. That said I cannot say that I've found a perfect kernel (grakernel may the one but it is for JB and higher only ) and still testing others.
So the short answer is that there are not such differences between them when it comes to battery drain (see my post in the dev because that's one of the open points yet)
... and only to ensure that we have all the same understanding: sediROM is my experiment to go to / to get / to become the perfect stable but actual ROM for the Glide. It is "on it's way" you now
For becoming that I need feedback of course and I believe there will be many things I may not seen/use like you do so don't expect something "perfect"
xdajog said:
It will be available soon - The first barrier was the post restriction which is ok now And now I need to find a place for uploading the 430 MB and then I will post it in the dev area..
--> http://goo.im/devs/thegreatergood/LiteKernel/ICS
Click to expand...
Click to collapse
You are really miss the point.
4.0 means android version not kernel version.
The litekernel package includes a boot image, that boot.img include kernel,ramdisk.
Ramdisk is the root on your android. Litekernel has some ramdisk modification too ( https://github.com/thegreatergood/LiteKernel---Glide/tree/master/Build4.2/ramdisk/sbin/ext https://github.com/thegreatergood/L...ster/Build4.2/ramdisk/sbin/LiteKernel_Manager )
Grakernel should work with any rom, it doesnt change ramdisk, just replace kernel and install modules to /system/lib/modules. I think modules in you rom is in /lib/modules on ramdisk, so you need to change my install script to modify ramdisk.
bubor said:
4.0 means android version not kernel version.
Click to expand...
Click to collapse
oh I'm quite new in that and a little disappointed now :crying: Well kernel v1.x is not for Android 1.x so .. in a perfect world the version naming would be everytime the same.. so everyone would know what it means... So I it may be the same as one of the 1.x LiteKernels available.
Grakernel should work with any rom, it doesnt change ramdisk, just replace kernel and install modules to /system/lib/modules. I think modules in you rom is in /lib/modules on ramdisk, so you need to change my install script to modify ramdisk.
Click to expand...
Click to collapse
Hm so you say replacing the kernel, adding the modules and it should work?
I've tried that already but without success (booting but display keeps black with some green pixels ..)
As I can see in your link the Litekernel mods are note relevant for functioning or am I wrong? They seem to do some power saving stuff nothing else?
xdajog said:
oh I'm quite new in that and a little disappointed now :crying: Well kernel v1.x is not for Android 1.x so .. in a perfect world the version naming would be everytime the same.. so everyone would know what it means... So I it may be the same as one of the 1.x LiteKernels available.
Hm so you say replacing the kernel, adding the modules and it should work?
I've tried that already but without success (booting but display keeps black with some green pixels ..)
As I can see in your link the Litekernel mods are note relevant for functioning or am I wrong? They seem to do some power saving stuff nothing else?
Click to expand...
Click to collapse
Litekernel has 2 version string, one from the build version and one from android version. Litekernel has some power save codes, it cases that deep sleep issue IMHO.
Did you download kernel from i9103 forum or mine from http://dualhoki.vim.hu/bubor/dev/grakernel/ ? Sound like you have i9103 version.
bubor said:
Did you download kernel from i9103 forum or mine from http://dualhoki.vim.hu/bubor/dev/grakernel/ ? Sound like you have i9103 version.
Click to expand...
Click to collapse
it was yours (1.4.3) - but I will re-test it again to be sure..
I want to give a try
i am very very very interrested in your ROM!
The BT-Headset function is very important for me, because for my car hifi handsfree bluetooth mode.
Battery Life
Since we are on the topic of battery life... does KitKat have the best battery life, or should I be using something else?
Hi,
Please can someone explain why Exynos has a bad rep for custom ROMs? Samsung release the kernel and I assume it contains either open source drivers or binary blobs. Either way we have a functional boot.img with a working ~3.4 kernel, that kernel should presumably boot any sensible 4.4+ system.img right?
I'm asking because I'm considering building a clean ASOP ROM for the Tab S just to get rid of the crazy amount of bloat. This is obviously trivial with the Nexus device line, but I'm just trying to understand why it's complex in this case? Can we not just use the stock kernel/drivers with any arbitrary userspace e.g ASOP git or CM? Does the SoC really matter to us for non-kernel projects? Or are all the problems purely in the custom kernel world?
Also, is there anything actually important in Samsung's userspace that i'm missing? It's really just the UI and little extra features for the camera and things right? I can't help but feel the speed gain from an ASOP built would be incredible, all the hardware should work just fine given a working stock kernel?
Thanks!
@eousphoros is working on porting CM right now. Why don't you PM him and see if you can put your heads together on it?
jasonfxp said:
Hi,
Please can someone explain why Exynos has a bad rep for custom ROMs? Samsung release the kernel and I assume it contains either open source drivers or binary blobs. Either way we have a functional boot.img with a working ~3.4 kernel, that kernel should presumably boot any sensible 4.4+ system.img right?
I'm asking because I'm considering building a clean ASOP ROM for the Tab S just to get rid of the crazy amount of bloat. This is obviously trivial with the Nexus device line, but I'm just trying to understand why it's complex in this case? Can we not just use the stock kernel/drivers with any arbitrary userspace e.g ASOP git or CM? Does the SoC really matter to us for non-kernel projects? Or are all the problems purely in the custom kernel world?
Also, is there anything actually important in Samsung's userspace that i'm missing? It's really just the UI and little extra features for the camera and things right? I can't help but feel the speed gain from an ASOP built would be incredible, all the hardware should work just fine given a working stock kernel?
Thanks!
Click to expand...
Click to collapse
The big problem I ran into is with gralloc/hwcomposer. The hwcomposer that ships with the device is 1.3 whereas the opensource is currently only 1.1. While the initial thought of just copying gralloc.exynos5.so hwcomposer.exynos5.so as propertietary blobs seems like it a good one, they are unfortunately linked to a ton of libraries in /system/lib that makes bringing them over troublesome at best. Though that being said that is the hack I used to get my one and only bootable rom up and running.
Going further the issue with the exynoshwc 1.1 that I have been fighting with is after opening up /dev/graphics/fb0 it trys to send it an ioctl that I assume is the S3C_WIN_CONFIG pointer and gets an ENOTTY back from the device. If you are interested in helping out please checkout the cyanogenmod porting thread in general where I have linked my local_manifests.xml with my git repo's and a blog of my progress.
Cheers.
EDIT: Has anyone ever requested source from samsung? What seems to be the most succesfull method?