[WIP][KERNEL][SCH-I705][2013-02-11] Jellybean Stock - Galaxy Tab 2 7" Android Development

Jellybean Stock
FIRST AND FOREMOST
**do this at your own risk**​
READ FIRST
THIS IS A WORK IN PROGRESS! DO NOT USE THIS KERNEL IF YOU DO NOT KNOW WHAT YOU ARE DOING
Features
Built from sch-i535 (yes, i535) 4.1 Jellybean source. This is for testing only.
Download boot.img
367471a0c5e7c70698d3214b1ca725a3
Source
https://github.com/MrHyde03/android_kernel_samsung_espressovzw-jb

Confirmed this kernel works. injected into a S3 SynergyROM jb 4.1 build and it boots right up. Obviously, since it's a S3 build, it's rather unusable. If anyone else with a 705 wants to get a JB port going please, by all means, feel free to use this!

any reason why this wouldn't work with one of the other wifi gtab2 rom's to make them work on the vz gtab2's?

The wifi tabs are completely different than the vzw tabs. The i705's closest relative is the i535 (vzw galaxy s3). It just wouldn't be very easy at all.. if it's even possible.

Related

[Q] AOSP ROM for Galaxy S?

Hey guys, been out of the loop for a while as I've been settled on JPY for a few weeks now. However, I saw a friend flash his Desire today with Oxygen, a gingerbread-based AOSP ROM. All the SGS ROMs I can find so far are based on the stock Samsung firmware - is there any work being done on a full AOSP ROM like Oxygen or Cyanogen? I can't find any details about this anywhere.
I am very curious about this question. Because if answer is simply no, it's time to sell Galaxy S. Gingerbread will be the last update from Samsung and AOSP could be the future of this phone then CM7 for SGS seems to have big problems and it's the only AOSP ROM for SGS which I'm aware of...
What big problems?
I'm using CM7 for a month right now and it's pretty stable if i can say. Yes, it lacks some features and some bugs are not fixed yet (theres a workaround tho), but if you follow it's thread the progress they make are great. They're already into mainline, so probably it will reach RC status in a month/maybe less, who knows.
After the devs are done, i think there will be a custom ROM based on CM7/AOSP.
~drz
CM7 is getting there. And with Gingerbread coming out, that should make things easier for the dev.
Yes, but with no source then there is nothing big. GB leak, only helped them with "less" important stuff (FM radio, etc.)
~drz

Once official ICS is out, wht's involved for camera fix

Anyone know what's needed to get the camera fixed once Samsung releases the official ICS ROM over the next few days? Does the kernel have to be re-compiled with a driver for the camera, or do you just drop in a drive file and presto, it works?
harry_fine said:
Anyone know what's needed to get the camera fixed once Samsung releases the official ICS ROM over the next few days? Does the kernel have to be re-compiled with a driver for the camera, or do you just drop in a drive file and presto, it works?
Click to expand...
Click to collapse
Once they get a work able ROM to kinker with it should be a just taking apart the driver
What does that mean, taking apart the driver. Is it a file? And if so, why do they have to take it apart rather than drop it where it goes?
Half the problem we have is that current ICS ROMs use an old kernel because we dont have a Samsung ICS kernel and no one has created fully custom one. Its really holding back the AOSP and AOKP ROMs, and its why they are slow in real usage. The camera drivers in the old kernel are probably not compatible with ICS.
rovex said:
Half the problem we have is that current ICS ROMs use an old kernel because we dont have a Samsung ICS kernel and no one has created fully custom one. Its really holding back the AOSP and AOKP ROMs, and its why they are slow in real usage. The camera drivers in the old kernel are probably not compatible with ICS.
Click to expand...
Click to collapse
Samsung today released the source code for ICS on galaxy tab 2 of 7 and 10 inch. Does this help for complete builds of aokp and aosp?
Galaxy Tab 2 has different SoC, so i don't see how this will be useful for us.

[Q] ICS for Droid 3 Recommendations

I've been running Liberty 2.0 on my D3 for quite a while now. Starting to get jealous of everyone who's one or even two builds up on me.
I looked into what ROMs were available for the D3 for ICS, specifically because some of the custom apps I use are not compatible with JB yet. I found HashCode's CM9 build and his AOKP build (which could be the same thing, and I just don't understand.
I also posted once before where someone recommended Gummy for the Droid 3, but I could never nail down which version was the most up-to-date and was working the best. I learned that they stopped working on the Gummy ROM over the summer, but if they had a working build, I would love to try it out.
All I am looking for is the most complete build of ICS on the Droid 3. I use this phone as my primary device, so I would like to be able to use the camera, internet, data, etc.
If anyone has any other suggestions, please feel free to recommend what you use/have used.
joefuf said:
I've been running Liberty 2.0 on my D3 for quite a while now. Starting to get jealous of everyone who's one or even two builds up on me.
I looked into what ROMs were available for the D3 for ICS, specifically because some of the custom apps I use are not compatible with JB yet. I found HashCode's CM9 build and his AOKP build (which could be the same thing, and I just don't understand.
I also posted once before where someone recommended Gummy for the Droid 3, but I could never nail down which version was the most up-to-date and was working the best. I learned that they stopped working on the Gummy ROM over the summer, but if they had a working build, I would love to try it out.
All I am looking for is the most complete build of ICS on the Droid 3. I use this phone as my primary device, so I would like to be able to use the camera, internet, data, etc.
If anyone has any other suggestions, please feel free to recommend what you use/have used.
Click to expand...
Click to collapse
There is no 100% working ICS rom as of now, but with Kexec they have a custom kernel booting and building from there. I would settle into a GB rom for stability/everyday use and have either an ICS or JB rom just to test. You can check the development forum for the current active CM9/CM10/AOKP by Hashcode, the latest CM10 (Jelly Bean) Kexec rom only seems to have a sleep issue and no camera, everything else seems fine so far. Safe Strap 3.05 lets you have up to 5 bootable systems without swapping nandroid backups; Stock + 4 custom rom slots.
http://blog.hash-of-codes.com/how-to-safestrap/ Here is Hash's website about safestrap and to download.
http://forum.xda-developers.com/showthread.php?t=1804665 Here is the thread about Hash's current work on Kexec and available roms. Read up some of the last ~20 pages for current rom and information on it, just make sure to learn the new safestrap before playing around.
As for other roms; The Gummy team split up as I recall, no more Gummy roms...
Personal main usage; I use Maverick ROM 4.0, good battery, good tweaks, looks nice.. version 4.5 has overclock, but a bug in it causes battery drain so stick with 4.0.

[Q] Looking for a fast JB Rom + A probably stupid question

I was looking into Jelly Bean ROMs here, and I couldn't find anything that's working as I had hoped for.
Or I just didn't look through stuff on here in more detail.
So I was looking at some 'light' ROMs and found SlimBean, but it only seems to support i9000 (as listed here) whereas I'm running i9001.
Here comes the stupid question - would it work or not?
I kind of want to test that out, because the ROMs I used previously didn't have a working microphone (which I kind of needed for making calls) so I'm thinking this one would have a working one and would have a decent amount of Project Butter.
So anyway, what JB ROM would you recommend? It doesn't have to be 'slim', as long as most stuff works on it.
Hi,
most or nearly all roms wont work on your device. I found a nice JB Rom called Mackay Rom for my Samsung Galaxy S.
Its fast and stabil. If you find this Rom for your device, you could try it, he is updating this rom fast and the changes are nice.
Most JB Rom use CM10 as basis so the difference wont be that huge^^
None of the i9001 Jelly Bean ROMs are fully functional at the moment, as you have noticed. i9000 ROMs will not work on i9001, as it is a totally different phone. Only things we have similar is the screen, battery size and the form of the phone, CPU & GPU being different makes it impossible to use the same ROMs.
There is a lot of work to be done and a few talented people doing the work. Just keep on looking in the Galaxy S Plus I9001 Android Development, all progress will be posted in there. Pretty much the only JB rom we have is DoomNEXUS by Doomsday94.
There also is the I9001 Q&A section that these questions should be directed to.
Slim Bean Best one

[Q] Any other ROMS for the S4 Active?

Has anybody been able to find any ROMs for the S4 Active? Preferably, the i537, but I'm willing to try anything for the GT-I9295. I know it's early, as the Safestrap method is fairly new, and the kernel can't be touched right now, so a 4.3 ROM is out of the question. I'm using the ROM listed here:
http://forum.xda-developers.com/showthread.php?t=2406177
I'm loving stock, but I have Cyanogenmod on my Nexus and love the customization. Does anybody know of anything close to that available for the Active?
Yea I believe its ported from the International version...they call it google edition I think! If I helped ya..it dosent hurt to hit the thanks button! :good:
Actually there is a pre-release 4.3 ROM available, it's the MI2 build for the I537 and yes it's a leak from AT&T (thanks to designgears and you can find it here). Two issues with that one if you choose to use it:
1) You may not be able to update to the official OTA 4.3 expected sometime later this month (according to rumors, that is)
2) There's no working root so if you must have that, don't bother with this build just yet
There is a third issue that appears to be the most common problem with the MI2 build and that's the screenshot feature which isn't working, it's covered in the thread for the MI2 build.
Because it's a pre-release similar to the MF1 pre-release leak, it appears to not allow an OTA but since there hasn't been any 4.3 OTA updates from AT&T as of yet nobody really knows what's going to happen.
Also, if you flash that MI2 build, your only alternative will be to fall all the way back to the MF1 build since no ODIN One-click exists for the MF2 or MF3 builds, but you can switch between the MF1 and MI2 builds (confirmed by others and I've done it several times in the past week myself).
Aside from that "official" ROM leak, the only other current working option is using Safestrap on MF1/MF2/MF3 (with the appropriate kernel modules) along with the AOSP ROM provided by LeJay which you can find here.
That's pretty much it. I have the I537 as noted so I don't muck with the I9295 ROMs but I think there's at least the one CM10.2 build for it, and no, it doesn't work on the I537 even with Safestrap.
EDIT: DOH, forgot about the ROM from d8389 he just released yesterday, also made from the MI2 build and you can find that one here - that's for the I9295, btw.
br0adband said:
Actually there is a pre-release 4.3 ROM available, it's the MI2 build for the I537 and yes it's a leak from AT&T (thanks to designgears and you can find it here). Two issues with that one if you choose to use it:
1) You may not be able to update to the official OTA 4.3 expected sometime later this month (according to rumors, that is)
2) There's no working root so if you must have that, don't bother with this build just yet
There is a third issue that appears to be the most common problem with the MI2 build and that's the screenshot feature which isn't working, it's covered in the thread for the MI2 build.
Because it's a pre-release similar to the MF1 pre-release leak, it appears to not allow an OTA but since there hasn't been any 4.3 OTA updates from AT&T as of yet nobody really knows what's going to happen.
Also, if you flash that MI2 build, your only alternative will be to fall all the way back to the MF1 build since no ODIN One-click exists for the MF2 or MF3 builds, but you can switch between the MF1 and MI2 builds (confirmed by others and I've done it several times in the past week myself).
Aside from that "official" ROM leak, the only other current working option is using Safestrap on MF1/MF2/MF3 (with the appropriate kernel modules) along with the AOSP ROM provided by LeJay which you can find here.
That's pretty much it. I have the I537 as noted so I don't muck with the I9295 ROMs but I think there's at least the one CM10.2 build for it, and no, it doesn't work on the I537 even with Safestrap.
EDIT: DOH, forgot about the ROM from d8389 he just released yesterday, also made from the MI2 build and you can find that one here - that's for the I9295, btw.
Click to expand...
Click to collapse
I'll keep playing the waiting game then... Maybe I can submit a request for Cyanogenmod to be made for this device.
Until the bootloader is unlocked, it's most likely not going to happen at all. It's possible that someone with enough talent can put together a CM10.1 ROM which uses the current kernels (I think, I'm not 100% sure on that), but the MI2 4.3 build now is pretty locked down as it is (no known root at the moment and it looks like Safestrap may be a no-go as well for that or future builds).
The honest truth is the GS4A is simply not popular enough to get any reaction from the CM crowd at all, unfortunately, and it's entirely possible it may not even be available for much longer given that unpopularity. It's not selling well, and the few of us that do have them are just that: few and far between.
It's sad because it's a great device; it IS an S4 with a lower resolution camera and the water-resistant aspect as well as the LCD panel (not AMOLED like the S4) which is just fine by me, I can see it better in daylight than an AMOLED anyway. But the locked bootloader basically ensures the level of interest is negligible at best, not much can be done about it unless a miracle comes along at this point.
I'm very happy with mine for many reasons, not just 'cause I got it so cheap.
br0adband said:
Until the bootloader is unlocked, it's most likely not going to happen at all. It's possible that someone with enough talent can put together a CM10.1 ROM which uses the current kernels (I think, I'm not 100% sure on that), but the MI2 4.3 build now is pretty locked down as it is (no known root at the moment and it looks like Safestrap may be a no-go as well for that or future builds).
The honest truth is the GS4A is simply not popular enough to get any reaction from the CM crowd at all, unfortunately, and it's entirely possible it may not even be available for much longer given that unpopularity. It's not selling well, and the few of us that do have them are just that: few and far between.
It's sad because it's a great device; it IS an S4 with a lower resolution camera and the water-resistant aspect as well as the LCD panel (not AMOLED like the S4) which is just fine by me, I can see it better in daylight than an AMOLED anyway. But the locked bootloader basically ensures the level of interest is negligible at best, not much can be done about it unless a miracle comes along at this point.
I'm very happy with mine for many reasons, not just 'cause I got it so cheap.
Click to expand...
Click to collapse
I think our best hope is for @Hashcode to get kexec working with SafeStrap. Then we will be able to use ROMs with any kernel. Until then we're stuck with GPE 4.2.2.
Hashcode made a post or two at his blog/site stating that things are becoming incredibly tough to make such workarounds viable anymore, even to the point where it's not even worth the time and trouble to make the effort at all in some situations. I think with the GS4A, more specifically the AT&T I537 model, we could just have a device that simply isn't going to get itself cracked wide open without some small miracle happening.
Come on, someone working at Samsung... have some pity on us and drop us something to help out, will ya?
I've started a request forum here:
http://forum.cyanogenmod.com/topic/80004-cyanogenmod-for-the-s4-active/
If anyone would like to back me up, it'd be much appreciated.
Decided it wasn't worth the BS of heading back to Best Buy so I'll stick with MF1 for now. I did make a reply at the CM forum about the potential of someone building CM10.1 as a flashable zip for us and provided the link to the kernel source for the I537, maybe someone with some spare time might be able to create something.
I really wish I'd spent more time learning how to do that; if I had the necessary skill set I'd build it myself I suppose but I've never been into that side of the device firmware/ROM stuff.
But who knows...
I'm running Shostock v2.3 on my I537 with one of my rom slots in safestrap. i'm on MF2. of the S4 ROMs, i've only tried Shostock and Goldeneye, but i'm sure other S4 ROMs will work too. when you install one, you also have to install the modules pack and camera fix from the ported google edition thread. the only other problem is the menu and back buttons don't work out of the box with an S4 ROM because our buttons aren't capacitive. thankfully, Darkman was kind enough to show me how to fix those so they work like normal.
hokeymcf said:
I'm running Shostock v2.3 on my I537 with one of my rom slots in safestrap. i'm on MF2. of the S4 ROMs, i've only tried Shostock and Goldeneye, but i'm sure other S4 ROMs will work too. when you install one, you also have to install the modules pack and camera fix from the ported google edition thread. the only other problem is the menu and back buttons don't work out of the box with an S4 ROM because our buttons aren't capacitive. thankfully, Darkman was kind enough to show me how to fix those so they work like normal.
Click to expand...
Click to collapse
Can you share how to edit ROMs to add the physical back and menu buttons? Thanks
GT-i9295(i537) running SafeStrap
yankeesfan714 said:
Can you share how to edit ROMs to add the physical back and menu buttons? Thanks
GT-i9295(i537) running SafeStrap
Click to expand...
Click to collapse
well, i don't edit the ROM before flashing it. after flashing the ROM, any updates for it, the modules pack, and the camera patch, i go into /system/usr/keylayout using a file explorer, and add:
key 139 MENU
key 158 BACK
to gpio-keys.kl with a text editor. after that, reboot and they work like they should.
hokeymcf said:
well, i don't edit the ROM before flashing it. after flashing the ROM, any updates for it, the modules pack, and the camera patch, i go into /system/usr/keylayout using a file explorer, and add:
key 139 MENU
key 158 BACK
to gpio-keys.kl with a text editor. after that, reboot and they work like they should.
Click to expand...
Click to collapse
Is it possible to add this to either the modules zip or the camera fix to make it easier for users? Ideally this would be added to the camera fix since I think @Hashcode is going to automate the modules in SafeStrap eventually.
On another note, I had no idea we could flash regular GS4 ROMs, this opens up a world of possibilities. I assume we can only flash 4.2.2 ROMs though?
Devo7v said:
Is it possible to add this to either the modules zip or the camera fix to make it easier for users? Ideally this would be added to the camera fix since I think @Hashcode is going to automate the modules in SafeStrap eventually.
On another note, I had no idea we could flash regular GS4 ROMs, this opens up a world of possibilities. I assume we can only flash 4.2.2 ROMs though?
Click to expand...
Click to collapse
i have no idea. i could try, but it's probably a job better suited to someone who really knows what they're doing, since i'm only as good as the tutorials i find on the internet.
once again, i dunno. i'm on MF2, but shostock is MF3. so since that's different but still works, it might be possible to flash a 4.3 ROM, but the fact that i read that there's no going back once you do flash it, i haven't tried it.
i agree that it's awesome we can actually use regular s4 ROMs.
yankeesfan714 said:
Can you share how to edit ROMs to add the physical back and menu buttons? Thanks
GT-i9295(i537) running SafeStrap
Click to expand...
Click to collapse
So in theory any stock based s4 4.2.2 ROM will run with this buildprop modification?
GT-i9295(i537) running SafeStrap
It's not a build.prop edit, but yeah, I think any S4 4.2.2 ROM would work.
S-Beam
Set them next to each other and use S-Beam, it's what it was designed for. Or even Bluetooth would work.
Just so everybody is aware @my-blue-snog-box has created a flashable zip file that will edit the keyboard file and get the hard keys working. It can be found here. If you try any S4 ROMs please post the functionality of them so we can create an index of ROMs working with SafeStrap.
I've posted over there that I got Hyperdrive ROM working, you just need to be careful during setup.
CM Unofficial 2013 10 10 fkosa's reply
I am running CM 20131010 Unoffical - jactiveltxxx from, ofcourse it is 4.3 and it is running smothly.
Havn't found any anoying errors yet.
http://forum.xda-developers.com/showthread.php?t=2395242&page=11
I tried to make some roms for myself and found out the following:
from: CM 20131017 Nightly - jltxxx - was a bit slow, and it felt like the touch was a bit delayed verry anoying
from: CM 20131021 Nightly - jltxxx - here there was something wrong with the screen.
But then again the nightly builds tends to a bit unstable from time to time.
Any Galaxy S4 Rom
I just recently got the galaxy note 2 and loving everything about it inside and out. But I was just wondering if there are or will be any rom or ports of a galaxy s4 rom to our galaxy note 2? Ive look in the android forums but did not see anything besides the hawkish rom which I am now currently using...

Categories

Resources