yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] Crawshayi:
Have you tried any of these solutions? There seem to have been a number of people with that problem: http://productforums.google.com/forum/#!topic/gmail/mJo_X3UJvQA
[Fascinate Android Development] djp952:
Easy. In the upper-right hand corner is a SHARE button. You can gmail it to yourself, and then attach it to a post here. We can look at it and see what's going on
[Fascinate Android Development] icemanwbs:
Ummm, I have it in my email, now how do i attatch or to post? :o
[Fascinate Android Development] JJ5150:
That thread is 3 years old. :D
[Fascinate Android Development] Crawshayi:
So is Gingerbread though, which is what this rom is :p

edit: yeah looks like most of the people replying were using 2.2, but I figured narrowing it down might give a better clue (the Calendar in particular). If this was me I would have just flashed back to stock and been done with it by now lol

edit2: I would suggest trying something really simple if you didn't already, and that is clear all data on the google apps, remove your google account from the phone, reboot and re-login and see if it all fixes when it syncs up
[Fascinate Android Development] icemanwbs:
Ok, I now have 2 logcats I emailed to myself. Now, how on earth do I post one here? ???:(:confused:
[Fascinate Android Development] djp952:
All good, I PMed you my e-mail address, at a minimum I can attach them to a post here, but I hope to have some time to look at them. If the problem isn't obvious, I will at minimum post the exception here so others can jump in. I'm traveling Thursday/Friday, so I may not have as much time as I'd like to help you out immediately.

I've never used the XDA app, but when using the web interface, under this box where you can reply there is a section called "Additional Options", with a button that says MANAGE ATTACHMENTS. That's typically how I attach files. I can understand it is likely more difficult than that when using the device itself :D Like I said, no worries, send 'em over and I'll have a look!!
[Fascinate Android Development] djp952:
Attached is icemanwbs logcat output.

Unfortunately, I don't see anything that's crying out "Google Play Services" to me, other than perhaps this section about Ads. There was also an exception from Tapatalk, that I guess isn't relevant to the problem at hand.

W/Ads (27648): IOException connecting to ad url.
W/Ads (27648): java.net.SocketException: Connection reset by peer
W/Ads (27648): at org.apache.harmony.luni.platform.OSNetworkSystem.read(Native Method)
W/Ads (27648): at dalvik.system.BlockGuard$WrappedNetworkSystem.read(BlockGuard.java:273)
W/Ads (27648): at org.apache.harmony.luni.net.PlainSocketImpl.read(PlainSocketImpl.java:458)
W/Ads (27648): at org.apache.harmony.luni.net.SocketInputStream.read(SocketInputStream.java:85)
W/Ads (27648): at java.io.BufferedInputStream.fillbuf(BufferedInputStream.java:166)
W/Ads (27648): at java.io.BufferedInputStream.read(BufferedInputStream.java:225)
W/Ads (27648): at org.apache.harmony.luni.internal.net.www.protocol.http.HttpURLConnectionImpl.readLine(HttpURLConnectionImpl.java:660)
W/Ads (27648): at org.apache.harmony.luni.internal.net.www.protocol.http.HttpURLConnectionImpl.readResponseHeaders(HttpURLConnectionImpl.java:690)
W/Ads (27648): at org.apache.harmony.luni.internal.net.www.protocol.http.HttpURLConnectionImpl.retrieveResponse(HttpURLConnectionImpl.java:1040)
W/Ads (27648): at org.apache.harmony.luni.internal.net.www.protocol.http.HttpURLConnectionImpl.getResponseCode(HttpURLConnectionImpl.java:726)
W/Ads (27648): at com.google.ads.b.run(SourceFile:283)
W/Ads (27648): at java.lang.Thread.run(Thread.java:1019)

There seems to be a lot of chatter about connectivity in the logs, perhaps you can try disabling the Google AdMob stuff in Google Play Store's settings to see if that helps to begin with.

Have you made any modifications to the network/3G settings of the phone? Are you on Verizon's network, or on a partner CDMA network? I also see that in this particular log you were using tethering, do you still run into the problems if you reboot but don't activate tethering at all?

I'm afraid it didn't stand out like I was expecting it to :crying: I'm hoping that one of the guys out here can have a look at the log and see whatever it is I'm missing!

Good luck my friend, I'm out of time until the weekend. Got a plane to catch in a few hours :crying:
[Fascinate Android Development] icemanwbs:
Yes I'm on verizon. Wondering if its a GAPPS thing. What gapps package is best on this?

Reinstalled zip, so far so good :o
[Fascinate Android Development] icemanwbs:
Ugh, still acting up :(
[Fascinate Android Development] JJ5150:
Sorry to hear that dude. Have you tried an older version maybe? I have 2.8.1 Full Wipe zipped. Try this...Just unzip and Odin.

https://www.dropbox.com/s/82zie2xt6wx4m8u/geewiz-2.8.1-fullwipe-04252012.tar.md5.zip
[Fascinate Android Development] fawzisaeed:
When you use a program morelocal2 stops messaging program (shutdown strongly) and also I can not receive any messages from friends far return to the default language with the knowledge that in the geewez version 4.4 software works successfully
[Fascinate Android Development] JLawL:
Anyone still have a link to 2.8.1?

Because of the Kernel I use that seems to be the most stable for me and apparently I lost my backup >.>

EDIT: Nevermind lol.

Downloaded it from JJ's sig xD
[Fascinate Android Development] scott2020:
I have been playing with GW 4 after just receiving my Fascinate. I figured I try this ROM since the stock GB seemed to work well. I did ODIN back to stock Eh03 and let it boot. Then I ODIN to GW 2.9.2 fullwipe, but it always boots into recovery. I can't get past it to actually get into the ROM. When I ODIN I am sure to choose repartition, etc. What am I missing? ODIN to stock works great, as well as ODIN to the updated GW. Thanks!

EDIT: I think I got it. I ODIN without the PIT file and it seems to be working. Hopefully that is it!
[Fascinate Android Development] djp952:
Sorry I didn't see this sooner, but I'm glad you got it working! The .pit file should only be necessary one time, and only if the stock partitions have been modified. As one that has never modified the stock partitions (no, really, never have!) I don't know why it would cause a problem for 2.9.2.

In the future if you run into problems (or for others that encounter them and see this), there is an easier way to go from GeeWiz 4 back to GeeWiz 2. Download the update-zip versions of GeeWiz 2 (SYSTEM and KERNEL, separate here) and place them on the root of your SDCARD. Reboot into recovery. Install both update-zips and then execute a factory reset (Wipe Device Data/Wipe all user data). This will have the same effect as ODIN-ing it would have, with the extra benefit that your DATA volumes will remain EXT4 rather than RFS.

Hope this helps in the future!
[Fascinate Android Development] JLawL:
Nevermind worked on the 3rd download. I'm having great luck with corrupted files >.>
[Fascinate Android Development] scott2020:
Thank you! Is it possible to convert to EXT4 after using ODIN to flash and loading up all of my apps?
[Fascinate Android Development] djp952:
Sure! Just reboot into Recovery and select Convert Device File System, then the [ext4] option. You should have 2GB free on your sdcard if you can, otherwise the big DATA volume may not convert. Really easy!
[Fascinate Android Development] scott2020:
EXT4 does make a big difference. I really like this and seems to work well. The only issue I have is Google Voice seems to stop running, so I don't get my text messages. If I open it, it will refresh and be OK for awhile. Eventually it seems to close and doesn't stay running in the background. Is there a task killer running on this rom? I checked out the task killer app but I don't see how to exclude GV. thanks again!
[Fascinate Android Development] AaronCompNetSys:
There is no task killer app in this ROM, but I have had problems with some of the new versions of Google Voice. This version has been rock solid for me for a while: http://xdaforums.com/showthread.php?t=1002279
[Fascinate Android Development] refthemc:
Sorry to bump an old thread, was there ever a wifi only patch for this rom?
[Fascinate Android Development] a senile fungus:
Search for geewiz 4.4

He's got the full ROM and also the media only version available
[Fascinate Android Development] JLawL:
I checked the last few pages but couldn't find anyone with a link in their post / sig..

Anyone happen to still have 2.8.2? I was using it with Devil Kernel and it seemed to be more stable.

Alternatively, if anyone is using Devil with 2.9 could you link me exactly which version you are using?

I try repeatedly to switch to 4.0+ roms but always end up finding some app or aspect that I can't use. Most recently it was my Paypal Here card reader. Only seems to work on JB Roms on my phone lol.
[Fascinate Android Development] AaronCompNetSys:
I found this stashed away, will that work? geewiz-2.8.1-system-04252012.zip
[Fascinate Android Development] JLawL:
That would work if I had a way to download it xD

And yea I guess its 2.8.1... whatever the one was prior to 2.9.2 lol.
[Fascinate Android Development] AaronCompNetSys:
https://docs.google.com/file/d/0B_q3JcNMHmUYZ2h0cXlNWlJPUEk/edit?usp=sharing
[Fascinate Android Development] svan71:
Ocean Waves

i really wish the stock live wallpapers weren't pulled. from this rom..Ocean Waves was a sweet wallpaper ...
[Fascinate Android Development] JJ5150:
There are some in the OP, not sure the one you're looking for is there or not.

Sent from dat.killer.SGS4
[Fascinate Android Development] svan71:
The OP whoda thunk it...thank... you it was right there all this time...
[Fascinate Android Development] lord dredd:
i totally agree

I actually prefer to have a data button in drop down menu which GW lacks aand also the GB camera takes like a second and a half extra in clicking a snap ,

but this ROM by DJ is too good not to be used :)

so i have put my those preferences on the backseat and enjoying the 2.1 now and indeed stock kernel ( as we are calling it coz DJ incorporated it with his release) performs very well.

thanks again DJ your Hardwork is highly appreciated and regarded mate .

God bless

PS : its good that we have you , ccampos with us on the fascinate front and now as the TSM is back we all are gonna have a blast :)
[Fascinate Android Development] djp952:
I think I found the problem in the kernel, testing it now to see if I'm right. I think it's just a bad voltage constant in the battery driver. I'll PM you if I'm really onto something.

As for requesting, call me old fashioned. Besides, by asking people I get the opportunity to ask questions and learn why they did what they did! :cool:
[Fascinate Android Development] djp952:
Once I get off my butt and document that recovery like I promised yesterday (oh how developers hate documentation!), I can look into adding the Mobile Data option back into the power-button pop up, if that would suffice. Editing the drop-down is probably too advanced for me, but I know exactly where the pop-up code is and if the function(s) called by Froyo to enable/disable are close to the same in GB, I think it can be done!
[Fascinate Android Development] Wolfkmann:
So, I Odin'd TKSB 1014 and then GW 2.1 everything said PASS then RESET, but I can't get it to reset. I can't get the phone to turn on at all. I don't even see the green battery when it is plugged in to the charger. PLEASE HELP
[Fascinate Android Development] QuattroMechanic:
I think you should have flashed gw2.1 first, booted once then flash TKSGB 10/12. 10/14 had issues last time I checked but they may have been fixed
[Fascinate Android Development] djp952:
Does the phone still go into Download mode by holding volume down while inserting the USB cable? How about if you hold down the power button with the battery in ... do you get a gray battery image? Getting the green battery image requires the kernel to be up and running (and I think /system being mounted properly, but don't quote me on that)

I got an e-mail earlier with your original description ... i was going to ask what ROM you were coming from, was it one of the MTD ROMs? I don't think it's even possible to mess up the bootloaders with ClockworkMod, that would be something ODIN would do.

It's actually pretty hard to completely brick a Galaxy S, you have to trash one of the bootloaders (I know, I've done it!). I'm not sure if a PIT problem can cause a total brick or not, but I don't believe so. I suppose if the PIT was bad ODIN may flash the wrong data over the bootloaders? That would be a brick situation if it's possible.

If you can get into download mode, the only thing I can really recommend trying is a full stock ODIN (like ED05) with the atlas_2.2.pit file. The "wipe" ODIN I posted doesn't have the bootloaders in it to avoid any possibility of exactly this situation. You would need a true FULL ODIN file that replaces everything on the device.

FULL ED05 ODIN WITH BOOTLOADERS AND PIT (pentafive): http://xdaforums.com/showthread.php?t=1178544

If you can't get into Download mode, I'm not sure there is anything that can be done short of being really good with a soldering iron to re-flash the boot loaders. I took one look at that process to try and fix a bricked Fassy I have and it was like "oh hell no". Really really tiny parts involved.
[Fascinate Android Development] Wolfkmann:
Thanks for the response. My phone is alive now. Here is the saga. I was coming from stock kernel and PWGB. It bricked when I tried to flash the zip of TKSGB and GW 2.1 All odin attempts were unsuccessful until I found and downloaded stock ed05 kernel. Then I was able to odin that and the pit 2.2 file simultaneously. I then odin'ed stock DI01 rom and it booted back to life. I could always get into download mode, it just that everything I tried resulted in the red FAIL! message. So, with ed05 as my kernel, I odin'ed GW 2.1 and it booted and all is well. feeling confident now, I went back to odin and tried to put on TKSGB followed by GW 2.1 and went back to brick. So currently I am back to stock ed05 kernel and GW 2.1 on top. Now I begin to reload all apps and data.
[Fascinate Android Development] AuroEdge:
I guess I don't understand why the phone discharges battery while it is plugged into a wall socket? Why can't it pull all of its power usage from the AC source?

I tried the full wipe v2.1 ODIN with atlas 2.2.2 pit. After the flash the phone will reboot into recovery and not boot into Android when I exit. Not sure what to do. I went a different route and installed the CWM zip and that worked fine.

I think others might find it useful to have an option in the recovery to format all phone partitions to ext4. As it is you have to go through each partition individually correct?
[Fascinate Android Development] mzrdisi:
Is anyone having the screen light up for no apparent reason? It's creepy because it seems like when I go to look at my phone it does it.
[Fascinate Android Development] sendan:
10:20 pm every night for me, lol.

also Djp952, can you think of any reason that any modified SystemUI.apk/res/layout/status_bar_expanded.xml causes statusbar force closes? At first I thought it was me just compiling it wrong, but it's only that file (status_bar.xml works fine) and I tried the SystemUI.apk from notta's EH09 theme and it has the same error. (he has a modified status_bar_expanded.xml as well)

I'm just skipping it for now but if you have any insight it would be appreciated :D

Thanks
[Fascinate Android Development] AuroEdge:
Yes. I don't seem to get this bug on PWGB
[Fascinate Android Development] nitsuj17:
did you install the proper frameworks with apktool before modding? what does the logcat say when fc-ing?
[Fascinate Android Development] QuattroMechanic:
is anyone having the random reboot issue?? not sure if its gw2.0 or tksgb 10/12

causing this.
[Fascinate Android Development] sendan:
Yeah proper frameworks are installed, as for a logcat...I'll try to get one now.

EDIT: This is the only logcat I could get so far that has anything to do with it...I'll keep trying but it's hard to do when it's a error at boot I guess. Any advice otherwise?

Maybe If I could restart the process while running a logcat? I don't know I'm not too knowledgeable with this.

Alright well disregard my posts, this is just a problem with apk manager on my computer. Not sure what's wrong but it has nothing to do with this ROM.
[Fascinate Android Development] briguyy:
I just want to say the battery life with this ROM is great. I unplugged it at 3pm yesterday moderately used it till 12am then forgot to plug it in..when i woke up at 9am i still had 60% left! I just had to plug it in at 4:30 today after moderate use.

BTW-im using the stock kernel

Thanks for a great biuld!
[Fascinate Android Development] mzrdisi:
I'm not having any reboot issues with stock kernel provided.

I did notice that Google Maps was fixed as far as multi-touch working properly. However navigation was the same issue. I was stuck in the top down view while using nav. Normal view is top down, but somewhat off center depending on your location and area when your next turn is.

The only way I could fix this was by removing maps from the system/apps folder and reinstalling from the market.
[Fascinate Android Development] lord dredd:
well i didnt face any reboot or FC issues with GW 2.0 or 2.1,

but yeah i did face some strange FCs and ocassional lagin OS when i used the TKSGB kernel ( i am sure i did everything right when i tried it )

i suggest you better try and flash the stock kernel. updated at pg one and see how it all goes.

the TKSGB has been performing well in general though with most of the people
[Fascinate Android Development] QuattroMechanic:
Tried reflashing kernel and bootloops. So I reflashed everything but I'm on gw 2.1 and Tksgb 10/15. With no changes in voltage control and it hasn't rebooted or lagged at all.
[Fascinate Android Development] djp952:
Hi everyone; just wanted to check in and let you know I had to take a couple days off from checking on the ol' GeeWiz, but I'm going to start trying to fix some of the issues again.

> Random screen on ... seen it myself. No idea why, but I hope to capture the event and see what exactly is causing it.

> Google Nav ... hmmmm ... first Flash and now Maps are both solved by installing from the Market? That cannot be a coincidence, and could be something really simple like me missing something it's doing other than the APKs. Given that like nobody else's ROM has this problem, that really points to me not grabbing something I should be. I'll do a more diligent diff of before and after on the DATA volume from a Market install to see if that's accurate.

> No Battery recharge after full charge/drain: I know *exactly* what's causing it and got sidetracked while I was working on trying to fix it. It's not very broken in reality, the root cause seems to be some bad code merging on Samsung's part moving their battery driver(s) into GB, not a simple constant like I first guessed. I did get my phone to recharge at one point on Saturday ... kinda :D It started way too soon (@99%, due to a quick voltage drop by starting up Netflix of all things), then it kinda crapped out anyway.

> Touchscreen Lock-up in Google Maps .. happens to me, is very annoying since you have to pull the battery. I can't repeat it on demand yet, but it's frequent enough that it should be able to be caught. It could be related to the whole Flash/Navigation debacle.

> Other stuff ... I'll catch up on as best I can. I'm intrigued by the status_bar_expanded.xml thing, I don't know what that's for but since my phone is at 77% and has a ways to go to get to 100% to try the battery thing again ... may as well have a look!!

Thanks for the patience!!! :cool:
[Fascinate Android Development] sendan:
Don't worry about the status_bar_expanded.xml thing, it was a problem with apktool itself. Sorry about confusing you:(
[Fascinate Android Development] djp952:
- Post #2 updated with "documentation" about GeeWiz Recovery.

It's a start :D ... there will be questions, and that's ok!! EXT4 SPARSE backups in and of themselves should pique curiosity, but the honest answer is that they were my way of converting to EXT4 more quickly than a full EXT4 image until I got YAFFS2 to work. Then I contributed what I thought was some slick modifications to that format to allow the data to be GZIP-ed on the fly back to the AOSP project, so while it may be worthless in the end, it will always be special to me! LOL.
[Fascinate Android Development] crakedparrot:
Great so far, been running for about 24 hr. Nice work!
[Fascinate Android Development] AuroEdge:
I tried out TSM recent release. Even after a few cycles my battery on it was draining quite fast. Went back to GeeWiz and it is performing very well like before my experiment.
[Fascinate Android Development] shag_on_e:
You are an artiste sir!

~~~~There is no spoon~~~~
[Fascinate Android Development] crakedparrot:
Boot Animation

I am trying to use a custom boot but cannot get it to work. I have renamed the stock one and named the new one to sanim.zip as instructed on first page of posts.

Really, I could live with the animation but the boot sound is LOUD and obnoxious.

Any ideas?
[Fascinate Android Development] QuattroMechanic:
If I download one of jaekar's boot animation cwm zips do I just move it under system.media.bootanimation.zip or is there more to it?
[Fascinate Android Development] crakedparrot:
Thanks to both of you! got rid of the sounds. Still didn't get the animation to work but no big deal, the samsung boot is much easier to deal with now that the awful sound is gone.
[Fascinate Android Development] davwman:
getting unsupported battery with 1800mah samsung battery. I thought this issue was resolved?
[Fascinate Android Development] QuattroMechanic:
It's better to have all your apps on sd card(app2sd) or leave them be?
[Fascinate Android Development] nitsuj17:
most apps on ur sdcard (even with faster sdcards) will run slower and less responsive than if kept internally in /data/ or /system/
[Fascinate Android Development] davwman:
anyone running this and lean kernel just found out the kernel is being worked on again and it might include the fix for unsupported batteries.
[Fascinate Android Development] Wolfkmann:
Came from PWGB and have been on this rom for a week now, with stock kernel, and no problems! It is running great. I don't know if it is due to the rom or it is an illusion, but I am getting a better 3G connection. I currently have less dead spots at work and around town it seems.
[Fascinate Android Development] davwman:
Lost data and now it wont reconnect to 3g. Hopes its something they can fix on verizons end.
[Fascinate Android Development] ssignature:
Just want to chime in that this ROM w/ TKS is making my fassy the best it's ever been. Thanks!
[Fascinate Android Development] killerkiwiHD:
wow, based on the comments, this looks like something i would love to flash my phone with. But my only fear is the modem problem, i just have this phobia that i wont get my 3g working after i flash the odin package. Also, i have a really f***ed up clockworkmod recovery, i was wondering if the geewiz recovery will completely remove clockwork. Sorry to sound like a noob, but i really dont wanna eff up:)
[Fascinate Android Development] Wolfkmann:
All I can tell you is that this rom gives me better 3G connection than PWGB did. Why don't you odin this, then odin a clean version of cwm.
[Fascinate Android Development] ssignature:
The full package of GeeWiz has it's own recovery, but I don't think it's as flexible as CWM 3 (or maybe I just don't know it as well). I Flashed my phone in the following order: Odin GeeWiz, Odin CWM 3 (blue), CWM TKS 1021. I reinstalled Titanium Backup from the market, restored my apps from TiBU. Then I added in Voltage control, Memkill, and modified the Dalvik heap to 80. I'm still tweaking my UV settings. I had Voodoo lagfix previously installed and it didn't have to install it again when I odin'ed the ROM. I was even able to switch back to my standard battery today. It's the best this Fascinate has ever run.