How long does it normally take HTC to release kernel source? Are they behind on this one or what? I'm dieing to take advantage of some of the early gingerbread stuff, some of the HD ports and of course some over-clocking and better battery life, but cant. Unless i want to lose my camera. It seems like these 0004 and late 0003 hardware revisions have been out for quite a while with no kernel source love. Come on HTC, I'm dieing over here!!!!
anybody know how long it normally takes?
nugzo said:
anybody know how long it normally takes?
Click to expand...
Click to collapse
I may stand corrected here, but I believe that the source tree for Htc#17 was released recently. I think I read something about it in the netarchy thread but don't quote me on it.
try the sbc no have 4.2.2 kernel. it works fine on a 004 evo.
I have a late 003 model with the new camera and don't have any camera problems when I try new stuff out. Have you actually TRIED flashing any of these things you want?
deathsled said:
I have a late 003 model with the new camera and don't have any camera problems when I try new stuff out. Have you actually TRIED flashing any of these things you want?
Click to expand...
Click to collapse
Try every day. Thats also why i made this thread and bumped it the next day, because i haven't actually tried any of the stuff i'm complaining about. I'm not talking about sense custom roms, they normally all work. My 0004 Camera doesnt work with the bundled kernel of any gingerbread rom, or any CM6 rom. Also it doesnt work with any of the NEW sense ports from the HD devices. I will try the 4.2.2 like suggested earlier, hopefully that'll do it.
fixxxer2008 said:
try the sbc no have 4.2.2 kernel. it works fine on a 004 evo.
Click to expand...
Click to collapse
Kernel works ok, the camera doesn't. I'm downloading another sense rom and will try 4.2.2 with it. I would have thought overclocking and camera would have been big news for 004 hardware. I've been on XDA everyday since i got my 0004 and haven't seen anything anywhere about custom kernel for 0004. PLEASE prove me wrong
Tried 2 more roms with the sbc 4.2.2 no havs, rom boots, but no camera. Can you please verify your comment? thanks so much
Have you tried flashing the stock kernel then flashing a universal kernel. (of course after reboot). Supposedly it copies your drivers from the previous kernel
Yellowcard8992 said:
I may stand corrected here, but I believe that the source tree for Htc#17 was released recently. I think I read something about it in the netarchy thread but don't quote me on it.
Click to expand...
Click to collapse
I couldnt find anything on that. I would have thought that would have been a big deal. That was the first kernel with HTC's 30fps fix, and source would explain how they did it.
dwertz said:
Have you tried flashing the stock kernel then flashing a universal kernel. (of course after reboot). Supposedly it copies your drivers from the previous kernel
Click to expand...
Click to collapse
Well a lot the roms i use have the stock kernel from the beginning, well atleast all the regular sense roms. Most of the devs have been using the 15 or 17 as their base kernel. so to answer the question, YES i have, twice today. Still no camera. Thanks for the suggestion.
nugzo said:
Well a lot the roms i use have the stock kernel from the beginning, well atleast all the regular sense roms. Most of the devs have been using the 15 or 17 as their base kernel. so to answer the question, YES i have, twice today. Still no camera. Thanks for the suggestion.
Click to expand...
Click to collapse
but the roms you have tried with the stock kernel is the kernel for hardware 004? I think they #15 is the one for 004 http://forum.xda-developers.com/showpost.php?p=9875223&postcount=2
HAve you tried Calkulins EViO http://forum.xda-developers.com/showthread.php?t=811695 It has the camera working for 004. They pushed some drivers that was needed for the camera. If you read the details in the post it shows which drivers were copied. I dont remember which post but probably 100 back from the end.
1) HTC is breaking the law by not immediately releasing the kernel source when the OTA hit production status. That's why the Gingerbread source came out right when the Nexus S, the first Gingerbread-running production device, went on sale.
2) Toastcfh has said that if HTC hasn't released the kernel source by then, he will work on getting the 004/late-003 camera drivers working as soon as he and Shinzul finish off WiMax for AOSP/CM.
dwertz said:
but the roms you have tried with the stock kernel is the kernel for hardware 004? I think they #15 is the one for 004 http://forum.xda-developers.com/showpost.php?p=9875223&postcount=2
HAve you tried Calkulins EViO http://forum.xda-developers.com/showthread.php?t=811695 It has the camera working for 004. They pushed some drivers that was needed for the camera. If you read the details in the post it shows which drivers were copied. I dont remember which post but probably 100 back from the end.
Click to expand...
Click to collapse
The camera will work with that particular HD rom. It is using the HTC #17 kernel which works 100% with 004. I'll see if i cant find what you were talking about in that thread though.
drmacinyasha said:
1) HTC is breaking the law by not immediately releasing the kernel source when the OTA hit production status. That's why the Gingerbread source came out right when the Nexus S, the first Gingerbread-running production device, went on sale.
2) Toastcfh has said that if HTC hasn't released the kernel source by then, he will work on getting the 004/late-003 camera drivers working as soon as he and Shinzul finish off WiMax for AOSP/CM.
Click to expand...
Click to collapse
I wonder why they are bein so stingy with the new Evo Kernels. You reckon it has something to do with the fps fix? I bet they used the same fix we were already using and are trying to keep a lid on it lol.
nugzo said:
I wonder why they are bein so stingy with the new Evo Kernels. You reckon it has something to do with the fps fix? I bet they used the same fix we were already using and are trying to keep a lid on it lol.
Click to expand...
Click to collapse
Nope, they actually used a different fix for that. They're just being flat-out douchebags. You can find more information here.
nugzo said:
The camera will work with that particular HD rom. It is using the HTC #17 kernel which works 100% with 004. I'll see if i cant find what you were talking about in that thread though.
Click to expand...
Click to collapse
Not sure if this will work http://forum.xda-developers.com/showpost.php?p=9572828&postcount=384
drmacinyasha said:
Nope, they actually used a different fix for that. They're just being flat-out douchebags. You can find more information here.
Click to expand...
Click to collapse
Interesting read, Thanks. So i guess the earlier poster with the supposed late 0003 that is working with everything isnt actually a new camera 0003.. Didnt think i missed the source on that one, its kind of a big deal! There will be a ton of new custom kernels when the source is released due to the excellent battery on the newer kernels. Not to mention the 0004 support.
nugzo said:
Interesting read, Thanks. So i guess the earlier poster with the supposed late 0003 that is working with everything isnt actually a new camera 0003.. Didnt think i missed the source on that one, its kind of a big deal! There will be a ton of new custom kernels when the source is released due to the excellent battery on the newer kernels. Not to mention the 0004 support.
Click to expand...
Click to collapse
Precisely. Some of the 003's, and most (but not all) of the 004's use the new camera, which had the drivers added in 3.30.651.3 (and .5). That's the kernel we really need, as it affects AOSP ROMs too, like CyanogenMod. Getting 3.70.651.1 is necessary too though for Sense users, to get like you said, the battery and speed improvements.
dwertz said:
Not sure if this will work http://forum.xda-developers.com/showpost.php?p=9572828&postcount=384
Click to expand...
Click to collapse
Thanks Dwertz for all of your effort. That post was basically to get cameras working on the HD ports with the stock kernel. Not really what i'm looking for, but again thanks. As you can see this thread has some more concrete info now and like i thought, we are still a nogo for custom kernels and 0004 hardware. We are approaching 120 days. It should happen any day now... My fingers are crossed
That and you gotta think that they might of released the source by now if they didn't run into the multiple OTA's recently. maybe they decided to hold off and just release the latest one instead of releasing back to back sources when one would be obsolete.
Related
I'm getting a replacement evo on tuesday, I currently have a launch date evo with hardware 002 so im not quite up to date with the latest evos.. Now assuming it comes hardware 004 what would be the best method to root??? Also does it work with cm6 I read something about camera issues.. And last but not least does it work with kernels such as netarchy's with everything working??
Thanks for answering my questions really appreciate it, if there is anything else I should know about the newer evos please feel free to school me on them.
Sent From My Htc Evo!!!
jayv1717 said:
I'm getting a replacement evo on tuesday, I currently have a launch date evo with hardware 002 so im not quite up to date with the latest evos.. Now assuming it comes hardware 004 what would be the best method to root??? Also does it work with cm6 I read something about camera issues.. And last but not least does it work with kernels such as netarchy's with everything working??
Thanks for answering my questions really appreciate it, if there is anything else I should know about the newer evos please feel free to school me on them.
Sent From My Htc Evo!!!
Click to expand...
Click to collapse
If I'm correct, I DO think it's possible to root. However, the new Camera hardware will not work with CM6
Greenfieldan said:
If I'm correct, I DO think it's possible to root. However, the new Camera hardware will not work with CM6
Click to expand...
Click to collapse
That my friend is horrible news!
Sent From My Htc Evo!!!
jayv1717 said:
That my friend is horrible news!
Sent From My Htc Evo!!!
Click to expand...
Click to collapse
You know what IS good news though? The CM team knows about the issue and is working on it. And they tend to work pretty quickly
Greenfieldan said:
You know what IS good news though? The CM team knows about the issue and is working on it. And they tend to work pretty quickly
Click to expand...
Click to collapse
lol is there somewhere specific that you heard that from?.. Although im sure it'll get fixed
Sent From My Htc Evo!!!
jayv1717 said:
lol is there somewhere specific that you heard that from?.. Although im sure it'll get fixed
Sent From My Htc Evo!!!
Click to expand...
Click to collapse
Nothing other than they know about it...and they're working on it
The 004 (and some 003s) have a new camera which uses different drivers, and since HTC is breaking the law by not releasing the kernel source ("yet") the CM team has to build up the drivers from scratch. Toastcfh has told me that he will start working on the camera as soon as he finishes polishing up WiMax.
As for rooting, it's possible. 2.02 and 2.10 hboot have both been rooted, they just take some effort, and do not panic. Also, knowing how to BS to a Sprint store rep in case you brick your phone is a good idea, just in case.
drmacinyasha said:
The 004 (and some 003s) have a new camera which uses different drivers, and since HTC is breaking the law by not releasing the kernel source ("yet") the CM team has to build up the drivers from scratch. Toastcfh has told me that he will start working on the camera as soon as he finishes polishing up WiMax.
As for rooting, it's possible. 2.02 and 2.10 hboot have both been rooted, they just take some effort, and do not panic. Also, knowing how to BS to a Sprint store rep in case you brick your phone is a good idea, just in case.
Click to expand...
Click to collapse
Does that mean no kernels work? For sense roms other then stock htc kernels
Sent From My Htc Evo!!!
Only the 3.30.651.3-or-later based kernels will work with the 004/new003 camera at this time. Period.
drmacinyasha said:
Only the 3.30.651.3-or-later based kernels will work with the 004/new003 camera at this time. Period.
Click to expand...
Click to collapse
Does that include netarchy's kernels?
Sent From My Htc Evo!!!
I have tried every kernel I can find and so far none of them work for me with the 004 hardware. I am currently looking for the stock #15 kernel if anyone has a link!!
I really wouldn't worry about it... All the refurb EVOs I'm seeing coming out of the warehouse are either 002 or early 003s. The 004s are too new as of right now.
I have a 002 Evo from launch day. It's started missing calls. Like no missed call notification, nothing in my call log. I'm afraid all I can do is swap it out under TEP. If anyone has any suggestions other than replacing it, let me know! Of course I've rebooted my phone. I know most of you will be jealous...but I have my choice of hardware versions for my replacement phone. (One of the techs in my Sprint store is also my friend.)
Those of you that have 004s, are you happy with your camera, and the ROMs you can run where your camera works? I'm rooted and currently running Fresh 3.5.0.1, but want to play around with Shinzul's 4g CM, Miui, a gb ROM, and maybe an HD or Z ROM. I have run Miui, as well as CM in the past. Should I ask for a 002, or will I be able to use a 004 with the camera working?
Also, suggestions for backing up and restoring to the new hardware phone would be appreciated. I'm thinking of nandroiding and removing the wimax.img before restoring. Will that be ok on new hardware, with new H-boot and all? I have H-boot .76, running the 11.19 radio (have tried going back to the original, no better), the original wimax radio, and PRI 1.34_003. Fresh 3.5.0.1 is based on the latest OTA 3.70.651.1.
Thanks for any advice. I did try to search, but since my questions are pretty hardware specific, it was difficult to get relevant hits.
Happy with 0004... but I'm rooted with stock ROM.
Sent from my PC36100 using XDA App
I know most of you will be jealous...but I have my choice of hardware versions for my replacement phone. (One of the techs in my Sprint store is also my friend.)
Click to expand...
Click to collapse
I'm not so sure about this. To sprint, an Evo is an Evo. I dont think the techs can "choose" what version to order.
And honestly, I've had a version 2, 3, and 4, and all of them have been exactly the same. Even with the camera change with the 04, I cant tell the difference at all.
I'd go with 003, no question. You have more kernels to choose from.
_MetalHead_ said:
I'd go with 003, no question. You have more kernels to choose from.
Click to expand...
Click to collapse
Even with some of the 003s having the newer camera? Thanks for your help.
I didn't even think about that. I guess it's a crap shoot. I wouldn't go with 002 for the sole reason that they are older (I'm weird like that) and if you go with 004 you are guaranteed to get a phone that is not compatible with every kernel out there. If you go with 003 at least there is a chance of getting a normal one and not a later one with the new camera.
_MetalHead_ said:
I didn't even think about that. I guess it's a crap shoot. I wouldn't go with 002 for the sole reason that they are older (I'm weird like that) and if you go with 004 you are guaranteed to get a phone that is not compatible with every kernel out there. If you go with 003 at least there is a chance of getting a normal one and not a later one with the new camera.
Click to expand...
Click to collapse
Good point.
smarcin said:
Good point.
Click to expand...
Click to collapse
+1 don't go for a four. Still some problems with custom kernels like others said.
I've got a hardware v3 with the new camera. I've run the newest Fresh rom, myns, caulks, cm 6.1, Cm7, and evervolv. As far as kernels, I've played with most all of them. I haven't experienced any issues, camera or otherwise after HTC released source for 15. I'm pleased with the performance out of it, as far as smoothness and quickness goes.
*edit* I came from a launchday v2, got this one under TEP, new not refurb.
Sent from my PC36100 using XDA App
_MetalHead_ said:
I didn't even think about that. I guess it's a crap shoot. I wouldn't go with 002 for the sole reason that they are older (I'm weird like that) and if you go with 004 you are guaranteed to get a phone that is not compatible with every kernel out there. If you go with 003 at least there is a chance of getting a normal one and not a later one with the new camera.
Click to expand...
Click to collapse
Ive got an 003. What are the benefits to the 004 camera over the 003? Thank you
tailsthecat3 said:
Ive got an 003. What are the benefits to the 004 camera over the 003? Thank you
Click to expand...
Click to collapse
I don't think there are any benefits at all. It's just different, not any better or worse.
Thanks....
Kinda funny no one even mentions which screens anymore. Remember that whole argument? Novatech vs. Epson?
vinscuzzy said:
Kinda funny no one even mentions which screens anymore. Remember that whole argument? Novatech vs. Epson?
Click to expand...
Click to collapse
Yeah, the Epsons suck and I got stuck with one
it's not a matter of what you go with, it's a matter of what they give you. you dont really have a choice unless you buy one used
I have the 0004 HW and I don't know what all the fuss is about. I haven't really had any trouble getting a kernal I want that works with this HW. If it is a Sense rom, run a Netarchy Kernal, they all support 0004 anymore, and if it is an AOSP rom, run Savaged.Zen kernal. They support 0004. I am running CM7+4G with a savaged.zen kernal, (I KNOW I AM SUPPOSED TO RUN THAT KERNAL THEY SAY I HAVE TOO, BUT YA KNOW WHAT? THE SAVAGED.ZEN KERNAL WORKS BETTER, AND 4G WORKS!!!!)
I would have said 2 months ago when I got an evo, that the 0004 HW was crappy as noone supported it, main reason I kept to Fresh. But now, most kernals I like support it, and except when they had CM6.1.2+4G, I haven't had a rom not work with the camera.
I think you just get what you get. I got a replacement last week, its an 003. ##786# tells me it was activated in july and refurbed last month.
Has there been any announcement of the official OTA gingerbread for the incredible? I'm coming from the fascinate, so I'm not used to any support, but I heard HTC is really good about updating their phones.
I understand there is a gingerbread rom out, but I think I'm done flashing ROM's on my phones. They seems to cause more problems than they're worth.
Thanks.
As of now, no GB for us. We just have to wait to see what the future has in store.
Sent from God, who uses CM7 RC1.
brian85 said:
Has there been any announcement of the official OTA gingerbread for the incredible? I'm coming from the fascinate, so I'm not used to any support, but I heard HTC is really good about updating their phones.
I understand there is a gingerbread rom out, but I think I'm done flashing ROM's on my phones. They seems to cause more problems than they're worth.
Thanks.
Click to expand...
Click to collapse
No announcement.
But in terms of flashing roms causing trouble?
Not sure how it really can. Directions are easy enough to follow, and nandroid backups are really the only thing that you need to keep in mind.
And cm7 has been pretty good so far, stable, good battery life, etc.
No trouble at all for me.
brian85 said:
Has there been any announcement of the official OTA gingerbread for the incredible? I'm coming from the fascinate, so I'm not used to any support, but I heard HTC is really good about updating their phones.
I understand there is a gingerbread rom out, but I think I'm done flashing ROM's on my phones. They seems to cause more problems than they're worth.
Thanks.
Click to expand...
Click to collapse
Almost all of the roms I have played with on my phone are very stable. I have been running Incredibly re-engineered for about 10 to 14 days with no resets or forced closes. Im constantly adding in apps or changing themes and what not. If you want GB pick a rom and go for it.
Well to be honest there is no polished GB ROM.
If you're the type to look for a one-time update, I'd wait a few more weeks.
As for ROM's causing problems.. I've been using SR 3.5 with chad's incredikernel for a couple of months with no problems at all. Battery life is so much better than stock and it runs faster too.
All up to you though, it does take some research to get through all the steps. As long as you take precautions like backing up (takes maybe 2 minutes), the risk is little to none.
brian85 said:
Has there been any announcement of the official OTA gingerbread for the incredible? I'm coming from the fascinate, so I'm not used to any support, but I heard HTC is really good about updating their phones.
I understand there is a gingerbread rom out, but I think I'm done flashing ROM's on my phones. They seems to cause more problems than they're worth.
Thanks.
Click to expand...
Click to collapse
If your looking for gingerbread this is the most stable and supported build out. http://t3hh4xx0r.com/?page_id=1151
Enjoy!
Almost forgot about OMFGB.
They were kicked off this forum for some reason, not sure why.
Have u tryed the latest build
POQbum said:
Almost forgot about OMFGB.
They were kicked off this forum for some reason, not sure why.
Click to expand...
Click to collapse
HTC Incredible OMFGB 2.3.2
jaysckap said:
If your looking for gingerbread this is the most stable and supported build out. Can't post link I am a bottom feeder and post count is important!!!
Enjoy!
Click to expand...
Click to collapse
The file size seems kind of small compared to other roms 68.4 mb.
Rick_V said:
The file size seems kind of small compared to other roms 68.4 mb.
Click to expand...
Click to collapse
Yup it is. From the changelog:
"Nightly Build 2/ 6 |1 .1 .1 | Extremely optimized, resulting in 60+MB being cut!"
Sent from my ADR6300 using XDA App
POQbum said:
Almost forgot about OMFGB.
They were kicked off this forum for some reason, not sure why.
Click to expand...
Click to collapse
Just to answer the question and not start another endless debate... the dev was axed initially for allegedly including warez in a ROM and/or allegedly not crediting the work of others that he used. The subsequent bans were for his creating new accounts to circumvent the original ban. The last time, he undid himself.
.
BrettApple said:
Yup it is. From the changelog:
"Nightly Build 2/ 6 |1 .1 .1 | Extremely optimized, resulting in 60+MB being cut!"
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Thanks I will give it a try.
POQbum said:
Well to be honest there is no polished GB ROM.
As for ROM's causing problems.. I've been using SR 3.5 with chad's incredikernel for a couple of months with no problems at all. Battery life is so much better than stock and it runs faster too.
Click to expand...
Click to collapse
+1
10 char
I installed it seems pretty good. Got a few questions though I am a relative newbie when it comes to this stuff. There was a GAPPS.zip file with it how do I install that? There is no market and I think that the GAPPS fixes that. It has a meta-inf folder and a system folder inside the zip. Also there is a little Android dude that is looked on the home screen that has little comments is there some way to remove that? Thanks in advance.
Rick
Rick_V said:
I installed it seems pretty good. Got a few questions though I am a relative newbie when it comes to this stuff. There was a GAPPS.zip file with it how do I install that? There is no market and I think that the GAPPS fixes that. It has a meta-inf folder and a system folder inside the zip. Also there is a little Android dude that is looked on the home screen that has little comments is there some way to remove that? Thanks in advance.
Rick
Click to expand...
Click to collapse
Boot to recovery and select install zip from sd card.
Thanks I wasn't sure. Worked perfectly I have see posts talking about meta and having to install them with another program. I am liking this ROM a lot.
Cm7 has been good to me so far.
Sent from my ADR6300 using XDA App
OMFGB fo lyfe.
OMFGB is the best ROM I've used. It's close to stock and really fast. I use the newest incredikernel, and it's amazing.
I really like the OMFGB and would like to try it with incredikernel. I have never flashed a kernel. I have a question if I back up my existing OMFGB and decide to go back to it will it have the existing kernel or the new one I flashed? I would guess that since the default kernel was part of the original install it would revert back to that I just want make sure. Also to flash the new kernel I go into recovery,wipe cache,dalvik-cache and then just install the kernel from the sd card zip.
Now that we have S-off (thanks alpharev donations def on the way) and we are working at getting a recovery wouldnt it be possible to port incredible-s roms, since they are almost the exact same phone? Different radios and a few other things? Im not a dev, just wondering if anyone is considering that. Since there are a ton of roms out already for the Inc-S.
Incredible S has official support of CM (no release yet that I'm aware of, haven't checked in a couple days). I don't see why this can't be extended to the I2.
nimdae said:
Incredible S has official support of CM (no release yet that I'm aware of, haven't checked in a couple days). I don't see why this can't be extended to the I2.
Click to expand...
Click to collapse
I miss CM7. I had a G2 that I rooted (painstaking root process by hand and terminal emulator) and that was such a great stable rom. I tried a few others MIUI, Mexidroid... ect. All in all CM7 was the best. I would be so happy if they support it. Although I do have to say, im really starting to get used to Sense. Its a really nice interface. If I had to have one, ide take this of stupid motoblur or touchwiz anyday.
I stopped using Sense in lieu of LauncherPro some time ago as that was the environment I was use to while using CM7. Can't wait to get back to CM7 so the bloat is gone and I get the unleash the full potential of my I2.
I would love to see MIUI, I had it on my original INC and I love it. Weekly updates and it seems like they just keep improving it. Very fast and stable. Long way from where it started.
I recently sold my inc and now I'm stuck with a palm pre plus. I was going to hold out for the droid 3 or bionic but if the inc 2 gets cm support I will have a hard time not buying one.
nfcrockett said:
I recently sold my inc and now I'm stuck with a palm pre plus. I was going to hold out for the droid 3 or bionic but if the inc 2 gets cm support I will have a hard time not buying one.
Click to expand...
Click to collapse
We already have a couple CM devs expressing interest.
nfcrockett said:
I recently sold my inc and now I'm stuck with a palm pre plus. I was going to hold out for the droid 3 or bionic but if the inc 2 gets cm support I will have a hard time not buying one.
Click to expand...
Click to collapse
wtf a Palm Pre Plus?!?!?! id rather have a blackberry lol.
na all jokes aside..come back to the Incredible side of the device world, you will not be let down.
haha I'm glad someone feels me, I lucked out and have been using my buddy's inc but he ended up selling it so as I type I'm activating the pre *sad face*
xgunther said:
We already have a couple CM devs expressing interest.
Click to expand...
Click to collapse
That makes me happy in my pants.
To answer the OP's question. Yes. Incredible S --> Incredible 2 ports will be disgustingly easy.
As a matter of fact, we should be able to make a universal 'patcher' that you can flash after any incredible S rom to make it 100% dinc2 compatible. No porting necessary.
1- Flash Incredible S rom
2- Flash patcher script
3- Done city
deficitism said:
To answer the OP's question. Yes. Incredible S --> Incredible 2 ports will be disgustingly easy.
As a matter of fact, we should be able to make a universal 'patcher' that you can flash after any incredible S rom to make it 100% dinc2 compatible. No porting necessary.
1- Flash Incredible S rom
2- Flash patcher script
3- Done city
Click to expand...
Click to collapse
Well that would be Incredible (no pun intented)
It's possible it could be that simple. However, I suspect we will need a different kernel and different driver set. I believe our radio hardware is slightly different (I could be wrong on this), as well as filesystem layout.
Of course, we can't know this for sure until the work actually starts. I suspect it'll be easy to port over, but not THAT easy, unfortunately. Considering AlphaRev is using only a slightly modified hboot from the IS for the I2, it very well could be that easy
nimdae said:
It's possible it could be that simple. However, I suspect we will need a different kernel and different driver set. I believe our radio hardware is slightly different (I could be wrong on this), as well as filesystem layout.
Of course, we can't know this for sure until the work actually starts. I suspect it'll be easy to port over, but not THAT easy, unfortunately. Considering AlphaRev is using only a slightly modified hboot from the IS for the I2, it very well could be that easy
Click to expand...
Click to collapse
i would imagine your right. the radios are gonna be different on account of the incS being GSM and the inc2 being CDMA. hopefully it is easy though, and hopefully it comes soon.
deficitism said:
To answer the OP's question. Yes. Incredible S --> Incredible 2 ports will be disgustingly easy.
As a matter of fact, we should be able to make a universal 'patcher' that you can flash after any incredible S rom to make it 100% dinc2 compatible. No porting necessary.
1- Flash Incredible S rom
2- Flash patcher script
3- Done city
Click to expand...
Click to collapse
I disagree on how easy that will be, you will need a different RIL (and associated files, including phone.apk and settings.apk most likely) along with a different kernel.
jcase said:
I disagree on how easy that will be, you will need a different RIL (and associated files, including phone.apk and settings.apk most likely) along with a different kernel.
Click to expand...
Click to collapse
Everything you mentioned can be done with just a few lines in a patcher. I've done it before. It's not rocket science. And when its done, it can be universally applied to all roms between the two devices. Even a tiny bit of logic to determine source vs sense. (otherwise resulting in two patchers)
deficitism said:
Everything you mentioned can be done with just a few lines in a patcher. I've done it before. It's not rocket science. And when its done, it can be universally applied to all roms between the two devices. Even a tiny bit of logic to determine source vs sense. (otherwise resulting in two patchers)
Click to expand...
Click to collapse
I would be very interested in seeing this done in a few lines. I am fully aware of the possibility of doing it, I just don't see it happening easily and in a few lines.
I'm not arguing or bashing, I would just like to see it. Please link me to your previous incarnation of such a patcher
jcase said:
I would be very interested in seeing this done in a few lines. I am fully aware of the possibility of doing it, I just don't see it happening easily and in a few lines.
I'm not arguing or bashing, I would just like to see it. Please link me to your previous incarnation of such a patcher
Click to expand...
Click to collapse
You are getting bashy. And you are clearly trying to belittle my statements by requesting direct links to my work, in order to disprove something you know damn well is possible. We have been doing between the desire/evo/inc/n1/etc for a long time now. Even kiddie kitchens have a button to 'port' a rom.
Regardless of how many 'lines' a script would be, flashing would be dead simple by the end user. And yes, creating it should be very easy on my end.
My d**k is bigger than yours!
Sent from my ADR6350 using XDA App
deficitism said:
You are getting bashy. And you are clearly trying to belittle my statements by requesting direct links to my work, in order to disprove something you know damn well is possible. We have been doing between the desire/evo/inc/n1/etc for a long time now. Even kiddie kitchens have a button to 'port' a rom.
Regardless of how many 'lines' a script would be, flashing would be dead simple by the end user. And yes, creating it should be very easy on my end.
Click to expand...
Click to collapse
Lol ok dude whatever, I made it clear I simply wanted to see it. I'm not a ./autohack dev, so I am unfamiliar with what those kinds of devs are doing, hence me asking to see. Nothing more or less than simple curiosity.
You getting all defensive/pissed over such a simple request, is pretty darn funny. Will have to screen shot this one.
I've had my Epic Touch 4g for about 3 weeks now and I have noticed something outside the normal LoS threads I've seen lately. I only seem to get LoS when I flash kernels, mainly ones with CWM 4 or 5 or ones that are rooted.
The issue clears up as soon as I flash the stock EG30 rom. It's the same deal with either EG12 or EG30 modem.bin.
Not really looking for answers, I can wait a few weeks for you guys to work your magic. I just wanted to set a precedent with my own experiences.
Sent from my SPH-D710 using XDA App
I better hurry and comment before this one gets locked.
I've owned the phone for a little more then 2 weeks. I have had a total of 4 LOS events. 3 with a Zedomax kernel(all in the same day) and once with the latest lost kernel experimental. For the last week the lost kernel stable has had none. Can't comment on unrooted los because my phone was only stock for 15mins after unboxing.
haha yea my phone lasted 15 minutes as well from my boys house to mine..lol @OP I am not sure how much reading you do on here but I hear a whole lot of stories of people who get LOS and there phone has been untouched. I have a friend who has had the phone for a month or so and has only had 3 LOS but all from the same tower(phone rooted).
Don't try and figure it out, sit back and wait for an answer, return your phone if you like or sell it but unless you are a developer or know about phone software and you have a solution. I personally think we should refrain from making statements we are not 100% sure about. IMHO
NoT trying to be disrespectful but its a pretty touch subject in here and honestly you are like the millionth person to say the same thing in a new thread....lol
playya said:
haha yea my phone lasted 15 minutes as well from my boys house to mine..lol @OP I am not sure how much reading you do on here but I hear a whole lot of stories of people who get LOS and there phone has been untouched. I have a friend who has had the phone for a month or so and has only had 3 LOS but all from the same tower(phone rooted).
Don't try and figure it out, sit back and wait for an answer, return your phone if you like or sell it but unless you are a developer or know about phone software and you have a solution. I personally think we should refrain from making statements we are not 100% sure about. IMHO
NoT trying to be disrespectful but its a pretty touch subject in here and honestly you are like the millionth person to say the same thing in a new thread....lol
Click to expand...
Click to collapse
+1
10 char
alex6969 said:
Not really looking for answers, I can wait a few weeks for you guys to work your magic. I just wanted to set a precedent with my own experiences.
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
As far as "here's my proof with evidence in anecdotal form" is concerned, that precedent has already been set.
The facts are this:
1.) Untouched stock units have had LOS (mine included).
2.) Samsung seems to have released incomplete source. What is missing (whether it is in the source or in tool-chain/build parameters) is unknown.
3.) Kernels built from said source seem to exacerbate the problem
4.) You can have root AND the stock (pulled) kernel.
5.) Root binaries and/or busybox do not cause LOS.
6.) rooted+stock kernel installs seem to have the same occurance of LOS as bone stock, uninformed alarmist anecdotes notwithstanding.
7.) This has been covered in over 9000 threads already. Please search in the future.
8.) Samsung and Sprint are aware of the issue (in stock phones) and are issuing inconvenience credits if pressed and are supposedly working on a firmware to fix the issue.
Please pass this information on to the next student of science who presents his "proof" of this "discovery", as there will likely be more.
Now how do you like them apples ......my boys wicked smart .....
Good will hunting
But seriously please search and find the previous 50 threads that say the same uninformed thing ... If it was only a root thing would Samsung be fixing it ..... Hell no
Sent from my SPH-D710 using xda premium
I have had my phone since launch day and have only had LOS one time when it tried to go into roaming and never got back a signal. That was shortly after I rooted with a stock kernal. I have not had LOS since but I have never flashed a custom kernal or ROM. The phone has been mostly trouble free.
Where did you find the EG30 modem bin?
Ditto. WTF SamSprint?
daneurysm said:
2.) Samsung seems to have released incomplete source. What is missing (whether it is in the source or in tool-chain/build parameters) is unknown.
Click to expand...
Click to collapse
I looked into this more late last week. The kernel source is complete. I'm not certain that it's unmodified, but I'm no longer certain it's modified either. The majority of the difference between EG30 and source-built kernels is a bunch of debugging options that Samsung left enabled in the kernel defconfig--options that alter the core behavior of the kernel enough to plausibly exacerbate a code bug.
daneurysm said:
3.) Kernels built from said source seem to exacerbate the problem
Click to expand...
Click to collapse
I posted a source-built kernel that's as close to stock EG30 as possible, but I've not gotten any feedback on it. Does someone dare to try?
mkasick said:
I looked into this more late last week. The kernel source is complete. I'm not certain that it's unmodified, but I'm no longer certain it's modified either. The majority of the difference between EG30 and source-built kernels is a bunch of debugging options that Samsung left enabled in the kernel defconfig--options that alter the core behavior of the kernel enough to plausibly exacerbate a code bug.
I posted a source-built kernel that's as close to stock EG30 as possible, but I've not gotten any feedback on it. Does someone dare to try?
Click to expand...
Click to collapse
Thanks for the informative post.
I've been on Starburst+LoSTkernel for almost a week now with no problems. Before that I was strictly a pulled-stock kinda guy given my experiences. But I'll give that a shot and let you know. I get very infrequent LoS with stock kernel, though they do happen once every 2-3 weeks...usually a few times that one day. So, in a few days of very routine use (location/tower/times always the same, to a tee) I'll have a pretty good idea, assuming randomness doesn't factor into it as much as it could.
mkasick said:
I looked into this more late last week. The kernel source is complete. I'm not certain that it's unmodified, but I'm no longer certain it's modified either. The majority of the difference between EG30 and source-built kernels is a bunch of debugging options that Samsung left enabled in the kernel defconfig--options that alter the core behavior of the kernel enough to plausibly exacerbate a code bug.
I posted a source-built kernel that's as close to stock EG30 as possible, but I've not gotten any feedback on it. Does someone dare to try?
Click to expand...
Click to collapse
I've been using it since I posted my last reply last night. No more LOS than stock so far...and typically with the Samsung-source compiled kernels I've used I would have seen at least one by now.
I do get reboots after I get some texts, but, every other kernel (even stock) was doing this...I think it's the ROM...so, don't even worry about that. Later I'll nandroid back to my original stock install and flash this kernel on top and report back.
daneurysm said:
I've been using it since I posted my last reply last night. No more LOS than stock so far...and typically with the Samsung-source compiled kernels I've used I would have seen at least one by now.
Click to expand...
Click to collapse
That's good news.
My goal with that kernel is to just be stock, so if it's indistinguishable from stock behaivor wise, that's a good thing.
LoStKernel may have made much of the source-based problems irrelevant. But perhaps the defconfig changes may still prove useful.
mkasick said:
That's good news.
My goal with that kernel is to just be stock, so if it's indistinguishable from stock behaivor wise, that's a good thing.
LoStKernel may have made much of the source-based problems irrelevant. But perhaps the defconfig changes may still prove useful.
Click to expand...
Click to collapse
Just to keep moral up I want to specify that "no more LOS than stock" means "stock rarely gets LOS and so far I have gotten absolutely none."
Good work man, thanks for the effort.