Related
[Kernel] .29 Alpha for Cyanogenmod 5 Based ROMs 【aHero】 - For the Impatient
Here's a quick and dirty kernel compile with bluetooth and SetCPU OC both working for this ROM (and any Cyanogenmod based Hero ROM really). Should not be overclocking on boot.
Uses koush anykernel format to make it compatible for any CM based ROM.
I don't plan to update this. I had no intentions of making a Hero kernel so I probably wont be updating this. It was kind of an accident. I don't even have a GSM Hero. Anyways flash and enjoy! Devs can take what I did on my .config and make it good. There's some weird stuff in it.
If this eats your phone please do not hunt me down.
jaymac407 said:
Boots, testing more now..
Update: Wifi works, bluetooth works, OC seems to work (I THINK)
Good work.
Click to expand...
Click to collapse
I copied the netfilter options too. If someone can try to see if Wifi-tether works that would be awesome.
So apparently my kernel boots this aHero and fixes bluetooth. It's a .29 kernel based on the new source code.
Mind you that I might be missing some things. I took around 20 minutes comparing the existing .config and making one that is more similar to the Cyanogenmod .config by eyeballing differences and copying pasting code (yes really). I got really lazy toward the end because the .config was so damn long.
I at least enabled squashfs so the .sqf files decompress for sure now. Set localversion to cyanogenmod. You can see what I did to it in the download link as well, where I have a pastebin of what I did before I disabled perflock.
I also disabled a crap load of debug options that were enabled for some reason.
credits:
cyanogen for CM5. Based .config off his ROM
toastcfh for the kernel source code and being the father of all MSM7K overclocks
koush anykernel
.config here:
http://forum.xda-developers.com/showpost.php?p=6548814&postcount=53
how do i use this on ahero ? just flash it over the rom ?
Is this applicable to VanillaEclair?
Just flash this zip over my aHero?
Re: [Kernel] .29 Beta for Cyanogenmod 5 Based ROMs 【aHero】 - For the Impatient
Dont work for me om cyanogen mod, runs so slow it freezes. Cant get in set cpu and look
Sent from my HTC Hero using Tapatalk
going to test this now. I will update.
it sseems to freeze at boot (aHero 1.0 with JIT)
mine freeze at hero screen
Does it need a wipe and reflash first, or should it be ok to try over current CM ROM ( Vanillain 3.0 test version) ?
furrypotato said:
Does it need a wipe and reflash first, or should it be ok to try over current CM ROM ( Vanillain 3.0 test version) ?
Click to expand...
Click to collapse
There specific patches for the villain roms, theres one for Vanillain 3. There is a thread with them on xda
I tired it on Vanillian but cant seem to get past the lockscreen
I downloaded toastcfh's kernel source, but I didn't have time to compile..
anyway thanks for compiling, and I'll test it and report back soon..
Demologic said:
There specific patches for the villain roms, theres one for Vanillain 3. There is a thread with them on xda
I tired it on Vanillian but cant seem to get past the lockscreen
Click to expand...
Click to collapse
And me. Best wait I guess for a fix later.
Heh, awesome.
Be advised that this sometimes freezes randomly, that's the only bug I can see so far. Especially during going from and to sleep. That's the only issue that needs to be resolved. Apart from that, everything seems to work.
jaymac407 said:
Heh, awesome.
Be advised that this sometimes freezes randomly, that's the only bug I can see so far. Especially during going from and to sleep. That's the only issue that needs to be resolved. Apart from that, everything seems to work.
Click to expand...
Click to collapse
Try in setcpu to make the governor performance, if not msm7k
the ondemand governor code was broked in HTC source in .27
can i download the zip and flash it on ahero 1.0????
xaueious said:
Try in setcpu to make the governor performance, if not msm7k
the ondemand governor code was broked in HTC source in .27
Click to expand...
Click to collapse
Only options are performance and ondemand. Neither option seems to help with the crashes.
i have downloaded the zip on first page and flash over ahero 1.0 without JIT my phone boots and come to lockscreen and then i cant anything
my phone is xperia arc s(LT18i), i flash cm9 fx116 server days ago, wifi is ok. Today i download cm9 source and build on my ubuntu with lunch cm_anzu-userdebug. after i flash the generated system.img to my phone and reboot, everything is ok and looks like fx116 but the wifi, it stays" Turning Wi-FI on...". do wifi in cm9 need a patch?
CM 10.1.0 RC2 code base has been released and here it is for your flashing pleasure!
DISCLAIMER:
I am new to android development so more of a builder than a developer at the moment. So please do BACK UP your phone before you get started. If you know how to fix an issue in the ROM then feedback is more than appreciated. Bug reports are welcome, however please understand that I probably won't be able to figure out the solution without help. You can expect that CM code updates will be rolled into this ROM as these come out though.
For those of you looking for Skype audio this ROM does not yet fix it BUT I have tried the tinyalsa_audio stuff from Adam77Root and that does get Skype working just fine, but then it messes up your phone audio to where you don't hear anything or send anything out about 3/4 of the time. So we're getting close but not quite there yet... Oh and bluetooth calling was not fixed when skype worked, so there's something else wrong there...
RC1 was accidentally released with the tinyalsa_audio driver.. So this is RC2 with the "correct" libaudio which means skype is broken but calls work...
Using CWM:
1) BACK UP your current ROM!!!
2) Preform wipe / factory reset
3) Flash the ROM: cm-10.1-RC2-20130530-UNOFFICIAL-i927.zip (MD5 = 2e65e45bdc7539d5260062abdf6cd1cd) Mirror 1
4) Optionally flash GAPPS: gapps-jb-20130427-nonneon-tonyp.zip (MD5 = 13fc57e24ead77ec2613efd643af3800)
Stuff that I've noticed that looks to be fixed / has changed since M3:
- Moved over to KickAss kernel and battery life now totally rocks!
- Picture editing in the gallery is also working fine now.
- HDR photo capture looks to be working just fine also...
- Lock screen lag much less noticeable, but I do sometimes need to press the button twice...
Known issues without workarounds:
- Audio in skype is there but plays back at wrong rate (slower than normal, woman's voice sounds like a man's)
- I was not able to get my two bluetooth headsets working but bluetooth GPS works fine
Known issues with workarounds:
- GPS works great and fast but reports 0-2 satellites only, NMEA data stream seems to be incorrect, so parsing this data may be touchy in some apps
- Pictures taken by camera are shown rotated 90 degrees (then can be manually rotated within the gallery app)
Please don't report any of the above known issues. General CM 10.1 bug tracking thread <- Please check here before posting a bug report!
I'm sure there are others but I've not noticed them yet. I don't use a hands free but I can confirm the bluetooth does work with an external GPS for instance.
Change log:
20130530 - Corrected call audio issue and CM 10.1.0 RC2 code base
20130525 - Moved to KickAss kernel and CM 10.1.0 RC1 code base
20130503 - Fixed gallery pic editing, update OTA image
20130502 - Combined LiteKernel built 20130418, broke the gallery pic editing, added OTA support
20130417 - Combined LiteKernel built 20130414 into the ROM, no need to flash kernel seperately
20130416 - New LiteKernel build by bubor
20130415 - WiFi fix by bubor applied
20130412 - M3 code release, still using LiteKernel from 20130222
20130405 - Rolled back non-monthly code updates to revert this back to the original M2 code release. Corrected build environment to generate proper boot.img, No longer using the one from the LiteKernel which means that the LiteKernelManager is not messing around with settings now.
20130404 - Used the 2013/02/23 branch of the device tree and also re-synced with the CyanogenMod source. SD card mappings now match the CM10.1 later builds so recommend wiping and re-installing fresh for this one,
20130402 - Build LiteKernel into the ROM so no need to flash the kernel separately
Credits:
- KickButtowski for the kick ass KickAss kernel
- tonyp for the non-neon GAPPS package
- bubor: WiFi tether fix and new kernel that fixed data usage, image editing in galley and google now hotword detection as well as new GAPPS
- Adam77Root for the libaudio code that fixed the camera audio in video recordings
- yohan4ws for pointing me towards Adam77Root's libaudio stuff
- gtmaster303: CM 10.1 bug tracking thread maintenance
- The-Covenant team: For the device tree and vendor proprietary files
- dman3285: For the tutorial on building CM10 and CM10.1 from source, and all your work getting this setup
- thegreatergood: For the LiteKernel source and binary
If I've missed anyone apologies in advance and just let me know and credit will be added...
And here is the ling to my device tree should anyone want to follow along. Seperate branch available for the tinyalsa_audio for the more adventurous ones.
Reserved...
sweeeet!
wow, another rom i will try it tomorrow, juts 1 question, if i flash lite kernel the wifi will work? and how about ohter mods or skype?
I am gonna try it tomorrow, thanks thanks
Awesome, thanks!
Can you please list the non working things you have already discovered?
lorddavid said:
wow, another rom i will try it tomorrow, juts 1 question, if i flash lite kernel the wifi will work? and how about ohter mods or skype?
I am gonna try it tomorrow, thanks thanks
Click to expand...
Click to collapse
Correct - If you flash the LiteKernel on top of the ROM then the WiFi will work.
braintweaker said:
Awesome, thanks!
Can you please list the non working things you have already discovered?
Click to expand...
Click to collapse
Done...
This is pretty much just a new build with all the upstream commits, correct?
I suggest everyone review my bug tracker thread before posting bugs, as these builds are one in the same rom...
http://forum.xda-developers.com/showthread.php?p=38339702
gtmaster303 said:
This is pretty much just a new build with all the upstream commits, correct?
I suggest everyone review my bug tracker thread before posting bugs, as these builds are one in the same rom...
Click to expand...
Click to collapse
Agreed.
This build is based on:
- CM 10.1 M2 release code base (released 4 Mar 2013 so the Feb ROMs are based off the M1 release)
- The-Covenant device tree and proprietary files which I assume have not been touched since end of Feb
- thegreatergood's LiteKernel binary which is the same as the other ROMs
So any issues that were related to the kernel or device specific stuff will still be there, but CM based issues may have been resolved. Case in point the audio playback lag is now fixed on my phone.
YMMV of course!
I am doing right now a backup of my current rom. I really want to see if skype and magic jack works now. I will post back in some hours.
Is bluetooth handsfree fixed in this build?
Re: [DEV][ROM][JB 4.2.2][Unofficial] CM10.1-M2 3/31/2013
One question. Do i need to flash the keyboard fix? and the rom is compatiblr with the mod to put external sd as internal? i try to flash but never boot. I will try again in a few moment
Sent from my SGH-I927 using xda app-developers app
jzamoras said:
Is bluetooth handsfree fixed in this build?
Click to expand...
Click to collapse
In my test both headsets connected fine but one gave no sound and the other gave me only static. Not sure if the mic was working on either one. I don't usually use bluetooth so can't say for sure but I think this is still an issue on this build at this time unfortunately.
lorddavid said:
One question. Do i need to flash the keyboard fix? and the rom is compatiblr with the mod to put external sd as internal? i try to flash but never boot. I will try again in a few moment
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
You won't "need" to but the crashing keyboard gets annoying fast. So installation of a keyboard from the play store (I used the hacker's keyboard) is a must to make this usable. now if there is a "fix" available for the stock keyboard on the JB builds then let me know what it is and I'll see about adding it to the ROM by default.
As for the memory cards, the internal is mounted as /mnt/emmc and the external is mounted as /mnt/sdcard. Not sure if that answers your question...
spyke555 said:
In my test both headsets connected fine but one gave no sound and the other gave me only static. Not sure if the mic was working on either one. I don't usually use bluetooth so can't say for sure but I think this is still an issue on this build at this time unfortunately.
Click to expand...
Click to collapse
Is the same I got using AOKP. I guess I'll wait then.
spyke555 said:
You won't "need" to but the crashing keyboard gets annoying fast. So installation of a keyboard from the play store (I used the hacker's keyboard) is a must to make this usable. now if there is a "fix" available for the stock keyboard on the JB builds then let me know what it is and I'll see about adding it to the ROM by default.
As for the memory cards, the internal is mounted as /mnt/emmc and the external is mounted as /mnt/sdcard. Not sure if that answers your question...
Click to expand...
Click to collapse
I was talking about these patches http://forum.xda-developers.com/showthread.php?t=2067954
there is a patch for swap the external sd with the internal, and another for the keys in the keyboard.
Edit: i think that the keyboard patch no needed. But the Patch to swap the the external SD as internal, doesnt work. The rom never boot when i install it.
Another thing, its me, or the wifi is very very slow? i am downloading skype from the market and is taking so much.
Sorry if i wrote something bad :/
Just corrected the link to the LiteKernel, you may want to download this new link and re-apply to make sure you have the latest kernel installed. Trying to get this built into the ROM to avoid any further confusion...
Ok, i will try it again, but the skype/magicjack audio issue still exist
Just posted a new ROM build that now has the LiteKernel-20130222 built in. No need to flash separately. CM code is the same so no change there. If you already downloaded the 20130331 version and installed to 20130222 kernel then no need to re-download.
CM10.1-M3 release should be coming out shortly so do expect another update soon...
spyke555 said:
Just posted a new ROM build that now has the LiteKernel-20130222 built in. No need to flash separately. CM code is the same so no change there. If you already downloaded the 20130331 version and installed to 20130222 kernel then no need to re-download.
CM10.1-M3 release should be coming out shortly so do expect another update soon...
Click to expand...
Click to collapse
I'll jump as soon bluetooth thing is fixed
Not sure if im posting in correct area,
If Posted in wrong area, my Bad..
Ever since MultiRom come out for D851, People have been experiencing Kernel panics with the latest updates from the CM Sources. (Not everyone, But Most)
The method I used below has worked with no problems with me. I cant say it will work with everyone. But it worked for me..
I know installing a Full Kernel ZIP file on secondary rom can either take 45 mins or longer, or not even work at all. (My Experience.)
But the method listed below, only took 5 secs and worked perfectly..
Now I just wanted to post a work around for the people that are experiencing Kernel Panics when using MultiRom..
Example: you install CM-12 as a secondary rom, Reboot and it crashes with Kernel Panic,
Work around: This awesome Kernel: Optimized SM-4.9.3 Kernel V2.2 for D855/D851/D850/LS990 http://forum.xda-developers.com/lg-g3/development/kernel-optimized-sm-4-9-3-kernel-t2976049
Take that kernel and unzip file. Then in Multi rom settings in TWRP-MultiRom goto list roms.. Pick the Rom with the kernel panic and Then remove Boot image..
click on the add boot image now.. and then goto the unziped kernel from above, Find the boot.img and click on it.. it will add it.. takes only a few secs.
Reboot.. Kernel panic is now gone..... (Becides, that Kernel works great)..
Note: that above example is for Lollipop only.. I havent tested it with any other kernels.. Most kernels that I unziped had that bump stuff listed for the locked bootloaders.
and no correctly listed boot.img So.. it wouldnt work...
You can also Make a Backup of your current working boot image and then flash that into it, Havent testing it like that, but should work the same.
The other work around I heard posted is:
Install to primary ROM then move to secondary rom.
Thank you for this. I have been flashing RIN kernel after any cm12 I've installed since installing MultiROM. Seems to work too, but the hour long wait to flash a 7mb kernel really bugs me.
Next time I flash a cm12 as secondary I'll give this a go.
Eliminater74 said:
Not sure if im posting in correct area,
If Posted in wrong area, my Bad..
Ever since MultiRom come out for D851, People have been experiencing Kernel panics with the latest updates from the CM Sources. (Not everyone, But Most)
The method I used below has worked with no problems with me. I cant say it will work with everyone. But it worked for me..
I know installing a Full Kernel ZIP file on secondary rom can either take 45 mins or longer, or not even work at all. (My Experience.)
But the method listed below, only took 5 secs and worked perfectly..
Now I just wanted to post a work around for the people that are experiencing Kernel Panics when using MultiRom..
Example: you install CM-12 as a secondary rom, Reboot and it crashes with Kernel Panic,
Work around: This awesome Kernel: Optimized SM-4.9.3 Kernel V2.2 for D855/D851/D850/LS990 http://forum.xda-developers.com/lg-g3/development/kernel-optimized-sm-4-9-3-kernel-t2976049
Take that kernel and unzip file. Then in Multi rom settings in TWRP-MultiRom goto list roms.. Pick the Rom with the kernel panic and Then remove Boot image..
click on the add boot image now.. and then goto the unziped kernel from above, Find the boot.img and click on it.. it will add it.. takes only a few secs.
Reboot.. Kernel panic is now gone..... (Becides, that Kernel works great)..
Note: that above example is for Lollipop only.. I havent tested it with any other kernels.. Most kernels that I unziped had that bump stuff listed for the locked bootloaders.
and no correctly listed boot.img So.. it wouldnt work...
You can also Make a Backup of your current working boot image and then flash that into it, Havent testing it like that, but should work the same.
The other work around I heard posted is:
Install to primary ROM then move to secondary rom.
Click to expand...
Click to collapse
Or you can try the tootsie-pop test kernel. I implemented the multirom patch into it tonight. If everything works fine it'll be been bumped into the stable kernel and be included with bliss pop and Resurrection remix ROMs.
aclegg2011 said:
Or you can try the tootsie-pop test kernel. I implemented the multirom patch into it tonight. If everything works fine it'll be been bumped into the stable kernel and be included with bliss pop and Resurrection remix ROMs.
Click to expand...
Click to collapse
Yes from what I have tested it works with any Compatible flashable Kernel that unzips and has a boot.img..
The above kernel that I listed on post #1 is Stable but is overclockable, If you dont want that.. Then dont use that one, It was only listed as an Example.
I use that kernel with no problems.. I dont OC my phone, but its nice to have the option to do so.
Ill test out the tootie-pop kernel the next time I feel like messing with my phone.
Now isnt a good time, Im sick, and I have already messed up my linux system and my windows system (windows 10 Enterprise build 9926).. Had to do a fresh install on windows.. my linux doesnt want to let me mount my own drives in gnome.. Says I dont have access do to some error, But I am running Ubuntu Vivid 15.04.. so thats to be expected..
So touching my phone isnt a good idea right now.. I might just end up blowing it up the way my luck is going.
Thanks to the OP. This was a quick and simple fix to a frustrating issue.
Sent from my LG-D851
After doing a little research, and finding out that the MultiRom is pretty much dead. I decided to delete it all together and stick with the one rom that seemed
very stable and likable for me. I wont say what rom that was as to respect all developers on this forum.. So I stopped all testing and experiments dealing with MultiRom..
If the Developer once again decides to post updates and fixes. I will again. try it.. but for now.. I will no longer post any workarounds or help with this MultiRom section anymore...
As you know that thread was closed in the ROM Development section..
as topic thanks
I'm sorry.
This device cannot be more dead now.
Rest in peace, Marshmallow-less phablet.
Spaqin said:
I'm sorry.
This device cannot be more dead now.
Rest in peace, Marshmallow-less phablet.
Click to expand...
Click to collapse
I'll be honest: I needed just few more weeks with working USB to get Marshmallow fully functional. I got it running on E988, but some important stuff was broken, thus, device was unusable.
I got it to boot without SELinux - device tree needs new set of rules/fixes on current ones, because some old QCOM rules are dropped from vendor repos since mako isn't officially supported for M. That was ~90% fixed.
There were other problems which made device useless: modem and sensors - main reasons I haven't finished what I started. I had issues with reboots by DSP subsystem on every damn build, and just before my USB died, while experimenting with kernel and init files, I got an idea to disable modem and sensors services (they were causing DSP subsystem reboots) and boom, Marshmallow booted. Managed even to login to my Google account, install apps, use it for a while but had to revert back to LP - main phone without working modem is a tablet, not a phone Unfortunately, some time after that my USB decided to become just a simple charging port, so job was left unfinished.
So whoever is willing to tackle this issue:
- GPU drivers need update, both ion and gpu/msm update (kernel) and libs (need newer libs from mako/flo)
- Modem and sensors HAL need some updating - possibly only libs should be updated, since there were no changes in msm8960/apq8064 3.4 kernels connected to drivers
- Some SELinux stuff needs to be fixed
- Our device is stuck with OpenSSL, Marshmallow uses BoringSSL which has crippled some OpenSSL symbols, so there are some compatibility modules with missing symbols which need to be written... at least, that had to be done back then. Not sure now, it's nearly 5 months later now. Missing symbols can be the reason why both current and Lollipop (kanged from F240) modem/sensors didn't work, I really haven't managed to get usable logs before device's total freeze and reboot with these two services on, so whoever fixes this, well, gets functional Marshmallow
- Camera HAL, our issue since last KitKat days
but I saw that the official Cyanogen mod still release update for e988 ?
any reason as to not using it ?
Paleskin said:
but I saw that the official Cyanogen mod still release update for e988 ?
any reason as to not using it ?
Click to expand...
Click to collapse
There are still CM 12.1 nightlies for G Pro? Miracle, especially since we don't have a maintainer anymore... Just be sure to change kernel because default one still has blackouts - there were no commits or fixes on main CM kernel since last year.
ShadySquirrel said:
There are still CM 12.1 nightlies for G Pro? Miracle, especially since we don't have a maintainer anymore... Just be sure to change kernel because default one still has blackouts - there were no commits or fixes on main CM kernel since last year.
Click to expand...
Click to collapse
Can't this blackout fix, solved on SlimLP, be checked in for upstream cyanogenmod ?
SlimLP is the only usable ROM for e980, all the other rooms suffer from screen blackout. On slimlp the only eventual problem is with the camera, but this can be fixed by using opencamera, as opencamera uses diferent threads, and in my case fixes a lot of problems.
bedi1982 said:
Can't this blackout fix, solved on SlimLP, be checked in for upstream cyanogenmod ?
SlimLP is the only usable ROM for e980, all the other rooms suffer from screen blackout. On slimlp the only eventual problem is with the camera, but this can be fixed by using opencamera, as opencamera uses diferent threads, and in my case fixes a lot of problems.
Click to expand...
Click to collapse
Someone could try to push that, but I don't know if they will accept it - it requires some device tree changes to be reverted (reverting only kernel commit renders Live Display useless, you also need changes in device_e980 and device_gproj-common).
I still have a bitter taste from back then when RIL problem occured due to their tinkering with Telephony frameworks - it took nearly 6 months for them to fix that officialy, even with two or three workarounds already available on Gerrit and numerous reports on JIRA.
ShadySquirrel said:
I'll be honest: I needed just few more weeks with working USB to get Marshmallow fully functional. I got it running on E988, but some important stuff was broken, thus, device was unusable.
I got it to boot without SELinux - device tree needs new set of rules/fixes on current ones, because some old QCOM rules are dropped from vendor repos since mako isn't officially supported for M. That was ~90% fixed.
There were other problems which made device useless: modem and sensors - main reasons I haven't finished what I started. I had issues with reboots by DSP subsystem on every damn build, and just before my USB died, while experimenting with kernel and init files, I got an idea to disable modem and sensors services (they were causing DSP subsystem reboots) and boom, Marshmallow booted. Managed even to login to my Google account, install apps, use it for a while but had to revert back to LP - main phone without working modem is a tablet, not a phone Unfortunately, some time after that my USB decided to become just a simple charging port, so job was left unfinished.
So whoever is willing to tackle this issue:
- GPU drivers need update, both ion and gpu/msm update (kernel) and libs (need newer libs from mako/flo)
- Modem and sensors HAL need some updating - possibly only libs should be updated, since there were no changes in msm8960/apq8064 3.4 kernels connected to drivers
- Some SELinux stuff needs to be fixed
- Our device is stuck with OpenSSL, Marshmallow uses BoringSSL which has crippled some OpenSSL symbols, so there are some compatibility modules with missing symbols which need to be written... at least, that had to be done back then. Not sure now, it's nearly 5 months later now. Missing symbols can be the reason why both current and Lollipop (kanged from F240) modem/sensors didn't work, I really haven't managed to get usable logs before device's total freeze and reboot with these two services on, so whoever fixes this, well, gets functional Marshmallow
- Camera HAL, our issue since last KitKat days
Click to expand...
Click to collapse
how the progress ? :fingers-crossed:
Paleskin said:
how the progress ? :fingers-crossed:
Click to expand...
Click to collapse
Had it booting (fixed selinux and most driver issues), and that's it. No RIL, so no data/signal; no GPS; no Sensors... Practically useless. Probably stuff with libs, but I don't have neither time neither knowledge to fight with that... especially since my e988 is almost dead, no matter what I do - my phone's usb is "working", battery is long time under normal capacity (can't survive even 12h), now my modem is causing random reboots on both stock and ASOP, display has black marks on one side... practically, a zombie So I'll be ditching this phone soon, and all work I've done for it.