yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Development and Hacking General] cmonex:
just some small corrections:

in 05 20 A0 E3 01 10 A0 E3 73 EF A0 E3 03 40 A0 E3 00 50 A0 E3 00 30 80 E5

you shouldn't need to change 00 30 80 E5 etc to 01 xxxxxx. that would corrupt the STR instruction there unnecessarily. so, generally, the byte directly before x0 80 E5 should not be changed.

and the binary part is not really needed to calc the numbers. the desc

"4F 3F A0 E3 02 30 83 E3 45 2F A0 E3 05 10 A0 E3 02

The 4F is in binary = 1001111

Now take the 02 from the values 02 30 83 E3 and convert it to binary = 10

Add this to the end of the 4F binary string = 100111110"

worked only because the F in 3F means shift the value left by 2 (multiple by 4), so when you attach the 10 in binary that will perform this shift too luckily.

if it were 3E then this desc would be incorrect.

here is the precise table to do these calculations:

value = first byte multiplied by x in second byte (little endian)

1 = 40000000;

2 = 10000000;

3 = 4000000;

4 = 1000000;

5 = 400000;

6 = 100000;

7 = 40000;

8 = 10000;

9 = 4000;

A = 1000;

B = 400;

C = 100;

D = 40;

E = 10;

F = 4;

(this is in hexa!)

you only care about the second number in that byte.

example: 4F 3F A0 E3

4F is multiplied by 4 (as showed in second byte 3F).

the rest doesn't matter.

this is followed by 02 30 83 E3

first byte here means you add 2.

the rest doesn't matter.

(actually if the second byte (30) doesnt end in 0 then you have to use the table above)

so final value is 4F * 4 + 2 = 13E in hex, i.e. 318 in decimal. :)

i guess the rest is ok, and i can't explain it as well as he did. :) but maybe this helps someone.
[Windows Mobile Development and Hacking General] c0rnholio:
Thank you, Sir! That was exactly the part I was sometimes wondering about when my calculations failed...

BTW: You explaination is clear and easy to follow. Thanks again.

Cheers
[Windows Mobile Development and Hacking General] Andy Phillips:
Ahhhh....

But does this get us any closer to using v4!?:D
[Windows Mobile Development and Hacking General] c0rnholio:
No, but it clear some things up.

I'm currently investigating v4 and a lot of things have changed.

The logging is now in binary format, and it seems that txt-logging is also supported but I'm not able to activate it. Only binary logs and they are not very helpful. It seems that the compliance check in bbc 4 has been extended to check for the device type. I found some registry keys that definately affect the connection state.

I sent a request for some info to the hermes guys, but none answered. As long as I don't get that info I cannot prove my theory.

These keys are:

HKLM\System\Versions\DeviceVersionInfo

Access=?

DeviceType=?

FunctionCode=?

Method=?

Request: http://xdaforums.com/showpost.php?p=1273817&postcount=18

If you change one of these keys (they are there in the 2.1.2.54 version on my ameo also) and reregister the connection could not be established anymore. If I change it back and reregister everthing is fine again.
[Windows Mobile Development and Hacking General] Andy Phillips:
Thanks!

Good to know that you're working on this. Personally I'd love to help but some of the hex stuff is way over my head...

But if you need me to test anything on my wizard let me know!
[Windows Mobile Development and Hacking General] gladiac:
I still think a wrapper providing the version information for bbconnect would be the finest solution since you don't need to hack system-dlls. Or am I wrong? It would be supernice to have some kind of configfile containing the version information bbconnect needs and the wrapper just provides them to bbconnect. That way you could run every bbconnect on every windows mobile.
[Windows Mobile Development and Hacking General] c0rnholio:
I totally agrre with you, but it's not so easy. It seems that you need to write a loader (and BB 4 comes with it's own loader) wich calls the BB Software and than intercepts the calls to GetVersionEx (AND for BB 4 the calls to the device version info).

I found that the registry keys I asked for are the same on my device, which is not allowed to run BB 4, and a Hermes which IS allowed to run the BB 4 client. So I asume that they read out the deviceID from the System (like HERM100, HERM200 and so on).

I currently don't have the time to get that deep into the system and get knowledge about how to write such a loader. Thus NO SOLUTION (at least from me) at the moment.

I can only make assumptions because they seem to have disabled the clear text logging.

Cheers
[Windows Mobile Development and Hacking General] palmop:
I have it working on my S621 with T-mobile WM6 rom. Download the cab from:

http://www.sems.org/entry.asp?ENTRY_ID=225

PalMop
[Windows Mobile Development and Hacking General] beginner:
The link for bbconect activesync doesn't work...
[Windows Mobile Development and Hacking General] palmop:
Link is fixed :)
[Windows Mobile Development and Hacking General] walshieau:
guys you dont need to write a loader... im using v4 with the Hermes and posted my results a few weeks ago..
[Windows Mobile Development and Hacking General] titus666:
The problem at this stage at that v4 only works on the Hermes and the Dash...
[Windows Mobile Development and Hacking General] gladiac:
Which is a great problem for me and my artemis. Using WM6 there is actually no official blackberry connector supporting it.
[Windows Mobile Development and Hacking General] Andy Phillips:
Opened BBService.dll

Guys,

I opened bbservice.dll with a hex editor and found that the Universal and the Wizard are named in this file....right where it looks like it's doing some version checking! Maybe this has something to do with it?

:confused:
[Windows Mobile Development and Hacking General] eddie_f:
BBConnect on a PocketLoox T830

Hello cornholio,

hello everybody,

I've been following this thread now for a while and was very excited to try the BB Connect software on my Fujitsu-Siemens PocketLoox T830.

Basically the T830 is a WM5 device and best of all, the WM5 version number is 5.1.195 (Build 14955.2.3.0). No need to hex edit and reflash the rom. So I downloaded the MRE,unlocked the RAPI and changed the registry key for AKU to .2.0.0.

Then I downloaded the BBConnect software for the MDA Vario from the T-Mobile website (V 2.1.2.31). After 2 failed installations I finally got the installation working (something like gwes.exe, can't remember the exact error message).

Now the BBConnect Software says PIN Pending, shows the IMEI and does not connect to the network. The service immediately stops after I push on restart (not connected). When I check the info tab I can see the correct systemversion 208.108.34.203. Nothing wrong here, but the BBConnect client doesn't show a transport version number. It's just empty.

OK my private SIM card is not Blackberry enabled, but my company has several Blackberry enabled cards and I will try one on monday. Since I'm one of the BB admins this should be a piece of cake. Hopefully the BBConnect will connect to the network, but I fear that there's something wrong because there is no transport version number shown. Or is this just a cosmetic problem on my device?

Good work with the hack dude, I hope I can get this to run on my pocket pc, I don't like the BB devices much.
[Windows Mobile Development and Hacking General] KarmaNP:
Hello

I was wondering if anyone has hex values that will change the 5.2.1413 to 5.1.195. This is a new build for Universal and released by Ivan.

Thanks
[Windows Mobile Development and Hacking General] eddie_f:
Ok I tried the T-Mobile SIM card with blackberry now and the service is always stopped. When I manually start the service it says not connected for a few seconds and then stops again. The info tab says:

BlackBerry-Version:2.1.2.31

Transportversion:

Systemversion: 208.108.34.203

Devicetype: FUJITSU_SIEMENS-GPRS

As I said before, the transportversion info is empty. Maybe there is something missing on my device?

Does the devicetype play a role when the service tries to access the BB network?

Thanks in advance.

--edit:

I attached my BBLog.txt as zip file. You can see that the BB Connect Software fails on the devicetype and the hardware ID:

2007/6/11 15:57:56 486.061 PCBB eacb5962 DeviceMgr::getSystemVersion: INFO: normalized versions being used to derive OsVersion:
2007/6/11 15:57:56 486.061 PCBB eacb5962	szCEOSVersion: 5.1.195
2007/6/11 15:57:56 486.061 PCBB eacb5962	szAKUVersion: .2.0.0
2007/6/11 15:57:56 486.062 PCBB eacb5962	BBCWMAppVersion: 2, 1, 2, 31
2007/6/11 15:57:56 486.062 PCBB eacb5962 [DeviceMgr::GeneratePseudoRandomOsVersion] supplied with the following Device Information
2007/6/11 15:57:56 486.063 PCBB eacb5962	CE OS Version = 5.1.195 length = 7
2007/6/11 15:57:56 486.063 PCBB eacb5962	AKUVersion = .2.0.0 length = 6
2007/6/11 15:57:56 486.063 PCBB eacb5962	App Version = 2, 1, 2, 31 length = 11
2007/6/11 15:57:56 486.064 PCBB eacb5962 [GeneratePseudoRandomOsVersion] derived OS version: -798219573 (decimal), d06c22cb (hex)
2007/6/11 15:57:56 486.068 PCBB eacb5962 [bbHostNetGetSoftwareInfo] success: deviceClass="", deviceClassLength=0, version="208.108.34.203", versionLength=28, localization="d", localizationLength=2
2007/6/11 15:57:56 486.073 PCBB eacb5962 (I)reg: BB_CONNECTIVITY_NONE
2007/6/11 15:57:56 486.074 PCBB eacb5962 [bbHostNetGetHardwareInfo] success: hwId="358898001501712", hwIdLength=30, deviceType="FUJITSU_SIEMENS-GPRS", deviceTypeLength=40
2007/6/11 15:57:56 486.077 PCBB eacb5962 (E)reg: Unknown hardware id and device type
2007/6/11 15:57:56 486.077 PCBB eacb5962 (I)multitask: Failed to start tasks
[Windows Mobile Development and Hacking General] KarmaNP:
I tried the v4 with newer wizard and Universal roms and bbconnect 4.0 worked perfectly. It didn't work the last time I tried it about a month ago. I was looking for the new hex value but midget_1900 informed me that 4.0 works with newer wm6 roms and it did.
[Windows Mobile Development and Hacking General] beginner:
Does it mind that v.4 will run on Athena when wm6 comes or we found what to change?, cornholio, how is your agenda this days?
[Windows Mobile Development and Hacking General] Andy Phillips:
Which ROM's?

Any chance you that you know which rom's?

Myself, I'm interested in the wizard rom's but I'm sure other device owners would like to know!;)
[Windows Mobile Development and Hacking General] KarmaNP:
I'm using the core 2.0 for my wizard and Midget's lates rom for universal.

Hope that helps.
[Windows Mobile Development and Hacking General] beginner:
What is the AKU corresponding latest Midget?
[Windows Mobile Development and Hacking General] Andy Phillips:
Hmm

I have that very rom on my wizard..but I couldn't get BBC v4 to work! Did you have to change the AKU version?
[Windows Mobile Development and Hacking General] beginner:
BB 4 on ATHENA

I have it running!!! and after 3 softresets still alive...

only change aku to .3.0.0

new bb looks amazing, surfing directly on internet. Now the excel looks excel (it's the only one I made some check)

Note: it killed my today screen. first time I obtained to have it running, the spbdiary and clock on TODAY disappear, and after softreset the htc works 20% of the times. After hardreset, installing only the bb, the default calendar and so on on TODAY disappear and no way -I don't know how to do outside settings- have it again. Live is not perfect...
[Windows Mobile Development and Hacking General] Andy Phillips:
Cool!

What's your OS version?:D
[Windows Mobile Development and Hacking General] beginner:
wm 5.0, 5.1.465
[Windows Mobile Development and Hacking General] Andy Phillips:
Thanks

Thanks....

Now to find a wizard rom with :D that version!
[Windows Mobile Development and Hacking General] beginner:
As I said there are some collateral problems, at least for me, in TODAY screen. but we should solve.

Edit: Looks solved this issue if you reinstall today items after bb running for a while -and some softresets-
[Windows Mobile Development and Hacking General] walshieau:
To All...

All users of WM6... your device does not need to be hex edited...

RIM are now allowing 5.2.1238 (Build 17745.0.2.3) to connect to their servers... only this CE Kernel and Build have been approved at the Moment...

the new v4.0 software also checks for the Hardware Device its running on...
[Moto 360] niels-cil:
Hello,

The screen of my moto 360 goes randomly off and vibrates at that moment, just like when you dim the screen with your hand., but now I'm using it. It's very frustrating because I can't even open an app normally or the screen goed of and I need to start over again. Does anyone know how to fix this?
[Moto 360] Fizzit:
Having same issues with mine.

Really strange and really annoying. Its like when u cover it with palm. It vibrates and screen goes off but ur in the middle of trying to do something. Anyone else having this problem?
[Moto 360] michealcell:
Glad I'm not the only one having this issue, just got my Moto 360 today. I'll be in the Settings or other parts of the watch and it will just randomly turn off. It is really frustrating to deal with.
[Moto 360] footboydog:
I have the same issue. I have pretty hairy arms so I wonder if the hairs are somehow triggering the capacitive touch screen.
[Moto 360] bustanut666:
you guys try to do a reset on the watch yet?? not just a reboot..
[Moto 360] haroyac:
Any updates on this? I'm having the same issue
[Moto 360] Raphaello:
Any updates? I have the same issue :( I think it happend after udate to 5.0.2 but I'm not sure.
[Moto 360] nondescriptivenickname:
I'm also having the same problem. I picked up a new Moto 360 during the BBY sale rush of the last couple of days. At first it was buggy but the screen seemed to stay on while working with it. Then it had a system update, and since then most bug issues (like the faces not updating with the companion app changes) went away, however from that point the screen constantly shuts off, usually with a little buzz, while I'm interacting with the watch.

For instance, regarding the sensor used to turn off the watch if you palm it. I thought maybe that was it, so I was looking for a way to turn that off. I went into settings, and spend about 10 times of the screen shutting off before I could get to "accessibility settings" just to see if that might be there.

This problem occurs whether I'm wearing the watch or not (trying to eliminate arm hair or similar), and has occurred after a factory reset and re-pair with my phone (Note 4). Ambient sensor settings don't help, because all that does is make the screen go dark instead of off, but it still reverts back to the clock no matter what I was doing.

Any ideas? Any way to turn off a sensor perhaps, maybe in a custom ROM? Since this seems to be associated with an update near as I can tell, I wonder if a fix is coming from Moto or if it's too rare of an issue to be on their radar.
[Moto 360] nondescriptivenickname:
As an update, I replaced the watch with a new one, and this new watch is perfect. It started on outdated software which I left on for a bit to make sure it didn't show the problem, then I updated. Still no issues. I think there is a chance the problem is software regardless, but either way it must be a small portion of watches and isn't necessarily tied to any particular outside software influence (phone model or android version, or installed apps as NONE of those things changed). My advice to people reading this thread is to exchange the watch or get an RMA if possible.
[Moto 360] funkung:
Same Issue

Hi All,

I have the same issue. Sent it back for repair so let's see...
[Moto 360] cdf3:
Same issue here as well
[Android Q&A, Help & Troubleshooting] seVenaiLor:
Hi mates,

I just bought new device Overmax Vertis 4010 you. I tryed unlock bootloader by some programs: iroot, z4root, superoneclick etc. but nothing works, device is rebootint without root. I'm desperate, i really need this..

Secondly, i dont now how to make my statusbar transparent, i turned it on in nova launcher but still nothing.

can anyone help me?
[Galaxy Tab 2 Q&A, Help & Troubleshooting] umbesca:
Hello, first sorry for my english, I'm italian and fortunately google translator helps me, :D

My tablet GT-P5100 (wi-fi and 3G) does not light nor goes in download mode and does not turn on no lights battery charge. The warranty is out and samsung ask me 250 euro for repair it!!!! After several phone calls and emails with Samsung I have confirmed that there are no hardware faults and they were able to turn it on (as you can see in the attached picture).

I have opportunities to fix the problem or will I have to use it as a paperweight?

Help me, thanks
[Galaxy Tab 2 Q&A, Help & Troubleshooting] GuestK0058:
If you're able to get into download mode, you can simply flash a custom recovery or the stock rom. This tablet doesn't have a locked bootloader or KNOX.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] umbesca:
this is the problem! Does not turn on! Not without JTAG or similar
[Galaxy Tab 2 Q&A, Help & Troubleshooting] jrc2:
But can you get into download mode?
[Galaxy Tab 2 Q&A, Help & Troubleshooting] umbesca:
no :crying: but samsung service center yes :confused:
[Galaxy Tab 2 Q&A, Help & Troubleshooting] jrc2:
The picture you have in the OP shows it in download mode.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] umbesca:
is the photo I sent her samsung. I with any key combination I can put iun download mode and neither longer charge the tablet and I do not know how to do
[Samsung Galaxy Nexus] QA Bot:
Q&A for [ROM] [KTU84Q] Dreams version 5.2.3

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [ROM] [KTU84Q] Dreams version 5.2.3. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Samsung Galaxy Nexus] jjrojo:
Trying to boot, google logo bucle.
[Samsung Galaxy Nexus] Carlos_Manuel:
What's the type of your Nexus's eMMC chip?

You could try to get it booting by flashing this kernel:

https://drive.google.com/file/d/0BxlYDVLp_RkMU25hNkI1SDJqMjQ/view?usp=sharing

fastboot flash zIamge zImage

if that command doesn't work then try fastboot flash zImage
[Samsung Galaxy Nexus] jjrojo:
I have V3U00M eMMC chipset.

I'l try right now.
[Samsung Galaxy Nexus] Carlos_Manuel:
Ok :)

Hmm..

Something is still wrong as even I can't get this booting
[Samsung Galaxy Nexus] jjrojo:
Flashed rom, gapps from fml thread. Reboot bootloder, flashed zimage.

Sorry still in boot logo bucle.

---------- Post added at 12:51 PM ---------- Previous post was at 12:43 PM ----------

One guy told him have a completly working rom with data inclusive.

They spoke about selinux context in android services.

Although here the trouble like be before rom init, kernel maybe.

I'm not developer, some years in linux nothing more.
[Samsung Galaxy Nexus] jjrojo:
You have problem with new selinux system in android 5.0 more gpu drivers.
[Samsung Galaxy Nexus] Carlos_Manuel:
There's some selinux denials that I must fix.. :)
[Samsung Galaxy Nexus] jjrojo:
Yes. I'l stay out for some hours. Later in the night i'l connect.
[Samsung Galaxy Nexus] rohitchouhan07:
Buddy ..can u tell me why tgere is screen glithes in recents...
[Samsung Galaxy Nexus] Carlos_Manuel:
On a test version of dreams lollipop build (Dreams 5.3.0), or on kitkat (Dreams 5.2.3)?
[Samsung Galaxy Nexus] rohitchouhan07:
On the lollipop test build ...(5.3.0.1) so i returned back to your kitkat stable build .....also can u please tell me how to get the launcher witj black app drawer ...which u used in lollipop on your kitkat rom.........( the 4.3 like launcher)
[Samsung Galaxy Nexus] Carlos_Manuel:
That's because a lollipop build does not have fixes and workarounds for the old ddk.

Launcher with a black drawer:

Launcher2.apk, on my ROM there's only Launcher3 which allows translucent navigation bar ans status bar.
[Samsung Galaxy Nexus] rohitchouhan07:
Plss dont give up on the dreams lp .....

Have u checked fml or cm 12 ,i think they fixed the graphical glitches and recents lag.......n also camera problem seem to be widespread i found camera not connecting isuue on a nexus 4 nd 5 stock builds.....
[Samsung Galaxy Nexus] Carlos_Manuel:
Yes I've checked those and I've got some fixes from theeir repositories.

Camera: just probably needs an updated api to work correctly on lollipop

lags: are present because of an old ddk, lags aren't bothering me.

I am trying to fix WiFi hotspot but I cannot find the reason why it doesn't want to work. I'e elaready checked kernel and on the kernel everything should be correct and... I just have no more ideas.. :(
[Samsung Galaxy Nexus] Dominicjobs:
Anyone have problems sending long SMS?

Anyone have problems sending long SMS?
[Samsung Galaxy Nexus] adrieledy:
Zip

Can you please put the lollipop rom in a zip file?
[Samsung Galaxy Nexus] Akosijasper:
dreams

is this rom better than other LP roms?
[Samsung Galaxy Nexus] resporival:
Green Line in Recorded videos..

Lagging in Rotation ...
[Samsung Galaxy Nexus] WinMD:
graphic glitches

Super! Very stable, camera works fine! Graphical glitches in recent applications and in rotation. Green line in recording videos still there. Old SMS-app, please change at new.
[Galaxy Note 3 Q&A, Help & Troubleshooting] Neo3D:
Does anyone have problems with the Galaxy video player not remembering its setting?

For example:

When this window pops up, I select ALWAYS but the app never remembers its setting, it's really annoying! And it pops up this window again everytime I play a video.

My friend has this same problem on her Note 3 as well. She has a Verizon version. Mine is T-Mobile. I think it's a Galaxy problem.

Does anyone know how to fix this?
[Galaxy Note 3 Q&A, Help & Troubleshooting] Neo3D:
Does anyone else have this problem?
[Galaxy Note 3 Q&A, Help & Troubleshooting] Graffiti Exploit:
I don't know if I'm really right on this but that window pop ups for specific actions. For example if you open a video file from File Manager opening an mp4 file then select always with Video Player then it will open it always with Video Player. However, if you do the same with an for example an mkv file then it will pop-up the window again since it is not the same action. So basically you have to do the always thing for every possible action. Different scenario = different pop-up action/history.

Again not sure of this but this works for me.
[Galaxy Note 3 Q&A, Help & Troubleshooting] ShadowLea:
It's a KitKat bug.

I have the same problem with Tapatalk, AndroZip and Youtube.

It started with the 4.4.2 update. I factory reset immediatelly after. Didn't help. It just changed the apps with the problem from Tapatalk & Quickpic to Tapatalk, AndroZip and Youtube. Reinstalling, clearing data, clearing cache, factory reset, reflash, none of it makes any difference.

Sadly, this bug occurs even when you repeat the same file over and over again, telling it 'Always' every time.
[General Questions and Answers] Impalerion:
hello, the deal is that I forgot my facebook app / messenger password and do not remember it.

I have android xperia z2, is there a way I could connect my phone to a computer and open up some cache files or something so I can view it in plain text? I repeat its not for web browser login details, but for fb app.

can recover it via email because email service I used to create account went offline.

thanks.