Related
Hey with this new kernel that has been really impressive to me
I want to work with any Devs out there to bring this kernel to them for testing
I think a lot of people would really like it since it has choices for CFS/BFS RHack/NoRHack
So, if any devs want to work with me on bringing this any build - email me
[email protected]
Hopefully, I want to create a kernel for everyone to use - I know CM's has been more popular for its features - but this one has the features plus a really good speed
I would really like to work with any Eclair Devs to improve the speed of this before I make my Eclair ROM (sooner or later - may need a break first for life lol)
I was really behind on this working on the kernel way too much - so 2wks behind
wesgarner said:
Hey with this new kernel that has been really impressive to me
I want to work with any Devs out there to bring this kernel to them for testing
I think a lot of people would really like it since it has choices for CFS/BFS RHack/NoRHack
So, if any devs want to work with me on bringing this any build - email me
[email protected]
Hopefully, I want to create a kernel for everyone to use - I know CM's has been more popular for its features - but this one has the features plus a really good speed
I would really like to work with any Eclair Devs to improve the speed of this before I make my Eclair ROM (sooner or later - may need a break first for life lol)
I was really behind on this working on the kernel way too much - so 2wks behind
Click to expand...
Click to collapse
are you saying that it has the same features as the CM kernel, but it's faster?
prince.siraj said:
are you saying that it has the same features as the CM kernel, but it's faster?
Click to expand...
Click to collapse
That's what it looks like.
Need this in a Hero ROM
Would love this for SuperD.....
hey i just tried out your kernel on eclair. i used your kernel from 2.6 cfs w/ ram hack on my custom speed demon build of eclair using manups ramdisk and i am unable to pass splash screen. prolly needs more implementation of eclair goodies
What files did you "transplant" to use the kernel on another build?
u must unpack the boot.img's then replace kernel
Hero_Over said:
u must unpack the boot.img's then replace kernel
Click to expand...
Click to collapse
THanks, Im gonna do some experimenting on a 1.6 build later
Anyone else trying this kernel on Eclair other then Herver?
I'm waiting to switch to Eclair until a fast/responsive kernel is implemented.
Tried BFS/RAMHACK with Manup's Eclair ROM, kernel loaded properly, ran quickly, only issue was that bluetooth didn't work.
My issue with all these different kernels out there, is that I'd like to see source code accessible, or at the very least, maybe attach the .config file, so I know what exactly has been changed.
Ok lol who wants for what ROM?
You have to grab a few things from it - such as the rootdir plus setup xbin if it doesn't use it
hi wes.
i would certainly like to help the cause and assist in improving upon things (where possible and if feasable), but i would really need to see the source and .config to make advancements.
is this available on your github?
you're handing these out pre-built? Do you have somewhere we could download the source?
Figured I'd test it, and figured it wouldn't work...
The kernel (CFS + ram hack) doesn't work as a direct drop-in on dwang.
wesgarner said:
Ok lol who wants for what ROM?
Click to expand...
Click to collapse
You should do one for hero/espresso.
wesgarner said:
Ok lol who wants for what ROM?
You have to grab a few things from it - such as the rootdir plus setup xbin if it doesn't use it
Click to expand...
Click to collapse
If you wanna help me, then
g'day Wes,
like the rest - I am curious to know if it possible to see the source and the .config? Is there anyway you could make this available? thanks in advance mate...
peace..
bump for update dammit. Donut is still ALive!
R3N0V4D0 said:
bump for update dammit. Donut is still ALive!
Click to expand...
Click to collapse
No it isn't, go back to sleep and don't be bumping ancient threads.
Guys,I want port this rom: http://forum.xda-developers.com/showthread.php?t=1763514. Is there a guide for do this? Thanks in advance!
Sent from my nexus s using xda app
Spidergio said:
Guys,I want port this rom: http://forum.xda-developers.com/showthread.php?t=1763514. Is there a guide for do this? Thanks in advance!
Sent from my nexus s using xda app
Click to expand...
Click to collapse
The OP in that thread says:
4. No ports based on my ROM zip file, manifest.xml will be updated regularly and feel free to compile from source
Start elsewhere, unless you want to learn to compile. Come back with a ROM you're allowed to port and post it here. Then we'll help you
same
trying to port a rom also still working on it
Porting can be easy or hard depending on many factors.
First of all, if the rom type the you are porting (AOSP, Sense, AOKP, CM7/9/10, Touchwiz, Motoblur, etc.) already has similarly typed ROMs for your device your life will be much easier as you will have a base to work with.
The general idea for an easy port is to use the boot.img, keylayout, modules, and many libs from a similar ROM that already exists for your device. Also, the build.prop and updater-script will need edited (updater-script for most, but not all, ROMs).
If you are on an HTC device and you go grab a Touchwiz ROM to port, you're most likely going to have a bad time. Start with something that exists in large quantities for your device. AOSP ROMs are usually a great place to start.
estallings15 said:
Porting can be easy or hard depending on many factors.
First of all, if the rom type the you are porting (AOSP, Sense, AOKP, CM7/9/10, Touchwiz, Motoblur, etc.) already has similarly typed ROMs for your device your life will be much easier as you will have a base to work with.
The general idea for an easy port is to use the boot.img, keylayout, modules, and many libs from a similar ROM that already exists for your device. Also, the build.prop and updater-script will need edited (updater-script for most, but not all, ROMs).
If you are on an HTC device and you go grab a Touchwiz ROM to port, you're most likely going to have a bad time. Start with something that exists in large quantities for your device. AOSP ROMs are usually a great place to start.
Click to expand...
Click to collapse
I am on a nexus s and now i want TO port the touchwiz5. Can anyone help me? I am a student! I'm inexperienced, but I want to try.. Thanks .
Sent from my nexus s using xda app
Perfect Android is a redistribution of the Android Open Source Project and Google software code that I have lightly modified to make as a daily driver for myself that I'm sharing with the community. This project doesn't have and won't focus on adding a ton of features and mods but instead focus on stability, and reliability so yes basically this is a stock like rom but not just stock my only efforts will be to make it run better, and be more polished, and complete.
GOOGLE APPS ARE INCLUDED
DOWNLOAD:
https://hotfile.com/dl/181925379/d84644d/perfect_grouper_ota_2012-12-01.zip.html
Mirrors:
If you have an error or something pops up I ask that before you post about it please make sure that you are running the ROM as provided. I cannot troubleshoot anything that is related to using other kernels, mods, or themes.
This ROM is basically like a stock rom of jelly bean so there is not a need for screen shots ........
Always remember that XDA started out as a great place and will remain a great place as long as we are great to each other anything used in this ROM is available upon request and feel free to use this as a base rom for any other project my ROM is un-branded just give me some mention .......
WANT TO CUSTOMIZE THIS ROM READ THIS:
Like the ROM and want to add or remove anything or customize for yourself use this http://forum.xda-developers.com/showthread.php?t=633246 DSIXDA's Kitchen. Its a great kitchen for customizing prebuilt ROMs
CREDITS:
CyanogenMod Team
Google - I used their apps
AOSP - of course
Probably gonna add a changelog here
AOSP 4.2 ROM so quickly? That will be interesting
Can you have some screenshots?
yep its uploaded
it looks just like stock I built it to be at least as good as what you get from google if everything is working correctly that is when I will begin modifying but for now it looks like the stock ROM so I didn't think screenshots would be needed
first of all you have to give us changelog, then i'll flash it, because now i don't know exactly what are the differences between Your rom and stock, so is it worth flash it?
Patroy said:
first of all you have to give us changelog, then i'll flash it, because now i don't know exactly what are the differences between Your rom and stock, so is it worth flash it?
Click to expand...
Click to collapse
Its solely up to you guys if you want to flash it as this is an expensive hobby for me I'm just sharing what I do with the community so is it worth it, for me yeah, for you I really don't care, I hope I'm not coming off as an ass but I have to draw a line somewhere. I not making any claims with this ROM I just sharing it if you use it fine if not fine, I don't get into the whole screenshots large claims huge changelog thing I just post and share I also maintain this ROM for the Sprint Galaxy Nexus which it has done just fine so if you want you can do a search here and see what and where I come from .......
I'm very happy when see any new rom in N7 development, because nexus need fresh look from developers, so i was thinking that You could push some new tweaks into ours devices. Almost all roms here are just "cleaned" or "minimalistic" or "performanced" in real these rom are almost stock with the same user experience. So do not get angry when I want to know if there will be something more here...
Does it work with twrp?
After flash with twrp, I see the information is Android 4.2 JOP40C. I dont know whether it is flashed or not?
I will happily try your rom to see how it compares to CleanRom, give my feedback tomorrow
Patroy said:
I'm very happy when see any new rom in N7 development, because nexus need fresh look from developers, so i was thinking that You could push some new tweaks into ours devices. Almost all roms here are just "cleaned" or "minimalistic" or "performanced" in real these rom are almost stock with the same user experience. So do not get angry when I want to know if there will be something more here...
Click to expand...
Click to collapse
I'm not getting angry with you in fact I agree however, regardless of how you feel about those roms someone still put that effort into them. Honestly for me the N7 is a new device and before I go making claims that my ROM can start your car and end world hunger I want to make sure that it at least meets stock standards. AOSP has done a lot of work to somewhat remove google entries in their code so it has taken me a few days to re-build AOSP code to work correctly with G-APPS and other Google code I do NOT claim to be an over the top developer I just do this as a pastime I have certain things that I do not like and thats why I have started making my own ROMs so that I always get what I want. Now I can tell you this and I know this as a fact THIS IS NOT A WINZIP KITCHEN ROM IT IS BUILT FROM SOURCE it took hella work to get it up to a win zip ROM and thats where we're at so far lol. When I learn all the changes to the 4.2 coding I will start to add small feature to my ROM.
SuperBoUDS said:
Does it work with twrp?
After flash with twrp, I see the information is Android 4.2 JOP40C. I dont know whether it is flashed or not?
Click to expand...
Click to collapse
yes it works with TWRP and the information in the About screen is correct
There isn't developer section in setting menu. Is this normal?
SuperBoUDS said:
There isn't developer section in setting menu. Is this normal?
Click to expand...
Click to collapse
Tap on the build in settings>about phone 7 times and it appears.
Paul
Sent from my Nexus 7 using xda app-developers app
PAULO76 said:
Tap on the build in settings>about phone 7 times and it appears.
Paul
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thank you! I dont know this.
This ROM doesn't include busybox. I think jakdillard should install busybox by default .
Testing this ROM with LeanKernel.
SuperBoUDS said:
Thank you! I dont know this.
This ROM doesn't include busybox. I think jakdillard should install busybox by default .
Testing this ROM with LeanKernel.
Click to expand...
Click to collapse
lol who knows I might depends on how things go with this
Installed thid yesterday and so far no problems, nice deep sleep of 96%. Nice work
With leanKernel, I just have 86% batterry overnight :crying:. I charged it fully the night before.
SuperBoUDS said:
With leanKernel, I just have 86% batterry overnight :crying:. I charged it fully the night before.
Click to expand...
Click to collapse
haven't checked for myself but is leankernel updated for 4.2
this is just a demo of a kernel based on quarx 3.0.8 kernel sources,maybe later i'll try to merge several fixes or something but till then lets say i've reached a small milestone like finishing to compile this kernel,booting it up,take some screenshots from it.
known bugs,just like initial quarxs or blenchose commits.
Warning:flash at your own responsability,works only with cm 10.1 under boot options by ticking 2ndboot and ticking adb disable
link to kernel:http://www.mediafire.com/?vdjoj438tlvz2lw
NOTE:kernel sources are based on quarx repo on github:https://github.com/Quarx2k/jordan-kernel
What's this? A fix for CM10.1 23/01?
I think it's a 3.0 kernel... so not a fix.
i think , quarx2k also made many changes with his CM 10.1-3.0 branch which corresponds to the 3.0 kernel ..( eg - hwcomposer sources)
so it will be better if u can compile and upload both ROM + KERNEL package in order to have maximum working efficiency
Shubhamqweasd said:
i think , quarx2k also made many changes with his CM 10.1-3.0 branch which corresponds to the 3.0 kernel ..( eg - hwcomposer sources)
so it will be better if u can compile and upload both ROM + KERNEL package in order to have maximum working efficiency
Click to expand...
Click to collapse
you're right,because i could not boot this kernel on 4.1.2 so tried with 4.2.1 without adb manual boot,the difference is that i added forced module unloading and allow old eabi binaries to run with this kernel trying to get some backwards compatibility thus my conclusion is that either this kernel needs scratch bins in the os for propper functioning
rodrigoswz said:
What's this? A fix for CM10.1 23/01?
Click to expand...
Click to collapse
nope,my bad to mention that is an kernel build on quarx repo
You know opening a new thread was unnecessary as we already have a 3.0 kernel thread and CM10.1 also.... BTW the kernel and CM10.1 are both easily compiled if you know what you're doing
Let's Go ^_^
Kayant said:
You know opening a new thread was unnecessary as we already have a 3.0 kernel thread and CM10.1 also.... BTW the kernel and CM10.1 are both easily compiled if you know what you're doing
Let's Go ^_^
Click to expand...
Click to collapse
The thread is already reported
Sent from my MB526 using xda premium
nogoodusername said:
The thread is already reported
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
thank you for your support nogood username,that helps alot and to what i can do for this comunity,for example my own kernel sources for linux kernel 3.7.5,as of this post was just an test to see if it works and 3.7.5 yup it likes the cpcap drivers and firmware,just some gpu issues to display under menuconfig
drunk_ryder24 said:
thank you for your support nogood username,that helps alot and to what i can do for this comunity,for example my own kernel sources for linux kernel 3.7.5,as of this post was just an test to see if it works and 3.7.5 yup it likes the cpcap drivers and firmware,just some gpu issues to display under menuconfig
Click to expand...
Click to collapse
I appreciate your work, and I'm not the one that reported (as far as I remember)
Sent from my MB526 using xda premium
nogoodusername said:
I appreciate your work, and I'm not the one that reported (as far as I remember)
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
maybe i started wrong but my intention was to give some help for the comunity,as for my attempt on kernel 3.7.5:bump cant port sgx drivers,got cpcap to show up in menuconfig even mapphone but its like impossible to show up,tried a workaround with similar devices to get the gpu drivers but no chance
drunk_ryder24 said:
maybe i started wrong but my intention was to give some help for the comunity,as for my attempt on kernel 3.7.5:bump cant port sgx drivers,got cpcap to show up in menuconfig even mapphone but its like impossible to show up,tried a workaround with similar devices to get the gpu drivers but no chance
Click to expand...
Click to collapse
Thanks for your efforts I think I was the one that reported it can't remember now ..... The reason I did it was because like you said you're trying to port 3.7.5 which we already have thread for where you cab discuss about porting 3.0.0 kernels
Some advice and questions......
I was wondering why are you trying to port 3.7.5 which is not even on any other android device yet??
IMO I think a higher version of the 3.0 base kernel is not needed as am sure most of the new things in it would not benefit us as we probably couldn't use it anyway since we have old drivers, old cpu/gpu etc.....
Getting it to show up in defconfig is not the hard part you can activate anything you want from there they are just the configuring files the hard part is configuring the activated drivers for the defy which requires dev work and debugging just look Quark's commits
I think what we have is fine and I don't think anything much higher would be any benefit for us also we have older drivers and the things we need for 4.2 to work properly are in 3.0.8 like the new wifi drivers maybe Quarx will update it to a higher minor version later like he did with 2.6.32.9 to 2.6.32.60......
Don't worry yourself to much there are many other things you can do to help us in the defy community. This is not worth your time trust me from experience :cyclops:
Btw the menuconfig iust activates the stuff you want for your device and mapphone_defconfig is where all the options you picked from menuconfig is stored. Each defconfig is different as they are specify to one device.
Kayant said:
Thanks for your efforts I think I was the one that reported it can't remember now ..... The reason I did it was because like you said you're trying to port 3.7.5 which we already have thread for where you cab discuss about porting 3.0.0 kernels
Some advice and questions......
I was wondering why are you trying to port 3.7.5 which is not even on any other android device yet??
IMO I think a higher version of the 3.0 base kernel is not needed as am sure most of the new things in it would not benefit us as we probably couldn't use it anyway since we have old drivers, old cpu/gpu etc.....
Getting it to show up in defconfig is not the hard part you can activate anything you want from there they are just the configuring files the hard part is configuring the activated drivers for the defy which requires dev work and debugging just look Quark's commits
I think what we have is fine and I don't think anything much higher would be any benefit for us also we have older drivers and the things we need for 4.2 to work properly are in 3.0.8 like the new wifi drivers maybe Quarx will update it to a higher minor version later like he did with 2.6.32.9 to 2.6.32.60......
Don't worry yourself to much there are many other things you can do to help us in the defy community. This is not worth your time trust me from experience :cyclops:
Btw the menuconfig iust activates the stuff you want for your device and mapphone_defconfig is where all the options you picked from menuconfig is stored. Each defconfig is different as they are specify to one device.
Click to expand...
Click to collapse
thats the whole point,everithing gets trouc the cross compiler even battery and every hw aspect for defy,but cant seem to get sgx drivers on it it boots but only backlight flickers,also the importance of this is that one day we might bump in a problem like this(maybe future android versions will use kernel 3.7.5 as default)and my opinion is that we should have some widen experience about it in any way possible
Kayant said:
Thanks for your efforts I think I was the one that reported it can't remember now ..... The reason I did it was because like you said you're trying to port 3.7.5 which we already have thread for where you cab discuss about porting 3.0.0 kernels
Some advice and questions......
I was wondering why are you trying to port 3.7.5 which is not even on any other android device yet??
IMO I think a higher version of the 3.0 base kernel is not needed as am sure most of the new things in it would not benefit us as we probably couldn't use it anyway since we have old drivers, old cpu/gpu etc.....
Getting it to show up in defconfig is not the hard part you can activate anything you want from there they are just the configuring files the hard part is configuring the activated drivers for the defy which requires dev work and debugging just look Quark's commits
I think what we have is fine and I don't think anything much higher would be any benefit for us also we have older drivers and the things we need for 4.2 to work properly are in 3.0.8 like the new wifi drivers maybe Quarx will update it to a higher minor version later like he did with 2.6.32.9 to 2.6.32.60......
Don't worry yourself to much there are many other things you can do to help us in the defy community. This is not worth your time trust me from experience :cyclops:
Btw the menuconfig iust activates the stuff you want for your device and mapphone_defconfig is where all the options you picked from menuconfig is stored. Each defconfig is different as they are specify to one device.
Click to expand...
Click to collapse
and how is that a problem if someone wants to attempt a higher version kernel?
if there is no benefit then there is no loss either
I understand your point and even I know nothing is impossible.
BUT, there has to be a logic in things that you are doing, isn't it? Believe me, Nobody is discouraging him. Anyways, its a matter of understanding and not a debate.
FYI and to my knowledge, very few devices like xperia T/V has kernel 3.4
abhifx said:
and how is that a problem if someone wants to attempt a higher version kernel?
if there is no benefit then there is no loss either
Click to expand...
Click to collapse
Like brajesh.sharma87 said am not trying to discourage him anything am just giving him some advice. This is mainly just my opinion based on experiences I had trying to port the newer wifi drivers from 3.0 base to our 2.6 kernel..... he doesn't have to listen to what am saying.
Like brajesh.sharma87 said it's matter of knowledge because the Linux kernel changes so much between versions and the work Quarx has done on the 3.0.8 base may become outdated and needs to be changed to get it to work for the new base.
Am just trying to put things into prospective as I think it's not worth his time and effort trying to port a higher version kernel without good knowledge and experience on kernel porting. Again that's for him to decide.
Drunk_ryder24 if you still want to try here are is something you can do that may help -
If you haven't already tried this but try cherry-picking Quarx's commits from the p-android-omap3-3.0 branch since the code is related to the defy but keep in mind not all of Quarx's work may work on the new base.
Kayant said:
Like brajesh.sharma87 said am not trying to discourage him anything am just giving him some advice. This is mainly just my opinion based on experiences I had trying to port the newer wifi drivers from 3.0 base to our 2.6 kernel..... he doesn't have to listen to what am saying.
Like brajesh.sharma87 said it's matter of knowledge because the Linux kernel changes so much between versions and the work Quarx has done on the 3.0.8 base may become outdated and needs to be changed to get it to work for the new base.
Am just trying to put things into prospective as I think it's not worth his time and effort trying to port a higher version kernel without good knowledge and experience on kernel porting. Again that's for him to decide.
Drunk_ryder24 if you still want to try here are is something you can do that may help -
If you haven't already tried this but try cherry-picking Quarx's commits from the p-android-omap3-3.0 branch since the code is related to the defy but keep in mind not all of Quarx's work may work on the new base.
Click to expand...
Click to collapse
well ive done cherry picking from quarx repo and i must say that quarx done an excelent job compiling the modules since they are recognized and compiled by the toolchain with no major errors,just a few ignorable errors,boy quarx must have nerves of steel to bare so much time in developing from scratch,oh btw i will post this as a reply in 4.1.2 tread,ive mixed kernel zimage and ramdisk of quarx 2.6.32.60 after applying sevenrock's kernel 2.6.32.9-the whole point is that it might have been something changed in either ril or wifi module cause 2.6.32.60 seems just a little laggy but no ringtone bug or reboots by this method
drunk_ryder24 said:
well ive done cherry picking from quarx repo and i must say that quarx done an excelent job compiling the modules since they are recognized and compiled by the toolchain with no major errors,just a few ignorable errors,boy quarx must have nerves of steel to bare so much time in developing from scratch,oh btw i will post this as a reply in 4.1.2 tread,ive mixed kernel zimage and ramdisk of quarx 2.6.32.60 after applying sevenrock's kernel 2.6.32.9-the whole point is that it might have been something changed in either ril or wifi module cause 2.6.32.60 seems just a little laggy but no ringtone bug or reboots by this method
Click to expand...
Click to collapse
That sounds good am I bit surprised it worked so well with not that much errors but thats's good Yh I know Quarx is unstoppable and good luck with the project ..... If you need any more advice or help just shoot me up with a pm and I will see what I can do
kayant said:
that sounds good am i bit surprised it worked so well with not that much errors but thats's good yh i know quarx is unstoppable and good luck with the project :d..... If you need any more advice or help just shoot me up with a pm and i will see what i can do
Click to expand...
Click to collapse
thanks for your support,its wellcomed
Okay last couple of questions, than I need a break :fingers-crossed:
1-Once I "Flash" a ROM, do I need to keep the .ZIP file on my phone assuming I have backed up my current ROM. They don't take up a ton of room but I don't like keeping a ton of stuff on my phone. It is nice to have it case I don't have the backup.
2-There are hundreds of different ROMS out there.....
I currently have ViperXL which seems awesome....
Some ROMS seem really stripped down.....
IS that what it comes down to in ROMS....Asthetics? The look and feel?
3-Now that I have a rooted phone....that I can update constantly (Jellybean etc) how far will this current model go (2 more major updates....Keylime etc)
Thanks for all of the help along the way!!!
Once you flash you can delete the zip
Everyone has their personal opinions about Rom you could love viper but someone could not like it and prefer hatka/clean Rom or cm
If we don't get the key lime pie kernel for the one xl it'd be heard porting HTC roms over due to lack of kernel but aosp will probably do well... We can portsense 5 here
a box of kittens said:
Once you flash you can delete the zip
If we don't get the key lime pie kernel for the one xl it'd be heard porting HTC roms over due to lack of kernel but aosp will probably do well... We can portsense 5 here
Click to expand...
Click to collapse
Hmmm.Newbie here!!!
Does that mean there will be an easy fix for Key Lime Pie? A ROM will most likely be developed?
I hear a lot of talk about Kernels but that seems too much for me to grasp....:laugh:
I was under the impression that once I rooted my phone, I could always flash a ROM to keep it current with the most up to date version of Android.
Is that not the case?
demert858 said:
Hmmm.Newbie here!!!
Does that mean there will be an easy fix for Key Lime Pie? A ROM will most likely be developed?
I hear a lot of talk about Kernels but that seems too much for me to grasp....:laugh:
I was under the impression that once I rooted my phone, I could always flash a ROM to keep it current with the most up to date version of Android.
Is that not the case?
Click to expand...
Click to collapse
Without kernel source that's a bit hard to do sometimes and HTC doesn't have the best reputation
a box of kittens said:
Once you flash you can delete the zip
Everyone has their personal opinions about Rom you could love viper but someone could not like it and prefer hatka/clean Rom or cm
If we don't get the key lime pie kernel for the one xl it'd be heard porting HTC roms over due to lack of kernel but aosp will probably do well... We can portsense 5 here
Click to expand...
Click to collapse
a box of kittens said:
Without kernel source that's a bit hard to do sometimes and HTC doesn't have the best reputation
Click to expand...
Click to collapse
So HTC will need to release the "Kernel" (Some Source Code) I assume.....
From there, People will Develop ROMS based on that.......?
Without that is this phone is dead in the water as far as updates are concerned?
Just think of this...the kernel contains all the proper WiFi libs and camera libs and a lot of other things...without the proper kernel wed have to hack things which can take a while and produce worse results...the Rom is not based off kernel it's based off the Rom... Than they build from their if it's aosp they build from source and port over if it's sense they do the base and build off that
a box of kittens said:
Just think of this...the kernel contains all the proper WiFi libs and camera libs and a lot of other things...without the proper kernel wed have to hack things which can take a while and produce worse results...the Rom is not based off kernel it's based off the Rom... Than they build from their if it's aosp they build from source and port over if it's sense they do the base and build off that
Click to expand...
Click to collapse
Got it.....
but what is Aosp??
Hopefully the fine folks on this forum will work their magic for complete noobs like me....I would hate to not keep up with the times :fingers-crossed:
It was a headache for me just to get it rooted and ViperXL installed =)
We will get aosp keylime roms for sure. We have an awesome dev community. We probably won't get a keylime sense Rom because HTC most likely won't develop one for this phone. But aosp (android open source project) which is the os written by Google for their nexus devices that the oems take and make their own version (sense, touchwiz, etc) should always get updated
Sent from my VENOMized HoxL
area51avenger said:
We will get aosp keylime roms for sure. We have an awesome dev community. We probably won't get a keylime sense Rom because HTC most likely won't develop one for this phone. But aosp (android open source project) which is the os written by Google for their nexus devices that the oems take and make their own version (sense, touchwiz, etc) should always get updated
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
That's awesome news....
I'm not a fan of HTC Sense.....
I opted out of it with the VIPERXL Rom....
Glad to hear my HTC One X will stay current for some time.....
I hate buying a new phone every other year to stay current with Software etc!!!
My HTC desire which the last official Rom was gingerbread, is running jb 4.2.2 dont worry xda makes phones future proof
Sent from my VENOMized HoxL
1) You can just delete it. I usually save on my computer for a while, just in case I want to move it back on the phone to re-flash, in emergencies, etc. I usually try to have either (but not both) a nandroid or the ROM zip on the phone, just in case.
2) The differences are aesthetics, features, performance. The thread for each specific ROM will usually have a good description of the features. But you may need to learn some more of the lingo, before you really understand what they are talking about. Start looking through the threads, and you will start to figure out what the differences are, which ones you may like, what others like, etc. Then just choose a few, and flash away.
3) Completely depends on how long the device keeps developer interest, and whether HTC actively supports the device and (as mentioned) releases kernel source for the device for the given Android build.
For example, if HTC decides not to release KLP for the device, and doesn't release kernel source, it makes it really difficult for devs to make custom ROMs with all the hardware components working properly (cameras, Bluetooth, etc.). But its not impossible, and if some devs are still inspired, they may try to make things work as much as they have time for.