Just to get passed the kernel issues for a while, couldn't the devs use the working Gingerbread kernel in the ICS build, or does ICS require the newer kernel?
Unfortunately it appears as though the Gingerbread kernel, even though it is working, is still too different from the kernels used on Ice Cream Sandwich. Hopefully someone can come up with a working one soon, but for now (especially 4.0 users) it seems we're a little stuck.
silentdoh said:
Unfortunately it appears as though the Gingerbread kernel, even though it is working, is still too different from the kernels used on Ice Cream Sandwich. Hopefully someone can come up with a working one soon, but for now (especially 4.0 users) it seems we're a little stuck.
Click to expand...
Click to collapse
I'm genuinely surprised that no one has figured out this issues with the 4.0 kernel, yet.
Yeah, I think we don't have anyone who has enough experience to really do it at the moment. Zaclimon has been trying, but I think he is stuck. Where did jackpotcalvin go, anyway? He got it working for the 5.0, we could sure use his help!
Sent using Tapatalk
iJimaniac said:
Yeah, I think we don't have anyone who has enough experience to really do it at the moment. Zaclimon has been trying, but I think he is stuck. Where did jackpotcalvin go, anyway? He got it working for the 5.0, we could sure use his help!
Sent using Tapatalk
Click to expand...
Click to collapse
I am asking help from stratosk (the semaphore kernel dev for the I9000). Maybe he can find out some problems and help me with it (however he don't own the device ). At least if tdm has left his source tree updated. We could get at least a boot even though only the wifi would worked
zaclimon said:
I am asking help from stratosk (the semaphore kernel dev for the I9000). Maybe he can find out some problems and help me with it (however he don't own the device ). At least if tdm has left his source tree updated. We could get at least a boot even though only the wifi would worked
Click to expand...
Click to collapse
If I'm correct the biggest issue(s) is the camera and bluetooth not working because of the kernel. Okay, is this because the kernel isn't seeing the hardware? Or is the kernel module not able to be loaded by the ICS kernel?
abtekk said:
If I'm correct the biggest issue(s) is the camera and bluetooth not working because of the kernel. Okay, is this because the kernel isn't seeing the hardware? Or is the kernel module not able to be loaded by the ICS kernel?
Click to expand...
Click to collapse
I don't know but I'm talking about the 4.0 as we don't have ICS ready yet
Related
Has anyone been able to port android 2.2 froyo to the hero, if so can you share the update.zip to flash
-------------------------------------
Sent via the XDA Tapatalk App
dom5079 said:
Has anyone been able to port android 2.2 froyo to the hero, if so can you share the update.zip to flash
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Umm. This will likely be a longer port than a day or so The N1 is a different resolution, and we need to get drivers sorted.
Maybe it will be done some time, but people are only just starting work on this
anon2122 said:
Umm. This will likely be a longer port than a day or so The N1 is a different resolution, and we need to get drivers sorted.
Maybe it will be done some time, but people are only just starting work on this
Click to expand...
Click to collapse
If you go in the CDMA Hero forum, you can see that there is yet a port of froyo. Sorry for my english
But are the drivers the same as the ones from 2.1 roms
-------------------------------------
Sent via the XDA Tapatalk App
and (correct me if wrong), but sources will eventually / soon hit the Android git's, and it's easier to build that stuff from source than trying to modify a ROM that's build for a way different device.
Not that it can't be done... but I think a lot of devs are still busy playing with kernels and optimized sense leaks, instead of trying hard to mod a Nexus-Froyo ROM, only to have sources available the moment you're done .
Froyo can run on the .29 kernel, so the drivers shouldn't be a problem.
dragossh said:
Froyo can run on the .29 kernel, so the drivers shouldn't be a problem.
Click to expand...
Click to collapse
Well get cracking then?.... No, no, I'm only playing.
Call me over-optimistic if you want, but when I see Pulser say
anon2122 said:
people are only just starting work on this
Click to expand...
Click to collapse
....what I actually hear is "I'm on it,... You'l have it soon".
No pressure bruv,......
I noticed that the community has not successfully made a Kernel thats works without doing a boot-loop. Could it be possible that there is E-Fusish type security measure, like the Droid 2 and X, that prevents users from loading custom kernels that Verizon implemented? Thats the only explanation I can think of why we are having issues with our Galaxy versus other carrier's versions.
Sent from my SCH-I500 using XDA App
Samsung gave us a BUNK defconfig
the bootloader's not locked, kernel isn't signed
I've got a working kernel that boots, but the accelerometer is screwed up
jt1134 said:
Samsung gave us a BUNK defconfig
the bootloader's not locked, kernel isn't signed
I've got a working kernel that boots, but the accelerometer is screwed up
Click to expand...
Click to collapse
Sorry for my next noobish question but has anybody sent an email to Samsung about getting a fixed source code or is it pointless until 2.2 drops?
Sent from my SCH-I500 using XDA App
pointless? I guess that depends on who you ask. But yes, Samsung has received much electronic mail from smartphone enthusiasts over the past few weeks.
jt1134 said:
pointless? I guess that depends on who you ask. But yes, Samsung has received much electronic mail from smartphone enthusiasts over the past few weeks.
Click to expand...
Click to collapse
I will talk to my Samsung rep to see if there is anybody I could escalate this to in their North America branch to get this fixed but highly unlikely thou.
Sent from my SCH-I500 using XDA App
@Jt
I will be back on irc tommorow, but I have the accelerometer fixed on my kernel just no wifi, bluetooth or sound still. Have you found a fix for any of these, or are you still using my config?
AFAICT everything works now. I started with your config as a base
jt1134 said:
AFAICT everything works now. I started with your config as a base
Click to expand...
Click to collapse
This is good news, no?
Very nice gang.. I will block off some time for sure to stop in and see what's shakin' this evening..
Dirrk.. what initramfs are you using? I was able to compile with yamaha_b5 and your ramdisk, then I got the no sound/orientation/etc.. However it seems when JT compiles, he uses koush's ramdisk, and gets sound (orientation still off).
If I compile with b5_yamah + koush ramdisk (from his git), Odin fails to flash every time. If I switch back to your ramdisk, odin flashes, kernel boots, etc..
Sounds like you guys are making some good progress. Thanks for your hard work. Can't wait to be able to overclock this sucker.
jt1134 said:
AFAICT everything works now. I started with your config as a base
Click to expand...
Click to collapse
Are you using a different ramdisk to get it fixed as mentioned below v
namebrandon said:
Very nice gang.. I will block off some time for sure to stop in and see what's shakin' this evening..
Dirrk.. what initramfs are you using? I was able to compile with yamaha_b5 and your ramdisk, then I got the no sound/orientation/etc.. However it seems when JT compiles, he uses koush's ramdisk, and gets sound (orientation still off).
If I compile with b5_yamah + koush ramdisk (from his git), Odin fails to flash every time. If I switch back to your ramdisk, odin flashes, kernel boots, etc..
Click to expand...
Click to collapse
Can you send me koush's ramdisk. I have been out of town working for the past few days
Dirrk said:
Can you send me koush's ramdisk. I have been out of town working for the past few days
Click to expand...
Click to collapse
Maybe JT or someone at a linux box can tar it up if you need it as an archive.. I don't have any git software here at work..
http://github.com/koush/fascinate_initramfs
namebrandon said:
Maybe JT or someone at a linux box can tar it up if you need it as an archive.. I don't have any git software here at work..
http://github.com/koush/fascinate_initramfs
Click to expand...
Click to collapse
Thanks man wow after rereading ur op it says its on koush's git lol
Quick question, i've gotten rom building down with CWM and Amon Ra but now I want to dabble in kernel modding but I want to get a general preference on where everybody started at.
Sent from my SCH-I500 using XDA App
This is a thread for USEFUL discussion about the logistics involved in reverting the Razr back to GB (please keep the discussion on topic). I know there are those out there that want it.
I am throwing 50 bucks into a pot to the Dev that first finds a way.
What I have gathered. With the release of kexec, we now have the ability to flash custom kernels to our Razrs. From what I understand, the thing preventing the reversion to GB is the change from the GB kernel to ICS kernel...
So in theory, we should be able to fllash the gingerbread kernel, then the stock GB rom and we should be good?
Thinkin out loud, is any of this sound feasible?
EDIT: Bounty withdrawn, seems impossible due to locked bootloader as well...
asuhoops8628 said:
This is a thread for USEFUL discussion about the logistics involved in reverting the Razr back to GB (please keep the discussion on topic). I know there are those out there that want it.
I am throwing 50 bucks into a pot to the Dev that first finds a way.
What I have gathered. With the release of kexec, we now have the ability to flash custom kernels to our Razrs. From what I understand, the thing preventing the reversion to GB is the change from the GB kernel to ICS kernel...
So in theory, we should be able to fllash the gingerbread kernel, then the stock GB rom and we should be good?
Thinkin out loud, is any of this sound feasible?
Click to expand...
Click to collapse
Hi!
This is a feature request. There's no development involved. You should post questions in QA section. Or make the same question in kexec thread.
Thank you!
sorry for the wrong spot.. i didnt want to hijack the kexec thread and move it off topic. I thought there would be development involved in getting a GB kernel ported to work with kexec.
maybe someone else with more knowledge can chime in. My bad if i am mistaken
Sorry, but for what i understand,
Kexec able us to load a custom kernel after boot and not flash a custom kernel.
so i think dev have to find an other way. But they have more stuff to do than finding a way to downgrad i guess
sevenup30 said:
Sorry, but for what i understand,
Kexec able us to load a custom kernel after boot and not flash a custom kernel.
so i think dev have to find an other way. But they have more stuff to do than finding a way to downgrad i guess
Click to expand...
Click to collapse
I agree. Many devs are focusing on stabilizing CM9 and working to bring us CM10, I dont think GB is on their agenda but maybe some dev is willing to do it.
sevenup30 said:
Sorry, but for what i understand,
Kexec able us to load a custom kernel after boot and not flash a custom kernel.
so i think dev have to find an other way. But they have more stuff to do than finding a way to downgrad i guess
Click to expand...
Click to collapse
Is anyone able to confirm this is actually how Kexec works? and along these lines, i mean why couldnt we just load the GB kernel like any other custom kernel?
romdroid. said:
I agree. Many devs are focusing on stabilizing CM9 and working to bring us CM10, I dont think GB is on their agenda but maybe some dev is willing to do it.
Click to expand...
Click to collapse
Yes i realize most are, thats why i was putting my money where my mouth was. ICS has been a disaster for me on 3 razrs i am currently back on my bionic. I was hoping it would be a fairly simple project since all i was thinking needed to be done was to update the existing moto GB kernel for Kexec, and make a flashable zip of the stock moto GB rom
but i :dunno: im not a dev by any means
asuhoops8628 said:
This is a thread for USEFUL discussion
Thinkin out loud, is any of this sound feasible?
Click to expand...
Click to collapse
Not Development. Moved to General
asuhoops8628 said:
Is anyone able to confirm this is actually how Kexec works? and along these lines, i mean why couldnt we just load the GB kernel like any other custom kernel?
Yes i realize most are, thats why i was putting my money where my mouth was. ICS has been a disaster for me on 3 razrs i am currently back on my bionic. I was hoping it would be a fairly simple project since all i was thinking needed to be done was to update the existing moto GB kernel for Kexec, and make a flashable zip of the stock moto GB rom
but i :dunno: im not a dev by any means
Click to expand...
Click to collapse
Yes, it will verify the signature of your stock kernel then at just the right time hijak the boot process and load the custom kernel. I'm not a dev so i can't say if it can be done or not, but i would imagine not.
Edit: meant to add i think the biggest problem is that the bootloader changed between gb and ics. So without am unlocked bootloader don't think its happening.
Sent from my DROID RAZR using xda app-developers app
kintwofan said:
Yes, it will verify the signature of your stock kernel then at just the right time hijak the boot process and load the custom kernel. I'm not a dev so i can't say if it can be done or not, but i would imagine not.
Edit: meant to add i think the biggest problem is that the bootloader changed between gb and ics. So without am unlocked bootloader don't think its happening.
Sent from my DROID RAZR using xda app-developers app
Click to expand...
Click to collapse
So basically, without being able to also revert my bootloader version, i am up the creek as they say.
Thanks for the info, definately an educational experience...
I ended up buying a new Razr Maxx off ebay that still has GB, now i just need to root and freeze the updater and im golden
torecdude said:
Hi,
I'm trying to extend my battery life. I read fast dormancy can extend my battery life significantly, but it depends on my device and mobile network provider.
Should i remove it? any one has tried it and can give me some feedback?
Thanks!
Click to expand...
Click to collapse
after update to 4.2.2 atrix heats too much.......... any solution?
Samdroid1991 said:
after update to 4.2.2 atrix heats too much.......... any solution?
Click to expand...
Click to collapse
Create your own thread. it is a compkletely different problem. also, it has been answered in cm10.1's thread. in the last few pages, i think @palmbeach05 has covered this and other issues.
As for OP: AFAIK, fastdormancy comes preinstalled, depends upon your carrier and it automatically start to work whenever it detects your carrier supports it. but in my experience, i got better results removing it than wit it enablesd maybe due to the alpha nature of the kernel
andresrivas said:
Create your own thread. it is a compkletely different problem. also, it has been answered in cm10.1's thread. in the last few pages, i think @palmbeach05 has covered this and other issues.
As for OP: AFAIK, fastdormancy comes preinstalled, depends upon your carrier and it automatically start to work whenever it detects your carrier supports it. but in my experience, i got better results removing it than wit it enablesd maybe due to the alpha nature of the kernel
Click to expand...
Click to collapse
can u get me a link for atrix 4g stable ics kernel???
Samdroid1991 said:
can u get me a link for atrix 4g stable ics kernel???
Click to expand...
Click to collapse
Reported (again)
Samdroid1991 said:
can u get me a link for atrix 4g stable ics kernel???
Click to expand...
Click to collapse
All kernels nowadays are 3.1.10. This is, has been, and will be until officially upgraded, an Alpha stage kernel. This means that there are major bugs present. Are there kernels out there that are stable enough at this stage? Yes. Most are within the individual ROM threads, others are in krystian's dropbox.
There are 2 versions of ICS that are popular amongst A4G users, AtrICS v 2.0 and CM9. Which one are you trying to use?
andresrivas said:
Create your own thread. it is a compkletely different problem. also, it has been answered in cm10.1's thread. in the last few pages, i think @palmbeach05 has covered this and other issues.
As for OP: AFAIK, fastdormancy comes preinstalled, depends upon your carrier and it automatically start to work whenever it detects your carrier supports it. but in my experience, i got better results removing it than wit it enablesd maybe due to the alpha nature of the kernel
Click to expand...
Click to collapse
Thanks for your reply, do you use epinter CM 10.1 too? do you think i should make a nandroid backup and try removing it?
torecdude said:
Thanks for your reply, do you use epinter CM 10.1 too? do you think i should make a nandroid backup and try removing it?
Click to expand...
Click to collapse
ALWAYS make a backup prior to any test modifications. That way if removing fastdormancy makes things worse for you, you have something to fall back on without having to go through the hassle of reflashing the entire ROM.
torecdude said:
Thanks for your reply, do you use epinter CM 10.1 too? do you think i should make a nandroid backup and try removing it?
Click to expand...
Click to collapse
I used it for a while, then I got back to AtrICS. As @palmbeach05 said, always do a nandroid backup before messing with anything system related.
palmbeach05 said:
All kernels nowadays are 3.1.10. This is, has been, and will be until officially upgraded, an Alpha stage kernel. This means that there are major bugs present. Are there kernels out there that are stable enough at this stage? Yes. Most are within the individual ROM threads, others are in krystian's dropbox.
There are 2 versions of ICS that are popular amongst A4G users, AtrICS v 2.0 and CM9. Which one are you trying to use?
Click to expand...
Click to collapse
im trying to use CM9 screen goes black after lock!!!!!!! n never comes back untill restart
i had same prblm with CM10.1 but i solved it using anothr kernel
can u suggest any kernel for CM9 ??
Samdroid1991 said:
im trying to use CM9 screen goes black after lock!!!!!!! n never comes back untill restart
i had same prblm with CM10.1 but i solved it using anothr kernel
can u suggest any kernel for CM9 ??
Click to expand...
Click to collapse
Sorry, wrong thread ^^
Try them all and see the one taht fits you better
Samdroid1991 said:
im trying to use CM9 screen goes black after lock!!!!!!! n never comes back untill restart
i had same prblm with CM10.1 but i solved it using anothr kernel
can u suggest any kernel for CM9 ??
Click to expand...
Click to collapse
Ok and you're experiencing a problem everyone has had or still has. Stop complaining or start developing a fix. Can't develop? Don't complain. Simple as that. Besides that, I mentioned it before, but I will reiterate the point again. THE 3.1.10 KERNEL IS AN ALPHA STAGE KERNEL. ALL ROMS RUNNING A 3.1.10 KERNEL BECOME ALPHA STAGE ROMS AS WELL. ALL LOWER REVISION KERNELS ON ANY 4.0 AND UP ROM WILL PROVIDE ISSUES AS WELL. This is pretty much a deal with what we, the devs of xda, can provide to you and other users, or move onto a new ROM or a new device.
Hey Guys,
After seeing what we were able to do with the AOSP Rom and SafeStrap, couldn't help but wonder if the same be done with Cyanogen? I know Cyanogen normally boots with AOSP style kernels, but if a Google Edition ROM can be booted... shouldn't Cyan be able to? Couldn't we use the GE/CM11 Edition in the Development Section, then remove the cyan kernel (so ours goes untouched, not tripping KNOX)?
I know that it would be feature barren due to kernel differences, but its still cyan
I'm wondering if that kind of magic could be used to port this ROM over?
http://forum.xda-developers.com/showthread.php?t=2643031
Ground Broken
I have begun working using a CM11 Base (4.4.4) and building around our kernel. It looks to be promising so far. But only time will tell
AngryManMLS said:
I'm wondering if that kind of magic could be used to port this ROM over?
http://forum.xda-developers.com/showthread.php?t=2643031
Click to expand...
Click to collapse
They already have AOSP SafeStrap... just read the instructions the guy that figured it out left on the ATT thread and use them to port that one
npjohnson said:
They already have AOSP SafeStrap... just read the instructions the guy that figured it out left on the ATT thread and use them to port that one
Click to expand...
Click to collapse
Alright so I just tried to do that. I got as far as the boot ani then it simply loops repeatedly and vibration keeps going off. I let it sit for 10 minutes I don't know if I am missing something or forgot something on the build I worked on. I can upload it to my AFH account if you want me to so you can see if I am missing something.
Also best of luck on the CM11 stuff. :good:
AngryManMLS said:
I'm wondering if that kind of magic could be used to port this ROM over?
http://forum.xda-developers.com/showthread.php?t=2643031
Click to expand...
Click to collapse
nothing, this ROM is MDK only. im pretty sure cm is the same way. i highly doubt we can get CM booting just by screwing with the kernel. i actually brought up the idea but.. it's probably not possible.
skepticmisfit said:
nothing, this ROM is MDK only. im pretty sure cm is the same way. i highly doubt we can get CM booting just by screwing with the kernel. i actually brought up the idea but.. it's probably not possible.
Click to expand...
Click to collapse
Actually, you are right, just screwing around with the kernel WILL NOT work, but building CM from source using the "build with stock kernel" option SHOULD work. If AOSP/GE will work, it should. Just ripping the Boot.mg out and replacing with ours will not work.
But I started work today and forked a lot of Github repos and have begun work on CM for SafeStrap. Time Will Tell
npjohnson said:
Actually, you are right, just screwing around with the kernel WILL NOT work, but building CM from source using the "build with stock kernel" option SHOULD work. If AOSP/GE will work, it should. Just ripping the Boot.mg out and replacing with ours will not work.
Click to expand...
Click to collapse
Yeah we do have a bit of the ground work with the AOSP/GE ROMs that mostly work on NC5 that could be used towards getting CM11 working. Now I don't know beyond that what it will take to get CM11 to work with the stock kernel but I would have to think that at least if it does get working then the issues we have right now on the AOSP/GE ROMs can be fixed since we'd have the ROM source/Github/etc to work from on this.
Well if anything, the at&t rom gives me hope for the future.. That ROM is a great daily driver. They even have WiFi tethering fixed (its a manual fix that requires putting commands into terminal emulator, its still a fix though)
Also for those who miss USB file transfer.. I've always found it to be way too slow for any practical purposes. Airdroid is way faster than USB mtp on touchwiz.