yashsingh1/xdaforums huggingface dataset:
[Xperia Z1 Q&A, Help & Troubleshooting] dlads:
Can someone explain how this has happened please?

I've just come from Paranoid Android and I messed up by flashing the FTF first when trying to re-install monx :eek: I know.

Then I went and flashed the 534 FTF to go back to basics and then used Vroot to root the phone (something to say about the IMEI too but i'll mention that at the end of this post)

Root went ok and then I installed a recovery and flashed monx 6.0.2, then simply rebooted.

Phone came on straight away, no need to flash the 757 FTF file (excluding System and TA)

?? I'm not sure if it held on to the 534 FTF or if the newer one simply wasn't needed, but it worked and still is.

About the vroot, I've been told that the makers of it send your IMEI to china for some reason, but i went back to 534 and by doing so my IMEI was set to 000000000000000 meaning that they'd have only got that if anything at all, so if you went ahead at any point and followed the tutorial i wrote at the beginning of this thread and you were worried too, then don't be as they'd have gotten the wrong IMEI anyway :)

confused and happy, strange combination :)
[Xperia Z1 Q&A, Help & Troubleshooting] gandalf_grey91:
RO / RW

Is it correct that Root Explorer is showing Root (/) and /mnt/idd are set to RW as default? /system and /lta-label are showing as RO by default. Shouldn't root at least be set to RO by default?
[Xperia Z1 Q&A, Help & Troubleshooting] gandalf_grey91:
Any one? I know its a stupid question but this is the Q&A thread in the Q&A subforum.
[Xperia Z1 Q&A, Help & Troubleshooting] gandalf_grey91:
Whats the point of Q&A thread for a ROM if the questions never get answered?
[Xperia Z1 Q&A, Help & Troubleshooting] dlads:
I get RO by default, thats normal. What the app does is nothing to do with the ROM.

Furthermore, it's Q+A yes, but that doesn't mean someone has to be here all the time, show some respect.

---------- Post added at 02:13 AM ---------- Previous post was at 02:12 AM ----------

To the people having a problem with the camera, use the full FTF not the stripped one.
[Xperia Z1 Q&A, Help & Troubleshooting] gandalf_grey91:
Thank you for your response.
[Xperia Z1 Q&A, Help & Troubleshooting] Snaqejack:
Hey and thanks for this rom, really made my phone feel snappier!

On a sidenote, i´ve read that lots of people are having problem with their camera not working and this is what i did to make it work for me.

Make sure you are rooted, restore your TA partition and you should be golden.

Atleast that worked for me.

However, the only thing i don´t like about this rom is the NFC icon that´s always showing in the statusbar, any way to hide it and not disable it since im using NFC with my BT headset.

Thanks!
[Xperia Z1 Q&A, Help & Troubleshooting] rafsi:
upgrading to 757

hi Guys,

first of all thanks for a wonderful ROM and all the support on the thread... I am new to Sony phones but am already become a fan due to this ROM...

Quick question. during my initial phone set-up I followed the OP and installed 4.2.2. rom then the root then the 681 ROM and FTF flash (w/ the excludes)... All good there....

now moving to 757, I just flashed the ROM via recovery, while I was waiting for flash-tool to do the 757 FTF file, the phone kinda rebooted itself into the 757 rom and it seems to work fine... my question, do I really need to use flash-tool to flash generic 757 (w/ the 2 excludes) or NOT ???
[Xperia Z1 Q&A, Help & Troubleshooting] gandalf_grey91:
I think you will find that one of the Xperia-oriented Xposed modules allow you to hide the NFC icon that is persistent on the statusbar.
[Xperia Z1 Q&A, Help & Troubleshooting] Snaqejack:
monx told me to edit build.prop which i did and now it's gone.

Skickat från min C6903 via Tapatalk
[Xperia Z1 Q&A, Help & Troubleshooting] dlads:
Gandalf is correct, there is an xposed module to hide stamina from the status bar, or you could just modify the battery icon like i did and do neither.
[Xperia Z1 Q&A, Help & Troubleshooting] ogunja:
C6943 works in version? Digital TV works?
[Xperia Z1 Q&A, Help & Troubleshooting] nisar87:
How to get the icons which you are displaying in screenshot?

Hello,

2days ago I installed your rom and working without any issue.

But there are few question which i want to know.

1- I have pebble smart watch, when i try to create the pair with bluetooth, it took lot of time to establish the connection. (few time restart, bluetooth on/off). But on stock rom, it was working perfectly without so much effort. (can you look at it again when have time)

2- Where from you get the icons and battery status. please refer the attachment.
[Xperia Z1 Q&A, Help & Troubleshooting] jothimurugan:
Sony Xperia Z1

Worst download place.please upload mediafire or any other good link
[Xperia Z1 Q&A, Help & Troubleshooting] upendra007:
network issues

hello sir i am using xperia z1 c6902 running 4.4.4.miu 7 with twrp &rooted .AS you mentioned i have followed all the steps worked fine for me but only problem is my network doest recognise,what shloud i do now?
[One (M8) Q&A, Help & Troubleshooting] cc999:
Has anyone noticed the Bluetooth range is very short on this phone?

Its like 1/2 the distance of the M7.

CC
[One (M8) Q&A, Help & Troubleshooting] craig0r:
Sh*t, really? I'm still waiting on my M8, but I was really going they had improved the Bluetooth signal.
[G2 Q&A, Help & Troubleshooting] SNaReX:
Maybe when you see my post, you said that 'another root question'. But it is not.

I own a D802.

I had install a kitkat 4.4.2 F320S rom on my phone. I had no issues. But I had lost my recovery.

Now I rooted my phone with ioroot25.

However, I cannot install recovery with freegee

It detects my phone as F320S and it doesn't support my device.

What I am supposed to do to install a recovery.
[G2 Q&A, Help & Troubleshooting] trickster2369:
You can't install custom recovery on kk yet, because there isn't one that works yet.

Thanks Devs. From my VZW G2.
[XPERIA X10 Q&A, Help & Troubleshooting] cekuku:
hi all i downloaded s1tool and restore with s1tool now my x10 only vibrate and green light then nothing happen any solution please thanks please help
[XPERIA X10 Q&A, Help & Troubleshooting] :
Are you able to get in FLASH MODE? If the answer is yes, Try to flash stock 2.3.3 firmware using FlashTool. This will help your phone to get get back to life atleast.

Hit THANKS, if I helped a bit :D
[XPERIA X10 Q&A, Help & Troubleshooting] cekuku:
yes it helped but now i ve x10mini kernel flashed the answer is no what can i do ? thanks
[XPERIA X10 Q&A, Help & Troubleshooting] :
That means no green light while trying to enter in flashmode! Is that so?

Do you have stock ftf file of your phones firmware?

Hit THANKS, If I helped a bit ￼
[Galaxy S 4 Q&A, Help & Troubleshooting] Xyronna:
Hello

I'm sorry for my english

My phone i9500

I'm using CyanogenMod and did not like the keyboard on this rom.

Where can I find Samsung's original s4 keyboard apps up to date.

Thanks for everything
[Galaxy S 4 Q&A, Help & Troubleshooting] jeffrey268:
I don't beleve it is possible to use the stock Samsung keyboard on a non touchwiz rom.
[Windows Mobile Development and Hacking General] levenum:
Hi Peter.

The only problem I can see in your code is that you are using char instead of WCHAR. Windows Mobile devices only use UNICODE for API calls.

I don't think it is causing the error, but it is strange that you manage to get the correct text out using it.

The only thing I can think of is using GetWindowText and SetWindowText APIs instead of sending the message directly.

Maybe this will solve your problem.
[Windows Mobile Development and Hacking General] OdeeanRDeathshead:
I also notice that you did not initialize the buffer. The string needs to be null terminated so try initializeing all the elements before putting your 'A' in.

I thought 120 was not supported on this system ERROR_CALL_NOT_IMPLEMENTED.
[Windows Mobile Development and Hacking General] Peter Bruderlin:
Guys,

Thanks very much for the suggestions.

As for not initializing the buffer, I think the WM_GETTEXT call does that, all I do with the buffer[0] = 'A' call is to modify a single character that now contains the text that was copied out from the control.

But I take your point about using WCHAR, I'll do that when I get a chance.

And I'll try the Get and SetWindowText calls.

Thanks again.
[Windows Mobile Development and Hacking General] Peter Bruderlin:
Ok, How about this then?

The buffer is initialized by the WM_GETTEXT message, and it is set to the correct value (ie the initial contents of the control).

Changing the first character works.

The WM_SETTEXT message fails (result == 0) and the translated error (120) as displayed in the message box is "This function is only valid in Win32 mode."

The SetWindowText also fails with the same last error.

Does anyone know what "Win32 mode" is? I have spent time searching the MSDN and googling it. I've seen some references to it as an error message, but I haven't found an explanation.

Thanks,

Peter

WCHAR buffer[100];
HWND hCtl = ::GetDlgItem(hDlg, IDC_TITLE);
LRESULT result = ::SendMessage(hCtl, WM_GETTEXT, (WPARAM)80, (LPARAM)buffer);
buffer[0] = WCHAR('A');
//BOOL textResult = ::SetWindowText(hCtl, (LPCWSTR)buffer);
result = ::SendMessage(hCtl, WM_SETTEXT, (WPARAM)0, (LPARAM)buffer);
if (result == 0)
{
WCHAR errorTitle[] = L"LastError";
LPVOID lpMsgBuf;
DWORD error = ::GetLastError();
::FormatMessage(FORMAT_MESSAGE_ALLOCATE_BUFFER | FORMAT_MESSAGE_FROM_SYSTEM | FORMAT_MESSAGE_IGNORE_INSERTS, NULL, error, 0, (LPTSTR)&lpMsgBuf, 0, NULL);
::MessageBox(NULL, (LPCTSTR)lpMsgBuf, (LPCWSTR)errorTitle, MB_OK | MB_ICONINFORMATION);
::LocalFree(lpMsgBuf);
}
[Windows Mobile Development and Hacking General] levenum:
Ok, there is no apparent reason why your code doesn't work. Like OdeeanRDeathshead said according to MSDN error 120 means 'This function is not supported on this system.', something you definitely should not be getting.

One question: is this code inside a class member function? I am asking because of the '::' in front of every API.

Try removing them and see what happens.

Also, no need to use WCHAR('A'), just write L'A' save your self some typing in the long run.

P.S. In my year and a half of programming for Windows Mobile I never heard of a 'Win32 mode' or a function not working because of it. The error may be elsewhere in your code, some problem with name-spaces perhaps?
[Windows Mobile Development and Hacking General] OdeeanRDeathshead:
Are you running this on an actual device or just the emulator?
[Windows Mobile Development and Hacking General] OdeeanRDeathshead:
That error message comes from the free evc compilers. In the tool "error lookup" and in the help, it gives that mesage to correspond to that number.

I have just tested everthing you did. My dialog also uses a class with static methods for its routine. I used your exact code in the initial dialog handler and experimented with the origional contents of the controll. I tested on 2002 2003 2005 devices and can't make it fail. The worst i can get to happen is if there is no text to start with, just a square character displays after the A.

the only thing different is that you say two dialogs use that routine, but I am guessing that you are not doing bothe at once at this time.
[Windows Mobile Development and Hacking General] OdeeanRDeathshead:
perhaps you could work around this. Define a value to use as your own message like #define MY_SETUP_MESSAGE ...some value.

Then do nothing in the handler for WM_INITDIALOG except post your own setup message. Do all your normal stuff there. If that succeeds then take a closer look at the timing of WM_INITDIALOG, else there is something waky going on.
[Windows Mobile Development and Hacking General] levenum:
Hang on a second, you wrote:

Is that correct or is it a typo? According to MSDN non zero return for SetWindowText means success, not failure.

One thing you should try is calling SetLastError(0) before calling SetWindowText. Last error is no automatically reset in any way, so it is possible that error 120 is a result of a previous function. Although that still wouldn't account for not seeing the change text in the control.

In any case this is strange. I always initialize controls in WM_INITDIALOG handler and it never failed before.
[Windows Mobile Development and Hacking General] Peter Bruderlin:
Ah, you're right. Sorry, I screwed that up. I misread the MSDN there and did a GetLastError anyway, which returned 120.

SetWindowText returns a value of 1, which implies success, but it wasn't successful in the sense of setting the text, when you see the about box it is unchanged.

I also did a SetLastError to zero before the call, and did a GetLastError after it (even though the return code said success), and it was zero. So by all accounts (return code and GetLastError) it should have worked but didn't. The about box is unchanged.

I have also SetLastError to zero before the SendMessage to set the text. That returns zero, and I am sure that the MSDN says should be TRUE if the text is set, so an error. Trouble is, GetLastError then gives zero implying that there was no failure. When you see the about box, the text is not changed so it did fail.

I will have to experiment some more. Maybe I can't set text in a static for some reason. Do I need to call InitCommonControls for that or something (which I haven't done)?

I will also have to try setting text in an edit control.
[Windows Mobile Development and Hacking General] OdeeanRDeathshead:
I used the format message and got the same win32 mode stuff now. However, the text was modified to the new value. I think the win32 mode error message is a bug. Put the same code into the emulator and the error returned is invalid handle. At least invalid handle is something more definite. In both cases, emulator and real device, even though the returned value is 0 for WM_SETTEXT, and the error message is there, I do not think there is an error. Have you just tried it without any error checking?

Are you creating the dialog using creatdialog/dialogbox?
[Windows Mobile Development and Hacking General] Peter Bruderlin:
Hi OdeeanRDeathshead, thanks for the reply.

I don't think the invalid handle error is right here because I have used the same control window handle (hCtl) a couple of statements before to retrieve the text and that worked. I guess what I haven't checked is whether the control window handle is changed somehow as a result of the first call, but that would be really weird.

You said that even though SendMessage/WM_SETTEXT returned 0, you thought it probably wasn't an error. Well, there is support for that in that when I SetLastError to zero just prior to calling it, and call GetLastError just after, the error code was zero, thus no error. But the reason I think that there WAS an error is that it did not modify the static control. This is what I get if I effectively don't do any error checking.

As for how I am creating the dialog, the only code I have modified from the original project created from the application wizard is in the WM_INITDIALOG section of the About function that I showed you above. The dialog is created in the WndProc message handling function for the main window, part of which is below. If it is the IDM_HELP_ABOUT command, from the menu, it calls DialogBox specifying the dialog message processing function 'About' where my modified code is.

The code below is produced by the application wizard.

LRESULT CALLBACK WndProc(HWND hWnd, UINT message, WPARAM wParam, LPARAM lParam)
{
int wmId, wmEvent;
PAINTSTRUCT ps;
HDC hdc;

static SHACTIVATEINFO s_sai;

switch (message)
{
case WM_COMMAND:
wmId = LOWORD(wParam);
wmEvent = HIWORD(wParam);
// Parse the menu selections:
switch (wmId)
{
[b]case IDM_HELP_ABOUT:
DialogBox(g_hInst, (LPCTSTR)IDD_ABOUTBOX, hWnd, About);
break;[/b]
case IDM_OK:
SendMessage (hWnd, WM_CLOSE, 0, 0);
break;
default:
return DefWindowProc(hWnd, message, wParam, lParam);
}
break;
etc

I think I am going to have to experiment some more on the weekend. Try some other controls etc.
[Windows Mobile Development and Hacking General] Peter Bruderlin:
By the way I meant to mention that exactly the same thing happens in both the emulator as well as my Atom. So far, in all of the combinations of code, I have not been able to programmatically change the text content of a static control on a dialog.

And I've just noticed that my attempt to highlight (bold) the relevent part of the code above didn't work.

D'oh!
[Windows Mobile Development and Hacking General] Peter Bruderlin:
Actually I have just thought of something that may be relevent.

The emulator and SDK that came by default with VisualStudio2005 is WindowsCE 2003. When I first tried my code in the emulator, it worked. I could not only set text in a static control, I was also successfully manipulating a date/time picker in a separate dialog. I did lots of GDI rendering in the main window as well. And this code also worked on a friend's WindowsCE2003 PDA.

Things looked good until I tried it on my Atom which is WindowsMobile 5.

None of the above worked (except the GDI rendering). I thought it may have been a problem with the development environment. So I downloaded the WindowsMobile 5 SDK which includes a WM5 emulator. I thought this is bound to fix the problem, ie generate the code with the WM5 SDK.

All of my problems above are with WM5 project and emulator. And I said I was using this way back in the first post.

OdeeanRDeathshead, I had a quick look at your profile and you seem to have some earlier XDA machines. Are you using Windows Mobile 5?

If the problem does turn out to be Windows Mobile 5 related, then that says something very bad about backwards compatibility for that platform. Could it also be a WM5 bug? Surely not something so fundamental as this?
[Windows Mobile Development and Hacking General] OdeeanRDeathshead:
I use evc++3 for a compiler, mainly because I am the kind of person who thinks - if its not broaken why change. I have an Atom and do use it to run code on. I have all os, ie 2002,2002pe,2003,2003se,2005, so I don't think this problem is with the device. It may be vis studio 2005, but others have said it works OK.

PPC operating systems have a nasty history of backwards compatibility issues. I could not say that this is the issue here, but it is definately one reason I stick to a lowest common denominator approach. Why not just get evc3 or evc4 and give them a try. They are free.
[Windows Mobile Development and Hacking General] Peter Bruderlin:
I guess I was hoping to do it with Visual Studio 2005 because that is what I use at work. These days I mainly program in C#/.NET.

I kind of miss the low level stuff that I used to do on windows a long time ago. But I reminisce.

I'm assuming that evc++ is embedded visual c++? It sounds like really good advice, I'll look for it and it sounds like it will fix all my problems. Especially if as you say, it works for WindowsMobile 5. Can you tell me if you are supposed to use the WindowsMobile 5 SDK with it?

So OdeeanRDeathshead and levenum, thanks a lot for your help guys.

Peter
[Windows Mobile Development and Hacking General] OdeeanRDeathshead:
You will not be able to use the 2005 sdk with it because microsoft decided that from now on we should all pay to use vis studio 2005. Unless there is something specific you want from the 2005 sdk that is not available in previous sdk's then that should not be a problem.

If you want to do c# for ppc then I know that vis studio 2003 worked with no problems for me in the past. One problem with all these different tools is that the platform manager in each seems to b incompatible with previous os. In evc4(2003 os) I can never get it to connect to 2002 devices. This results in a lot of manual copying of files.
[Windows Mobile Development and Hacking General] levenum:
On that note, eVC 3.0 can't connect to anything above 2002, (I also use it for compatibility), but at least eVC 4 can connect to WM5 devices, although it *****es along the way about unknown platform and CPU. Just click yes on all the messages.
[Windows Mobile Development and Hacking General] Sleuth255:
Peter:

VS2K5 should work just fine. Just set your target to PPC ARM device.

Actually, I think this is the root of your problem. PPC targets WinCE not Win32. I'm not aware that you can dynamically change the properties of a static dialog control through messaging in WinCE.
[Windows Mobile Development and Hacking General] OdeeanRDeathshead:
I do it all the time. In most of my dialogs, they start off as nothing in any of the child windows and I fill them out in the initial message. This is because I am normally resizing/repositioning on the fly anyway so doing the text as well makes sense. I also normally use another message of my own making to do things I want after the window was created. eg. If setting up some objects is going to cause the ui thread to have a delay then I would not want it to happen until after the visible components were looking nice.
[Windows Mobile Development and Hacking General] Sleuth255:
hmmm... IMO then there's no reason Peter's code shouldn't have worked... Very odd. I have not personally used this technique tho; as an MFC developer, I generally just derive from CDialog and use the class functions to modify control properties. Go here for a description of one method that I have used. I also have not loaded WM5 extensions and am not running the WM5 simulator in VS2K5.
[Windows Mobile Development and Hacking General] Peter Bruderlin:
I can't seem to find it now but the Microsoft site (somewhere) said that the evc utilities were for mainaining old Win32 code, VS2k5 was targetted at newer code (presumably managed .NET stuff). Could it be possible that they want to actively stop people using Win32 with VS2k5? I can't remember the exact words but it seemed along those lines.

Don't forget that the same exe that showed errors on WM5 (both emulator and my Atom) worked fine on WindowsCE 2003 (both emulator and real machine).

I've done quite a lot of Win32 on PC type windows, and WM_INITDIALOG was always the place to modify controls before the dialog was displayed. It always worked perfectly, controls always existed at that point and could be manipulated.

Anyway I've just downloaded evc4 and sp4. Do you know if that includes a WM5 emulator? Do I need anything else?

Thanks
[Windows Mobile Development and Hacking General] Peter Bruderlin:
I've just downloaded and installed evc4 and applied service pack 4 (which is apparently needed to support WM5).

I've created my simple "Hello world" application and when I saw it in the emulator I wondered how you could usefully develop something for a mobile device because the application window area is too big, and (weird!) the menu was at the top. So I built the ARM version and ran it on my Atom and it looks like absolute crap.

The menu is at the top, like it's a PC app. You lose the space devoted to the top menu bar. What happened to the two softkey type menus at the bottom? It looks like the intention is to get the bottom area where the WM5 bar is, except the keyboard put's its icon in the middle of that space.

There is a close cross icon thing near the top right, right under the normal close cross icon.

This is the biggest pile of fecal matter I have seen in some time. Please tell me I have done something wrong and forgot to set the "Look like a Windows Mobile 5 application" checkbox, and forgot to download a Windows Mobile 5 emulator.

Oh, and in case this is your favoured look and feel, sorry about the fecal matter thing. :-)

Peter
[Windows Mobile Development and Hacking General] KTamas:
EVC4 is for WM2003SE and below, it does not even support the WM5 SDK...
[Windows Mobile Development and Hacking General] KTamas:
WM5 development is meant to be with VS2005.