NOTE: This PATCH is compatible ONLY with MY GB Kernel version 2.6.2 and beyond. Older Kernel versions are NOT Compatible!
Why bother with this patch? For me, the old Froyo WiFi Calling was very finicky and often times did not work due to router configurations. With Native GB Wifi Calling, I was able to have WiFi calling as long as I have a stable WiFi signal regardless of router configurations. Besides this is Native GB app, so it matches up nicely with GB ROMs, such as CM7, AOSP, GB MIUI, etc..
The Patch ==> Native GB WiFi Calling Patch <==
[ Installation Procedure ]
Before installation, make sure the following lines exist in the build.prop located @ /system folder (these lines should be there in all CM7 or AOSP derivatives)
rild.libpath=/system/lib/librilswitch.so
rilswitch.vendorlibpath=/system/lib/libhtc_ril.so
rilswitch.ganlibpath=/system/lib/libganril.so
1. Reboot to recovery
2. Install zip
3. Reboot, DONE!
[ Patch Details ]
This patch included the latest RIL (Radio Interface Layer) libraries from the Leaked GB ROM for Glacier.
Currently, all CM7 derivatives are using FROYO version of WiFi Calling module, since the real GB leak, a Native GB version is now available. I had the kineto_gan.c source code from HTC Saga a month ago, but we didn't have the matching libraries and GB WiFi Calling App until recently with the Leak.
The patch included Native Gingerbread ril libraries and Native Gingerbread WiFi Calling app. The patch will DELETE the FROYO WiFi calling App and REPLACE Froyo version of ril libraries to Native Gingerbread versions.
Reserved 1...
Nice network name. Its awfully similar to mine
Wait so if we're on CM 7.0.3 we need to flash this for the updated app right? Then flash the kernel?
silentsnow31802 said:
Nice network name. Its awfully similar to mine
Click to expand...
Click to collapse
This is supported by my own kernel with kineto_gan.ko modules compiled from HTC Saga's source code... I am not aware of your version... Did you compile the kineto_gan.c file from source?
PhantomRampage said:
Wait so if we're on CM 7.0.3 we need to flash this for the updated app right? Then flash the kernel?
Click to expand...
Click to collapse
You should flash the kernel first, then the patch 2nd.
faux123 said:
This is supported by my own kernel with kineto_gan.ko modules compiled from HTC Saga's source code... I am not aware of your version... Did you compile the kineto_gan.c file from source?
Click to expand...
Click to collapse
I meant your router name (dd-wrt). I am a much simpler man that that, in fact I dont understand half of that sentence lol.
silentsnow31802 said:
I meant your router name (dd-wrt). I am a much simpler man that that, in fact I dont understand half of that sentence lol.
Click to expand...
Click to collapse
Oh.. I am a Linux Mac Guy... I own several Mac products and all 3 of my routers all run DD-WRT Linux LOL...
So faux is this only to be used with your kernels or does it also work with the cm stock kernel from from the latest nightlies? Didn't see much reference to other kernels in your op.
corwest said:
So faux is this only to be used with your kernels or does it also work with the cm stock kernel from from the latest nightlies? Didn't see much reference to other kernels in your op.
Click to expand...
Click to collapse
It DOES NOT work with any other kernel because they don't have kineto_gan.ko which is needed by GB wifi calling module.
kernel modules such as kinteo_gan.ko MUST follow the exact version of the kernel. So ONLY my GB kernel version 2.6.2 and beyond will work.
Got it. Looks like ill flash your kernel then
you the man, on my next pay day going to donate a little something something to ya.
faux123 said:
It DOES NOT work with any other kernel because they don't have kineto_gan.ko which is needed by GB wifi calling module.
kernel modules such as kinteo_gan.ko MUST follow the exact version of the kernel. So ONLY my GB kernel version 2.6.2 and beyond will work.
Click to expand...
Click to collapse
I installed this on 2.5.2 and it seems to be working.
silentsnow31802 said:
I installed this on 2.5.2 and it seems to be working.
Click to expand...
Click to collapse
LOL, OK... Good.... I didn't expect that... The CM7 hacked code is quite different from official HTC code, things like MTU and such are all different. Surprised it worked...
Just be aware may not be 100% compatible or optimized. The official HTC code is designed to work with it
faux123 said:
LOL, OK... Good.... I didn't expect that... The CM7 hacked code is quite different from official HTC code, things like MTU and such are all different. Surprised it worked...
Just be aware may not be 100% compatible or optimized. The official HTC code is designed to work with it
Click to expand...
Click to collapse
Well I still wouldn't suggest doing it as I did it by mistake, just saying that it did work. I suspect it would be unstable. I did not use it for very long so I can not comment on the stability at all. I ended up updating to your latest kernel as you suggested.
rild.libpath=/system/lib/librilswitch.so
rilwitch.vendorlibpath=/system/lib/libhtc_ril.so
rilswitch.ganlibpath=/system/lib/libganril.so
Shouldn't the 2nd line read
rilswitch.
Faux, this is not working with the Canadian Pure Sense rom. I applied you Kerner first and then the patch, and nothing. Any idea why?
EDIT: BTW, not all the lines where there in the build.pro folder. How can they be added? Another patch?
marcos.lennis said:
Faux, this is not working with the Canadian Pure Sense rom. I applied you Kerner first and then the patch, and nothing. Any idea why?
EDIT: BTW, not all the lines where there in the build.pro folder. How can they be added? Another patch?
Click to expand...
Click to collapse
No they are there, just look carefully. But its still not working for me either on the canadian pure sense rom. Maybe we have to be on one of his kernels??
wickedny15 said:
No they are there, just look carefully. But its still not working for me either on the canadian pure sense rom. Maybe we have to be on one of his kernels??
Click to expand...
Click to collapse
I am using one of Faux's kernels, the last one he made specially for the MySense GB leak rom and the Canadian Rom, and still it does not work.
marcos.lennis said:
I am using one of Faux's kernels, the last one he made specially for the MySense GB leak rom and the Canadian Rom, and still it does not work.
Click to expand...
Click to collapse
okay, same here. I flashed his new kernel for the Canadian Leak and flashed the wifi calling app again and still doesn't work. Its stuck on "Enabling - Please wait while connecting to T-mobile Network"
Edit: by the way I wiped cache, dalvik and fixed permissions
Related
I take no credit for this other than building it and uploading it. This is 100% based off of code from Team Douche. Special thanks to cyanogen, Zinx, and Kmobs for giving us such great code to work with. Special thanks to Gridlock32404 for all the help he's provided me with android in general.
This is basically the same as the CM7 Alpha roms, but with all of CMParts and CM Settings removed.
http://www.multiupload.com/DU6VR2OMH7 (GingerBaked)
http://dl.dropbox.com/u/16719351/gapps-newmarket.zip (gapps)
http://dl.dropbox.com/u/11228290/recovery.img (ClockworkMod 3 Recovery)
If you haven't already been running a CM7 Alpha, you'll need to manually flash a new recovery image since 2.3 based roms are not compatible with the current recovery found in ROM manager.
Download the recovery image posted above, and flash using fastboot.
$adb reboot bootloader
$fastboot flash recovery /path/to/recovery.img (replace path/to/ with the actual path to where you downloaded the recovery image)
If you'd rather flash the recovery from the emulator follow http://forum.xda-developers.com/show...&postcount=361
once you have the new recovery, install the ROM through recovery as you normally would. You'll need a full wipe. After flashing the ROM, you'll need to flash the gapps posted above. Thanks to Grankin01 for putting those together.
Also, if you decide to go back to a froyo rom, you'll need to flash the old recovery. If you need help flashing the recovery,
check this thread: http://forum.xda-developers.com/showthread.php?t=852905
Also, if you are having trouble with adb/usb drivers check out the below thread by b16a2smith
http://forum.xda-developers.com/showthread.php?t=896206
Known Issues for this ROM are the same as all of the current CM7 alpha builds.
First post!
gridlock32404 said:
First post!
Click to expand...
Click to collapse
lmao!!
10char.
option94 said:
lmao!!
10char.
Click to expand...
Click to collapse
Really... I'm gonna give this a try, I'll be back with what I find
stlouie65 said:
Really... I'm gonna give this a try, I'll be back with what I find
Click to expand...
Click to collapse
Awesome. Let me know how you like it.
option94 said:
Awesome. Let me know how you like it.
Click to expand...
Click to collapse
Yes Sir, will do.
YAY more crack flashing
Flashed, booting up now
stlouie65 said:
Flashed, booting up now
Click to expand...
Click to collapse
same here
Wow thanks for this. And this is the real deal, proper credits and all. Unlike some previous ones. Will be flashing this one soon.
After initial boot, this ROM boots quickly. I did attempt to open the wifi calling, just opened and closed. Gonna load the rest of my apps and test the camera
bobsbbq said:
Wow thanks for this. And this is the real deal, proper credits and all. Unlike some previous ones. Will be flashing this one soon.
Click to expand...
Click to collapse
The lack of credit is why I put this together in the first place.
So if the issues are the same and what not and its just cm parts removed, what are the benefits of this vs cm7 ...?
Sent from my MT4G running Gingerbread
Jaskwith said:
So if the issues are the same and what not and its just cm parts removed, what are the benefits of this vs cm7 ...?
Sent from my MT4G running Gingerbread
Click to expand...
Click to collapse
well obviously its for people who want a more original themed GB rom instead of having all the CM stuff.
what can we expect from this ROM that would differ from the other CM7 thread? i dont understand the necessity of fragmentation on a particular ROM unless each iteration has its own unique features that sets it apart from the next...
pgarza said:
what can we expect from this ROM that would differ from the other CM7 thread? i dont understand the necessity of fragmentation on a particular ROM unless each iteration has its own unique features that sets it apart from the next...
Click to expand...
Click to collapse
It's being checked out now
So basically this is just like the first CM Alpha that was released, but just with recent stuff? I remember the first Alpha had no CM stuff.
Sent from my HTC Glacier
pgarza said:
what can we expect from this ROM that would differ from the other CM7 thread? i dont understand the necessity of fragmentation on a particular ROM unless each iteration has its own unique features that sets it apart from the next...
Click to expand...
Click to collapse
It is very simple. This is a close to AOSP ROM with CM base and Framework, just all the CM stuff removed. So you get a more pure Gingerbread feeling ROM like the Nexus S shipped with. Obviously it is not compiled on the original source yet but you get the same kind of experience.
Everybody has different taste. This is more of a very light ROM
bobsbbq said:
It is very simple. This is a close to AOSP ROM with CM base and Framework, just all the CM stuff removed. So you get a more pure Gingerbread feeling ROM like the Nexus S shipped with. Obviously it is not compiled on the original source yet but you get the same kind of experience.
Everybody has different taste. This is more of a very light ROM
Click to expand...
Click to collapse
Appreciate this very much Bob, it's running smooth, still configuring my apps so I can run a fix_permissions to get all right
pgarza said:
what can we expect from this ROM that would differ from the other CM7 thread? i dont understand the necessity of fragmentation on a particular ROM unless each iteration has its own unique features that sets it apart from the next...
Click to expand...
Click to collapse
from what I've read it appears it would be like Running eVil D's MT4G-G2 ROM as opposed to CM 6.1.2 RC2.
GingerBaked and MT4G-G2 = Pure Vanilla Android
CM 7 and CM 6.1.2 RC2 = Tweaked / Modded Vanilla Android
About to flash CM7. Seen some mention of 'kernal' in various threads. What does it do? and do I need to update it?
Cheers.
same question
The Kernel controls things like battery drain and CPU levels for overclocking etc... its not a must do but recommended for best performance. there is probably not a "best" one but more like the best that suits you. If you are running CM7 i would recomend Vork Kernel's or ManU kernels
Richardtrip's kernels are also very good: overcklocking, manual voltage level, Two-way call recording.
plohoi said:
Richardtrip's kernels are also very good: overcklocking, manual voltage level, Two-way call recording.
Click to expand...
Click to collapse
Have you used the call recording? If so how do you "activate" it or listen to the calls afterwards?
CdTDroiD said:
Have you used the call recording?
Click to expand...
Click to collapse
Yes call recording is working fine.
CdTDroiD said:
If so how do you "activate" it or listen to the calls afterwards?
Click to expand...
Click to collapse
There are several apps in http://forum.xda-developers.com/showthread.php?t=993793 thread, I used app by skvalex.
Since I'm new to Desire and HTC- what is the difference between Sense and AOSP kernels?
(before you ask- I know what AOSP is)
Do Sense firmwares require some extra drivers/modules/settings in kernel?
gen_scheisskopf said:
Since I'm new to Desire and HTC- what is the difference between Sense and AOSP kernels?
(before you ask- I know what AOSP is)
Do Sense firmwares require some extra drivers/modules/settings in kernel?
Click to expand...
Click to collapse
Hi there!
Sense is HTC proprietary software built over the top of Android. This code is not open source and is what HTC use to set themselves apart from other manufacturers like Samsung etc. Sense is what they sell as their user experience.
AOSP stands for Android Open Source Project. Since Android is an open source operating system, Google publish all the code and necessary tools to develop Android. Companies like HTC get the code and then write Sense over the top. Devs in this community like Cyanogen take the AOSP code and build their ROMS from scratch.
When you see ROMS that are for Sense 2.1 on Gingerbread for example this means that someone has been able to port software running on other phone models like the Desire HD or Incredible etc to your phone model (Desire)
As for the kernels you will need to make sure that the kernel you run is supported on the device and that's about it. The Kernel has to have some key components or the phone won't work so the ROM you use just uses them.
Having said that, ROM developers usually optimise around one or two particular Kernels. They are usually included in the ROM or the Dev will tell you which one they recommend for certain purposes.
You do have to have apps in the system that can access settings if customising the performance beyond what the dev has already done is what you want to do.
Thanks for the answer but it's not exactly what I'd like to know
Thing is- what makes Sense kernel incompatible with AOSP firmware (and vice versa)
Sorry for not answering what you were looking for. I'll try again.
The Kernels for Sense would have specific code that enables features in the phone that HTC build. LED control, light sensor etc. I assume Sense is quite strict about what it will work on and what it won't.
The AOSP Kernels are built without knowing the exact hardware maps of the internal components and as such won't work with Sense because they simply don't know how due to HTC keeping a lid on all source work for Sense and the handset itself.
The best developers can figure most of it out (certainly I am not a dev, just a geek ) and teams like CyanogenMod have it mostly discovered and configurable.
Is that more helpful?
Isn't Sense a HTC's android framework "mod"? I mean does it "just" provide more/different functionality than AOSP?
AFAIK all kernels must be built knowing exact hardware map, otherwise some devices will not work or kernel will not boot. The only autodetect I'm aware of is display panel type and filesystems (I did mess with kernels @samdroid.net)
i have a question about kernels an such from what i understand is you don't need to update the kernel but its a good idea too do so. couple questions i have.
1. how do you know what kernel you have installed currently.
2. How do you flash or get a new one installed if you need or want it.
3. scene i am using core droid 6.3 gb2.3.3 what kernel would be the most compatible or effective?
I have had my inspire phone for 3 months an finally rooted it 3weeks ago sence then i have used the rom manager too play with different roms an make backups of the 2 i have found i like the most. After reading i have seen it stated too get the most out of these roms though you should install a different kernel.
To know your currently version, you have to go in parametres and then logiciel version and look at build. Sorry for my bad English.
Sent from my HTC Desire using XDA Premium App
I don't want open a new thread, so I will ask here.
Now I have
kernel
2.6.32.15-gf5a401c
baseband
32.49.00.32U_5.11.05.27
Click to expand...
Click to collapse
on stock pre rooted 2.2 Froyo.
I want put this ROM. Can I put this ROM with my kernel and radio or I musst put latest kernel and radio?
GTRSkyR34 said:
I don't want open a new thread, so I will ask here.
Now I have
on stock pre rooted 2.2 Froyo.
I want put this ROM. Can I put this ROM with my kernel and radio or I musst put latest kernel and radio?
Click to expand...
Click to collapse
You will find that many roms contain a kernel in the zip file, so it will often change when you flash a rom. If not, the developer may recommend one.
Radio is independent of rom flash, and unless you start getting connectivity problems there is normally no need to change it. Again, some developers will recommend a radio (and maybe a RIL if they know a particular combination works well with their rom.
I have ThunderSense v1, and I would like to know if there are any kernels that I can put on my HTC DESIRE CDMA to be able to undervolt using SetCPU. It is Sense 2.2 by the way.Thanks.
Belswick67 said:
I have ThunderSense v1, and I would like to know if there are any kernels that I can put on my HTC DESIRE CDMA to be able to undervolt using SetCPU. It is Sense 2.2 by the way.Thanks.
Click to expand...
Click to collapse
Set CPU Doesn't undervolt. It underclocks (Which in turn, lowers voltage).
Have a read here:
http://androidforums.com/desire-all...-bfs-axi-uvoc-published-20th-july-2011-a.html
well, still. is there a undervolted kernel that i can get?
Yes. All of them.
Did you see the "Everything desire is here thread"?
http://forum.xda-developers.com/showpost.php?p=12350779&postcount=3
Thanks man. but i have ONE more question.. Will any of the sense kernels work on a CDMA? cause i know that alot of work done is just for GSM. I dont want to mess up my rom, i know i can do a nandroid. but still... lol
edit: This is a Froyo Sense Rom, and every kernel that i see on there, is for GingerSense... ):
Thats a very good question, which unfortunately I do not know. I have no experience of CDMA devices. Possibly not actually
Alright bro, thanks anyways.
I think the issue is that decent kernel source wasn't available for the not so widely used CDMA.
From what I can tell, many Sense Kernels will work, but its the radio that is an issue, more explicitly, WiFi breaks...
Yup, the kernel source is actually the same. The compiled binary that most people release has bravoc disabled in some drivers (for making the kernel marginally smaller in size, like the wifi driver you mentioned). In almost every source file, there are if blocks to check whether the device is bravo/bravoc/passion.
Droidzone said:
Yup, the kernel source is actually the same. The compiled binary that most people release has bravoc disabled in some drivers (for making the kernel marginally smaller in size, like the wifi driver you mentioned). In almost every source file, there are if blocks to check whether the device is bravo/bravoc/passion.
Click to expand...
Click to collapse
In which case, do you know of any where bravoc has not been commented out? Have yours?
I dont know alot about sense kernels.
I assume Like AOSP, froyo and GB require different kernels. But how about GB ACES port v Runnymede? Can they use the same kernels?
rootSU said:
In which case, do you know of any where bravoc has not been commented out? Have yours?
I dont know alot about sense kernels.
I assume Like AOSP, froyo and GB require different kernels. But how about GB ACES port v Runnymede? Can they use the same kernels?
Click to expand...
Click to collapse
I haven't enabled the bravoc drivers either while compiling, though it's easy enough to enable it while building. Yup, my GB kernel's being used in a couple of the runny Ports and seems to work well. Don't know about Ace, but I believe the same kernel ought to work on it.
Unofficial-Official JellyBean for P930/935/936
Unofficial-Official JellyBean for P930/935/936 - N2 - with working WiFi. Just clean ROM like original from SU640.
Download: (Need minimum 630mb free size on System part )
http://dfiles.ru/files/w4gujg5ef
For information:
For JellyBean ROM for I-Project need 1Gb system size. So when you flash KDZ it will repart you eMMC.
I unpack KDZ from SU640, and repack System part.
Deleted all Operator Apps and Google Apps, remove SecurityCheck, adapt ROM for GSM, and now size of ROM ~ 630mb. And we can flash it via CWM without problem on old partition table and it working with old MODEM.
I ported new kernel 3.4 from LG F120S and SU640, adaptive it for P930.
My port Sphinx V4.1 - 4.1.2 JB for P930
Probably fix copability with different bootloaders;
Rework battery and charger drivers;
Translated to RUS/UKR
Need 646mb. free space on System part!
Download:
http://dfiles.ru/files/1er0nv65u
First patch for Sphinx ROM
Fix some bugs in sound driver;
Fix proximity sensor;
Some fixes for telephony.
Download: Global_Patch_1.zip
Second patch for Sphinx ROM
Fix random boots during sleep;
Added 2 new LG apps: PhotoAlbum widget + Photo wallpaper;
Restore EasySettings.
Download: Global_Patch_2.zip
Bugs:
Blue screen of death on Widows PC (try different mode connections); - turn-off "USB-debug"
Big thanks All authors who made Sphinx ROM!
Link available!
Awesome, awesome work. Can't wait to have official 4.1.2 on the P930!
miroslav_mm said:
Unofficial-Official JellyBean for P930/935/936
For JellyBean ROM for I-Project need 1Gb system size. So when you flash KDZ it will repart you eMMC.
Click to expand...
Click to collapse
Will this introduce any problems if switching between the already existing ICS, CMx ROMs other than needing the corresponding gapps lite from there on out?
I would be interested in your 3.4 kernel. Do you have the source on github?
I also be interested in his 3.4 kernel
tdmcode said:
I would be interested in your 3.4 kernel. Do you have the source on github?
Click to expand...
Click to collapse
tdmcode said:
I would be interested in your 3.4 kernel. Do you have the source on github?
Click to expand...
Click to collapse
Will available on my Github later.
Who install ROM please install patch_1.zip
If you delete strings from build.prop
ro.build.target_operator=SKT
ro.build.target_country=KR
you will see new settings for GSM and it remove T Roaming Settings.
miroslav_mm said:
Will available on my Github later.
Who install ROM please install patch_1.zip
If you delete strings from build.prop
ro.build.target_operator=SKT
ro.build.target_country=KR
you will see new settings for GSM and it remove T Roaming Settings.
Click to expand...
Click to collapse
Thanks for your work!
I have flashed this rom on my ATT P930，but Phone has been restarted and cant get into system.
so I restore to 20E.
Looking forward to your 3.4 kernel too!
navik said:
Thanks for your work!
Phone has been restarted and cant get into system.
so I restore to 20E.
Click to expand...
Click to collapse
Did you wipe your Phone via recovery? Its working without any problem.
miroslav_mm said:
Did you wipe your Phone via recovery? Its working without any problem.
Click to expand...
Click to collapse
Yeah no problems here. But I did install through CWM and not ROM manager. Out of habit I install new ROMs through CWM due to issues I have had with installing new ROMs through ROM manager.
Sent from my LG-P930 using xda app-developers app
miroslav_mm said:
Did you wipe your Phone via recovery? Its working without any problem.
Click to expand...
Click to collapse
Sure，I used recovery 5.82 and had wiped data ，wipe cache and wipe dalvik cache.
Thanks for reply and your work.
I will try again！
Sent from my LG-SU640 using xda premium
What are the advantages of the 3.4 kernel ? more compatible with JB 4.x.x ?
EDIT: Got the answer here for those interested: http://rootzwiki.com/topic/39958-what-is-the-value-of-the-linux-34-kernel/
Btw, great work.
just1nsama said:
What are the advantages of the 3.4 kernel ? more compatible with JB 4.x.x ?
Click to expand...
Click to collapse
Yes of course. Full ION support, better capability with CAF, JB-camera, full support Adreno (KGSL), bla-bla-bla....
miroslav_mm said:
Yes of course. Full ION support, better capability with CAF, JB-camera, full support Adreno (KGSL), bla-bla-bla....
Click to expand...
Click to collapse
Alight thanks ... i found more specifics here: http://rootzwiki.com/topic/39958-what-is-the-value-of-the-linux-34-kernel/
I see you created the repo on your github, but as of now it is empty, will you be adding the content in the near future ? Would really like to compile a PAC build with it and try it out
Thanks and keep up the good work :good:
Yeah that's all cool but the thing I am hoping to see is more stability. The 2.6.35 kernel was very stable. The 3.0.x kernel is not so stable.
tdmcode said:
Yeah that's all cool but the thing I am hoping to see is more stability. The 2.6.35 kernel was very stable. The 3.0.x kernel is not so stable.
Click to expand...
Click to collapse
Dont know about 2.6.35, but 3.0.x not stable because all using CM kernel for base. CM kernel base on CAF sources, not on LG original sources.
3.4 working very good for me. Battery life and performance on Stock 4.1 are great without any dirty tweaks and patches in kernel!
miroslav_mm said:
Dont know about 2.6.35, but 3.0.x not stable because all using CM kernel for base. CM kernel base on CAF sources, not on LG original sources.
3.4 working very good for me. Battery life and performance on Stock 4.1 are great without any dirty tweaks and patches in kernel!
Click to expand...
Click to collapse
CM took the lu6200 ICS sources and added display stuff from caf.
The original lge ICS ota was unstable for all iproj devices.
I have a weak p930 that will be the judge of the new 3.4 kernel. It reboots about every 5 to 15 minutes under the ics kernel. I will try when I get sources... No sources, no install...
Can't wait to flash this once WiFi is working
I don't have unlimited data and use WiFi a lot.
Flashed this ROM. It looks very good except WIFI issue. Am now testing battery drain. Looking for WiFi fix.
I've been checking this thread every
Hour for a WiFi fix... I use this as a WiFi only device so the lackthereof is a killer right now for me... That being said if anyone has a lead on what's breaking it I would love to help find a fix for the problem. Really never thought we would see a jb release for our device from LG but I believe it will be a major stepping stone for future development of our P93x's. Once again I wanna thank miroslav and all the other great devs and tinkerers who bust their asses to make our phones into beasts, and I look forward to seeing what awesomeness will come with these recent leaks.
Sent from my LG-P930 using xda app-developers app
Does anyone know what the Experimental kernel does?There are no informations about it in the OP of the Rom...I downloaded it but it appears to be for the Nexus 5...What is the difference between this kernel and the rom-kernel???
stathis_21 said:
Does anyone know what the Experimental kernel does?There are no informations about it in the OP of the Rom...I downloaded it but it appears to be for the Nexus 5...What is the difference between this kernel and the rom-kernel???
Click to expand...
Click to collapse
Who made the kernel?
After updating to the latest Mahdi rom and backing up what I had, I flashed the experimental kernel and wiped cache/dalvik.
It wouldn't boot, so I had to restore what I had.
No idea what it was supposed to do.
ruibing said:
After updating to the latest Mahdi rom and backing up what I had, I flashed the experimental kernel and wiped cache/dalvik.
It wouldn't boot, so I had to restore what I had.
No idea what it was supposed to do.
Click to expand...
Click to collapse
Yeah, if it said it was for the nexus, it wasn't going to work. Kernels should be device specific, and I am very skeptical of those that have been supposedly ported over, rather than compiled from the device's kernel source and then updated with new options.
Experimental in regards to kernel devevelopment means there are probably issues beyond the norm.
sleekmason said:
Yeah, if it said it was for the nexus, it wasn't going to work. Kernels should be device specific, and I am very skeptical of those that have been supposedly ported over, rather than compiled from the device's kernel source and then updated with new options.
Experimental in regards to kernel devevelopment means there are probably issues beyond the norm.
Click to expand...
Click to collapse
The filename is Mahdi-Hammerhead-exp-4.4.2-v1.7-23-03-2014.zip, but I thought that just meant it was somehow derived from the Nexus 5. Don't know why it would be posted in the Mahdi rom OP if it didn't have a chance of working.
To make myself clear.I said that nexus 5 thing, because the file of the kernel says hammerhead..But everything is fine..I use the rom as it is....I want to thank the dev for this amazing rom..A big thank you to all the devs..All of them have put a lot of work to their projects..I just made a question about this kernel.nothing else..Thanks for the reply..
stathis_21 said:
To make myself clear.I said that nexus 5 thing, because the file of the kernel says hammerhead..But everything is fine..I use the rom as it is....I want to thank the dev for this amazing rom..A big thank you to all the devs..All of them have put a lot of work to their projects..I just made a question about this kernel.nothing else..Thanks for the reply..
Click to expand...
Click to collapse
Mahdi has a good reputation for being dependable. Glad you found something you like!