yashsingh1/xdaforums huggingface dataset:
[Motorola Photon 4G] jokersax11:
As far as progress goes, alcohol(not money) is required as development is a huge pain in the (edited for language). It's trial and error and some people just have magical powers that others don't. Cm7 is based on aosp, while motoblur is too, motorola makes there own stuff to get it to work. Then they make there special files/drivers depend on other stuff that's theirs. Some of these drivers/files have no source. Theres where the problem is.

Now the GSM cm7 is actually a kang, or cm7 with built in moto files. The reason cdma doesn't work is because it isn't called correctly, as the files necessary are part of blur. The the other cm7 is pure cm. It's a long tedious road for anyone attempting cm but once we have it upgrading will be easy. Personally I think more people should be helping. Pm the CDMA dev and ask how to build to his point, sync with his git, read up on the cm forums and try to help. Even if you only fix a small thing, submitting it back to him and it will bring cm faster.

As far as me, I plan to start helping soon after I redo my dev box(ran out of room) . I hope others will too.
[Motorola Photon 4G] Lightsword1942:
Well, I found cybik's(GSM) source code (https://github.com/cybik/Sunfire) and have been playing around with building it. I'm not sure how much help I can be with it though.
[Motorola Photon 4G] shabbypenguin:
its true, development work is best done between .13-.20 BAC :)
[Motorola Photon 4G] devilsshadow:
seeing as how we don't pay these people to bring us anything, we can't really expect them to work on this day and night. I'm sure CM will be done eventually, I have no doubts about that. As for how long it's going to take, i really don't care. I'll happily accept a "when it's done" ETA.
[Motorola Photon 4G] Lightsword1942:
Yeah, I am just trying to see if there is anything that is holding development up.
[Motorola Photon 4G] Kcarpenter:
Balmers peak?
[Motorola Photon 4G] abowlby:
Beat me to it...
[Motorola Photon 4G] devilsshadow:
relevant

http://xkcd.com/323/
[Motorola Photon 4G] LexLuger82:
It is dead
[Motorola Photon 4G] xTMFxOffshore:
Why is it you are always so negative? Yet don't contribute anything but complaining. Just curious.
[Motorola Photon 4G] wisconsinated:
lol pwnd..........
[Motorola Photon 4G] cybik:
no it isn't.

technically, both are "kangs" in that we both took some sources and compiled them but HEAVILY based ourselves on original work done by other parts of the CM team, or at least, that's what I think when I say "kang". I'm not assembling from binary, but rather compile everything.

edit: I'll go one further explaining my "based on moto" approach. Right now, my build is most definitely NOT based on ANYTHING precompiled as far as the kernel is concerned - I am using the SOURCE packages that motorola happily provides on http://sourceforge.net/projects/photon4g.motorola/files/PHOTON-4G/4.5.1A-1_SUN-154/ . Also, as for ANY other phone, there are binary components that would require too much reverse engineering to re-code in their entirety. The RIL is one such example; another would be the decoding libraries and layers that use the Tegra2 system to its fullest. Those are, like for any other phone, "kanged" off of Motorola's own system. But the kernel and core drivers related to wimax (disabled), wifi and vpn are compiled by me. I even modified the default kernel config by activating EXT4 when the kernel gets compiled.

I've been taken by other issues related to some very dark and stormy territories called "work" and "socializing", AND my Ubuntu was misbehaving. So I rebuilt my system and am now on Gentoo, and I managed to build a cm7 that's currently running on my personal photon.

It's still in the works, people. But I don't do this for a living, and I rather enjoy my off time when I have it.
[Motorola Photon 4G] jokersax11:
Amen
[Motorola Photon 4G] devilsshadow:
there you go, OP. You happy now?

Christ, some people would chain you to a desk and whip you to code faster it they could...

enjoy your off time mate and ignore the naysayers
[Motorola Photon 4G] Kcarpenter:
Being chained to a desk and whipped isnt normal practice in other software shops? Damn it i need a new job...its made me hate my favorite fetish...
[Motorola Photon 4G] xTMFxOffshore:
Lol. Nice
[Motorola Photon 4G] LexLuger82:
Dickrider
[Motorola Photon 4G] xTMFxOffshore:
Niceeeee. How did you manage that?
[Motorola Photon 4G] cybik:
Easily, surprisingly enough.

Basically, their radio is purely bi-mode. But what is considered "acceptable" when returning REGISTRATION_STATE stuff in GSM/UMTS is "frowned upon" by the source when returning the same data set for CDMA... but they don't give much of a /expletive/ about THAT.

I basically added a software override that gets enabled only when "tegraworldril" is detected as the RIL Interface for CM7 and reports "oi, there's this extra bit" but allows CM to continue on its merry initialization.
[Motorola Photon 4G] xTMFxOffshore:
Works only on GSM networks?
[Motorola Photon 4G] cybik:
see second screenshot. look at the mobile network type.

Now grab your jaw off the floor and put it back where it should be.
[Motorola Photon 4G] LexLuger82:
Wow
[Motorola Photon 4G] Doballa:
Nice
[Motorola Photon 4G] devilsshadow:
/tenchar
[Motorola Photon 4G] Kcarpenter:
YAY FOR NEW FAPPING MATERIAL!!!!!

*Proceeds to fap*
[Motorola Photon 4G] mediaon:
seems like cdma radio also need some improvement like the signal lower than zte cdma handset even it's at the same place Mopho is dropping 1 or 2 bars
[Motorola Photon 4G] cybik:
don't use my work and make a cm7 port yourself then.
[Motorola Photon 4G] anoob4eva:
Cybik,

I personally wanna thank you for all your hard work. I am running CM7 (Kang) on my Photon at this moment and I love it. I still haven't decided if the battery issue impacts my life or not. But everything else is working (CDMA/GSM/Sd card/Youtube/Gapps/Wifi/GPS/and everything else)

I'm not even sure why this is still Alpha. Great work.

(And I really enjoy that this is the only way I know of so far to get Arabic working properly on Photon. If anyone has another way, please let me know so I can try).

Thanks again cybik and all other devs working hard here.
[Motorola Photon 4G] cybik:
Still alpha because it's not in CM's buildbot. For me, it means the code is not quite there yet.
[Motorola Photon 4G] jbuggydroid:
Just wondering how things are going cybik with stabilizing the ROM? Willing to help with testing if you need more testers on the cdma side.
[Motorola Photon 4G] bearw815:
This thread needs to be closed.

cn7 is alive and well here....

http://xdaforums.com/showthread.php?p=18450433
[Motorola Photon 4G] anoob4eva:
Yes I agree.
[Galaxy S II Themes and Apps] adz63:
deleted .............
[Galaxy S II Themes and Apps] jonny68:
Cheers mate but i wonder what it's like, probably still slow as hell and cr*p, Android seriously have to improve this market it really is absolutely sh*t compared to the iClone App store (literally the only thing that is better on the iClone)
[Galaxy S II Themes and Apps] petsasj:
Google has done it once again! This version is even slower than the previous one :p Way to go.
[Galaxy S II Themes and Apps] jonny68:
cheers mate that'll save me the trouble of downloading and installing it, Google should be ashamed of themselves the serious amount of money they have made/are making and they have an absolutely useless Android market, surely it cant take that much to design a decent market?
[Galaxy S II Themes and Apps] petsasj:
I agree with you. Just imagine how the market runs on a low-end phone, like the Ace or the Hero, if on the fastest android phone, the S2, it runs like crap.
[Galaxy S II Themes and Apps] ams84:
thx

it's very smoth :D
[Galaxy S II Themes and Apps] Barni86:
Doesnt work for me. Im still at version 3.20.
[Galaxy S II Themes and Apps] adz63:
use root explorer to replace the vending.apk in system/app with the file i have attached or watch the videos if you are stuck
[Galaxy S II Themes and Apps] VDK:
I don't know why it works slow sometime!
[Galaxy S II Themes and Apps] ephraim:
Why did he (youtube video) say 3.3.1.1 when it clearly says that it's version 3.3.11..
[Galaxy S II Themes and Apps] zoule HCo:
I make CWM & recovery version.. so its more easy :D

Flash through recovery (recommended)

clear cache partition and delvik cache..

What's changed?

- New setting: Auto-update apps (presumably, sets all apps to auto-update mode, woohoo!)

- New setting: Update over Wi-Fi only

- New setting: Auto-add shortcuts (automatically adds homescreen shortcuts for new apps, a la Honeycomb)

- Smaller font

- New app drawer icon

- Microphone (voice command) button in search menu

- Star rating chart on app pages

- Minor UI tweaks

Market 3.3.11

http://www.multiupload.com/8J3DUB8LNX
[Galaxy S II Themes and Apps] d3l1:
if you replace it with root explorer don't forget to set correct permissions: rw-r--r--
[Galaxy S II Themes and Apps] Jibreil:
If you are using the Vending.apk method via Root Explorer, make sure you set your Permission to the following:

R W

R

R

... now Reboot the phone!
[Galaxy S II Themes and Apps] jonny68:
---------- Post added at 01:10 PM ---------- Previous post was at 01:05 PM ----------

cheers mate ill do this instead.
[Fascinate General] electric bill:
I've had this issue since the update to ED01 (or maybe before, I can't remember). Anyway it's darn annoying. I froze the screenshot apk to keep the screenshots from happening but there is still the issue with random back/return button presses. Sometimes it's the home key. Sometimes the search key will long-press and cause voice search to come up. It's mostly the return/back key.

I've had this problem on two Fascinates (the modem died on my first one and was replaced about a month ago). It happened with ED05 and it is now happening (although less frequently) with PWGB EH09 ROM v2.0b3 running ED05 modem. My daughters fascinate was having the same problem on stock ED05.

I've searched through several forums and it seems that lots of people have the same or similar symptoms with the fascinate/captivate as well as with the Nexus S.

I see that google tracked it as a problem earlier in the year and claimed to be working the issue and had a fix that was supposed to be rolled out. Never happened.

I think I've narrowed it down to only happening when the phone is using 3G data.

I'd like to locate and fix the problem but I could use some help getting started. For starters, I'd like to get a development environment set up and running so that I can build and test kernels. I can do this on my own but if someone could guide me so that I don't have to go through that learning curve, it would be appreciated.

My first thought is that it's a driver issue. In the source code there's a folder under src/kernel/drivers named "input" that has a bunch of drivers. Does anyone know which driver is used for this phone?

Thanks,

Dale

UPDATE: 15 Mar 2012:

I added a 100pf capacitor to the interrupt line on the cypress touchkey chip today. Everything works fine now. dmesg shows that I'm no longer getting any false interrupts. I downloaded a 6meg file over 3G and had zero false interrupts. Without the cap there would have been at least a couple of hundred (I use dmesg to check for false interrupts since I have printk statements in my code). I'll keep testing but I think this is it. I'll try to get some pics of the tack on showing where I added the cap. It's some tiny sh-t to work on. I had to do the soldering under a microscope. It was not easy. The cap I put on is a 100pf 50v X7R I bought from Digikey. Digikey part number 445-6856-1-ND. I got a 100 of them for <$6 with shipping.

I'll go back to the driver and remove the software fixes to see if the hardware fix takes care of the problem completely.

The parts are $0.028 each if you buy a hundred. They're less than a penny if you buy thousands. Seems a shame that Samsung couldn't pony up an extra penny to keep this problem from happening in the first place.

For those of you who don't want to crack your phone open, there's still the software (read: duct tape) fix.

Here's a link to the thread showing the hardware mod http://xdaforums.com/showthread.php?p=23725671#post23725671
[Fascinate General] sageDieu:
Yeah a lot of people have tried to fix this but nothing has ever worked. It's a well-known issue.
[Fascinate General] electric bill:
Yeah, that's why I'd like to try to fix the problem. Not to dismiss the skills of the other people who have tried, but I'm pretty good at finding bugs in hardware.
[Fascinate General] sageDieu:
Well more power to ya, if you fix it then you will make a LOT of people very happy. You should absolutely get in contact with some developers of kernels (jt1134, sixstringsg, Tk-Glitch, sswek2, etc) if you have any ideas or get anything fixed. I'm sure they will be glad to help you out with the issue and use any of your changes in their kernels.
[Fascinate General] dff_jx:
i have a SGS I9000. my problem is phantom presses of menu and back button. tried flashing to stock firmware etr (original was xeu). installed ics. all with no result. FINALLY found that it occurs only when using packet data (edge) we dont have 3g yet. i ve tried disabling packet data and using wi-fi and there is no preblem.

the diagnosis finally comes to this - problem related with packet data and may be (most probably be) related to software bug in the touch button firmware.
[Fascinate General] Domush:
It only seems to happen to me at my house, which is in a low signal area. I'm betting it is buried somewhere in the tower switching code, as my phone switches towers constantly at home.

Sent from my SCH-I500
[Fascinate General] electric bill:
Yes the problem only seems to occur for me when on 3g and not wifi. I've verified this with the three other fascinates in my house. I'm digging through the interrupt routines now using the kgb kernel source.

Does anyone know which interrupt line on the processor the cypress touchkey device is connected to?

I'm almost ready to break open the phone and start probing with an o'scope.
[Fascinate General] ssewk2x:
Hey Bill (I'm also a Bill, heh) :

You'll probably want to check out the changes I did for the V13.1 Glitch kernel. They seem to have at least severely limited the phantom keypresses. I did find some GPIO pins that were configured differently by the dpram driver and the mach-aries.c gpio (and gpio while sleeping) settings, and making those match up seemed to help a lot.

I'm an embedded guy, but more on the software side. I don't particularly want to tear my phone apart and hit it with a scope, but hey .. if you do that and find anything, go for it!

FYI, I was able to determine that the IRQ number used for the cypress-touchkey driver, and the one that's firing during the phantom key events, is IRQ 334 (0x14E). Without having a schematic to look at, though, I wasn't able to figure out what might be causing it to fire, nor even begin to guess why it has something to do with poor signal strength.

Anyway .. I've been beating my head against this problem for a long time .. so if there's anything else you'd like to pick my brain about, let me know.
[Fascinate General] Fallen89:
Downgrade

I have found that the only thing that works is to

downgrade

. I am however through uscellular so my phone is the mesmerize. I tried talking to a representative about my problem but all they would say is to upgrade. After multiple tries and different methods I downgraded to DI14 from EH09 and I have not had one problem since. Besides one with random menu flashes but it turned out to be the application Zedge. Hope this helps. If not at least I can say I tried.
[Fascinate General] electric bill:
What? _I_ found out that it is interrupt 334! :))
[Fascinate General] ssewk2x:
Yes, yes you did, lol. And you're probably going to end up fixing the whole thing before i get a chance to look at it again, lol.
[Fascinate General] electric bill:
I've been testing the code for about a day. I added the int test to the interrupt handler just now and I'll test for awhile. I'll prob also put it on my daughters phone since she uses hers about 10x what I do.
[Fascinate General] ssewk2x:
Excellent. You're welcome to drop by the glitch kernel thread, btw. I've got some folks testing there with good results so far.
[Fascinate General] Hymizzle:
Superclean Rom has screenshot removed. Also Geewiz 2.4.2 has a mod to remove the screenshot, just flash this in recovery:

http://db.tt/xERensX3

It happens when you have a low signal. It's was so annoying but no longer have that issue.

Keep me Fascinated.
[Fascinate General] SnrSuave:
It's not just the screenshot that's annoying. When using navigation, the phone will keep saying "this will end the navigation" as if the back button keeps getting pressed. Sometimes the menu comes up as well. Really annoying and kind of dangerous to have to keep hitting cancel while driving. Removing the screenshot app will not fix this. I'm really hoping someone finds a true fix for this. Otherwise I'm getting a new phone soon.
[Fascinate General] electric bill:
I actually just re-enabled screenshot on my phone. The glitch kernel ( http://xdaforums.com/showthread.php?t=1252871 ) has a fix that they're testing that seems to work pretty good. I'm not sure if it's in their release or just in testing. I think comradesven is putting the code into the kgb kernel too http://xdaforums.com/showthread.php?t=1364912

I've been running my own butchered up kgb kernel for a few days with the fix and it seems to help quite a bit.
[Fascinate General] th3b3:


I had the same problem...I went to big red and exchanged my phone...well they actually sent me a refurb... this was last week
[Fascinate General] dff_jx:
Thanks all u guys. I 'd really appreciate if u could find a standalone fix for this issue i.e. no modded kernel only the touchkey fix. Thanks again.
[Fascinate General] electric bill:
yeah, I'm on my third phone. there's been some speculation that phones built early (ie when they just started making them) don't have the problem. the data code on mine is 08/05/2011.
[Fascinate General] electric bill:
technically if we change the driver code, which is in the kernel then it's been modded...

If you want to run fully stock ROM and see this problem go away then I think you can add a 120pf cap from the interrupt pin on the cypress chip to ground. I haven't tried it yet but I'm going to as soon as I get done testing the s/w fixes.
[Fascinate General] dssheeley1:
Any updates for this topic?
[Fascinate General] ssewk2x:
Still beating on it.

Bill (the op) has been writing a lot of filter code that sort of helps eliminate the symptoms (i/e: keeps false interrupts from being wrongly registered as keypresses), but the problem is still there and is still a hardware one.

I'm working (very slowly) at getting his stuff into the latest ICS Glitch kernel.

He's also contemplating a hardware mod that requires a microscope and a very tiny soldering iron. I'm scared...
[Fascinate General] electric bill:
Yeah. Here's the work we've been doing. This thread pretty well explains it:

https://github.com/Efpophis/Glitch/issues/9

Here's the kernel that I've been running:

https://github.com/dmriley/kgb

Make sure you use the dev version.
[Fascinate General] electric bill:
Whaaaaahahahahahaaa
[Fascinate General] andymetoo28:
mine used to do phantom screenshots a lot, but i found that if i "wiped the grease" off the key it kinda fixed it. dunno if its left over sweat residue or what. yummy huh?
[Fascinate General] neh4pres:
holy crap man.. To bad you probably didn't make a video of your accomplishment. It sounds very scary.And if i know my soldering skills,i would have that white chip covered in solder lol. Are you going to make your own thread so i can follow this?
[Fascinate General] ssewk2x:
Nice work, man. How would you feel about accepting donations + shipping charges to do this on some other folks' hardware?

I'd do it myself, but you lost me at "microscope."
[Fascinate General] electric bill:
:)

I bought one of these for each member of my family last year for Christmas so I have four of them to modify. This was my big motivation for finding a fix. I was tired of the kids complaining and saying "dad, when can I get rid of this defective piece of junk and get an ip---e?". I still have a year left on the contract (and I'm _not_ an apple fan).

I Just did the mod to my sons phone. His is completely stock EH03 rom/kernel. This time went much, much faster. I'll have to pry my daughters phone out of her hands to bring it in to work. I rooted hers and have been updating it with the mods as I went along so she's not been complaining about the screenshots. She has been complaining about the "sleep of death" tho so I'll probably put her back to stock.

As far as doing it for others, There's two problems.

1) I do the mod at work because this stuff is so small and my eyesight isn't what it used to be and I don't have a microscope at home. I'm pushing it a little by using company equipment to do this. They make us watch training videos about this kind of stuff. But nobody's going to complain if it's just my own phone and I do it on my own time and I supply all the parts and it doesn't cost the company anything etc. However, if I start using company equipment to make money.... I'm out of a job. They'll make a training video out of me. That's a huge problem for me on account of I use my paycheck to feed and house my family.

2) If I dork up your phone while I'm doing the work (or it goes up in smoke three days after you get it back), you're gonna be mad:mad: and want me to replace it. As stated in problem#1, I already have plenty of things to use my paycheck for.

Aside from that, If you want to send me your phone, along with a microscope and a liability release, I'd be glad to do this mod for you. :D
[Fascinate General] MLBZ521:
Bill! I'd hug you for this if it's a 100% fix....My phones been bugging me with this for as long as I've had it. Want to make this back story quick if I can... It ties into one of your posts here where you stated you thought this problem is more prevalent on newer models and not early production devices. I can debunk this as I have a Pre-Release (Pre-Production) Run Captivate. Build date is 10.04 and battery date: 2010.3.30. So I don't think that has to do with it.

Since I've had this phone, before AT&T released to the public, my Search button would randomly flash/press. Some ROMs have worked better, some worse. Some work great at first, but the longer it's on there the worse it gets.

Normally I'm able to ignore it or get by, or just stop using it when it starts tripping out really bad...but I started a new job a couple months ago and need to be able to use my phone more effectively during the day...which isn't always a possible.. I just happened upon this thread after searching how to just completely disable the search button itself, but I'd rather FIX it than just cover it up.

Anyways... Where specifically physically, did you solder the cap? (Pictures would be great too!) I've had many years soldering experience and produce pretty clean work, compared to a lot of other people I've worked with...

I may wait a little while longer before I do it to make sure your phones don't burn out as you mentioned, heh...or at least, wait as long as it takes to get the caps from DigiKey...lol

I appreciate your help with this and if it works and solves my problem I will do doubt have to make a donations for your time and research.

Feel free to PM me or just reply here to keep the knowledge public!
[Fascinate General] neh4pres:
Bill did a complete write up I'm the general section with pics. I would link but can't atm
[Fascinate General] coolpoete:
Hey guys,

Anyone know if there is a software fix for this yet? I'm looking into it for a friend of mine and don't see anything recent. Has everyone moved on to other devices??
[Fascinate General] neh4pres:
The software is built into the icy glitch kernel
[Fascinate General] jeddster2013:
Really? I'm running on Icy Glitch and still having problems with it..