yashsingh1/xdaforums huggingface dataset:
[Desire Q&A, Help & Troubleshooting] BustaVR6:
Ok, so this is my first post although I have lurked here for a couple of years. I wanted to try a different ROM so I am trying Oxygen after using CM6/7 for the last couple of years (I wanted to try something with a bit less bloat - I do love CM tho!).

Also I have tried searching but using the words Oxygen and Wallpaper in the same string brings back results about how to find the Oxygen wallpaper :rolleyes:.

From CM7 I rebooted into recovery, wiped the cache, the data and the dalvik cache. I then installed Oxygen 2.3.1. The first time it loaded I was greeted with my old wallpaper from CM7, now I thought this was strange but wasn't sure if I somehow chose a wallpaper that was also used in Oxygen. So to be sure I hadn't done something wrong, I rebooted to recovery again and did the following:

Wiped the cache, the data and the dalvik cache and re-applied the Oxygen ROM.

This time, on first boot, I get the original default Android (blue scene) wallpaper, however in the wallpaper chooser it isn't there, so after I chose a different wallpaper I can't go back.

Now you might think I'm mad to even care, I'm probably not going to use the stock wallpapers, however, what is going on? Am I not wiping enough of the phone memory? I thought the three options I was following would be enough. I don't want remnants of my old ROM hanging around and possibly causing issues with a new ROM.

Any help appreciated and thanks for reading!

(PS if it helps - HTC Desire, AlphaRev 1.8, Bravo CM7 r2 HBOOT, 5.17.05.23 Radio.)
[Desire Q&A, Help & Troubleshooting] stankyou:
Don't mind it its just how it goes with AOSP I believe. Wiping system, dalvik and cache is correct. ;-)

Sent from HTC Desire via XDA App
[Desire Q&A, Help & Troubleshooting] iain2510:
It could be to do with wiping system partition. The op cleared data and cache partitions but but specifically the system one.

Must threads seem to suggest a full, factory wipe when moving between ROM's.
[Desire Q&A, Help & Troubleshooting] MatDrOiD:
You also have to wipe /system, not just /data, /cache and dalvik-cache when changing roms.

SwiftKeyed from CyanogenMod with Transparent XDA App
[Desire Q&A, Help & Troubleshooting] BustaVR6:
Ah ok. So the option "wipe data/factory reset" isn't /system?

Sent from my HTC Desire
[Desire Q&A, Help & Troubleshooting] BustaVR6:
in that case (I should probably know this) what's the best way to clear /system?

Thanks for your help!

Sent from my HTC Desire
[Desire Q&A, Help & Troubleshooting] MatDrOiD:
Recovery or fastboot.
[Samsung Epic 4G Touch] uarefunnytome:
As a proud owner of this kick ass phone (No LOS Issue At All) I keep seeing lot's of posts on-line about siri and such Apple makes an iDeal about something that I feel that is already a part of the Android infrastructure. From what I can tell i am able to practically do everything that Apple makes a big deal about as being cutting edge. This maybe the case in their little iWorld but I just don't see the big deal!
[Samsung Epic 4G Touch] Will of fire:
Tell me about it my sister is so proud of her voice commands on her 4s. We have had that for some time now.
[Samsung Epic 4G Touch] yoniinfante:
guys i dont know if you know these already but apple is made practically by samsung, if you open that 4s(****) or any apple product youll see samsung everywhere...retina display what??? thats amoled display>samsung, a4,a5 chipset>samsung....samsung's the best all time

Samsung Galaxy S2 Epic 4G Touch Proud Owner HERE!!!
[Samsung Epic 4G Touch] drksilenc:
the retina is actually an lg display the only things samsung makes for apple now is the chip and memory if im not mistaken
[AT&T Samsung Galaxy S II SGH-I777] runtohell121:
Rearth Ringbo

When I first opened it, feeling the screen protector, it feels thin compared to the Anti-Glare I had on my iPhone 4 from Power Support USA. This screen protector seems like a fingerprint magnet, more fingerprints on the screen protector than the phone. The feel to it is smooth, not like those "military grade" plastic feel like from InvisibleShield, ClearProtector, etc.

What it includes: 2 Screen Protector and Instructions, along with 3 piece of paper (Installation guide, Feedback, and 15% coupon)

Quality: 8.5/10

Packaging: 10/10

Easy to Install: 7/10 (10/10 for me, since I'm used to installing screen protectors)

2 Screen Protectors

On the phone
[AT&T Samsung Galaxy S II SGH-I777] cincy1020:
Hi:

I bought these also. It went on perfectly (on the second try, I ruined the first one :o ). Not even one bubble.

Looks, clear and nice.

IMPOSSIBLE to keep clean. Fingerprints everywhere.

And, even if you want to clean it, you have to rub and rub to get it clean.

I would NOT buy these again because of the smudges.

I do have one question for you, since you said you're an expert :) at installing screen protectors.

Is it possible to remove the screen protector without damaging it, so it can be reused. I have to exchange my phone.

Is there any way to clean a screen protector that got lint on it (on the adhesive side) when trying to apply it? I read somewhere scotch tape works, but it didn't work for me. Because if I could get the lint off, the first screen protector I tried to apply would be good.

Thanks!
[AT&T Samsung Galaxy S II SGH-I777] runtohell121:
I personally don't see that this screen protectors are reusable.. I tried it once with Power Support USA by using water to wash off all the lint, letting it dry a little bit, not completely all, and then apply it back up, works, but might have 1 or 2 bubbles.
[AT&T Samsung Galaxy S II SGH-I777] harlenm:
If you peel it off and get dust on the back side of it, use magic tape to remove the dust. Works good as a prep before applying them to get any dust or lint off the screen.
[AT&T Samsung Galaxy S II SGH-I777] runtohell121:
^Yup

My installation process:

1. Wipe screen as clean as possible with a microfiber/glasses cloth

2. Get some magic/scotch tape and use the sticky side on the screen to remove any leftover dust/lint throughout the screen, especially on the sides/edges.

3. Remove the "2" side first, or at least that's what I always do.

4. Remove the "1" side and start applying on the screen protector on slowly, removing any air bubbles if there is any.

Always try to install it without any air bubbles.
[AT&T Samsung Galaxy S II SGH-I777] champofthesun:
what case is that?
[AT&T Samsung Galaxy S II SGH-I777] runtohell121:
SGP Neo Hybrid

It's for the international version, fits perfectly just that it covers the top noise canceling mic.
[AT&T Samsung Galaxy S II SGH-I777] mike619:
Hard to tell from the pics, but does it cover the entire screen? A few protectors I've seen have a cut out for the speaker at the top but cut out everything above that. I believe the Belkin is like that. Also, does the protector have a cut out for the front facing camera, or does it go over it entirely?
[AT&T Samsung Galaxy S II SGH-I777] runtohell121:
^^it covers the whole screen
[Epic 4G Android Development] mkasick:
11/22/11 Update: Added "reboot bml8 recovery" patch for ROM Manager suppport.

11/8/11 Update: Updated keyfix kernel with the EI22 initramfs. Also, Samsung has placed the previous official (and now labeled EI22) source tarball on their opensource site.

10/24/11 Update: It appears that Samsung has removed the "official" Epic GB source tarball from their website. I've mirrored it for anyone interested in the original release. For anyone actually looking to build with the sources, you're probably better off using Rodderik's GitHub

10/19/11 Update: As everyone's found out by now, Samsung released official Epic GB sources last night. There's not that many changes to our device in the official source tree compared to the previous, but a few appear to be subtlely important (see abbreviated deltas). It still needs some work to get into a buildable state, but it does appear to work great on EH17!

I've updated most of my patches for GB, conveniently packaged together. I've also uploaded a new EH17 kernel that works on stock (rfs) EH17 ROMs and includes the keyboard fixes with optimized values, along with userdebug and kexec support. Feel free to give it a try.

Meanwhile Rodderik is updating his GitHub repo to include all these patches for folks to clone from, stay tuned.

Happy hacking!

So apparently when Samsung released the kernel sources to the Mesmerize's Gingerbread update a month-and-a-half ago, that source tree contained almost-buildable kernel sources for our device as well.

I've patched the sources (removed modemctl definition, added tfsr driver, compile right camera driver) to build for the Epic. I've also built a custom EH17 kernel combining these sources with the EH17 initramfs. It's essentially stock EH17 with ro.debugging=1, adbd always-spawning during recovery, and testkey signature verification. I'll get to porting over some other patches (like the dropped key fix) soon.

As for compatibility with EH17, the source tree itself appears to have been checked out on 8/30 and looks to include everything EH17 does. I ran "strings Image | sort -u" on both kernels to make sure there weren't any obvious strings/symbol differences between them. The ones that remain appear to be minor, but legitimate fixes.

Thanks to jt1134 & Rodderik for pointing out that the Mesmerize source released contained Epic code, and Tortel & ugothakd for testing.

GitHub repo, thanks Rodderik!

To build:

Grab SCH-I500_USCC_Opensource_Update3.zip SPH-D700_GB_Opensource.zip from opensource.samsung.com, extract.

Run "make mrproper" to get rid of atlas (Mesmerize) config junk.

Patch to complete Epic support.

Build with EH17 initramfs as usual, use victory_8G_defconfig for kernel configuration.

Mirror links:

Official GB sources: SPH-D700_GB_Opensource.zip (originally posted on opensource.samsung.com, since removed.)

Epic GB source patches: kernel-GB-3a-patches.tar.gz

Source-compiled, keyboard fix EI22 kernel: kernel-GB-3a.tar.md5

(URLs for Mesmerize tree patches removed, although they're still valid.)
[Epic 4G Android Development] zanderman112:
Flashed this yesterday(11/13). Working good so far.

Edit: Oh, and first! Sorry iSaint
[Epic 4G Android Development] BoominSVX:
HAHAHAHA! Epic. I love you guys!
[Epic 4G Android Development] AproSamurai:
Yeah, um, I love you. <3 lol.
[Epic 4G Android Development] ugothakd:
No. I was first. I tested it lol

[edit] actually, tortel was first. but that was before i got on board.
[Epic 4G Android Development] Ceelos09:
Hmmmm...who would of known part of our kernel source was right under our noses :p
[Epic 4G Android Development] AproSamurai:
It just occurred to me that, with this finding a lot of good can happen, as well as ICS tomorrow. :D Depending on timezone I should say.
[Epic 4G Android Development] xboxfanj:
Sweet. Hopefully this'll help cm7
[Epic 4G Android Development] ac16313:
Heart just stopped beating LOL!

What about stratosphere then?

Oh well nice work!

Sent from my SPH-D700
[Epic 4G Android Development] dzl:
winning

bet samsung was just watching and waiting to see how long it took one of you/us to figure it out, lol.
[Epic 4G Android Development] bender beerman:
this is wonderful news :)
[Epic 4G Android Development] mkasick:
Ideally there would be one Samsung Android kernel source tree that would contain code for our device as well as all their others. However, I've been checking somewhat recently and code for Epic never appered in the GT-I9000 sources (which have been updated recently) nor in the Stratosphere ones.

It didn't occur to me to check the Mesmerize sources sooner, but as the only US device with an official GB release (still?) it shouldn't have been much of a surprise. It's also worth nothing that there appears to be GB sources for the Indulge in there as well. I'm not sure of their buildability though.
[Epic 4G Android Development] qbking77:
GREAT work mkasick.... everyone be SURE to thank him!
[Epic 4G Android Development] TexasLTE:
:) SWEET !!! :)
[Epic 4G Android Development] Neckberg:
Exciting! Do the cm7 guys know about this, or is already used in the build we have?
[Epic 4G Android Development] AproSamurai:
I'm not sure, JT helped Decad3nce with CM 7 though and they both hacked the EH17 kernel to work for this. So hopefully it's something Decad3nce can use.

He said he was moving so he probably won't be back until tomorrow.
[Epic 4G Android Development] ugothakd:
The main CM7 people are Decad3nce and jt and they haven't been on irc today.
[Epic 4G Android Development] -SpeedofSound-:
this is exactly what we been needing...THANK YOU VERY MUCH mkasick!! You rock my friend!
[Epic 4G Android Development] styles420:
Downloading now - going to see if I can compile a bootable kernel :)

Sent from my CyanogenMODed Epic
[Epic 4G Android Development] mkasick:
I believe JT was the one who discovered the Mesmerize sources were pertinent to us. He might've been able to compile something, but at least Rodderik was stuck on the missing tfsr driver without the right debugging bits.

I discovered this worked somewhat haphazardly when Rodderik mentioned the Mesmerize sources to me. They booted the first time with EH17 on SD, but wouldn't boot from flash. Since I was able to get it to boot off SD, debugging was a good deal easier.

In any event, it's a drop-in replacement for the current kernel used by the Epic CM7 build, so I'm sure they'll make good use of it sooner or later.

Actually what I'm curious about is if the reboot problems still persist with this. I haven't had one yet, but they haven't been a problem with stock EH17 on my device either.
[Epic 4G Android Development] mkasick:
Unfortunately I have to put this off another week since the source ate up all my free time this week. I'd like to get back to it soon though.
[Epic 4G Android Development] dzl:
Hmmm spin up a linux vm and move all development to a linux env? ;)
[Epic 4G Android Development] djgallis:
lmao / aint that the truth

---------- Post added at 03:10 AM ---------- Previous post was at 02:45 AM ----------

2nd that

i concur GREAT JOB .... even tho sammy making it almost all for not with its release "bastards" but in a good way :-)

ok holding my breathe ended with GB .... now let it begin for ICS & ........... go !!
[Epic 4G Android Development] KennyG123:
You will be one blue stiff since it usually takes 8 months AFTER Samsung announces they will support it for the Galaxy S series.
[Epic 4G Android Development] toadlife:
Been running the kernel you posted since the night of the 19th and haven't had a single reboot or GPS freeze since. No custom voltages or screen off profiles set!

Thanks for posting that kernel. :)
[Epic 4G Android Development] kalel_293:
the kernel is for rfs only right? so if imon ext4 rom, run ext4torfs zip then load the kernel in odin? would that work? tia...
[Epic 4G Android Development] antila:
Where can I get kernel to flash? Is it possible?
[Epic 4G Android Development] orlzzt:
If you Odin first using Crawrj's EH17 tar; do you even need to flash the EXT42RFS zip?

(I'm not being snarky; that's an actual question. Forgive the ignorance...)
[Epic 4G Android Development] kalel_293:
i dont think so...unless u flash an ext 4 rom...
[Epic 4G Android Development] bender beerman:
It seems like its pretty harmless to flash if you're already on rfs, and it only converts u to rfs if you're on ext4, doesn't do anything else. So its probably good practice to just flash it if you're unsure.

Edit: if you're sure you're rfs there's obviously no need to flash the gotorfs.zip
[Epic 4G Android Development] djgallis:
WORD UP !!
[Epic 4G Android Development] cornaljoe:
I've been running this with stock deoxeded EH17 and had my first random reboot last night. I flashed Maddagons 8lock theme and the AIO mod on top of it. I'm also using Tegrak to OC to 1.3 and have the V6 supercharger script running. It's been running pretty smooth otherwise so the reboot may have been caused by something else other than the voltage problem. I'll install SetCPU to test this.
[Epic 4G Android Development] kryptoniteman:
So many are experiencing no reboots with this on EH17?
[Epic 4G Android Development] cornaljoe:
It seems people who have been running this kernel for awhile are experiencing reboots aswell. A fix is in the general section thread as it seems to be a voltage problem at low CPU frequencies. It's a common problem with stock GB builds as the I9000 and Nexus S (IIRC) also had these problems.
[Epic 4G Android Development] styles420:
When is it ever "good practice" to just flash if you're unsure? That's like saying, "don't look both ways before crossing, just go for it" ;)
[Epic 4G Android Development] ugothakd:
It's the exact opposite. This is like a double check to make sure your on rfs.
[Epic 4G Android Development] bender beerman:
actually, i believe it's the exact opposite in this specific case only. the ext4torfs zip will only flash u to rfs from ext4, and it only does that if you're already on ext4, otherwise it does nothing. it's more like saying "it's good practice to wear a condom before having sex with that random chick off the street" it only works one way, it has no other purpose, and even if you're positive she's on the pill, it's still a cheap, quick insurance policy against future headaches.
[Epic 4G Android Development] KennyG123:
I figured that would happen. Reflashing GB leaks usually stops reboots for a day or two then they get more and more frequent. So same can be said for putting on a new kernel. As mentioned the Tegrak/SetCPU combo in General works well. I get 1 reboot every 5 days or so when I used to get 5 or 6 a day.
[Epic 4G Android Development] KennyG123:
Will we see an EXT4 version soon?
[Epic 4G Android Development] tommi_han:
Seems to be working without reboot for 3 days with eh17 deodexed odin and this kernel...only addon is eh17 hotspot, no maddoggins lock or AIO...
[Epic 4G Android Development] KennyG123:
Awesome. So you have like 72 hours up time in settings?
[Epic 4G Android Development] andygallo:
Hello,

Sorry if this has been asked before, I don't think I saw it mentioned yet.

Would it be possible to roll in some of the settings in this thread into this kernal?

http://xdaforums.com/showthread.php?t=1276417

Maybe that will help the reboots that some are seeing in EH17?
[Epic 4G Android Development] toadlife:
Those settings are not necessary. Random reboots do not happen with this kernel.
[Epic 4G Android Development] KennyG123:
I read some people were starting to get them after 3 days.
[Epic 4G Android Development] andygallo:
That's what I read too. A stock gingerbread kernal with key fix and voltage/reboot fix would be awesome. Hopefully, mkasick can hook us up (fingers crossed).
[Epic 4G Android Development] toadlife:
I never go three days without rebooting so I would never find out. With the previous leaked GB kernels I would get the reboots constantly - sometimes minutes after booting up. I still haven't gotten one with this kernel so I'm a happy camper.

:)
[Epic 4G Android Development] andygallo:
Oh, cool, that's good to know, thanks for the info. Sorry, I would have tried it, but I have no real way of testing myself anymore. Just wanted to make sure before I go flashing it on my friends Epic.
[Epic 4G Android Development] antila:
Sorry for the qiestion

I've already asked but still don't undestand. Guys, please, how can I install this kernel if I don't have linux and can't compile the kernel from the sources?

Please, I really need some advice?

Can I odin it?

Thank you!
[Epic 4G Android Development] tommi_han:
Yea just Odin...put the.tar file in the phone section of Odin. Seem this kernel is quite stable no reboot except when my battery died
[Epic 4G Android Development] poit:
Has anyone noticed higher battery drain with this kernel? I'm using it on stock EH17, and battery drain seems significantly higher than "stock" gingerbread.
[Epic 4G Android Development] drjonesok:
I'm getting 60% left on my original battery after 24hrs of moderate use. I was getting 30% left after 12 hrs use with the stock froyo. Also this kernel hasn't had any random reboots and my gps works! All the recent GB roms I've tried before had that reboot bug. Thank you for the kernel!

I installed with ODIN using the deodexed/rooted/cwm/busybox eh17 rom in the bootloader slot and put this kernal in the PDA slot. BTW I tried to install two eh17 battery % mods and neither showed up. Not a big deal though.
[Epic 4G Android Development] KennyG123:
I would try a reflash or get Better Battery Stats to see what's using your battery. I am on Rodderik's beta from the source and battery is as good as any GB ROM I have tried.
[Epic 4G Android Development] ugothakd:
Are you trying to brick your device? Where did you hear anyone use the bootloader slot?! NEVER put anything there, and NEVER check update bootloader.
[Epic 4G Android Development] drjonesok:
I've always used the bootloader slot for roms and I've flashed a ton of times. What problems have people been having with it? I guess I'm supposed to use the pda slot for roms? The only times I've had problems is with the reflash partition checked while flashing a modem. It was a semi brick, was able to use odin after leaving the battery out for 30 mins.
[Epic 4G Android Development] ac16313:
Actually I think you can check update bootloader if its a full rom. But for kernels NOO.

Sent from my SPH-D700
[Epic 4G Android Development] pgdeaner:
Working great

Every time I have tried another EH17 build I have had random reboots. Even with voltage tweaking.

I started with Deodexed-Rooted-CWM-Busybox-EH17.tar

registered with the market and let it download updates.

Loaded this kernel - noted that the battery use was higher than some of the test roms I had been using.

Loaded SetCPU and set it for 1000 max and 100 min and set the scaling to on demand.

Uptime is nearly 48 hours with no issues.

Edit: Also, I always use the PDA slot for ROMS and Kernels.
[Epic 4G Android Development] KennyG123:
Awesome. The random reboot issue requires more than just voltage adjustments. It also needs a Screen Off profile. But glad this kernel works for you.
[Epic 4G Android Development] poit:
Looks like my battery issues were caused by not getting everything setup right. The biggest offender was forgetting to set the Wifi sleep policy to

'never sleep". That seems to make a big difference for me. I also found that when I reinstalled Facebook it set itself to update every hour, usually I keep updates set to manual and notifications off. Today after 8 hours of light to moderate use I'm still at 80% battery. That's way better.

By the way, still no random reboots, although I've had to restart the phone a few times in the last couple of days because of badly behaving apps. I'm on "stock" EH17, no voltage tweaks.
[Epic 4G Android Development] lilajrestnom:
Ok so I'm a lil confused...

Lets say I wanna use this kernel with random roms thunderhawk rom

I would odin the eh17 modem

And in the pda I would have the .tar fils found in the thred? But which one? What is the patches one for?

Or would I have to flash the rom after the modem and then flash this kernel?
[Epic 4G Android Development] bender beerman:
ummm... maybe try one flash at a time, just to eliminate potential issues. the tar comes with a modem and kernel, so start with that. then flash the kernel. then odin the modem after that
[Epic 4G Android Development] poit:
Thunderhawk appears to be an EG22 rom, and I think this kernel is built for EH17 only. That's what I'm using it for, I don't think it has been tested on an EG22 Rom and you may end up with a phone that won't boot. (Be sure to do a nandroid backup before you start)

Anyway, you can flash this kernel right over a working install after you get everything else running . you want the one labeled:Source-compiled, keyboard fix EH17 kernel: kernel-GB-2.tar.md5. the others aren't compiled kernels, they are source and patches.

Use odin, put it in the pda slot, uncheck all the options except auto-reboot.
[Epic 4G Android Development] lost_:
cancrusher said he's using Rodderik's test kernel (based on this kernel) on random eg22. there might be others.