yashsingh1/xdaforums huggingface dataset:
[Galaxy 3 General] smekkos:
Hi,

wanted to let everybody know that the (homemade) Jig used to unbrick a galaxy S

works perfectly on a galaxy 3! (tested with my gf's). this will enable download mode without the 3 button combo! info on the jig can be found here: http://xdaforums.com/showthread.php?t=819551
[Galaxy 3 General] Kaleptik:
Does this also work for a hard brick?
[Galaxy 3 General] i_rnb:
wow..!! :O
[Galaxy 3 General] smekkos:
nope this is only for a soft brick. u should read the post in the link al the info is there. u can only force download mode if the bootloader is (semi) intact
[Galaxy 3 General] Kaleptik:
That's hard for us to do lol. I think everyone has come across the fact that the bootloader shouldn't be flashed.
[Galaxy 3 General] smekkos:
maybe true i'm not in that much into the galaxy 3 game, but for me with the galaxy S it saved my life. so perhaps in the future with gingerbread roms where u must change the bootloader. mine got screwed downgrading gingerbread to froyo for CM7.
[Galaxy 3 General] Kaleptik:
That IS useful :)
[EVO 4G General] DirtyShroomz:
Seems like God has it's issues too

http://androidandme.com/2011/04/car..._campaign=Feed:+androidandme+(Android+and+Me)

Sent from my spaceship!
[EVO 4G General] mattykinsx:
But but but ...Verizon is God.

This is what I've been saying, technology isn't perfect.

No amount of money can protect you from problems.
[EVO 4G General] DirtyShroomz:
Sprints 4G has not gone down and we have five times the amount of users. 3G works fine in most areas except his borough on NY.

Either way, tech is tech, things happen.

Sent from my spaceship!
[EVO 4G General] popular nobody:
You know I could explain what went wrong here, but I'm slightly enjoying the I told you so feeling. Also, I'd rather wait to see it reach 2 million LTE subscribers before I mention my reasoning. Having said that, Verizon's LTE strategy is fantastic for the consumers, and their 3G/4G offering is currently better than Sprint's. To say your carrier's 3G works fine everywhere but NYC is laughable and silly. Steps were made to make both 3G/4G more enjoyable for the customers, and your patience will be rewarded.
[EVO 4G General] Papa Smurf151:
Bwahahaha hmmm I wonder if he gonna show up. I'm sure he will in here eventually
[EVO 4G General] DirtyShroomz:
Sprints network works fine except areas being upgraded where towers are being removed and integrated into one, we know this already, so yes it works fine in most areas believe me. The only reason I mentioned NY is because that's his area.

Sent from my spaceship!
[EVO 4G General] CheesyNutz:
this will get good !
[EVO 4G General] NewZJ:
lets not hate
[EVO 4G General] gqstatus0685:
Thank god I have the AT&T network to fall back on when it comes to data. I live in NJ and the service has gone to ****s.
[EVO 4G General] tempe38:
Sprint's network works great, except where it doesn't. Their 4G has never gone down, especially where it hasn't gone up yet. :p
[EVO 4G General] wfrandy:
Well, apparently I don't live in "most areas". Speeds here in Reno, Nevada range from barely tolerable to pathetic. At my house I average about 200 kbs down with a low of 87 kbs to just over 500 kbs. At work, in the middle of town, it averages a little better, around 800 kbs, but is much more erratic with lows around 100 kbs, and very rare highs of around 1600 kbs. Bottom line though, virtually all other carriers are faster than Sprint is here, by a pretty good margin. And it has been that way for about six months now. And then their is the 4g that was promised by the end of the year when I got my phone last June, lets just say I am not holding my breath. I think it would be a pretty good bet that all the other carriers will have 4g here before Sprint does.

That said, I am not necessarily a disgruntled customer. With the exception of Verizon, Sprint has the best coverage here, But Verizon's 4g probably won't get here any sooner than Sprints. ATT's phone call quality sucks, even though their 3g data speeds are at least 2-3 times faster than Sprint on Sprints best day. And Tmobile has the best speed of all, but their coverage totally sucks. So they all have their pros and cons. I'll stick it out for another year, until my current contract runs out. If Sprint doesn't get their act together by then though, I will definitely consider moving on.
[EVO 4G General] rugedraw:
I've been with Sprint since 1999 and I'm not going anywhere; I'm a stick it through with them until their network gets better. However, I doubt that Sprint has been integrating the new system into the old one for over half a year in my area. In that amount of time, you would assume that at least one tower would be upgraded by now. My 3G service has 1x speeds everywhere I go in Miami.

Maybe it's one of those things where they can't flip the switch until EVERYTHING is upgraded......I don't know. However, anytime my girl sends me a short video of my kid doing something cute, it's a 20+ minute wait to download 5 MBs if I don't have 4G coverage or WiFi. I used to brag about how fast my phone was and now I try to sneak out of any conversation that has to do with data speeds. lol
[EVO 4G General] Award Tour:
DirtyShroom is thirsty to make his employer look good. Networks go down, and you act as if any of Sprint's network has never gone down before. Guess what, it has, and it probably will again.

BTW - I have absolutely no affiliation with Verizon. Don't even have an account with them (EVO/Sprint + ATT/iPhone). What I have said in the past is that:

A) Sprint's EVDO network in NYC is pathetic right now, and most signs point to overcapacity.

B) Verizon's LTE is both faster and more usable because of it's frequency.

So it seems as if Verizon's LTE network is currently down, doesn't effect me, and by the end of the day, it probably won't effect anybody.
[EVO 4G General] DirtyShroomz:
So now you lie? You clearly stated you moved one of your two lines to Verizon. I'm just showing you that even Verizon has issues. This is clearly affecting all 500k users.

Sent from my spaceship!
[EVO 4G General] Zabalba:
You should ;)
[EVO 4G General] Award Tour:
Find the post. You won't because it's all in your head. You choose to believe what you want to believe.
[EVO 4G General] DirtyShroomz:
Wow... So you never said you moved one line and were waiting until the Nexus to see if the network is fixed by then? Must have been another Award Tour or I could be completely wrong. Not searching on my phone for the post though.

Sent from my spaceship!
[EVO 4G General] mattykinsx:
I distinctly remember this being said as well.

Let's own up to what we say.
[EVO 4G General] dirkyd3rk:
I even remember you saying you moved a line to Verizon lol. People dont forget man!
[EVO 4G General] Papa Smurf151:
Agreed I remember that as well
[Android Software/Hacking General [Developers Only]] Dbrock1980:
what im looking to do is in the blur desk dock is when i press the alarm button i want it to use the GB time and alarm app instead of looking for the blur clock (which makes it FC) is there a guide somewhere or something to edit the button in the blur desk dock to make it point to a different app than the one it wants to go to?

not sure if that makes sense
[Desire Android Development] Kameo:
Hi guys, as the title says it's a work in progress, so please don't flame.

I was tired of waiting for the Trackpad2Unlock mod for GB-Sense roms to come, so i decided to give it a shot.

When i was on RCMix HD, i flashed a v1.84 update.zip to enable the trackpad2unlock feature.

So i unziped that file, and noticed that it only replaces the original HTCLockscreen.apk by another one.

I then decompiled both of them to see what were the differences.

Quick md5 hashes showed that only one file was modified: HtcLockScreen.smali

I then compared the original and modified files:

Original:

.line 800
.local v0, msg:Landroid/os/Message;
const/16 v1, 0x14

if-eq p1, v1, :cond_3e
const/16 v1, 0x13
if-eq p1, v1, :cond_3e
const/16 v1, 0x15
if-eq p1, v1, :cond_3e
const/16 v1, 0x16
if-eq p1, v1, :cond_3e
.line 804
iget-object v1, p0, Lcom/htc/lockscreen/HtcLockScreen;->mReminderView:Lcom/htc/lockscreen/HtcLSViewInterface;
if-eqz v1, :cond_3e
.line 805
iget-object v1, p0, Lcom/htc/lockscreen/HtcLockScreen;->mReminderView:Lcom/htc/lockscreen/HtcLSViewInterface;
invoke-interface {v1, p1, p2}, Lcom/htc/lockscreen/HtcLSViewInterface;->onKeyDown(ILandroid/view/KeyEvent;)V
:cond_3e
move v1, v4
.line 809
goto :goto_20
.end method

Modified:

.line 801
.local v0, msg:Landroid/os/Message;
const v1, 0x17
if-ne p1, v1, :cond_2d
invoke-virtual {p0}, Lcom/htc/lockscreen/HtcLockScreen;->goToUnlockScreen()V

:cond_2d
const/16 v1, 0x14
if-eq p1, v1, :cond_46
const/16 v1, 0x13
if-eq p1, v1, :cond_46
const/16 v1, 0x15
if-eq p1, v1, :cond_46
const/16 v1, 0x16
if-eq p1, v1, :cond_46
.line 805
iget-object v1, p0, Lcom/htc/lockscreen/HtcLockScreen;->mReminderView:Lcom/htc/lockscreen/HtcLSViewInterface;
if-eqz v1, :cond_46
.line 806
iget-object v1, p0, Lcom/htc/lockscreen/HtcLockScreen;->mReminderView:Lcom/htc/lockscreen/HtcLSViewInterface;
invoke-interface {v1, p1, p2}, Lcom/htc/lockscreen/HtcLSViewInterface;->onKeyDown(ILandroid/view/KeyEvent;)V
:cond_46
move v1, v4
.line 810
goto :goto_20
.end method

Basically it just inserts another check for var 0x17 (trackpad?) and then unlock the lockscreen if true.

So i did manage to update the Gingerbread Sense HTCLockscreen with this little hack.

No more need to slide down to disable the lockscreen, pressing down the Trackpad does it.

However... it doesn't wake the phone through the trackpad.

We still need to press Power :-/

To make a long story short, i managed to get tp2unlock, but not tp2Wake&Unlock...

I did try several other methods, like this one but with no go:

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

So if someone wanna give a hand... Feel free, the whole community is waiting for this mod.

Thanks for reading and your help :D

PS:

Provided in the link are the uncompiled files for

v1.84 original (the original RCmixHD a2sd htclockscreen.apk files)

v1.84 modified (the modified version to enable trackpad 2 wake and unlock)

gb sense tp2u (the modified Gingerbread Sense version to enable trackpad 2 unlock).

Edit:

I forgot to provide the HTCLockscreen.apk, just push it (with QtADB!) to system/app/.
[Desire Android Development] daddyspud:
nice work at least this is a start and maybe some who nows a little bit more will help
[Desire Android Development] cadavreatpinopl:
I don't think it depends on framework settings. As I developed AOSP for other device it was always a matter of editing keylayout file with adding/removing WAKE flag. Maybe just adding that flag to PROPER keycode will solve this? I tried but without success.

What else - I'd like to point you to frameworks/policies/base - there are files that describes some power management.
[Desire Android Development] Ninolina:
Delete... Wrong tread..:(
[Desire Android Development] bg_man:
Why don't you try with this one ;)
[Desire Android Development] Alex-V:
Good work... :)

but i think that are 2 things needed...the changed lockscreen and this trackpad to wake up...maybe try the same way with the file from this thread:

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

with kind regards...Alex
[Desire Android Development] ziggy1001:
I did does it work reliably for you? over a week now with this mod and ~50% fail rate
[Desire Android Development] KoTiX2:
I'm using CoolAcesv2 rom and looking at the inputs with the adb shell and the getevent command, seems like for the trackpad is still needed the curcial-oj.kl file as described here http://xdaforums.com/showthread.php?p=7236745#post7236745.

This is what i got:

add device 1: /dev/input/event9
name: "compass"
add device 2: /dev/input/event8
name: "curcial-oj"
add device 3: /dev/input/event7
name: "dummy_keypad"
add device 4: /dev/input/event6
name: "lightsensor-level"
add device 5: /dev/input/event5
name: "bravo-keypad"
add device 6: /dev/input/event4
name: "proximity"
add device 7: /dev/input/event3
name: "synaptics-rmi-touchscreen"
add device 8: /dev/input/event2
name: "projector-Keypad"
add device 9: /dev/input/event1
name: "projector_input"
add device 10: /dev/input/event0
name: "h2w headset"

/dev/input/event8: 0001 0110 00000001

Btw i already pushed the curcial-oj.kl in the phone but it doesn't do anything so i beleive it need the modded apk too.

I hope this helped a bit. :P
[Desire Android Development] Kameo:
I did try it... Here are my tests so far:

- created, edited and pushed system/usr/keylayout/curcial-oj.kl with the following, and it doesn't work.

key 272 DPAD_CENTER WAKE_DROPPED

- also edited the system/usr/keylayout/bravo-keypad.kl with the same line, no go.

Gonna dig with other tests, there must be a way to get the code to trigger the power button.

Once i get it, i think that i can replicate the snippet and get this to work.

Wish me luck.
[Desire Android Development] ziggy1001:
Good luck mate:cool:

If you look around there are a couple of threads where people have tried editing curcial-oj.kl and bravo-keypad.kl which seems to have no effect on trackpad. WAKE_DROPPED when added to menu or home in bravo-keypad.kl does give an unreliable wakeup but half the time it doesn't work. General consensus seemed to be GB uses a different location
[Desire Android Development] Kameo:
Thanks Ziggy.

In fact when i edit my bravo-keypad.kl, it works

all the time

with Power or Home or Menu, but

not a single time

(and believe me, i tried like 25 times in a row) with the Trackpad.

I'll investigate a little bit more.
[Desire Android Development] ziggy1001:
Well thats a step in the right direction:)

Could you please upload your bravo-keypad.kl with reliable menu home wake, myself and several others all have it working, but unreliably. Have you tried it for over 24H, for me if the phone has been recently used it seems to work but after a prolonged period in standby it generally seems to fail:(
[Desire Android Development] Ninolina:
Can you share that file which works all the time for Menu button? That's all I need and it will solve my problem..:-) Can you do that? Thanks in advance..:-)
[Desire Android Development] Kameo:
Ok, bad news, you guys are right.

If the phone is off for a while (more than 2-3 minutes), the keys don't wake the phone.

As if they were not power supplied.

Looks like a powersave function, sorry guys.

We still stuck to the same position.

Anyway i tried decompiling other android files to check which one triggers the PowerOn function, but haven't found it yet.

Anyone got a clue (i tried Rosie/SystemUI/Core/AndroidPolicy...)?
[Desire Android Development] ziggy1001:
I think it's obviously hidden very well (Damn HTC and their lack of sensible ergonomic design:mad:)

I did notice NeoPhyTe.x360's latest GB rom had "Wake UP desde Menu, unlock Trackpad" listed in the Features: sadly about 20mins after i queried this it was changed to "Wake UP from Menu" whether that's the same unreliable mod we have i don't know can't be arsed to flash just for that

But hey even more people will be looking for it now;)
[Desire Android Development] Kameo:
Yep, hopefully we might found it.

Just noticed Neo's back, so gonna give his Ginger-ReflexS/SenseHD rom a try.
[Desire Android Development] ziggy1001:
I think you are right about power save disabling menu wake when i put the phone on charge after 20 mins menu wake is still working

So presumably default setting is only Power button has power all the time maybe that's a solution allowing power to menu /trackpad always
[Desire Android Development] bg_man:
I've played with it but for half an hour.

I've found the GB still not stable enough and decide to wait for official HTC release.

So you are seems to be right.
[Desire Android Development] Kameo:
Little update.

I managed to debug which functions are called when the relevant button is pressed (power and all the others enabled in bravo-keypad.ki but 272):

For example, while pressing Power (keycode 26 or $1a), i get this:

Then it triggers other functions (turn lights on...) and then enable the lockscreen.

However, when i press the Trackpad, all i get is this:

Which looks like a motion/sensor tracking routine...

It got me puzzled, i really don't know where to go from here... :-/

Full debug log for Power button down here:

WindowManager - interceptKeyBeforeQueue keycode=26 screenIsOn=false keyguardActive=true
KeyguardViewMediator - wakeWhenReadyLocked(26)
dalvikvm - --- called into dvmAbstractMethodStub
InputManager-JNI - An exception was thrown by callback 'interceptKeyBeforeQueueing'.
InputManager-JNI - java.lang.AbstractMethodError: abstract method not implemented
InputManager-JNI - at com.android.server.PowerManagerService.getProximitySensorActive(PowerManagerService.java)
InputManager-JNI - at com.android.internal.policy.impl.PhoneWindowManager.interceptKeyBeforeQueueing(PhoneWindowManager.java:2749)
InputManager-JNI - at com.android.server.WindowManagerService$InputMonitor.interceptKeyBeforeQueueing(WindowManagerService.java:5255)
InputManager-JNI - at com.android.server.InputManager$Callbacks.interceptKeyBeforeQueueing(InputManager.java:404)
InputManager-JNI - at dalvik.system.NativeStart.run(Native Method)
InputDispatcher - notifyKey - deviceId=0x0, source=0x101, policyFlags=0x32000002, action=0x0, flags=0x9, keyCode=0x1a, scanCode=0x74, metaState=0x0, eventTime=5904047125987
LightsService - [LedInfo] setLight_native light=2 colorARGB=-11447983 flashMode=0 onMS=0 offMS=0 brightnessMode=0
lights - set_light_buttons_func: on=5329233 brightness=81
power - *** set_screen_state 1
SensorService - noteStartSensor: uid = 0x3e8, handle = 0x4
LightsService - [LedInfo] setLight_native light=0 colorARGB=-11447983 flashMode=0 onMS=0 offMS=0 brightnessMode=1
WindowManager - interceptKeyBeforeQueue keycode=26 screenIsOn=true keyguardActive=true
InputDispatcher - notifyKey - deviceId=0x0, source=0x101, policyFlags=0x2000002, action=0x1, flags=0x8, keyCode=0x1a, scanCode=0x74, metaState=0x0, eventTime=5904147369869
SurfaceFlinger - Screen about to return, flinger = 0x319288
LightsService - [LedInfo] setLight_native light=2 colorARGB=-8355712 flashMode=0 onMS=0 offMS=0 brightnessMode=0
lights - set_light_buttons_func: on=8421504 brightness=128
LightsService - [LedInfo] setLight_native light=1 colorARGB=-16777216 flashMode=0 onMS=0 offMS=0 brightnessMode=0
WindowManager - needSensorRunningLp, mCurrentAppOrientation =1
HtcLockScreen2.0 - HtcLockScreen: onResume
[Desire Android Development] emf12:
something new here? because this problem does not yet use Gingerbread Sense 2.1 ROM's for long time:(
[Desire Android Development] Kameo:
I didn't quit the work.

I tried another way, 2 days ago, with 6 hours of work... for nothing :-/

I've got another idea.

For now the only new GB rom running Trackpad2Wake/Unlock is Cyanogen.

So imma dig the code and check what i can borrow to implement in other roms.

But i really don't know where to start and i do it on my spare time... I tried yesterday for an hour but didn't find anything relevant.

If other wanna jump in, it would be great ^^

Anyway, just seen that a final Sense GB rom was leaked, maybe they finally included the tp2u. That would be so great.
[Desire Android Development] ziggy1001:
Sadly not fixed seems ergonomics not important to HTC which is BONKERS
[Desire Android Development] tristan202:
Sense 3.0 Lockscreen Trackpad2unlock

I have modded the new lockscreen from some of the GB Sense roms to make use of this feature. I used the one from InserCoin v16 as base, but it should work for any GB Sense rom.
[Desire Android Development] jungoed:
Doesn't work on oxygen 2.1.1
[Desire Android Development] sbdags:
Yeah it won't work on GB due to the way the power is not polled on the buttons.
[Desire Android Development] ziggy1001:
Thanks for the tp2unlock definitely a move in the right direction, just need to allow power to the buttons permanently in standby for wake function
[Desire Android Development] nimrodity:
it worked with froyo why did the change that.

i would be happy with menu-2-wake for now,but cant find any working,

anyone help please
[Desire Android Development] Muxeu:
Yep, it's work. Menu to wake, than trackpad to unlock.

Is any way to make just trackpad for wake&unlock?
[Desire Android Development] nimrodity:
didnt work for me on reflextsense 1.9.5,hm...
[Desire Android Development] ckhacks:
Works on Leedroid v16, but not if phone if in standby for more than a few minutes...
[Desire Android Development] sbdags:
Yeah it's the usual problem. There is no fix yet. Nice try though ;)
[Desire Android Development] nimrodity:
yes same here and in my opinion that is working,but eventually someoe will come up with a solution
[Desire Android Development] :
Tristan's mod is working fine - menu to wake, trackpad to unlock. ROM used - InsertCoin GB v16 A2SD. Not ideal, would prefer both in one button, but at last something functional. Thanks guys!
[Desire Android Development] t-pip:
Good work so far, but it doesn't appear to work here. OK for a couple of minutes then stops. Looks like the Power Save feature is killing it.
[Desire Android Development] sbdags:
Yeah good try Tristan but it's the same old problem - it only works for 5 mins then as long as you don't plug the phone in or touch the power button there is no way the menu button will wake the phone up.

Back to the drawing board unfortunately ........ :(
[Desire Android Development] oudbrood:
Redux 1.2 has also trackball wake. Maybe this code can help you.
[Desire Android Development] Kameo:
Can't be of any help for now, since it's based off GB-AOSP while we target GB-Sense...

I'm really out of ideas now, don't know where to look.

Should i decrypt libraries (.so files) or even the main boot.img, damn it's more complicated than i thought.
[Desire Android Development] snq-:
just a quick fyi: i have a working trackpad-to-wake solution without the infamous it-doesn't-work-after-a-while issue, will upload rsn
[Desire Android Development] chihliouma:
Hi SNQ-, please share the good news with us ASAP because I guess too many people are suffering this issue for a while and expect your solution eagerly. Thanks for your great work.
[Desire Android Development] Kameo:
Hi SNQ, great news.

In the meanwhile i downloaded your last git repo in order to compare it with changes in Cyanogen.

I think that i'm after a nice trick : WakeWhenReadyLocked, wanna share what you changed?

Thanks again mate, your doing an impressive work Reverse Engineering all that HTC stuff.
[Desire Android Development] snq-:
herro my name is dr dpadfix

here are the files required for proper dpad2wake functionality:

dpad2wake_fix_v01.7z

contents:

libui.so: hexedited libui.so (to route dpad key-events to PhoneWindowManager)

zImage-v03: hexedited kernel image (oj will not choke after a while when screen is off)

curcial-oj.kl: input device layout file

please note that this is not a flashable zip, and it is meant to be used by rom maintainers

in case you messed with bravo-keypad.kl, restore the original one
[Desire Android Development] coolexe:
awesome bro...:D:D
[Desire Android Development] ivicask:
Now i just need modified version with disabled power button, so that only trackpad wakes up phone, and i can die happy :)
[Desire Android Development] Kameo:
:eek::D:eek:

Impressive work SNQ, as always. Damn, i would have never sorted it out.

I mean, editing .so files, i was on a whole other route...

So basically, we need to:

- copy curcial-oj.kl to system\usr\keylayout

- copy libui.so to system\lib

- and to flash the kernel image.
[Desire Android Development] ziggy1001:
Apologies for dumb question but with QtADB where do i put zImage-v03 i assume i keep that file name?

Whoops a daisy Flash kernel image:o
[Desire Android Development] andQlimax:
Do you work as develoepr for htc or you are a genius? :D :p

Someone said you are a god, that wrong..you are god, unique!

Don't stop helping the desire community..we need you! Thanks! :)
[Desire Android Development] 3f1f37:
Dude your not GOD, your just insanely blessed by the almighty one and may he keep on blessing you.