yashsingh1/xdaforums huggingface dataset:
[Spice Dream Uno] SacredDeviL666:
Please be respectful and observant of all XDA rules, as well as towards each other.

Please use the links below if you have any questions about content you wish to post, or need help from the Moderator Staff.

Best Regards: Your Friendly Moderation Team

XDA Developers Forum Rules

Moderation Team

Rules for posting Development Threads

XDA-Developers and the GPL

Regarding Paid Themes On XDA

***WARNING*** Do Not Spam, Sell or Trade on XDA

Telegram Chat Channels - Way Forward

Spoiler content hidden.
[Touch Cruise ROM Development] lubmarinov:
Orbit2-- GPS cannot be detected with IGO PLS HELP?!?!?

I have a HUGE problem with getting my GPS running on my Orbit2. It came from O2 with CoPilot7 preinstalled with the maps of UK and Ireland, which I dont use, because I am not located inthere, nevertheless Copilot detects GPS signal and shows positioning, but i dint have the maps for the area that i am in.

I tried to install IGO6 and then IGO8 but I have the same problem-- it cannot detect GPS device, no matter what which COMM Port and BAUD Rate I select.

How come CoPilot detects, and IGO does not? I read that Orbit2 is not locked?!?

Should I boot the whole device using some other ROM.
[Touch Cruise ROM Development] .ForumUser:
This may be a silly question but, have you configured the GPS in iGO?

So you are not in Europe? I ask because the CoPilot Disk allows any country (or the whole) of europe (or is that just western, can't remember).
[Touch Cruise ROM Development] ---Alex---:
IGO has an option to auto detect the best settings, that is what you should use.
[Touch Cruise ROM Development] blaui:
I use IGo with Orbit2 and it works!

Use Autodetection or set the Com-Port to 4 and Baud to 57600...
[Spice Dream Uno] SacredDeviL666:
If you are seeing this message it is because you are viewing from a mobile app. This thread has been redirected to the link below.

Development Forum Rules​
[Spice Dream Uno] SacredDeviL666:
If you are seeing this message it is because you are viewing from a mobile app. This thread has been redirected to the link below.

[Mandatory] XDA-Developers and the GPL​
[Spice Mi 509 Guides, News, & Discussion] SacredDeviL666:
Please be respectful and observant of all XDA rules, as well as towards each other.

Please use the links below if you have any questions about content you wish to post, or need help from the Moderator Staff.

Best Regards: Your Friendly Moderation Team

XDA Developers Forum Rules

Moderation Team

Rules for posting Development Threads

XDA-Developers and the GPL

Regarding Paid Themes On XDA

***WARNING*** Do Not Spam, Sell or Trade on XDA

Telegram Chat Channels - Way Forward

Spoiler content hidden.
[Honor 7 Q&A, Help & Troubleshooting] Luukeri:
Hello my friends,

My son is using a honor 7 lite. He wants to use the Bluetooth connection of our Sony SRS-XB30 speaker . But despite my efforts to to connect it. It has no avail. The phone can't seem to find the wireless speaker. I followed everything but no success. Can anyone have an idea how to fix this. Thanks in advance.
[Honor 7 Q&A, Help & Troubleshooting] spirtix:
Honor 7 lite is not very similar to Honor 7, but it's basically Honor 5C. Try asking on their forum.
[Google Pixel 3 XL Guides, News, & Discussion] Nospine:
It seems that a large number of 3 XLs have shipped with some sort of "burn in" in the status bar area. There was a relatively active thread recently where some people, including myself, reported this.

Today I found a video that works really well for demonstrating the issue.

For those that can watch it and report their findings, here's the link (go to 3:44):

https://youtu.be/xHRDQHAy5dY

Go to minute 3:44 to see a grayish loading screen. I recommend viewing the phone in a dark or slightly dim room at 50 - 55% brightness. Make sure you are using fullscreen as well.

I'm including a photo of mine so you guys can get an idea of what the problem is.

View attachment 4633278
[Google Pixel 3 XL Guides, News, & Discussion] gaw316:
So what can be done?
[Google Pixel 3 XL Guides, News, & Discussion] southernstyle:
It's easier to see with attached images. Cause is likely bc you use nacho notch, which never uses the status bar pixels, thus making them the brightest. Or, normal usage, where most apps use darker shades of the header bar. It's on my phone too. It's the nature of OLED technology. I own an OLED TV, and it exhibits image retention. It also has a feature to refresh the panel to remove burn in and retention.

That said, the conditions used to find the issue are dim and solid color. If you are constantly in full screen looking at single color images with a dim screen, I'd suggest returning and getting a different phone (probably an LCD screen). Bc all OLED panels can do it. Not all do, but it's made of organic material. If you stare at the sun, it "burns in" your eye and you see a spot until you go blind or your eye refreshes.

Conversely, if you own a newer LED TV with a backlighting that is on the cheaper end, you'll definitely have dirty screen effect (DSE) which is essentially the same effect but due to poor manufacturing. It's noticable in panning shots and, you guessed it, solid color screens. My Samsung TV from 3 years ago is the worst. Big chunky darker bars running through the screen. That drove me more crazy bc you can't fix it. It's due to the **** manufacturing.

Google could fix this by using whatever they did with the nav bar. Notice there's no burn in down there. I personally wouldn't be worried. It's noticable once in a while for average users. Not the end of the world, unless you're like me and have OCD and it'll drive you up the wall. Then you should take the prescription I'm on, bc nothing really bothers me anymore.

tldr; cause different brightness used on status bar. Fix, new phone, Google, or LCD screen.
[Google Pixel 3 XL Guides, News, & Discussion] Fuzzy13:
I did the full immersive via adb shell and settings put global policy_control immersive.full so that both are hidden unless I pull down or swipe up to view the status bar or nav bar. This way they are not on the screen constantly. I did this with my Pixel 2 XL and after a year of 80% brightness and 7hrs of SOT daily, the burn in was very faint.

I hope the burn in is minimized via this method on my P3XL as well but if not, is what it is.
[Google Pixel 3 XL Guides, News, & Discussion] Nospine:
I don't use nacho notch (don't even know what it does), don't hide the notch either, and am aware that this is the nature of OLEDs which is why I hate them.

BUT.

The phone was like this STRAIGHT OUT OF THE BOX. A friend of mine also recently got a 3 XL... And guess what? His was also "burnt in" as soon as he turned it on.

I do use navbar apps to prevent uneven burn in on screen and that's how I've done it with my previous OLED phones.

I went ahead and requested an RMA but the sample size of 3 XLs that I've seen with this bar burn in is very high (as in, all 3 XLs have it to some extent, straight out of the box), so I'm not optimistic about the outcome.

Again, it's expected that OLEDs will wear down over time. Perhaps in a year some effects of burn in will be more noticeable, but the phones are SHIPPING LIKE THIS. That's a big problem. Is it burn in? Are they using a different panel piece for the notch area? Did someone goof up during testing and left a batch of phones with their screens on for too long? Who knows.
[Google Pixel 3 XL Guides, News, & Discussion] Nospine:
Nothing. Try an RMA and hope you get a device without burn in. All the 3 XLs have this burn in to an extent. Something went wrong at the factory, is my best guess.
[Google Pixel 3 XL Guides, News, & Discussion] bobby janow:
What do you consider a "large number of 3 XLs"? Can you point to any other documentation of this other that the two threads you are highly active in? It seems like you enjoy your iPhone X a lot more so I'm not quite sure why you need to come here and bash another device consistently. I mean if you're not happy with a device then return it and keep the one you are happy with. Image retention has been around for a long time, either live with it or not.
[Google Pixel 3 XL Guides, News, & Discussion] Nospine:
Wow, just wow.

Why so defensive? Do you feel threatened? You're even assuming that I'm bashing this phone; are you really that scared of people saying negative things about your precious new phone? I'm just here to do research.

Don't know where you got that I use an iPhone X, unless you misread one of posts... I have access to one, not that it is my personal device. Anyway, to put you at ease, I've been an Android user for a long time now. Started with an Xperia Play then jumped to Nexus and later Pixels 1 - 3. I like this phone, and I am relatively happy with it, but I'm not okay with receiving a phone with burn in straight from the factory.

I'll provide some sources for you, albeit, they're not official documentation. Just user reports:

https://www.reddit.com/r/GooglePixel/comments/9oc4ka/the_pixel_3_xl_at_least_the_unit_i_have_has/

https://www.reddit.com/r/GooglePixel/comments/9qvxdd/status_bar_burn_in_out_of_the_box/

https://www.reddit.com/r/GooglePixel/comments/9r82zi/anyone_without_a_status_bar_burn_in_on_their/

If you would, read through those.

You will see that people claim that the status bar actually has a slight tint to differentiate it form the rest of the screen and that's true, but the OPs in those are claiming that it's always visible even in fullscreen mode when watching a video or viewing a photo.

I've also personally seen demo units and a friend's unit that has it, as well as my own personal device of course. Also consider the people from the previous threads here.

Again, this is not image retention or burn in from personal use, I jus don't know what to call it. Phones are shipping with this already on them. I'm trying to gather information to understand what it could be, and see what my odds of getting a phone without this are (or if I should even bother with RMAs).
[Google Pixel 3 XL Guides, News, & Discussion] bobby janow:
Lol, threatened? About a phone? I feel threatened by some jackass tailgating me on the GSP at 75 mph but not by an internet post about a device. So we can dispense with the silliness, ok?

I did read those posts before I replied to you before. It seems like there is not a huge amount of support for your position although there is some. This has been going on for years now (supposed burn-in) and for some reason Google seems to get the brunt of the criticisms by anonymous users on forums. Personally, if I couldn't live with the device then I'd return it and move on. I don't find it helpful to just rant and complain when there are other alternatives.

What I meant by documentation on burn-in was independent, verified research by a reputable company or entity. Not a bunch of yahoos on Reddit. I find that disingenuous at best and more than likely people with nothing else to do. Bottom line, you don't like the phone then return it and buy an iPhone XS, which btw is absolutely gorgeous. I was on the fence for a bit but decided to give the 3 another shot this time around.
[Google Pixel 3 XL Guides, News, & Discussion] Nospine:
Ignore this post
[Google Pixel 3 XL Guides, News, & Discussion] Nospine:
You are affected by my posts after all. Your claims are heavily biased in favor of Google. Why? Otherwise you wouldn't be complaining about "Google getting the brunt of the criticisms by anonymous users on forums." You care about Google. It stings seeing this, therefore your response is to attack me, as you did with your first post.

Again, I'm not here to fight. After all, it wasn't me who came to this thread with an aggressive tone. If you're not going to help, then please go defend Google somewhere else.

If you plan to contribute then I'd appreciate it if you at least said whether you have burn-in or not. Either way, it would be helpful to know.

As for the sources, I did mention they were not official documentation, it's the best we have so far. The closest to "official" is that one post by a supposed journalist that mentioned the situation with his pre-release unit. Sadly, there isn't more than that, considering the visibility of the "burn-in" is dependent on many factors.

Also, I've been calling it "burn-in" but I'm sure it's another issue altogether with the panel they used. If it were actual burn-in we'd be seeing the status bar icons on there as well.

Ah, and I wish I had more phone choices but I use Project Fi, so I'm stuck with their small selection of phones. The Pixel line has been good to me so far, so I've stayed with these phones and Fi, but I can't deny that I would take an LCD phone (I know they have an LCD LG, but no LG for me) over an OLED any day of the week.
[Google Pixel 3 XL Guides, News, & Discussion] Nospine:
Anyway, that's that for me. I ain't looking for a fight. Never wanted to make Google look bad. Just trying to understand a situation that that I've seen on multiple 3 XLs
[Google Pixel 3 XL Guides, News, & Discussion] bobby janow:
I'm responding to your posts, that's it. Don't flatter yourself in importance. Nothing you say "stings" nor do I care what you do. I'm just correcting your inaccuracies and innuendos. I'm actually biased in terms of Apple since I own their stock but unfortunately I don't own Google. Apple stock got creamed on Friday but hopefully it will come back. Good luck on your RMA, you'll eventually get something you can live with.
[Google Pixel 3 XL Guides, News, & Discussion] zetsumeikuro:
Honestly I really doubt it's actual burn in or "differential aging" because I saw it on the white boot screen and this is on phone that I just got as well a few days ago. I don't hide the notch or use nacho notch and rarely have any apps that don't color the entire status bar. Seems for whatever reason the top of the display is always a shade darker than the rest. Google doing Google things?
[Google Pixel 3 XL Guides, News, & Discussion] Nospine:
Exactly! It's visible during the boot screen, but it just can't be burn-in since it's seen on newly opened phones... I just don't know what to call this. It might just be that the top is calibrated differently for some odd reason, somehow. I wish I knew for sure.
[Google Pixel 3 XL Guides, News, & Discussion] ps000000:
May be different screen piece ? in the manufacturing process.

just my idea.

(big regtangle one and two /or one notch piece)
[Google Pixel 3 XL Guides, News, & Discussion] Nospine:
That's a possibility. I've seen someone suggest that before, as well.
[Google Pixel 3 XL Guides, News, & Discussion] zetsumeikuro:
Yeah man it's a head scratcher. But if it's truly as the other poster is saying and they're separate panels then you'd be able to see it under the glass. Plus the Ifixit teardown they take the display out and it just looks like 1 big panel. https://www.ebay.com/itm/For-Google...d77ec31b9:m:m1d1CS5DqB0JZHN94mXt2Vg:rk:2:pf:0 show's a replacement panel and screen and it looks like it's one.
[Google Pixel 3 XL Guides, News, & Discussion] Deleted member 5445131:
+1, I thought I was going crazy but my 3 XL came like this too. I pre-ordered minutes after the link went live
[Google Pixel 3 XL Guides, News, & Discussion] Nospine:
I'll be receiving a replacement in a week or so. They did mention that they don't have any phones at the moment so it may be delayed, but hey, that might mean that I'll be getting a phone from a new batch, and we'll know whether this issue is unique to the first run of 3 XLs or not.
[Spice Mi 509 ROMs, Kernels, Recoveries, & Other De] SacredDeviL666:
If you are seeing this message it is because you are viewing from a mobile app. This thread has been redirected to the link below.

Development Forum Rules​
[Spice Mi 509 ROMs, Kernels, Recoveries, & Other De] SacredDeviL666:
If you are seeing this message it is because you are viewing from a mobile app. This thread has been redirected to the link below.

[Mandatory] XDA-Developers and the GPL​
[Wiko Rainbow Guides, News, & Discussion] SacredDeviL666:
Please be respectful and observant of all XDA rules, as well as towards each other.

Please use the links below if you have any questions about content you wish to post, or need help from the Moderator Staff.

Best Regards: Your Friendly Moderation Team

XDA Developers Forum Rules

Moderation Team

Rules for posting Development Threads

XDA-Developers and the GPL

Regarding Paid Themes On XDA

***WARNING*** Do Not Spam, Sell or Trade on XDA

Telegram Chat Channels - Way Forward

Spoiler content hidden.
[Upgrading, Modifying and Unlocking] aliasalias:
hello

ive just buy an phone who is called desay m9

the problem is i thinking it was wm5 on but i thinks its a verry strange copy of wm5!!!

no virtual keyboard , a majority of application doesnt work , its so sadly....

the spec is:

Hardware Specifications：

Operation System：Windows Mobile 5.0 AKU3.5

CPU: Inter Xscale 270+Skyworks Pegasus Q Frquency: 312MHZ

Internal memory：Flash 64M RAM 64M

Screen:3.0 inch handwritten

and other spec :

platform :win ce

user agent os windows ce (smartphone) version 5.1

cpu class : arm

version : 4.0(compatible , msie 6.0 , windows ce , iemobile 6.Cool

minor version : 6.8

user agent : mozilla / 4.0 (compatible , msie 6.0 , windows ce , iemobile 6

i just want now to upgrade in a wm6 or wm5'true'

but i dont know what kind of rom i nedd to these and i dont know the version of my rom

thank you to all your help!!!!

see ya , thanks!!!
[Upgrading, Modifying and Unlocking] aliasalias:
maybe there is a program for know rom version no?

thanks
[Upgrading, Modifying and Unlocking] Rodger_Dodger:
(

At me the same problem... Who knows where there is normal version WM?
[Wiko Rainbow ROMs, Kernels, Recoveries, & Other De] SacredDeviL666:
If you are seeing this message it is because you are viewing from a mobile app. This thread has been redirected to the link below.

Development Forum Rules​
[Wiko Rainbow ROMs, Kernels, Recoveries, & Other De] SacredDeviL666:
If you are seeing this message it is because you are viewing from a mobile app. This thread has been redirected to the link below.

[Mandatory] XDA-Developers and the GPL​
[XOLO A500S] SacredDeviL666:
Please be respectful and observant of all XDA rules, as well as towards each other.

Please use the links below if you have any questions about content you wish to post, or need help from the Moderator Staff.

Best Regards: Your Friendly Moderation Team

XDA Developers Forum Rules

Moderation Team

Rules for posting Development Threads

XDA-Developers and the GPL

Regarding Paid Themes On XDA

***WARNING*** Do Not Spam, Sell or Trade on XDA

Telegram Chat Channels - Way Forward

Spoiler content hidden.
[XOLO A500S] SacredDeviL666:
If you are seeing this message it is because you are viewing from a mobile app. This thread has been redirected to the link below.

Development Forum Rules​
[XOLO A500S] SacredDeviL666:
If you are seeing this message it is because you are viewing from a mobile app. This thread has been redirected to the link below.

[Mandatory] XDA-Developers and the GPL​
[Android Q&A, Help & Troubleshooting] totalgaara:
Hi,

I’m asking your help because i’m getting lost, i explain :

I’ve got a Acer Liquid Jade S (Acer S56) with a MT6752 CPU, it’s currently on Android 5.1 and i want to « port » higher Android from another phone with the same soc.

I already tried in august and july to build my own rom for this device but i never did it before, it was my first « rom building experiment » and nothing so far, it’s too hard for me, there is no device tree at all so ^^’

The good thing as i already said, there is a lot of other phone with the same CPU like Lenovo K3 Note, Lenovo P70, Jiayu S3 with latest android version custom rom.

I ported a 5.1 stock rom from the Lenovo P70 and it’s work (but still 5.1..) because the rom was x86 and that’s the issue...

There is a lot of rom but they are all x64 and i only got a x32 rom with my Acer (the cpu is compatible x64, strange choice from acer).

So i’m asking, how can i port if i don’t have a x64 kernel and « x64 base stock file », like lib64, it is possible ? Acer guive the Kernel Source, but for Kitkat, i’m asking if there is no way to « upgrade it » to support higher Android version and add x64 compatibility, but will it work (probably with some bug but don’t care ^^) ?

Because i don’t have the lib for 64, I know it’s possible because i look myself on lenovo website and they provide Android 5.1 x32 and not 64. Someone ported the stock rom to x64 but i didn’t find how…

Can you please help me ? I know that phone start to be « old » but it’s good for me, i’m not a Android « gamer », just want most recent android because apps starts to be not compatible with 5.1

Thanks
[Android Q&A, Help & Troubleshooting] totalgaara:
Any idea ?
[Android Q&A, Help & Troubleshooting] totalgaara:
UP
[XOLO Play 8X-1000/1100 Guides, News, & Discussion] SacredDeviL666:
Please be respectful and observant of all XDA rules, as well as towards each other.

Please use the links below if you have any questions about content you wish to post, or need help from the Moderator Staff.

Best Regards: Your Friendly Moderation Team

XDA Developers Forum Rules

Moderation Team

Rules for posting Development Threads

XDA-Developers and the GPL

Regarding Paid Themes On XDA

***WARNING*** Do Not Spam, Sell or Trade on XDA

Telegram Chat Channels - Way Forward

Spoiler content hidden.
[XOLO Play 8X-1000/1100 ROMs, Kernels, Recoveries, ] SacredDeviL666:
If you are seeing this message it is because you are viewing from a mobile app. This thread has been redirected to the link below.

Development Forum Rules​
[General Topics] oddjob2:
Hi all. I hope someone out there can help me. I am having a big headache with outlook at the moment. I am using a T-mobile touch plus with Outlook 2007 since Febuary and have had no problems with the device syncing using Activesync. Within the last week I plugged my touch in and Active sync said that I need to resync all contacts, I have no idea why, and when it synced it left out almost half the contacts. I have looked through all the contacts that didn't sync and can not see any pattern in why they haven't synced and other have. I don't think that I have changed anything on the phone, outlook or activesync. The contacts still exist in outlook. Activesync 4.5 has no settings for contacts to choose what to sync. I have tried to play with the catorgries to see if that made any difference. All the contacts are in the same contact folder as I only have one personal folder. I can not figure it out, and would love some help as I have lost all the usefull contacts on my phone. Please help!!! Cheers in advanced
[XOLO Play 8X-1000/1100 ROMs, Kernels, Recoveries, ] SacredDeviL666:
If you are seeing this message it is because you are viewing from a mobile app. This thread has been redirected to the link below.

[Mandatory] XDA-Developers and the GPL​
[Xolo Q1000] SacredDeviL666:
Please be respectful and observant of all XDA rules, as well as towards each other.

Please use the links below if you have any questions about content you wish to post, or need help from the Moderator Staff.

Best Regards: Your Friendly Moderation Team

XDA Developers Forum Rules

Moderation Team

Rules for posting Development Threads

XDA-Developers and the GPL

Regarding Paid Themes On XDA

***WARNING*** Do Not Spam, Sell or Trade on XDA

Telegram Chat Channels - Way Forward

Spoiler content hidden.
[Xolo Q1000] SacredDeviL666:
If you are seeing this message it is because you are viewing from a mobile app. This thread has been redirected to the link below.

[Mandatory] XDA-Developers and the GPL​
[Xolo Q1000] SacredDeviL666:
If you are seeing this message it is because you are viewing from a mobile app. This thread has been redirected to the link below.

Development Forum Rules​
[Xolo Q1010i] SacredDeviL666:
If you are seeing this message it is because you are viewing from a mobile app. This thread has been redirected to the link below.

Development Forum Rules​