yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] djp952:
Getting there very slowly but surely ... Mass Storage USB is working, at the cost of having a root shell ADB. I hate having to type "su" all the time :( USB took forever to do, but the stupid Samsung MTP/CDROM/RNDIS modes are gone *and* I managed to keep the dock audio and charging functions working (I don't think Cyanogenmod even does that right, but could be wrong -- it should be noted that "Kanged" from Cyanogenmod doesn't even

begin to describe

how much of the USB changes ultimatley came from their 2.6 kernel -- I am NOT knocking them!! Those guys are awesome!!)

Tonight's challenge is to try and figure out why any Google Apps I download ultimately crash and burn. It's just Gapps, updating things to the leaked JRO03O bits from the GNex may help.

Since I'm building and have nothing better to do for 20-30 minutes ... here is my current to-do list for GW Player (no particular order)

- Finish modifications to installd for DBDATA volume support

- Option to disable voodoo sound over A2DP connections, my receiver splats on heavy bass assume others will

- P2P Wifi? Possible? Useful? No Idea.

- IPv6 disable / ipconfig.txt error messages in logcat

- Frequent Trace errors in logcat due to missing kernel support -- may not be able to fix this; incompatible with Samsung modules

- Low Power/Charging mode doesn't quite work properly

- Camera issues - Flash disabled by default; focus seems wrong; video cam very slow and crashes occasionally

- Encryption Support? Would have to seriously change recovery?

- Smaller ramdisk / try to optimize RAM a bit

- Improve Dock Support

--- Custom "Dock" setting page that overrides stock one (done)

--- Auto-switch audio to dock on plug-in if set rather than forcing user to stop/restart playback

--- Option to keep screen on when docked

--- Option to force 100% audio volume when dock audio enabled

- Serial Number missing in Settings

- Hide "Update" in Settings if possible

- Bluetooth low power mode is not working; believe this is causing a significant battery hit

- USB Tethering support from Wifi connection?

- "Android is Upgrading" message on boot if odexed "user" build

- Superuser database issues; always prompting for Allow/Deny

- AtlasParts - read settings from kernel; don't assume they are stored properly

- Add 1.1GHz overclock setting (has 1.2Ghz now); add a couple new governors to make people happy

- Lost ADB root shell now that UsbDeviceManager is working, hacking ADBD didn't work, would be ok enough if "adb root" can be made to work right

- Google Apps downloaded from Play (update to Search/Velvet, My Tracks) are crashing with missing class errors but sometimes work?!?

I think I only need to fix a handful of these before I can release a Beta, as most are just mildy annoying and/or limiting for now. In all, the biggest problems that I don't think I can solve are the Trace (debugfs) errors since I cannot enable the necessary kernel support (CONFIG_FTRACE) without it blowing up the crap Samsung kernel modules and the general Camera maladies. I'm thinking of trying the legacy Camera/Gallery to see if they work better on this device.
[Fascinate Android Development] djp952:
Today was good, but still not ready to release as a beta. I managed to hack the kernel such that CONFIG_FTRACE can work with the Samsung proprietary modules (really didn't think I could), but it still needs some back-porting from Linux 3.x to get ATRACE working. Using the JRO03O modules solved many issues with Gapps, but form time to time Google Services Framework still dies and needs a Clear Data. Root shell over ADB is alive again, and I can generate a fake serial number using the Bluetooth MAC address of the device. The performance is still below my expectations, and "system_server" is the main culprit, but I have to fix a few more things before I can figure out why that is. My best guess at this point is that it's the way I hacked a VSYNC event into the 2.6 kernel Gingerbread display driver, but it's just a guess.

What you guys will get as a BETA will very likely not perform to my expectations and will leave something to be desired on battery life. My goal for release is to have as much as possible working "right" abnd hopefully I can handle any performance issues post-beta. We'll see. I may be as much as a week away still .. sorry, but my standards are a bit higher than most. I will give you something that's slow or sucks battery, but if basic functionality still isn't there ... no go!
[Fascinate Android Development] lord dredd:
take your time DJ

this is why we all love you :)

but on a side note , ( i know its too much and i must sday shamle4ss on my part ) but please give geeiwz an update based on the new showcase Rom if there is anything useful in it , also add some options in the kernel to have more options.

regards

PS : see when it comes to going on a tour or when i need my phone to work flawlessly on a busy day i always go back to Geewiz coz i know it wont ditch on any level ,

TBH i am on geewiz now since past few weeks coz i got sick of those random bugs in ICS and JB roms ( no offence intended to the RESPECTED DEVELOPERS )
[Fascinate Android Development] djp952:
Sorry GW Player is taking so long guys, but it is fairly Herculean of an effort for me. I spent the last 2 days fixing "Low Power Mode" (plugged in yet turned off), but I'm building what I hope to be the final iteration of that now. Turns out the AOSP battery charger works just fine on Fascinate, so I stopped fighting with the Samsung proprietary crap and switched to that. It required a new set of images for the charger to replace the stock green QMG animations, and I'm not very good at that stuff, so it took a while to come up with something I could be happy with. If you care, I've posted my (hopefully) final version of those graphics in the MODS/THEMES area (http://xdaforums.com/showthread.php?t=1875977). I hope you like them.

I've crossed "Recovery" off my list for now and will be using the GW 2.8 Recovery instead. That will save gobs of time, but I do want to go in there and add deletion of a couple Android OS directories from the SDCARD during data wipe. The main time constraint is that I need to set up a Gingerbread development environment for the changes. ugh. Thank goodness for Virtual Machines.

There are still a few roadblocks to a BETA, but I am going as fast as I can for ya :crying: Hope you're still here when I'm finally ready to give you something that kinda/sorta does what I think it should!!!
[Fascinate Android Development] phxshadow:
I am looking at getting the wife a new phone and was wanting to use the fassy she has a mini tablet. I was wondering if anyone has used google voice over wifi for phone calls? I am curious as to how well it works.

I am also having alot of reboots on my fassy. I think it might be an app but can't figure out which one it is. Where can I find the logcat on GW at ?
[Fascinate Android Development] swapnilss:
Eagerly awaiting for JellyWiz from you djp...... I hope it gets ready soon. Cant wait to have jelly bean experience on my fassy.
[Fascinate Android Development] lord dredd:
we are waiting eagerly mate :)

take your time .

god bless

regards
[Fascinate Android Development] JJ5150:
Are you working on OCing the kernel at all? seems like you have a few projects going on. GeeWiz player, Jellywiz, and the kernel? not sure what to look for first.
[Fascinate Android Development] lord dredd:
getting restless now :P

cant wait for G'Bean / GellyWiz / Geez&Jelly ;)

my 1/2 cent just ;) .................
[Fascinate Android Development] djp952:
Fair enough, it does seem like a bit of a tease at this point, doesn't it? How about a "preview" release for Player? Heck, I can upload an update-zip to mediafire and just link it in this thread for now if you'd like. Fair warnings: you need be on a stock-like setup already (no MTD), you can't use any other kernel, and you absolutely have to wipe data.

I just now solved a performance/battery life issue, too. I can see at least one or two more, but this was the biggest one. I found and eliminated a problem with the updated display driver that was causing 6-7% extra CPU at all times while the screen was on. So now I'm closer to about 4% CPU with the screen on and otherwise idle instead of more than 10% a couple days ago. Maybe I can track down that 4% as well, but the system has to use some manner of juice to keep updating the screen 60 times a second :) The system sensors also consume CPU that really can't be avoided.

OK, so you guys want a preview? Just for XDA GeeWiz 2.8 thread loyalists? If you don't need a camera flash, I think it's pretty damn close to being ready anyway. Most of the remaining work is tweaks and packaging. I can upload this latest build that completes the fix for the CPU usage after I smoke-test it.
[Fascinate Android Development] lord dredd:
Am game

Shooooooooot plz

GWizzing on beautifully :) and freakin loving it.
[Fascinate Android Development] djp952:
I just hope you're not terribly disappointed :crying: I've spent like 6 weeks on this stupid thing and it's still not perfect! LOL. But hey, who knew the lengths you have to go if you want to try to do something your own way. I mean come on, I had to make graphics for the freaking battery charger! Crazy. I never tried CyanogenMod or the other big names on my Fascinate, but I would be very interested to know how it stacks up in performance/battery/etc (the GPS will always suck, that one I already know - ha)

Oh, and the first person that asks me for custom battery icon mods before the camera even works properly is gonna get e-smacked!! :silly:

Code is all checked-in, building now. Should be about an hour, maybe 2 if I messed something dumb up. I'll post back with the link and some quick commentary
[Fascinate Android Development] djp952:
Update on the Player Preview ... after converting to EXT4 I've had problems and I was unable to re-apply the update-zip with SYSTEM formatted as EXT4. I believe there is an incompatibility with the old GeeWiz Recovery that I used to convert/re-format it. I suggest the RFS file system only until further notice.

If you want to go back to RFS, you have 2 options:

> Use ODIN to re-apply stock, then apply your recovery and flash the update-zip

> Use GeeWiz recovery to "convert file system" to RFS, then wipe data and re-flash the update-zip

Sorry. I knew this wasn't quite ready yet. My bad.
[Fascinate Android Development] scarfman4:
Boy you have been busy djp. Unfortunately I still have until Oct 1 before I can upgrade and I depend on my phone for now. But once I decide what phone I want to replace it with I would be happy to help test. This looks really cool.
[Fascinate Android Development] A-L31:
@djp952 you're awesome man :D

would you include the voice call and data in the future?
[Fascinate Android Development] djp952:
Thanks! Hopefully it will "ready" by then! This version is OK, but I'm more than a little embarrassed I never tried EXT4 and it screwed everything up. Something to do next week, right? There's also always deploying exclusively with ODIN to force RFS until I can find out what went so horribly wrong there :)

Actually, I branched the baseline tonight into "atlas" and "atlas3g" to investigate exactly that. My concern is that the performance is too bad for a daily-use phone, and of course I have a bit of a snafu in that I have no activated Fascinates left other than my wife's to test on, so we'll see how that goes. Can't promise, but I am taking a crack at it. I think the limited ability to test will be the bigger of the problems.
[Fascinate Android Development] swapnilss:
I'll have to sit & wait on the fence till this a fully functional Rom (with voice and data) as i have no substitute phone for my daily use. I'll be happy to help you djp with feedback after that..
[Fascinate Android Development] djp952:
Hi everyone. I found the problem with the Player Preview and EXT4 ... the ROM simply doesn't fit. I'm working to remove enough to get it working. It almost fits.

When I tested yesterday, I converted from RFS to EXT4 rather installing clean, which is why I started running into weird issues as files were missing from SYSTEM.

I've pulled the link for now, and will re-post something new once I have a solution. All I think I need to do is get rid of Google Earth - LOL. It's only in there because it's stock on the Galaxy Nexus.

edit: Fixed by removing Google Earth. The ROM now fits on an EXT4-formatted SYSTEM volume and so far is behaving normally, perhaps even a bit snappier thanks to EXT4.

GeeWiz 3 Player Preview JRO03L.20120912.133503 [update-zip]:

http://www.mediafire.com/file/28s6exw86gg12sl/full_atlas-rom-20120912.133503.zip
[Fascinate Android Development] JJ5150:
Great work, now I know what to use when I upgrade my phone. Any chance of getting the geewiz kernel oc by itself... for geewiz and for us still using the fascinate as our main driver?
[Fascinate Android Development] bmeek:
This sounds like a fun project but I've always been curious about the desire for a player version of a rom, with the phone and wireless data functions surgically removed, vs. any other rom in Airplane mode with Wi-Fi turned on.

Can someone please enlighten me as to the disadvantages of the latter?
[Fascinate Android Development] djp952:
Well, the main difference is really that the OS has no concept of phone at all. There is no dialer, no activation required, etc. It's not really surgically removed as much as it is more like a tablet build, much like what you would find on something like the Nexus 7.

From a usability perspective, you can do things like wipe data without needing to hack around the "hit send to activate your phone", or deal with applications trying to dial phone numbers. You also don't have to worry about enabling/disabling airplane mode, you won't see things in settings that relate to voice/cdma-enabled devices. None of the Google frameworks will try to do anything over GSM/CDMA at all, which streamlines initial setup and allows the device to know to ask for things like the time and timezone.

From a technical perspective, there are less processes running so there should be more memory/cpu free and improve battery life. In the specific case of the Fascinate at least, you can also keep using GPS and Bluetooth (I think you couldn't turn those back on in Airplane Mode on stock, could you?) There is no concept of voice/CDMA, so the device will never try to talk to the cellular network for any reason, which also saves on things (agreed Airplane mode has generally the same effect). You could even use a bad MEID, Verizon would never know!

I dunno ... in the end you do get basically the same thing, I guess it boils down to eliminating a small amount of hassle and presenting the device without functions that won't work. Like you said, it's a "fun project" for the most part.
[Fascinate Android Development] djp952:
One thing at a time my friend. Only have 10 fingers and a real job during the day :) Back-porting the changes to GW 2.8 kernel is easy (actually, almost trivial), it's giving you an application to control them that's hard!

You know ... since I added some mild overclocking to the JB kernel, I have to ask ... do you guys really see any difference? In theory, 1.2GHz is 20% faster than stock, but the bottlenecks seem to be more with the file system and the graphics, at least with Jelly Bean. I really don't see much, if any improvement from overclocking. I definitely see the extra battery drain, though!

Speaking of battery drain, I think I'm pretty close to as good as it's going to get now. Check out the attached picture. Not as good as GW 2.8 by any means, but much much better than a couple days ago! I should e-mail jt1134 and tell him about the video driver changes I made, they seem to have made a real difference.
[Fascinate Android Development] JJ5150:
I'm sorry, I didn't mean to sound like I was rushing you. I realize you're doing all this because you have your fassy non-activated and it's a really cool thing to have a Rom that allows you to continue to use the phone outside of a contract. I really dig that idea and your efforts in doing that for us. Along with that I feel the majority of the "loyals" here, I believe, are still using their fassy as their main driver.... at least that's what it seems, and I personally would like to see something geared towards us. With that said, GW is complete and anything extra is, well, extra.

Mind you I'm not rushing you or being greedy... I just got excited to see you back with more plans and more goodies... and I basically wanted to jump on that opportunity since I know your time is limited.

For the longest time I've wanted your kernel to be a little more flexible... similar to KGB... to get that edge back without having to use KGB.

I guess I'm saying all this because you deserve a great deal of appreciation and respect for your work, and I may have come off not doing that properly.

Whatever the case, GW works great as is and I'm happy to be using it as we speak. Thanks for listening.

Loving my SCH-I500 running GeeWiz using xda premium
[Fascinate Android Development] djp952:
LOL, why do you guys always think I'm upset with you? I try to use lots of smilies! :cyclops: :good::good: It's hard to convey if you're really being upset or just pretending with a smile on your face, I guess!

Anywhooo .. had a setback working on the camera when I realized that my flash wasn't working ... at all. Wasted a lot of time before trying stock, re-updating the firmware .. still no flash! Turns out the stupid thing broke!

Ever resourceful, I swapped the camera from an old bricked Fassy, and it works again (with stock). I'll keep an eye on this, if my new ROM/kernel is somehow damaging the camera board, that would be really really bad. Don't see how, but I think I will take out the stock firmware update portion of the kernel just in case. I don't believe it's necessary since jt1134/teamhacksung/cyanogenmod don't seem to ship the firmware files with their stuff. We'll see!

edit: Having a flash that actually functions is a big help! Full flash support has been fixed, including torch/flashlight mode (thanks to some jt1134 kernel changes as well). I think I know what's up with the preview focus, and if so I believe the camera will finally be done. You need a decent SDCARD to record 720p, though. Class 2s aren't good enough.
[Fascinate Android Development] djp952:
OK, it's going live tomorrow or Saturday. The camera is as fixed as it's going to be, and I've duplicated enough of the outstanding issues on my Galaxy Nexus to confident enough in this ROM now. There is a lot of packaging to do for ODIN, a lot of testing, but I will be releasing the "Player" ROM as GeeWiz Media 3.0 BETA:

- No support for device encryption at this time

- No USB tethering support at this time

- Some non-essential changes to INSTALLD service for DBDATA support are outstanding

- ATRACE command is not fully supported

- Recovery based on new kernel requires root on Linux (will not be included; old GW 2.8 recovery will instead)

- ANR (Application Not Responding) issues in systemui; strongly believe slow/bad SDCARD related

- Camera is imperfect but completely functional now; perfection requires more time/research than I could possibly provide. I'm hoping somebody else takes the time to really nail this down and configure the CE147 camera as well as Samsung did. It takes pictures, the flash works, they look pretty good, I'm done with it!

- Certain paired Bluetooth devices can cause BT issues on reboot; duplicated on my Galaxy Nexus so I'm not terribly concerned about them.

I cannot stress enough that your SDCARD has to be good for this ROM. When I was building it out, I was using a Class 10 Kingston card and ran into no weird issues, but when I swapped it out for the original Class 2 Samsung SDCARD I started getting ANR (Application Not Responding) issues, corrupt data, video and music problems, etc. I happen to know this particular Class 2 card is crap (it was replaced for a reason), so it's possible that others may not have the same issues, but ... consider yourself warned. I will be making a note of this when I open the new thread and strongly recommending a Class 10 card.

Anyway, here is a link to the "GeeWiz Media 3.0 BETA" update-zip that will be going live as soon as I can find the time to make/test the ODIN files and of course author the actual thread here at XDA:

http://www.mediafire.com/file/tom8o95uxzwvp58/geewiz-media-3.0-syskernel-20120913.zip

- Mandatory wipe data, then install ROM/Kernel, don't even consider using an alternate kernel, etc. Feature requests will be ignored until all core functions are to my satisfaction .. blah blah blah. You know the game :) It'd be live tonight if this was all I had to say "for reals". Unfortunately I have to go into detail about undoing MTD and reverting to stock, giving links to Recoveries .. ugh.

I don't expect it to be perfect, but I do think it's pretty damn good and does exactly what I set out to make it do. Hope to see some of you guys in the new thread!!

Please PM me with issues until the new thread goes live, then I would prefer you post them for everyone to see and provide their comments on.

PS - Up next is real work for about a week, then I hope to cycle back to GW 2.8 to upgrade it to 2.9 with fancy new options. After that I will continue my research into a voice/data version of this ROM. It's not looking promising for a full-blown voice/data ROM from what I know so far, but I say these kinds of things a lot. heh.
[Fascinate Android Development] JJ5150:
HAHA.. just trying to be polite... kissass style. :p:laugh:

How about "JellyWiz Player 3.0 Beta". :good:
[Fascinate Android Development] speedingcheetah:
bla..i am trying to restore my phone back to this rom...for some reason..other mtd roms keep corrupting my phone after a while..need more stable os...

got the rom installed, but the links to all the extras are dead...media fire says invalid or deleted....need the accurate battery mod and voice commands...
[Fascinate Android Development] JJ5150:
GeeWiz Nuance Voice Commands (EDIFY update-zip):

This update adds back the Nuance Voice Commands application that was removed from the base ROM

- Compatible with GeeWiz 2.3 - 2.8.1

http://www.mediafire.com/download.php?oyfowmus8by41xr

GeeWiz sbrissen Accurate Battery Meter (EDIFY update-zip):

This update replaces the AOSP battery meter and graphics with the sbrissen Froyo meter and graphics

- Compatible with GeeWiz 2.3 - 2.8.1

http://www.mediafire.com/download.php?kistcmrmzeq9yu8

These are my own uploads. Enjoy
[Fascinate Android Development] djp952:
Doh. I inadvertantly deleted them all a couple days ago to make room for GeeWiz Media 3.0. I'll get then re-uploaded and relinked as soon as I can. I should have known there was a reason I kept all those old folders out there. My bad.

Thanks for the save JJ5150!!!
[Fascinate Android Development] JLawL:
Lol. I just reloaded my phone to GeeWiz also and never saved the extras. So whenever you do get around to it! Much appreciated :)
[Fascinate Android Development] JJ5150:
which ones do you want I'll upload them
[Fascinate Android Development] djp952:
Thanks again JJ. I've been having logistical issues here restoring that data. My backup is a clonezilla of my laptop, which I cannot restore to my laptop since I need it for work (Windows 8). Turing that monster of a file into a Virtual Machine that works has been .. problematic.

Once I finally get that system back up and running, I promise to restore all the links I deleted by accident and then get a final final final final GeeWiz 2.9 out to you guys. Just put the stamp on and posted "GeeWiz Media 3.1" for the Wifi-only crowd tonight, and my goal is still to cycle back to Gingerbread for one last hurrah. Sorry it's (as usual) taking longer than I intended.
[Fascinate Android Development] lord dredd:
If i can be provided with the file names , i ll also try to dig into my backup and can upload to mediafire.