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.
I have finally, successfully, gotten jt1134's device tree and Froyo framework all configured for the Mesmerize. This is a Vanilla Froyo (no Cyanogenmod) build and works enough to play around with (= But, I should warn you, this isn't a terribly stable build, so don't freak out if something acts weird d= Also, I'm not responsible for any harm you may do to your devices..
It's late and I have an 8:00 am tomorrow so I haven't tested everything out yet, but what is working and not working should be similar to what jt1134 has listed over in his Fascinate thread. Here's what I've tried though:
Working:
Phone
SMS
GPS
WiFi
Not Working:
Data?
Bluetooth
Camera
sdcard?
Oh, and it may randomly 'boot loop' a few times.. don't freak out though.
For this to work you need to be using the Mesmerize Froyo kernel I recently posted. To get everything setup just download the ROM and the Kernel and put them on your sdcard. Boot into recovery and make a backup. Wipe your data and cache partition. Flash the ROM. Flash the Kernel. Reboot. Froyo! If you're going to try to adopt this ROM for everyday use (good luck), make sure you grab the GApps package and flash that last.
I haven't got a Mesmerize device tree on github yet, but you can find the alterations to the kernel up. Really, you should look at jt's source/github because that's where all the dirty work is done (= Also, some of his work is under ModADroid on github.
Download Links:
Mesmerize Vanilla Froyo ROM: http://dl.dropbox.com/u/464066/Mesmerize/ROMs/froyo_mesmerize_0122.zip
Mesmerize Froyo Voodoo Kernel: http://dl.dropbox.com/u/464066/Mesmerize/Kernels/0123_mesmerize_voodoo5.zip
I'll post a link to a nonvoodoo kernel when I get one compiled.
Froyo GApps: http://goo-inside.me/google-apps/gapps-hdpi-20101114-signed.zip
Be careful!! This kernel is named the same as jt's Voodoo Sound 2.1 Kernel that he released yesterday. You may want to rename one of the two if you plan on using both. The ROM will bootloop or freeze at the lockscreen if you mistakenly use a 2.1 kernel (=
Source:
http://github.com/jt1134
http://github.com/dcow
Credits:
jt1134 <-- for all the SCH-I500 framework work
punk-kaos <-- for his contributions to the SCH-I500 framework
phidelt82 <-- for keeping me company late at night (not like that.. ..) and for letting me bounce ideas off of him, calling me out when I'm being stupid, and flashing whatever I throw at him (=
Enjoy!
Let me be the first! Thank you so much this should hold me over until official release comes out.. Maybe even then lol, thanks again.
Sent from my SCH-I500 using XDA App
cpfeifer said:
Let me be the first! Thank you so much this should hold me over until official release comes out.. Maybe even then lol, thanks again.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Perhaps if we get a to a final release or beta then. I don't think you'll be wanting to employ this for everyday use until we get more issues fixed.
cpfeifer said:
Let me be the first! Thank you so much this should hold me over until official release comes out.. Maybe even then lol, thanks again.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
dcow90 said:
Perhaps if we get a to a final release or beta then. I don't think you'll be wanting to employ this for everyday use until we get more issues fixed.
Click to expand...
Click to collapse
It was definitely fun to play with, but yeah, as for everyday use, there is still work to do. Hopefully soon though. I know I'll be digging in some more tonight to see if I can find anything fixes.
be glad to help test things once you get a little bit more stable with this.
Sent from my SCH-I500 using Tapatalk
phidelt82 said:
It was definitely fun to play with, but yeah, as for everyday use, there is still work to do. Hopefully soon though. I know I'll be digging in some more tonight to see if I can find anything fixes.
Click to expand...
Click to collapse
The sdcard issue is just a problem with the init.rc I think.. but we'll see whats still not working after I get jt's latest source built and we can work from there.
Sent from my USCC SCH-I500..
dcow90 said:
The sdcard issue is just a problem with the init.rc I think.. but we'll see whats still not working after I get jt's latest source built and we can work from there.
Sent from my USCC SCH-I500..
Click to expand...
Click to collapse
I think it has to do with the mounting. It looked the same as the other init.rc's that I was looking at, but it was all running together at that point last night. I'll dig into it some more tonight and look at the mounting of the base init file and see what I can come up with. Hopefully something will jump out.
Dont pull bin/vold from a prebuilt image, make sure you're building the aosp version. Also, make sure you are pulling prebuilt/vold.fstab from my device repo.
Android uses the vold daemon and fstab files to manage sdcard mounts, not a simple mount command like the ones used in init.rc for other partitions.
Sent from my SCH-I500 using XDA App
Thank you guys for all the hard work!
Looking forward to trying this out! Just to be sure- when I'm done playing I can go straight back to the exact way I have it now as long as I have a nandroid backup? No harm done?
sent from my superclean mesmerize
co6alt said:
Looking forward to trying this out! Just to be sure- when I'm done playing I can go straight back to the exact way I have it now as long as I have a nandroid backup? No harm done?
sent from my superclean mesmerize
Click to expand...
Click to collapse
No, you also need to revert to a 2.1 kernel as well. I mean 2.1 will boot on this kernel, but I can't say that it will work perfectly, and I found my scdard still didn't after a restore until I reverted kernels.
So restoring doesn't change the kernels, just the rom?
sent from my superclean mesmerize
co6alt said:
So restoring doesn't change the kernels, just the rom?
sent from my superclean mesmerize
Click to expand...
Click to collapse
What you should do is download jt1134's Mesmerize Voodoo5 w/ Voodoo Sound kernel and flash it. You should then take a backup in perfect working order. If you want to play with 2.2, wipe, flash the rom, then kernel. When you're done, wipe, restore the backup, then flash the previous kernel.
Gotcha. Ha, I just found out about voodoo sound. That'll be tonights project, then 2.2 tomorrow hate this edge network junk
sent from my superclean mesmerize
co6alt said:
Gotcha. Ha, I just found out about voodoo sound. That'll be tonights project, then 2.2 tomorrow hate this edge network junk
sent from my superclean mesmerize
Click to expand...
Click to collapse
EDGE? AT&T.. What?
I've got the source downloading for jt's latest build so hopefully we'll have some improvements soon. (=
dcow90 said:
EDGE? AT&T.. What?
I've got the source downloading for jt's latest build so hopefully we'll have some improvements soon. (=
Click to expand...
Click to collapse
Sweet waiting for a few more things to be functioning before I try using it. Thought maybe about trying to tomorrow but only as a test.
Edit: I just flashes the ROM and Kernel last night 0 problems booting and starting up phone was basically functioning then when I installed the Froyo Gapps I couldn't use the phone anymore because no data connection couldn't get passed the google account setup but seemed to work.
The only thing that was weird is before I installed the gapps zip while playing around the phone kept going back to the silver Android logo seeming as if it was restarting and going back to the lock screen but I managed to test the Phone, called 611 got US Cellular so that works!
Thanks again for your work I definitely and looking forward to this.
Big thanks to the devs! This is an awesome step forward. I flashed the ROM and Kernel, and although it's definitely alpha, it's awesome progress!
<rant>
It's pitiful that team of hobbyists and enthusiasts, working for free, in their spare time can port 2.2 faster than Samsung, who employs a full staff of software and hardware engineers, armed with development tools and source code. SAMSUNG, YOU SHOULD BE ASHAMED.
</rant>
Yoder808 said:
Big thanks to the devs! This is an awesome step forward. I flashed the ROM and Kernel, and although it's definitely alpha, it's awesome progress!
<rant>
It's pitiful that team of hobbyists and enthusiasts, working for free, in their spare time can port 2.2 faster than Samsung, who employs a full staff of software and hardware engineers, armed with development tools and source code. SAMSUNG, YOU SHOULD BE ASHAMED.
</rant>
Click to expand...
Click to collapse
From what I've read, it isn't a question of capability, i'ts just politics.
Thankfully we have wonderful developers to take the crap manufacturers throw at us and turn it into what really should be!
bdemartino said:
From what I've read, it isn't a question of capability, i'ts just politics.
Thankfully we have wonderful developers to take the crap manufacturers throw at us and turn it into what really should be!
Click to expand...
Click to collapse
Oh I agree 100%. They COULD have rolled out 2.2 months ago, if they wanted to.
Yoder808 said:
Oh I agree 100%. They COULD have rolled out 2.2 months ago, if they wanted to.
Click to expand...
Click to collapse
Samsung could have rolled out an firmware update but from what I've read they leave it up to the carriers to decide when they roll out updates.. especially OTAs since its on their end. US Cellular does spend a large amount of time testing their phones before releasing anything because their still small business orientated. That said, they easily could have rolled something out for us much earlier than this, as far as the small business goes they could have released it un-supported to commercial users and told business' not to load it yet plus not shipped any phones with it.. at least we'd have the option then..
Roebeet and I have confirmed that the 1.2 bootloader is not locked, it just has changes that other devices have gained before the Gtablet.
The 1.2 bootloader is compatible with pershoot's Zpad kernel and Adam kernels. The newer bootloader causes older kernels to fail because it requires extra voltage levels from the bootloader.
Check out Pershoot's Zpad option here: https://github.com/pershoot/gtab-2632/commit/6665ebaa6cd071d4669578983e82ea36d58fc68a
The Gtab can run Pershoot's Zpad kernel on the 1.2 bootloader. This means that the Zpad and Adam's bootloaders were from a newer branch of Malata's internal smba1002 kernel repo. If any future Gtablet or Adam kernels come out past 2.6.32, they will most likely be incompatible with the 1.1 Gtab bootloader, so it is best if people start moving ROMs on to 1.2 to prepare. We know that Notion Ink has Malata working on a post 2.6.32 kernel.
I know Roebeet is updating his mods to run this new setup, so watch out for them.
Bottom Line:
- If you run a 1.1 ROM now, you can continue to do so.
- If you want to prepare for future development, just transition your next version to using Pershoot's kernel for 1.2 and the 1.2 bootloader
Hmm, seems some apologies are in order.
Good stuff guys. Glad to see that the G-Tab will be able to move on to the new stuff.
We really think this is an opportunity for the Adam and Gtablet efforts to unite under one effort. The system images have always been easily ported to each other, now the kernels are also.
rothnic said:
We really think this is an opportunity for the Adam and Gtablet efforts to unite under one effort. The system images have always been easily ported to each other, now the kernels are also.
Click to expand...
Click to collapse
I also think this is the way to go. It's rumored NI is going to release a GB update soon ( It should have hardware acceleration since it is from NI). Also there is a tremendous dev effort going on porting HC to Adam, in addition to NI's promise for HC.
ive updated the compatibility listing.
Fantastic news. Thanks for sharing.
Sent from my ADR6300 using Tapatalk
rothnic said:
Roebeet and I have confirmed that the 1.2 bootloader is not locked, it just has changes that other devices have gained before the Gtablet.
The 1.2 bootloader is compatible with pershoot's Zpad kernel and Adam kernels. The newer bootloader causes older kernels to fail because it requires extra voltage levels from the bootloader.
The Gtab can run Pershoot's Zpad kernel on the 1.2 bootloader. This means that the Zpad and Adam's bootloaders were from a newer branch of Malata's internal smba1002 kernel repo. If any future Gtablet or Adam kernels come out past 2.6.32, they will most likely be incompatible with the 1.1 Gtab bootloader, so it is best if people start moving ROMs on to 1.2 to prepare. We know that Notion Ink has Malata working on a post 2.6.32 kernel.
Click to expand...
Click to collapse
pershoot said:
ive updated the compatibility listing.
Click to expand...
Click to collapse
rothnic/pershoot- this is good news for the zPad and Adam - but not concerned about those devices, even if they're related. This is about the gTablet and if this bootloader requires certain things that come direct from the manufacturer - and discourage the custom creation and modification of kernels - how is that not locked?
If we have to use the zPad kernel on the gTablet because voltages have to be higher (odd) then don't we lose the advancements pershoot has made in the overclocking of the gTablet? And how does staying with a manufacturers regulated bootloader help with people who have decided not to use the crud coming from the manufacturers and instead want to make their gTablet more than it can be? Why are we still thinking we have to follow the manufacturer like sheep and not break away and become more?
Looking for answers, not trying to be antagonistic. Looking out for the community at large as well.
Good work on figuring that out for those on TnT and stock-based MODs. If it were going to be anybody it'd be you guys!
jerdog said:
rothnic/pershoot- this is good news for the zPad and Adam - but not concerned about those devices, even if they're related. This is about the gTablet and if this bootloader requires certain things that come direct from the manufacturer - and discourage the custom creation and modification of kernels - how is that not locked?
If we have to use the zPad kernel on the gTablet because voltages have to be higher (odd) then don't we lose the advancements pershoot has made in the overclocking of the gTablet? And how does staying with a manufacturers regulated bootloader help with people who have decided not to use the crud coming from the manufacturers and instead want to make their gTablet more than it can be? Why are we still thinking we have to follow the manufacturer like sheep and not break away and become more?
Good work on figuring that out for those on TnT and stock-based MODs. If it were going to be anybody it'd be you guys!
Click to expand...
Click to collapse
the voltages are not higher.
old/new bootloader kernel is the same (save for the attenuation of the extra voltage step). this is to update to the current standard of the device, as layed out by Nvidia.
Thats awesome news, and thanks Rothnic for posting it. I'm running one of Roebeets 1.2 ROMs now, so I look forward to being able to get pershoots custom kernel on it.
karlkarloff said:
Thats awesome news, and thanks Rothnic for posting it. I'm running one of Roebeets 1.2 ROMs now, so I look forward to being able to get pershoots custom kernel on it.
Click to expand...
Click to collapse
just flash the 0430 .zip from droidbasement labelled 'newbl', and you'll be set. that rom is froyo, so choose froyo.
if it doesnt flash properly with the stock recovery, then create a boot.img for yourself, stick that in the rom .zip, and flash.
pershoot said:
the voltages are not higher.
old/new bootloader kernel is the same (save for the attenuation of the extra voltage step). this is to update to the current standard of the device, as layed out by Nvidia.
Click to expand...
Click to collapse
Hmm - haven't seen any new standards from nVidia. Do you have a link?
So those wishing to use your kernel need to use the "new Malata bootloader" ones if they are on the 1.2 bootloader? Are you still going to be separating the kernels for those who want to stay away from what a manufacturer pushes and wish to stay with CM and other custom builds?
pershoot said:
just flash the 0430 .zip from droidbasement labelled 'newbl', and you'll be set. that rom is froyo, so choose froyo.
if it doesnt flash properly with the stock recovery, then create a boot.img for yourself, stick that in the rom .zip, and flash.
Click to expand...
Click to collapse
You're definitely going to need to provide a procedure for the above and then support it because there is a LIMITED few who even understand what you just told this user to do.
jerdog said:
Hmm - haven't seen any new standards from nVidia. Do you have a link?
So those wishing to use your kernel need to use the "new Malata bootloader" ones if they are on the 1.2 bootloader? Are you still going to be separating the kernels for those who want to stay away from what a manufacturer pushes and wish to stay with CM and other custom builds?
Click to expand...
Click to collapse
yes, just look at my github.
the kernels are seperate. this is outlined in the downloads and in source.
jerdog said:
You're definitely going to need to provide a procedure for the above and then support it because there is a LIMITED few who even understand what you just told this user to do.
Click to expand...
Click to collapse
just flash the .zip in recovery as you would any rom.
that's all.
if it hangs (it shouldn't, as someone else just did this without issue: http://forum.xda-developers.com/showpost.php?p=13588874&postcount=5), then you wait for someone to produce a boot.img in a 1.2 rom.
pershoot said:
just flash the .zip in recovery as you would any rom.
that's all.
if it hangs (it shouldn't, as someone else just did this without issue: http://forum.xda-developers.com/showpost.php?p=13588874&postcount=5), then you wait for someone to produce a boot.img in a 1.2 rom.
Click to expand...
Click to collapse
yeah - but you told the user to create a new boot.img, put it in the rom.zip and flash.... not wait for someone else. And what's the fall-back?
pershoot said:
yes, just look at my github.
the kernels are seperate. this is outlined in the downloads and in source.
Click to expand...
Click to collapse
Probably blind, but where in your github does it answer the question about nVidia and provide a link? and by your downloads are you referring to your blog site and the different blob of kernels? A suggestion would be to provide more of a writeup on which to choose - based on if you're going the manufacturer route or the custom ROM route.
Good work figuring out the locked bootloader and getting around it's restrictions.
pershoot said:
then you wait for someone to produce a boot.img in a 1.2 rom.
Click to expand...
Click to collapse
Only one person doing that as of now and I'm using the BC version. The updated version with the kernel will be released today
jerdog said:
yeah - but you told the user to create a new boot.img, put it in the rom.zip and flash.... not wait for someone else. And what's the fall-back?
Probably blind, but where in your github does it answer the question about nVidia and provide a link? and by your downloads are you referring to your blog site and the different blob of kernels? A suggestion would be to provide more of a writeup on which to choose - based on if you're going the manufacturer route or the custom ROM route.
Good work figuring out the locked bootloader and getting around it's restrictions.
Click to expand...
Click to collapse
the fallback is you reflash the rom. this is nothing new to the procedure.
this has been this way for weeks in my tree and blog postings. i need not add anything further to the postings. i just renamed the labelling to reflect the current gtab testing confirmation.
And how does staying with a manufacturers regulated bootloader help with people who have decided not to use the crud coming from the manufacturers and instead want to make their gTablet more than it can be? Why are we still thinking we have to follow the manufacturer like sheep and not break away and become more?
Click to expand...
Click to collapse
Let's be honest here, not every owner of a Gtablet is a developer that wants to unlock the pandora's box of great things that this thing is capable of. Some of us just (to be honest once more) wanted the cheapest alternative to the iPad that we could find. I use iPad, because it IS the industry standard...we wouldn't need terms like "iPad killer" if it wasn't what people strive to be or surpass, right?
in my opinion, the 1.1 based roms available right now do what you say we want, make it more than it can be. It takes the crud from the manufacturer and improves on it. Heck, some people actually like the crud from the manufacturer, but just utilize the market fix, to have access to more apps. I would say that most of the people that own a Gtablet flashed 1 rom, and still use it to this day, without messing with their Gtablet, for fear of breaking something (yea, that would be me) I'm perfectly happy with Vegan 5.1.1, and have no intentions of changing until there is an OFFICIAL Nvidea hardware supported rom, that allows for hardware acceleration. Kernel tweaks etc. are fine, and I'm running Clemsyns right now, but NVidea has stated that it will not support Harmony unless requested by a manufacturer. If we need their crud to get the drivers, then so be it...but we do need their crud, first. If NI is actually doing what VS can't, or doesn't want to do, then so be it, I'll take it. But, regardless, if the bootloaders are changing, and all new updates are going to be using that new format, then why not change with the times?
I can understand that the people sorking on 1.1 roms are feeling a bit jaded, since they are still working very hard on all of their 1.1 roms. I do sympathize with them, since it does appear that 1.1 is becoming a thing of the past.
I believe that Robeet's initial point was that there would be new Gtablets that will possibly be shipped with the 1.2 bootloader. Had those people come here and flashed a 1.1 Rom, not knowing the difference, they might be a bit upset with the results. 1.2 Roms needed to be made, just for the people that have the new bootloader. Me, personally, as I've said, I'll be sticking with my 1.1 Rom just the way it is right now until there is a huge significant change that will make me update to 1.2, and flash a new rom...but it must be stable, everything working, hardware accelerated, with kernels that work...might be a while before I switch from Vegan 5.1.1.
Regards,
Todd
pershoot said:
the fallback is you reflash the rom. this is nothing new to the procedure.
this has been this way for weeks in my tree and blog postings. i need not add anything further to the postings. i just renamed the labelling to reflect the current gtab testing confirmation.
Click to expand...
Click to collapse
https://github.com/pershoot/gtab-26...nvrm/core/common/nvrm_clocks_limits_private.h
https://github.com/pershoot/gtab-26...nvrm/core/common/nvrm_clocks_limits_private.h
https://github.com/pershoot/gtab-2632/commit/b957d369741cf432146405a956cbc578fd201c80
http://nv-tegra.nvidia.com/gitweb/?...ff;h=7c97a1a4ebdff710907f9361cc05c1459cdeb510
pershoot said:
https://github.com/pershoot/gtab-26...nvrm/core/common/nvrm_clocks_limits_private.h
https://github.com/pershoot/gtab-26...nvrm/core/common/nvrm_clocks_limits_private.h
https://github.com/pershoot/gtab-2632/commit/b957d369741cf432146405a956cbc578fd201c80
http://nv-tegra.nvidia.com/gitweb/?...ff;h=7c97a1a4ebdff710907f9361cc05c1459cdeb510
Click to expand...
Click to collapse
excellent - thanks pershoot.
which current roms are ok to use with the new 4g phone? i think it would be nice to know. also is there a stock rooted 2.3.4 i can use when i get my phone this week? i see there is already a kernel we can use which is awesome.
fixxxer2008 said:
which current roms are ok to use with the new 4g phone? i think it would be nice to know. also is there a stock rooted 2.3.4 i can use when i get my phone this week? i see there is already a kernel we can use which is awesome.
Click to expand...
Click to collapse
I may be wrong but I don't believe any ROMs work with our phone yet. What I did in the mean time was just root using the fastboot method and flash CWM. Works like a champ
that's funny because netarch said last week they would work.
2.3.4 stock rom please devs!
The kernel works (I have it on my phone) as netarch stated, but rom's I *BELIEVE* are not compatible
fixxxer2008 said:
that's funny because netarch said last week they would work.
2.3.4 stock rom please devs!
Click to expand...
Click to collapse
I said the kernels should work fine, and roms possibly.
On closer inspection of a system dump from an ns4g there are some differences that will prevent current custom roms from working properly.
I'd need a guinea pig with an ns4g to assist me in testing to find out the exact changes necessary to make them compatible.
Atm there are at least 2 files I've found that would need to change.
You can go ahead and flash Net's kernel and start overclocking though!
I ended up getting so used to stock 2.3.4 rom that I am still on it!
Sent from my Nexus S using XDA App
netarchy said:
I said the kernels should work fine, and roms possibly.
On closer inspection of a system dump from an ns4g there are some differences that will prevent current custom roms from working properly.
I'd need a guinea pig with an ns4g to assist me in testing to find out the exact changes necessary to make them compatible.
Atm there are at least 2 files I've found that would need to change.
Click to expand...
Click to collapse
Guinea Pig here...
netarchy said:
I said the kernels should work fine, and roms possibly.
On closer inspection of a system dump from an ns4g there are some differences that will prevent current custom roms from working properly.
I'd need a guinea pig with an ns4g to assist me in testing to find out the exact changes necessary to make them compatible.
Atm there are at least 2 files I've found that would need to change.
Click to expand...
Click to collapse
Count me in as well as a guinea pig.
hey netarchy just to hopefully speed things up, yall can join the nexus IRC room
ill be making a new thread regarding its details. i know ill be there waiting to test anything out
I put a stock deodexed rom together. If anyone is interested, let me know. It has net's kernel and a few apps kanged from cm, file manager, spare parts, nothing major. Im testing now and and will share...If anyone wants
mikeyinid said:
I put a stock deodexed rom together. If anyone is interested, let me know. It has net's kernel and a few apps kanged from cm, file manager, spare parts, nothing major. Im testing now and and will share...If anyone wants
Click to expand...
Click to collapse
I'd be grateful!
dalvarez7 said:
I'd be grateful!
Click to expand...
Click to collapse
I think its good, Ill upload now
looking for that link....!!!!
Deodexing tool?
mikeyinid said:
I think its good, Ill upload now
Click to expand...
Click to collapse
Which tool did you use to deodex the rom? I was using xUltimate.
dalvarez7 said:
Which tool did you use to deodex the rom? I was using xUltimate.
Click to expand...
Click to collapse
Thats what I used. The rom is ready, but you will have to still flash superuser in recovery. I dont think the script is right. Im not really a dev after all Just wanted this, so I made it happen...
*I dont think my net could be any slower...still uploading
mikeyinid said:
Thats what I used. The rom is ready, but you will have to still flash superuser in recovery. I dont think the script is right. Im not really a dev after all Just wanted this, so I made it happen...
*I dont think my net could be any slower...still uploading
Click to expand...
Click to collapse
Did you have any trouble deodexing any of the apks? Mine keeps failing on NetworkLocation.odex. I just pulled the apk and odex files out of the origi_app folder to get around it.
Ok, so this is a stock deodexed ROM for the NS 4G. I am not a dev, you flash this at your own risk. With that being said, Im running it and I havent found anything wrong...yet. It does have netarchy's bfs kernel, you will need setcpu to oc, it is good up to 1.4. Your phone may not be. Do not check set on boot in setcpu until you know your phone is stable. You WILL have to flash superuser in recovery, you can flash it right after you flash the ROM, no need to reboot. So, here it is...
O yea, I added spare parts, CM file manager, and CM mms.apk so it doesnt have to be white...
>>>>>>I recommend wiping data before flashing<<<<<<
ROM:
http://www.mediafire.com/?xz680krzo40a7z7
THEN FLASH THIS BEFORE YOU REBOOT OR YOU WILL NOT HAVE ROOT ACCESS
SU:
http://www.mediafire.com/download.php?7mv65eu6ki4fcbd
>>>>>>I recommend wiping data before flashing<<<<<<
dalvarez7 said:
Did you have any trouble deodexing any of the apks? Mine keeps failing on NetworkLocation.odex. I just pulled the apk and odex files out of the origi_app folder to get around it.
Click to expand...
Click to collapse
I had the same problem, I worked around it.
I posted the ROM in the dev section, If you have any bugs or feedback, post it here http://forum.xda-developers.com/showthread.php?t=1070383
Thanks guys...
mikeyinid said:
I had the same problem, I worked around it.
Click to expand...
Click to collapse
i had no problem deodexing using the htc/sgs kitchen. just and fyi. it did everything with no errors.
I just posted the new BlastOff BML kernel here.
This is the place to ask questions.
Can we get an ETA on when this kernel will land on Mars?
FBis251 said:
Can we get an ETA on when this kernel will land on Mars?
Click to expand...
Click to collapse
Well, soon (no eta) it will land on an updated 'unnamed - bhundven edition' rom!
Not sure if its just me but wifi is showing up as error. I tried redownloading and fixing permissions problem still their.
read the op
WI FI calling isn't working, is it gong to work w/ ?this kernel
Sent from my SGH-T959V using xda premium
mcarbaja said:
WI FI calling isn't working, is it gong to work w/ ?this kernel
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
This kernel is for BML roms. Wifi calling works on those roms because they are stock based.
I'm new to this phone and not sure what bml is or what its used for and is this kernel for ics based roms
asj2583 said:
I'm new to this phone and not sure what bml is or what its used for and is this kernel for ics based roms
Click to expand...
Click to collapse
New to this phone or not. Search is the best feature on XDA.
If it's not BML, it's MTD. Search the Q&A forum for MTD. There you will find a thread by eollie which quotes the epicmtd thread and a post of mine... here it is:
http://forum.xda-developers.com/showthread.php?t=1699506
(yes, I have answered this question a billion times. Why, because no one searches.)
Edit: No, this will not work with MTD roms, like CM7, CM9, AOKP, SlimICS, etc... This will work with Valhalla, Valhalla Black, Unnamed, Stock UVKJ6 based roms.
bhundven said:
New to this phone or not. Search is the best feature on XDA.
If it's not BML, it's MTD. Search the Q&A forum for MTD. There you will find a thread by eollie which quotes the epicmtd thread and a post of mine... here it is:
http://forum.xda-developers.com/showthread.php?t=1699506
(yes, I have answered this question a billion times. Why, because no one searches.)
Edit: No, this will not work with MTD roms, like CM7, CM9, AOKP, SlimICS, etc... This will work with Valhalla, Valhalla Black, Unnamed, Stock UVKJ6 based roms.
Click to expand...
Click to collapse
Thank for the reply, anyway to make it work on non compadiable roms?
Edit: nevermind i read the info on the link you provided and it looks like ics isnt possible on bml
Belongs in Dev?
blazen2000 said:
Not sure if its just me but wifi is showing up as error. I tried redownloading and fixing permissions problem still their.
Click to expand...
Click to collapse
Yes read op.
I first want to than you for your support on a "update for a BML kernel".
i think it belongs in dev but still don't have enough posts to post.
I ran into a few issues with no log cat because of hardware freeze.
1st Tegrak will not load module for custom tweaks. Hardware failure vibrates indefinitely, and battery pull needed. works fine if you don't try and tweak. running 1.4 GHz without optimization works fine but can't underclock because of issue. the screen freezes and becomes pixilated.
restoring from nano backup finishes but stays at gs4g boot screen for t mobile
nano restore might be user error. i just factory reset and restored from there using the one click. restoring nano after one clicking resulted in same boot screen freeze as original
im sorry i don't have log cats but i hope i can provide further information if requested.
running latest Valhalla Black Edition with 1.3 OC undervolted
created backup with VB kernel recovery
booted fine with first flash of kernel running at 1.4
tried tegrak to underclock 1.4 and hardware froze with pixilation of screen in very light but noticable amount
reboot
wifi fix didn't work with flashing with cwm, suceeded with flash just no end result
tried to recover using cwm recovery with modded kernel caused boot freeze
one clicked back with no problems
i love this forum and want to try and provide feedback when possible, thank you for all you have accomplished over the years and i can't wait to see the perfect kernel and modem for ics. FB i love the AOKP. Unicorn Power!!! thank you all for all of your awesome work.
Ughhhh..... Lets break this one down, bit by bit.
rbedell said:
Yes read op.
Click to expand...
Click to collapse
Chill.
rbedell said:
I first want to than you for your support on a "update for a BML kernel".
i think it belongs in dev but still don't have enough posts to post.
Click to expand...
Click to collapse
Just hit thanks. This does not belong in dev.
rbedell said:
I ran into a few issues with no log cat because of hardware freeze.
Click to expand...
Click to collapse
You probably forgot to wipe data/factory reset or something...
rbedell said:
1st Tegrak will not load module for custom tweaks. Hardware failure vibrates indefinitely, and battery pull needed. works fine if you don't try and tweak. running 1.4 GHz without optimization works fine but can't underclock because of issue. the screen freezes and becomes pixilated.
Click to expand...
Click to collapse
Tegrak will not work. This kernel is already OC/UV. You just need setcpu or rom toolbox to set the cpu speed.
rbedell said:
restoring from nano backup finishes but stays at gs4g boot screen for t mobile
nano restore might be user error. i just factory reset and restored from there using the one click. restoring nano after one clicking resulted in same boot screen freeze as original
im sorry i don't have log cats but i hope i can provide further information if requested.
Click to expand...
Click to collapse
nano backup only backs up the kernel. Don't use it!
rbedell said:
running latest Valhalla Black Edition with 1.3 OC undervolted
created backup with VB kernel recovery
booted fine with first flash of kernel running at 1.4
tried tegrak to underclock 1.4 and hardware froze with pixilation of screen in very light but noticable amount
reboot
wifi fix didn't work with flashing with cwm, suceeded with flash just no end result
tried to recover using cwm recovery with modded kernel caused boot freeze
one clicked back with no problems
Click to expand...
Click to collapse
I don't even understand this stuff. You should work on making yourself more clear with ENGLISH grammar. Spell check helps too. Not trying to be a jerk, it's just hard as hell to read.
rbedell said:
i love this forum and want to try and provide feedback when possible, thank you for all you have accomplished over the years and i can't wait to see the perfect kernel and modem for ics. FB i love the AOKP. Unicorn Power!!! thank you all for all of your awesome work.
Click to expand...
Click to collapse
ugh... then say that in the aokp thread, not here.
My crystal ball says: you are younger then 17yo.
You just cleared up a bunch of crap for me... no I'm not 17 I'm 23... was just tired and my battery doesnt hold a charge on the laptop, it shut off a few times before I could post. That was some info and things I had installed and tried to do... Like I said probably user error, I was extremely tired and forgot to wipe my phone first... Ill try and learn from my mistakes. And I'm sorry I forget there is a thanks button...
rbedell said:
You just cleared up a bunch of crap for me... no I'm not 17 I'm 23... was just tired and my battery doesnt hold a charge on the laptop, it shut off a few times before I could post. That was some info and things I had installed and tried to do... Like I said probably user error, I was extremely tired and forgot to wipe my phone first... Ill try and learn from my mistakes. And I'm sorry I forget there is a thanks button...
Click to expand...
Click to collapse
I'm just saying. Everything you type is one long run-on sentence.
Notice how I break mine up.
It makes what you are saying easier to convey to others.
Don't worry. I was tired and grumpy
So what we learned:
Type like you're writing a letter
Don't use nano backup
Download alogcat/alogrec
Wiping cache and dalvik is fine, don't always need to wipe data, but sometimes you do.
I get grumpy sometimes too
:laugh:
Is this the kind of battery life we can expect for the mtd version of this kernel and/or the aries kernel port? I noticed this does have some things from aries (per Github History). The battery life with this kernel is epic, better than anything else I've used.
Thanks,
David
We don't know what kind of battery life you will expect from the ICS kernel because no one has tested the ICS kernel because bryan hasn't finished creating it yet. If and when it's released you'll get to see what kind of battery life you get with the way you use your own phone.
asj2583 said:
I'm new to this phone and not sure what bml is or what its used for and is this kernel for ics based roms
Click to expand...
Click to collapse
iamperson347 said:
Is this the kind of battery life we can expect for the mtd version of this kernel and/or the aries kernel port? I noticed this does have some things from aries (per Github History). The battery life with this kernel is epic, better than anything else I've used.
Thanks,
David
Click to expand...
Click to collapse
FBis251 said:
We don't know what kind of battery life you will expect from the ICS kernel because no one has tested the ICS kernel because bryan hasn't finished creating it yet. If and when it's released you'll get to see what kind of battery life you get with the way you use your own phone.
Click to expand...
Click to collapse
There is a reason for calling this kernel BlastOff. It's going to go through the galaxy of snacks Google has named their Android releases. It's starting off on Planet Gingerbread, BML style.
Eventually, if the stars align, it will end up reincarnated as MTD on Planet Gingerbread.
After reincarnation, it will head towards planet ICS... and on and on...
For now, we are still packing the ship with goodies. OC/UV, governers, I/O schedulers, mmc changes, and bcm4329 have already been packed. But I'm still adding more!
So for the medium term, this kernel will stay BML. You may see me experiment with MTD, but I would stay away from that stuff and stick with the BML kernel for now.
Enjoy my naming scheme.
FBis251 said:
We don't know what kind of battery life you will expect from the ICS kernel because no one has tested the ICS kernel because bryan hasn't finished creating it yet. If and when it's released you'll get to see what kind of battery life you get with the way you use your own phone.
Click to expand...
Click to collapse
No need for that kind of reply, I was simply asking a question. From what I can tell, this does use bits and pieces from Aries and that's what prompted the question. I didn't ask for an eta or anything to that affect. I also know that battery life is dependent on usage, but I know for a fact that on gingerbread the standby time is leaps and bounds better than what we have for ics (currently) (for most users) . It's even been mentioned that the kernel for ics had some battery draining issues by Bryan himself.
Sent from my SGH-T959V using xda app-developers app
That "kind of reply" was merited. Like I said in that post, we're not gonna know how the battery will be until the kernel gets created and tested. I can give you a prediction and tell you that it'll last you 10 days with heavy usage but I may be wrong.
We won't know until we test it.
BTW, unnamed - bhundven edition has been posted to the teamacid github.
I'm not making an official zip yet, as we have some bugs still to work out, but if you want a rom to play around with the new kernel, git clone it and run the mkzip.sh.
Let me know what you think, if you feel so daring
(again, disclaimer, I'm not responsible for messing your phone up, thats your problem. This rom has been tested and won't brick you, unless you do something stupid. This rom will not work with any other kernel, for now.)