OOk guys so I found this thread which shows MS2 got a custom kernel. The proceduce is bit difficult but can be modified for working for Defy too.
Hope has struck back again.
http://forum.xda-developers.com/showthread.php?t=1908687
Update: 2ndboot module sources are here:
https://github.com/czechop/2ndboot
Quarx puts his kernel here:
quarx2k.ru
Sdcard symlink Fix:
http://forum.xda-developers.com/showpost.php?p=32428611&postcount=392
Thanks to walter.
-------------------------------------------------------------------------------------------------------------------------------
BIGNOTE: Green lens users who flashed redlens builds please dont try using flash, you will end up burning it like me and many others.
STEPS TO FOLLOW WHEN YOU HAVE BOOTLOOPS OR BLACK SCREEN WITH RED LED ON:
-1st of all set default boot to 2nd-boot
-Go to recovery and flash the 24.9 build
-Then flash the kernel 6.10
-After that flash the latest build
-Wait and you will have your phone working proper.
For Bl7 users:
kozaks said:
If your current kernel is 2.6.32.9-ge281b6e [email protected]#1 then the custom kernel won't boot. To get it boot, you need to flash the kernel shared by our friend. Post flashing your kernel should be 2.6.32.9-ge281b6e
[email protected]#1. Once this is confirmed go ahead and flash tbw custom kernel as defined in the first page. Should be good to go.
Link to 51#1 kernel.
http://forum.xda-developers.com/showthread.php?p=32538963
Click to expand...
Click to collapse
-------------------------------------------------------------------------------------------------------------------------------
A suggestion made by a member:
rodrigojfuentes said:
Hey, I just read in this post that flashing gapps before the kernel may prevent the kernel from successfully booting. I tried it and it worked fine. I think you should advice that in the OP
Click to expand...
Click to collapse
-------------------------------------------------------------------------------------------------------------------------------
FOR SIMUNLOCK:
Redhotero said:
Dont know if it's OT or what, but helped me a lot.
This is for the people who wants "sim unlock" in quarx 10/10
1- Download this rar http://forum.motofan.ru/index.php?act=Attach&type=post&id=243798
2- Paste bp_ptc in /system/bin
3- Paste init.mapphone_umts.rc in /system/bootmenu/2nd-boot
and then:
Credits to crakeron, labsin, Dabb and all the people who helped. Im just the messenger,
PD: sorry for my english and sorry if it was posted before
Click to expand...
Click to collapse
-------------------------------------------------------------------------------------------------------------------------------
Feature request for next kernel:
-OTG cable support
- FM transmitter capability Link(requested by amirali_b)
-Sim unlock support(requested by Redhotero)
-Wifi-direct(requested by mdsaif92)
(pm me to add other features)
Waiting for someone to compile a kernel so we can test
Sent from my MB525 using xda app-developrs app
hsrars-d said:
Waiting for someone to compile a kernel so we can test
Sent from my MB525 using xda app-developrs app
Click to expand...
Click to collapse
u can try currently available kernels just to try!
To see if the scripts and modules work xD
M sure they wont work right away
+Really great news
I tried boot my kernel with it (not booted, but log is good).
Waiting for source code and changes in kernel for 2ndboot
http://pastebin.com/jKjQ2ykn
In future i think we can make one kernel for defy and defy+
so just to clear things up for noobs like me: does this mean we could have a jellybean kernel, or is this still gb? and functions like wifi direct which need to be built in the kernel are possible now?
sent from my cm7 defy...
zakoo2 said:
so just to clear things up for noobs like me: does this mean we could have a jellybean kernel, or is this still gb? and functions like wifi direct which need to be built in the kernel are possible now?
sent from my cm7 defy...
Click to expand...
Click to collapse
It means we could use custom kernels.
I think that a developer could even port 3.0.x kernel on defy, if everything 'll go fine.
We may get swap support!(many more things)
Swap is really imp for us since 512MB ram is not enough for jb
Hope Quarx gets it working
Also does kernel version really matter?
I mean if an older kernel is working perfectly and has all ROM features working,why not use that only(2.6.35)
Also I dont think Defy's hardware supports WifiDirect
Sent from my MB526 using xda premium
It seems our sweetoldlittle Defy just won't get outdated soon! Great news, great devs
Sent from my MB525 using xda app-developers app
It works for defy, but unstable for now
http://forum.xda-developers.com/showpost.php?p=32120862&postcount=21
take your time quarx.we are patient it's an amazing news
Custom kernel from sources works too
Linux (none) 2.6.32.9 #1 PREEMPT Fri Sep 28 14:11:14 MSK 2012 armv7l GNU/Linux
Quarx said:
Custom kernel from sources works too
Linux (none) 2.6.32.9 #1 PREEMPT Fri Sep 28 14:11:14 MSK 2012 armv7l GNU/Linux
Click to expand...
Click to collapse
so finally , can we think of DSSCOMP , ION and hwcomposer ?
i know it too early to ask this question
but m very eager to know the answer from quarx
So it means we will have in near future new kernels and possibilty to brick Defy completly ? Or still Defy will be unbrickable and with new kernel
wifibdirect is a sofrware thing, not hardware. the defy would be perfectly capable, but we couldnt load custom kernels (until now).
sent from my cm7 defy...
sebx_g1 said:
So it means we will have in near future new kernels and possibilty to brick Defy completly ? Or still Defy will be unbrickable and with new kernel
Click to expand...
Click to collapse
As far as I understand from this is, the bootloader is still the same, so you still always be able to resurrect your defy with the stock sbfs :cyclops:
Quarx, I can't believe you are just one person... I mean, the progress you've done on the Defy in such a short time is really amazing!!! If the custom kernel gets developed half fast the speed of your mods, our little phone will be a blast pretty soon!!!
Can't Boot
Quarx said:
Custom kernel from sources works too
Linux (none) 2.6.32.9 #1 PREEMPT Fri Sep 28 14:11:14 MSK 2012 armv7l GNU/Linux
Click to expand...
Click to collapse
Can't boot, when i try 2nd boot, defy stuck on black screen 10 to 20 seconds, and reboot :crying:
I don't know why....
I suppose you followed the milestone 2 method directly.
Quarx has not released anything (afaik), and its not intended to users at this staqe.
dumb
hsrars-d said:
I suppose you followed the milestone 2 method directly.
Quarx has not released anything (afaik), and its not intended to users at this staqe.
Click to expand...
Click to collapse
I think quarx boot the mm2 method on defy directly... im dumb
Boss442 said:
I think quarx boot the mm2 method on defy directly... im dumb
Click to expand...
Click to collapse
Yes he did that first, then he modded it and got it to boot. :victory:
Related
Following the popular RM KERNEL series in .32 I present you the new .35 RM KERNEL for the cm9 and other ics roms.
THIS KERNEL IS NOW OBSOLETE, DON'T USE IT
Mine newest and stable kernel releases are now integrated into my version of cyanogenmod 9 please use only a kernel provided with that ROM, not this one.
Im leaving it for historical reason or for some geeks
ABOUT RM KERNEL
Click to expand...
Click to collapse
RM IS modification KERNEL. IT HAVE MANY modifications implement. TO MAKE YOUR PHONE FASTER,BETTER AND OTHER ALL.
IMPORTANT NOTES
Click to expand...
Click to collapse
THIS IS TESTING RELEASE OF RM 35 FOR PECAN. ALL BUILDS ARE experimental AND NOT MEANT TO BE USED AS DAILY DRIVER.
RM 35 PECAN IS BASED ON CM KERNEL SOURCE.
Features
Click to expand...
Click to collapse
SEE CHANGELOG EVERY BUILD HAVE SOMETHING NEW SO IT'S BETTER YOU SEE CHANGELOG.
KNOW BUGS
Click to expand...
Click to collapse
KERNEL VERSION NOT SHOW
DOWNLOADS
Click to expand...
Click to collapse
DOWNLOAD : V1100
HOW TO INSTALL
Click to expand...
Click to collapse
DOWNLOAD NEWER VERSION FROM TOPIC
PLACE ON YOUR SD CARD
REBOOT YOUR PHONE INTO RECOVERY MODE
WIPE CACHE,DALVIK CACHE AND BATTERY
FLASH KERNEL
REBOOT YOUR PHONE AND ENJOY
THANKS TO
Click to expand...
Click to collapse
CYANOGENMOD TEAM - FOR BASE KERNEL SOURCE CODE
PAX0R - 1ST SETUP OF PORTING CM KENREL ON PECAN
SOURCE
Click to expand...
Click to collapse
KERNEL SOURCE CODE : https://github.com/kerneldevs/RM-KERNEL-PECAN
SUPPORT
Click to expand...
Click to collapse
IF YOU LIKE MY WORK YOU CAN USE DONATE BUTTON TO SUPPORT MY WORK OR YOU CAN PRESS THANKS BUTTON TO SHOW YOUR SUPPORT .
MORE
Click to expand...
Click to collapse
WANT FAST NEWS ABOUT MY WORK? JOIN MY FACEBOOK GROUP : https://www.facebook.com/groups/OADPROM/
CHANGELOG
changelog
08-06-2012 v1000
1st release of rm 35 kernel for lg optimus me
based cm kernel source
ported kgsl from 3.0 kernel
added genlock
12-06-2012 V1100
ADDED OVERCLOCK
ADDED SIO AND VR
Backport calibrate from 3.0 kernel
update ksm to 3.0
backported binder from 3.0 kernel
well..seems its not stable or somethin??
Dont boot. No tux, nothing. Blackscreen only.
mardex80 said:
dont boot. No tux, nothing. Blackscreen only.
Click to expand...
Click to collapse
i'm tested on nightly 9 wait and in .35 there is no tux logo
Ops! Only seen black screen haha, i go to try again.
This is .35 kernel
I get stuck in LG logo. Nothing happens.
Wait... it worked.
Stuck on boot
Chibbo said:
Stuck on boot
Click to expand...
Click to collapse
Try to wait a little bit. Mine booted after 3 min apparently stuck in LG logo.
chibbo said:
stuck on boot
Click to expand...
Click to collapse
wait and there is not tux logo
As I said stuck on boot animation after 2 mins and buttons start flash
No overclock support?
It's working well so far, but i'll reflash the older one with nightly 9 because I can't even run a GBA game properly with 600mhz. I'll use it when overclock support is added.
drunkenbard16 said:
No overclock support?
It's working well so far, but i'll reflash the older one with nightly 9 because I can't even run a GBA game properly with 600mhz. I'll use it when overclock support is added.
Click to expand...
Click to collapse
oc will added in upcoming update
cips gokhle said:
oc will added in upcoming update
Click to expand...
Click to collapse
Hello, very good your work.
I'm testing your KERNEL (I boot without problems)
I now work the swap, which in the nightly 9 does not work
the problem is that not let me do overclocking. you're going to fix this?
from already thank you very much for taking care of our beloved LG P350
excuse my English I'm from Argentina
kpopablo said:
Hello, very good your work.
I'm testing your KERNEL (I boot without problems)
I now work the swap, which in the nightly 9 does not work
the problem is that not let me do overclocking. you're going to fix this?
from already thank you very much for taking care of our beloved LG P350
excuse my English I'm from Argentina
Click to expand...
Click to collapse
overclock already fixed now i'm compiling nightly 10 and it come with 35 kernel then i will make a zip to flash this kernel on other roms
Awesome work bro.
Sent from my X8 using xda premium
source code is up
https://github.com/kerneldevs/gtrk-FX-kernel
enjoy hacking
Changes this thread to rm 35 kernel
enjoy guys
UPDATE
12-06-2012 V1100
ADDED OVERCLOCK
ADDED SIO AND VR
Backport calibrate from 3.0 kernel
update ksm to 3.0
backported binder from 3.0 kernel
Advanced Stock ICS Kernel for Xperia SHere is a kernel based on the Stock ICS kernel with some features which come from DoomLord's GB kernel.
Features
autorooting
CWM recovery (with reboot recovery support)
init.d support (thanks DoomLord)
TUN/TAP driver
Download links
Build 17 (Fastboot)
Build 17 (CWM)
Build 16 (Fastboot)
Build 16 (CWM)
Prerequisites
An unlocked bootloader: Tuto here.
A stock ICS ROM (6.1.A.0.452 to 6.1.A.2.55). Don't expect this kernel to work with CM9/10.
How to flash
For elf files :
Read DoomLord's guide
You just have to replace kernel.elf by the name of the downloaded kernel in the flash command (eg : ics4.elf)
For zip files:
Flash the zip file from the recovery
Changelogs
Build 17 (08/12/12) :
Merge 6.1.A.2.55 kernel sources
Autodetect rom version in default.prop based on build.prop
Updated recovery, adbd and busybox (JB version)
Build 16 (01/11/12) :
Random reboot issue probably fixed (patch from CM10 kernel, thanks Kali)
Rom version increased to 6.1.A.2.50
Updated recovery, adbd and busybox (JB version)
SD card mounted by default in recovery
Vibration at boot removed, only led and backlight now
Build 15 (05/09/12) : Increase ROM version in default.prop from 6.1.A.0.452 to 6.1.A.2.45
Build 14 :
New MMC driver (from codeaurora) : it fixes issue while formatting partitions in CWM
Wifi module built from source (in the ramdisk)
Updated recovery
Disable again hardware clock
Build 13 :
Backup / Restore fixed with dedupe
Backlight enabled in CWM
Better "reboot recovery" handling in adbd / busybox and recovery
Build 12 :
Updated recovery
Hardware clock correctly saved (from CM9 kernel)
Build 11 : Go back to GCC 4.4 (fix artifacts with camera preview)
Build 10 :
Kernel built with GCC 4.6
Several autoroot fixes (Superuser app pushed just once and correctly removed in /data)
Working reboot recovery command (with adb too)
Updated su (3.1.1) and Superuser (3.1.3)
A bunch of new command included in the new busybox (ifconfig, wget, vi, and many more !)
Build 9 :
Kernel built from sources
TUN/TAP driver included (for VPN)
Build 8 : Fix mass storage in CWM
Build 7 : Fix MTP
Build 6 : Key mapping in CWM fixed
Build 5 :
New recovery built from latest CM9 sources
Fixed generation of md5sum with nandroid
Increased font size in CWM
Boot partition backup and restore
New adbd built from CM9 sources (fixed an issue with hardcoded sh path in /system)
Build 4 :
Correct su binary
Don't wait 3 sec if /cache/recovery/boot exists
Build 3 :
Leds and vibrator at startup fixed
Sources
Ramdisk sources
Kernel sources
Credits
DoomLord : many thanks to him for its kernel and all his scripts.
championswimmer and sminki for their help
FreeXperia team for their work on CM
makes it perfectly start does not make any errors
greetings and thanks
yes it boots!
(maybe you can help with my Question here )
Hey, I also have tested several times to include recovery, but withut succes, didn't get any further then a booting kernel without recovery or vibration and LED on to enter recovery but no entering recovery and kernel that doesn't boot.
Please pm me if you want to work together, I saw your kernel is from ICX team? I know nick very well so I'd would be a pleasure to work with you too
sminki said:
yes it boots!
(maybe you can help with my Question here )
Click to expand...
Click to collapse
for this question and any other other question similar to this
head here
http://forum.xda-developers.com/showthread.php?t=1659584
it has menu driven process to extract and repack kernel.elf (ramdisk also can be extracted and packed )
Welcome Champ, good to see you mate.
I will leave the thread here as knowing you, you will have a kernel ready for us in a few hours.:fingers-crossed:
thanks for the test guys... so now i'm diving into including recovery....
good to know i could pull off kernel.elf editing in my first attempt lol
@colossus if not in hours, then definitely within 1 or 2 days
EDIT :
can someone send me the kernel.elf from FXP122 cm9 ??
will save me the time to download the whole ROM
This is sweet, good job!!
john9 said:
This is sweet, good job!!
Click to expand...
Click to collapse
Only a few files to edit now
We'll keep you updated
Sent from my LT26i using XDA
championswimmer said:
btw if anyone wishes to do this before me,
this diffstats should help you
https://github.com/championswimmer/xps-ramdisk/commit/a61969aefca00ce3a6e4e112e97403fb6f0c79e9
it shows how doomlord added recovery to gb kernel..
Click to expand...
Click to collapse
cool.. well that's a hell of a lot easier than the manual route I was taking. This was my goal, but for personal rather than pseudo "xda glory" as I'm working with DooM's stuff I didn't feel right posting it without his permission, but he's probably too busy to care
go for it championswimmer :victory:
Excuse my noob-ish question, but... what's the difference between a 'stock' kernel with recovery and a completely custom kernel like DoomLord's? Is it to do with core frequencies/governors?
fNOOB said:
Excuse my noob-ish question, but... what's the difference between a 'stock' kernel with recovery and a completely custom kernel like DoomLord's? Is it to do with core frequencies/governors?
Click to expand...
Click to collapse
Frequencies and governors are one possible customicing for kernels, for the most users the most important thing. also Kernel modifing can allows you init.d support, undervoltscripts and also allows (or denies) MSC support... and, for shure, clean out some tings, make things more efficiently and and and... a dev is nearly totaly free to create a very customiced kernel with or without special Driver support or so
noob.fl said:
Frequencies and governors are one possible customicing for kernels, for the most users the most important thing. also Kernel modifing can allows you init.d support, undervoltscripts and also allows (or denies) MSC support... and, for shure, clean out some tings, make things more efficiently and and and... a dev is nearly totaly free to create a very customiced kernel with or without special Driver support or so
Click to expand...
Click to collapse
Cheers mate
sminki said:
cool.. well that's a hell of a lot easier than the manual route I was taking. This was my goal, but for personal rather than pseudo "xda glory" as I'm working with DooM's stuff I didn't feel right posting it without his permission, but he's probably too busy to care
go for it championswimmer :victory:
Click to expand...
Click to collapse
using someone's work just because 'he's too busy to care' is not the aim which we at xda strive for ...
i've already talked with Doomlord regarding using his recovery... and as long as I clearly mention it's his work and provide links back to his thread, he has no issues with anyone else using it...
(and i'll surely do that ^^ when i release a kernel containing his recovery, if i ever do that)
championswimmer said:
using someone's work just because 'he's too busy to care' is not the aim which we at xda strive for ...
i've already talked with Doomlord regarding using his recovery... and as long as I clearly mention it's his work and provide links back to his thread, he has no issues with anyone else using it...
(and i'll surely do that ^^ when i release a kernel containing his recovery, if i ever do that)
Click to expand...
Click to collapse
cool, i was only making a bad joke, we all know DooM cares
sminki said:
cool, i was only making a bad joke, we all know DooM cares
Click to expand...
Click to collapse
lol.. ok
and i'll bring you some unicorns soon
championswimmer said:
lol.. ok
and i'll bring you some unicorns soon
Click to expand...
Click to collapse
I can't wait! :victory:
so this kernel has the ro.secure property in default.prop set to 0??
Tnaks mate for your job!
tested right now the test version and the sony logo fades and reboots
can you plug it into a pc and run a logcat from command prompt and give me the output of any comes??
if cm11 out i will buy one
Sent from my Moto G using Tapatalk
I'm currently working on unofficial build CM10.2.
Kernel is done
device tree is done
vendor setup is done
Android sources currently downloading
testing not yet.
Riyal said:
I'm currently working on unofficial build CM10.2.
Kernel is done
device tree is done
vendor setup is done
Android sources currently downloading
testing not yet.
Click to expand...
Click to collapse
Not CM11, but still very exciting =)
TheQwertiest said:
Not CM11, but still very exciting =)
Click to expand...
Click to collapse
I will try cm11 once i get cm10 running. Thing is we don't have official android 4.4 roms yet I don't have any sources for 4.4 binaries and kernel
Riyal said:
I will try cm11 once i get cm10 running. Thing is we don't have official android 4.4 roms yet I don't have any sources for 4.4 binaries and kernel
Click to expand...
Click to collapse
We wait for CM11!
Xperia V, T doesn't have official 4.4 ROM too, but they have CM11.
Also, I think it's possibile developing CM11 or other CM11 based (KitKat) AOSP ROM.
Unfortunatelly I can't develop it...
I just will use it :fingers-crossed:
u guyz are lucky...u have munjeni wid u now. just be patient.. his hardwork brought cm11 novathor devices... which were abondoned on ics.
two reason i see z1compact as my next phone is that i dont like large phones and master munjeni has z1c also...
We can use CM11 from Z1 since Z1 CM11 on Z1C is working but there is no display available since CM kernel on MSM8974 need some changes related to the Z1C display Bad news is we can not use stock kernel since gralloc, copybit ..etc is not working than. I started working on CM kernel but hmmm CM kernel and stock kernel is a lot diferent so hard work is needed If we get CM kernel working we will get CM11 working with no big modifications
Edit:
Compared now stock Sony kernel source code from Z1 and stock ekrnel source code from Z1C, there is absolutly no diferencie, only one line is diferent in defconfig, line is CONFIG_MACH_SONY_*****_ROW, source is totaly identic. I'm confused now since have no idea why CM kernel working on Z1 but no on Z1C. Maybe I have downloaded wrong kernel for Z1 ??? I have downloaded https://github.com/CyanogenMod/android_kernel_sony_msm8974 branch cm-11.0 . Maybe these kernel not working on Z1 too ???
Can't wait to try CM
kernel config from boot.img
munjeni said:
Compared now stock Sony kernel source code from Z1 and stock ekrnel source code from Z1C, there is absolutly no diferencie, only one line is diferent in defconfig, line is CONFIG_MACH_SONY_*****_ROW, source is totaly identic. I'm confused now since have no idea why CM kernel working on Z1 but no on Z1C. Maybe I have downloaded wrong kernel for Z1 ??? I have downloaded{removed} branch cm-11.0 . Maybe these kernel not working on Z1 too ???
Click to expand...
Click to collapse
Hello,
I am not sure if this is helpfull, but I'll give it a try: You are right - there is absolut no difference between the two kernel configurations, beside that one line. Since there are already nightlies available for the Z1(honami) I thought there might some helpfull informations inside that nightly. Of course there was a boot.img inside the nightly and I found that script to extract the kernel.config from that boot.img. Using the extract-ikconfig from my xperia z(yuga) kernel located in ./kernel/sony/apq8064/scripts/extract-ikconfig.
If the extracted config is reliable, there are indeed many differences.
I attached the extracted config. Maybe you remove the Lines starting with # and the blank lines for a better compare.
Let me know if I can help in some way.
Kind Regards
I don't know whats going on or why CM kernel is working on Z1 and not on Z1C but I think these fails on Z1C is related to the baseband and bootloader? Just asking, DO NOT FLASH THEM!!!
And another thing is maybe dtbs is a thing related to the fail since I can see some things in dmesg related to the pingpong command in mdss_mdp_intf_cmd.
Error log -> http://pastebin.com/9zgcWd4a
Thanks to the developers who are trying to make CM11 working on this phone. I will buy this phone if CM11 is available
@munjeni
Guys I have compiled a CM10.2 kernel here. Who's willing to try it against Z1's CM10.2 ROM?
http://forum.xda-developers.com/showthread.php?t=2461282
I'll provide the source if it works.
Riyal said:
@munjeni
Guys I have compiled a CM10.2 kernel here. Who's willing to try it against Z1's CM10.2 ROM?
http://forum.xda-developers.com/showthread.php?t=2461282
I'll provide the source if it works.
Click to expand...
Click to collapse
You can try! You no need to install, simple boot them without installing! On next reboot your phone will boot normaly! So boot these image temporary by command:
fastboot boot boot.img
Nope, doesn't seem to boot :/
munjeni said:
You can try! You no need to install, simple boot them without installing! On next reboot your phone will boot normaly! So boot these image temporary by command:
fastboot boot boot.img
Click to expand...
Click to collapse
Yeah but I just relocked my bootloader yesterday. I won't be unlocking it till I get more time in development.
crytic said:
Nope, doesn't seem to boot :/
Click to expand...
Click to collapse
Weird then... The patch I applied to port z1 kernel to z1 compact made a fully working stock kernel. But when I applied it to CM kernel it doesn't even boot. Can you by chance get a copy of /proc/last_kmesg and upload it somewhere or here?
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
~ # ←[6nuname -r
uname -r
3.4.0cyanogenmod-g77098c0-dirty
~ # ←[6n
Click to expand...
Click to collapse
munjeni said:
Click to expand...
Click to collapse
Woot! There it goes Now I don't have to port CM haha!
Sweet, with or without display?
crytic said:
Sweet, with or without display?
Click to expand...
Click to collapse
With! Investigating between commits on git since using old working commits, need to find which commit broke display init. There is ~100 commits between but I will try every 20.th When commits get located than will try to fix upstream kernel . There is a lot of work but thats a only way by now.
munjeni said:
Click to expand...
Click to collapse
munjeni said:
With! Investigating between commits on git since using old working commits, need to find which commit broke display init. There is ~100 commits between but I will try every 20.th When commits get located than will try to fix upstream kernel . There is a lot of work but thats a only way by now.
Click to expand...
Click to collapse
git bisect to the rescue Well, if you need any help, just drop me a line!
.
.
.
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?
Due to several reasons I have stopped the deployment of the "monthly Update.Zip packages" !
Thanks for your understanding.
This thread will be used for the unified tegra-3.18 kernel only.
Twelve:
tegra-3.18_unified_dragon_kernel_12_v211213.zip
Eleven:
tegra-3.18_unified_dragon_kernel_11_v201218.zip
Ten:
tegra-3.18_unified_dragon_kernel_10_v201010.zip
Pie:
tegra-3.18_unified_dragon_kernel_p_v200310.zip
Oreo:
tegra-3.18_unified_dragon_kernel_o_v200310.zip
Changes/Features:
- Upstream to kernel version 3.18.140
- Various patches and security updates
- Added Wireguard support
- Added/Enabled various file systems (exFat, NTFS, Network Filesystems .. etc.)
- Changed kernel config to enable/improve support for varioius services (tethering .. etc.)
- Added "fix cpu frequency limitation"
- etc.
Installation:
1. Boot into TWRP
2. Install the Kernel Update.Zip file
3. Reboot into system .. no need for SuperSU / Magisk !
The package contains an Image.fit kernel binary only - and no ramdisk part !
This way the kernel should run on all available Android Oreo/Pie/Ten ROMs for the dragon device.
And there is no need for a new SuperSu/Magisk installation afterwards, unlike to "full boot.img" installation.
Sources:
https://github.com/followmsi/android_kernel_tegra
https://github.com/followmsi/lazyflasher/tree/followmsi-dragon
https://github.com/followmsi/AnyKernel2/tree/dragon
Download:
https://drive.google.com/drive/folders/18cqluw7lp1S720QdV0p-OtHfY9MNpSwn
Big thanks to @NYCHitman1 (Dirty Unicorn), @cheep5k8 (xceed), @Vartom and updateing from Team Mokee for the nice kernel sources !
Big thanks to @osm0sis (Anykernel2) and @jcadduono (lazyflasher) for the nice tools !
Enjoy
flashed your system image
devices does not boot
flashed back to stock
boots
edit: further details
every boot just dumps me into recovery.
dmitrygr said:
flashed your system image
devices does not boot
flashed back to stock
boots
edit: further details
every boot just dumps me into recovery.
Click to expand...
Click to collapse
Thanks for feedback .. no good news.
Sorry, I can not reproduce your problem.
Tested the system_vendor udapte.zip several times on my Pixel C.
No problem so far ...
You flashed the complete .zip via TWRP ?
What was your previous firmware level ?
Did you upgrade bootloader as well ?
What kernel do you have in use ?
EDIT:
Which Version of TWRP ?
Pls use xceed version for now.
The NYChitman1 version seems to have problems.
http://forum.xda-developers.com/pix...ock-bootloader-install-custom-t3307183/page14
followmsi said:
The NYChitman1 version seems to have problems.
http://forum.xda-developers.com/pix...ock-bootloader-install-custom-t3307183/page14
Click to expand...
Click to collapse
Only the latest one I released because I didn't put the proper flag in place -- the previous one works perfectly fine as indicated by myself and others.
Also, I find it interesting that you've created a development thread while you aren't actually developing anything.
Thanks for the update.
Still like to test your version.
Ok, the version from here is recommended .. http://forum.xda-developers.com/showpost.php?p=66557703&postcount=101
In the one from yesterday you fixed vendor image flashing via TWRP.. sounds nice.
When do you re-release this version ?
You may open a new thread for your TWRP releases ..
Thanks a lot for all your work!
New kernel released ... pls test
Update.ZIP_Nexus_Ryu_chromeos-3.18-kernel_v160519_followmsi.zip
There are lot of changes in compare to latest stock kernel .. https://chromium.googlesource.com/chromiumos/third_party/kernel/+log/chromeos-3.18/
Cheers
followmsi said:
New kernel released ... pls test
Update.ZIP_Nexus_Ryu_chromeos-3.18-kernel_v160519_followmsi.zip
There are lot of changes in compare to latest stock kernel .. https://chromium.googlesource.com/chromiumos/third_party/kernel/+log/chromeos-3.18/
Cheers
Click to expand...
Click to collapse
Many thanks for your work The kernel is for stock / AOSP roms? Running Dirty Unicorns and I think it´s not compatible :/
redukt said:
Many thanks for your work The kernel is for stock / AOSP roms? Running Dirty Unicorns and I think it´s not compatible :/
Click to expand...
Click to collapse
There are so many fixes since MXC89F kernel .. which was commited on Arpil 5th .. even it's the May release. Ok, was tagged on May, 4th.
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/MXC89F
Last changes .. 6 weeks ..
https://chromium.googlesource.com/c...+log/9c052efad6e651d33334b84c8f1feaf8945e8e7a
I am running the new kernel on latest M stock release .. MXC89F.
No problems so far .. really stable.
The kernel should run on all stock M releases for PixelC.
Used latest stock ramdisk to build the kernel .. maybe the dirty unicorn ramdisk is different.
But the actual kernel should work as well ..it's a dragon kernel.
Repack DU ramdisk with my kernel and it will most probably work as well .. maybe even with the same ramdisk, without repacking. Needs to be tested ..
Give it a try .. it will not hurt.
Cheers
Any chance of getting a port of multirom? Let me know if there's any interest, and what I can do to help.
nic. said:
Any chance of getting a port of multirom? Let me know if there's any interest, and what I can do to help.
Click to expand...
Click to collapse
Sounds good .. have it running on Nexus 7 flo .. really like it.
MultiROM for PixelC would be really nice .. the chromeos is part is maybe tricky.
But like SuperSU .. automatic chromeos image unpack and repack, if required at all.
It seems Tassadar is not around anymore .. not sure if he will come back.
Some new guys have taken over .. they just made a new update release for TWRP and MultiROM..
Works fine
Are you able to port it to Pixel C ?
Thanks
followmsi said:
Give it a try .. it will not hurt.
Cheers
Click to expand...
Click to collapse
Bootloop
Restored my Nandroid and device is up
DU is CM based and unfortunately incompatible :/
followmsi said:
Sounds good .. have it running on Nexus 7 flo .. really like it.
MultiROM for PixelC would be really nice .. the chromeos is part is maybe tricky.
But like SuperSU .. automatic chromeos image unpack and repack, if required at all.
It seems Tassadar is not around anymore .. not sure if he will come back.
Some new guys have taken over .. they just made a new update release for TWRP and MultiROM..
Works fine
Are you able to port it to Pixel C ?
Thanks
Click to expand...
Click to collapse
I am wanting to dig into the Linux4Tegra side of this, and was hoping that some of the work for multirom could or had been done. I don't know anything about the chromeos bootloader. Looking into it, Chrubuntu might be a viable path for this. I feel like this device is gimped with Android.
redukt said:
Bootloop
Restored my Nandroid and device is up
DU is CM based and unfortunately incompatible :/
Click to expand...
Click to collapse
Thanks for the test ..
Restore DU boot.img and you are back to normal ..yep
I will unpack the DU boot.img and have short look .. just to check it.
nic. said:
I am wanting to dig into the Linux4Tegra side of this, and was hoping that some of the work for multirom could or had been done. I don't know anything about the chromeos bootloader. Looking into it, Chrubuntu might be a viable path for this. I feel like this device is gimped with Android.
Click to expand...
Click to collapse
Sounds like a lot of work .. but if you have the right people involved ..
Maybe xceed or nychitman will know better how to "manage" the bootloader ..
As I know, until today, "nobody" knows how to remove the 30 second warning time beep sound ****.
Right now I am happy to "manage" the layer above .. boot.img and recovery.img
redukt said:
DU is CM based and unfortunately incompatible :/
Click to expand...
Click to collapse
What are you talking about? We're not CM based.
followmsi said:
There are so many fixes since MXC89F kernel .. which was commited on Arpil 5th .. even it's the May release. Ok, was tagged on May, 4th.
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/MXC89F
Last changes .. 6 weeks ..
https://chromium.googlesource.com/c...+log/9c052efad6e651d33334b84c8f1feaf8945e8e7a
I am running the new kernel on latest M stock release .. MXC89F.
No problems so far .. really stable.
The kernel should run on all stock M releases for PixelC.
Used latest stock ramdisk to build the kernel .. maybe the dirty unicorn ramdisk is different.
But the actual kernel should work as well ..it's a dragon kernel.
Repack DU ramdisk with my kernel and it will most probably work as well .. maybe even with the same ramdisk, without repacking. Needs to be tested ..
Give it a try .. it will not hurt.
Cheers
Click to expand...
Click to collapse
I had been keeping up with the chromeos-3.18 branch upstream, but I realized that a majority of the commits do not even apply to Dragon -- so it wasn't all that worthwhile to have in the majority of cases. With that said, I decided to go back to the MXC89F source until the next batch of source is released in June.
NYCHitman1 said:
What are you talking about? We're not CM based.
Click to expand...
Click to collapse
Well my bad...DU is AOSP based. I get mixed up with all several custom roms on my devices :silly:
NYCHitman1 said:
What are you talking about? We're not CM based.
I had been keeping up with the chromeos-3.18 branch upstream, but I realized that a majority of the commits do not even apply to Dragon -- so it wasn't all that worthwhile to have in the majority of cases. With that said, I decided to go back to the MXC89F source until the next batch of source is released in June.
Click to expand...
Click to collapse
You are right .. there also many fixed not relevant for dragon at all.
But it´s a fresh kernel .. upstream
I was so free .. and made a new DU kernel now .. used your ramdisk and my fresh chomeos-3.18 build from today.
@redukt, please test this kernel again .. on DU
Update.ZIP_PixelC_Ryu_chromeos-3.18-kernel_DU_v160519_followmsi.zip
https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Thanks .. still bootloop ?
redukt said:
Well my bad...DU is AOSP based. I get mixed up with all several custom roms on my devices :silly:
Click to expand...
Click to collapse
Please test this one ... Update.ZIP_PixelC_Ryu_chromeos-3.18-kernel_DU_v160519_followmsi.zip
https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Thanks !
followmsi said:
Please test this one ... Update.ZIP_PixelC_Ryu_chromeos-3.18-kernel_DU_v160519_followmsi.zip
https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Thanks !
Click to expand...
Click to collapse
!!! Device is booting!!!
Meh... forget to install SU lol.... Will have a look in kernel auditor
Many thanks
edit: I have to flash the latest supersu (beta v2.74-2) to get root again. Will test your kernel til the next DU weeklie as dd. I´ll have a look at the frequency overview and kept stock settings / governor. System runs fluid with no hickups or so. Great work!
Looks also very interessting ..stabilize-smaug-7897.B-chromeos-3.18
https://chromium.googlesource.com/c...kernel/+/stabilize-smaug-7897.B-chromeos-3.18
Will see .. today they released the 3rd N preview ... maybe it´s time for some N testing.
As I understand correct .. using N ramdisk and the same kernel from today should work on N as well.
We will see ...
Cheers