yashsingh1/xdaforums huggingface dataset:
[Google Pixel Watch] kpjimmy:
When I learned that I could buy a google leather strap and swap out 20mm straps with a tool I jumped at the chance. I also bought one of the google elastic straps. Both are very nice and nice quality and a bit pricey. However those two are worth the cash IMO. I was able to swap out straps to a canvas strap. As third party, I bought a cheapy 20bux velcro strap and total garbage and looks cheap. Do not recommend. I also bought a bracelet for 25 bux off amazon. It took about 3 weeks to get to me but it works. I have a PVD version so I bought the PVD bracelet to fit. And they do fit. However, I do suggest if you can find one get a bracelet with microadjust holes at the clasp. I will post pics later today. Thanks for taking the time to read! Please send me any questions you may have.
[Google Pixel Watch] StrangerWeather:
To me the Hazel band looks grey. I'd be grateful for some 3rd party recommendations if you guys have any. I find grey a bit dull. Thanks!
[Google Pixel Watch] kpjimmy:
Here's the pvd bracelet from Amazon. The connectors are prone to being scratched pretty easily.

There's others out there now. Pretty sure they're all the same.the stamped clasp is a bit larger on the others I've seen in pics.

Miimall Compatible for Google... https://www.amazon.com/dp/B0BHY9RFJF?ref=ppx_pop_mob_ap_share

View attachment 5770103View attachment 5770105
[Google Pixel Watch] UK_Wildcats_Fans:
I have purchased two bands.

My favorite - nylon band

Metal metallic band
[Google Pixel Watch] kpjimmy:
I like the looks of them. But I personally don't love the dramatic tapering of the straps and makes the strap skinnier than I personally prefer. I have a ton of watches with a bunch of different straps. I tend to try to make the strap look as close as the lug width can go to and I don't mind a slight taper after that. However now have the stretch OEM bracelet, I think that fits...well mostly lol m the lugs are dark green, which is kinda odd but works.
[Google Pixel Watch] Nekromantik:
I hope some watch band companies release some for pixel watch as currently over priced google and then cheap chinese ones are only options.
[Google Pixel Watch] kpjimmy:
This the OEM Google stretch ones. Super comfy and worth the price imo. You have to know what your wrist is size when ordering. Mine is the small. Sizes go from extra small to extra large.

View attachment 5776189
[Google Pixel Watch] kpjimmy:
Ringke just released their metal bands that are shipping 1/25. Weird because I just got notification that mine shipped today (1/17). Well the label was created. The band is 100 USD, a far cry from the one I posted that took about a month to get to me from China. This Ringke version comes with tools as well to adjust the band. This band is an oyster style bracelet with a butterfly deployant. With the "R" stamped at the clasp. Looks decent, but not sure 100 decent.

Here's the link if you feel as brave/or stoopid as me lol

Google Pixel Watch | Metal One Band - Ringke Official Store

The solid chain structure design provides smooth integration between the smartwatch and watch band for Google Pixel Watch

www.ringkestore.com
[Google Pixel Watch] Nekromantik:
they only made it for the silver watch which is annoying
[Google Pixel Watch] rodken:
The option is to purchase the one sold on Amazon which I just purchased and installed.

-- If there is any consolation, 3rd party aftermarket chargers are now available.
[Google Pixel Watch] kpjimmy:
I bought the pvd
[Google Pixel Watch] kpjimmy:
I got it installed and I can attest, that this is way better quality. But is it 100 bux worth? Having handled hundreds of different straps, I have to say yes. But to a non watch person, it's subjective. To me it's leaps better than the Amazon one I posted earlier. View attachment 5814969
[Google Pixel Watch] Ghisy:
I ordered the Caseology Nano Pop strap for 17 bucks today! Looks nice!

https://www.amazon.com/Caseology-Silicone-Designed-Google-Pixel/dp/B0B2VF5QDL
[Google Pixel Watch] Ghisy:
Alright, it arrived today! Replacing the original strap was fairly easy (although this mechanism Google used is kinda weird) and the watch just pops in the Caseology strap from underneath. This area of the band is rubber-ish so it stretches a little so you can slide the watch in. It seems pretty protective with the raised bezels around the screen.

I've just put the watch on for a few minutes with it but it seems quite comfy. I love the look of it! It gives the Pixel Watch a completely different design in my opinion, in a good way.

The only thing I don't like is the way it closes: Google's sports band is much cooler with the double hole thingy (not sure what it's called). Caseology's is more traditional with the metal buckle. We'll see tomorrow how it feels as I should be wearing the watch most of the day outside.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] vietan:
Hi

I'm using the P858Y version of this device

And i simply can't get twrp working on it

What i've done:

- Enable OEM - USB debug

- Get to download mode

- Untick auto reboot on Odin

- Flash TWRP with Odin: So far, every version from 3.0 - 3.7 of the device on twrp website

Everytime i tries to boot to twrp, it just get black screen with backlight still lit, the twrp seem working cause i can swipe or touch the screen and it vibrate, but can't see anything

And i have to flash back to stock rom in order to get back to normal

- I've tried to use adb to control twrp with the back screen but the internal storage doesn't show up on my pc, simply can't flash anything with adb

Device on stock rom is normal, the screen, Touch screen is normal aswell

I don't know what i did wrong in the process

Any idea how i can get custom rom to work on this device

Don't know if anyone has experience this problem.

Every help i can get is appreciated
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] chefez:
Hello friend! I'm a noob and can't help you (yet), but someday maybe I can help you.

for now I recommend looking for some twrp here that has been made for your model specifically (in this case the Tab A 10.1 2016)

if you've already done that and didn't find any related post, maybe we just have to wait for someone less noob to help us.

I also have a problem related to the SM T113NU tablet. I tried using Odin 3.13.1 and TWRP 3.0.2 but I was unsuccessful. Simply when I try to access the TWRP menu only the factory menu appears.

I wish you success and that you manage to resolve the issue.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] vietan:
Many Thanks brother, i've search many thread and somes are having problem just like me. Maybe it just Samsung being an ass like they always did
[Huawei P50 Pro] paulrousseau123:
Hi, I read quite some posts about how people are making all google apps work on the P50 pro (eg via GSPACE or Lighthouse or other similar apps) but does anyone know whether its alos possible to work work with a 'Work Profile' (enterprise usage). The company I work for creates a secure Work Profile via the Maas360 and I assume this apps checks whether this is a genuine GMS based phone... so would this work also?
[Samsung Galaxy S21 FE] omricn:
I live in Israel, bought my phone a few months ago and I'm afraid I'm not going to receive the A13 update.

I checked and my CSC is MAX, looks like this CSC is for T-Mobile Austria.

What should I do now?
[Samsung Galaxy S21 FE] MaStErB_1984:
Perhaps be patient and wait a moment....or your still able to flash another CSC like EUX which might also be working!
[Samsung Galaxy S21 FE] omricn:
Well I checked here https://samfrew.com/fQ/m/912/r/MAX/o/13/b/b/d/d/and indeed the MAX Region still does not have the update listed as many other regions as well.

Guess I'lll wait and cross my fingers.
[Samsung Galaxy S21 FE] omricn:
Received the update today :)
[Sony Xperia XZ2 Premium Questions & Answers] xtc218:
Hello community, I have a bricked Xperia Xz2 Premium, I was analyzing several posts on how to revive it with QPST, the device is detected but I cannot revive it, if anyone has knowledge on how to revive it, I would greatly appreciate your help.

the device does not turn on, the LED does not light, windows detects it as qusb_bulk.
[Touch Diamond, MDA Compact IV ROM Development] mondilv:
As is.

Just press the "!COOK.CMD" file. (or make your changes before)

Old opinion:

>>8M of PP - after long time of testing looks as the optimal size for performance/RAM.<<

New opinion:):

12M PP looks bit more responsible to interface.

New packages & drivers.

Tweaked several packages - for less memory use.

Tried to put all possible configs in one OEM/xxxconfig folder.

UC ready, - look to _ADDS/Internal Storage forder for example.

Mark all content of "Install" forder as "read only". Or you loose it after install or hard reset.

The best way - look inside "provision.zip" and make your own config file. Put it in "Install" folder and line as

"XML: \Storage\Install\provider.xml" to "sdconfig.txt".

Password for provision.zip you can find at the help page of Connection setup.

You need unsigned HardSPL!

Don't forget about hard reset after first install & make content of "Internal Storage/Install" READ ONLY!

RESOURCES

"LEGO": http://rapidshare.com/users/JW7QII

Snapshots: http://rapidshare.com/users/7L0TM7

Cabs: http://rapidshare.com/users/E8A83X

-=NEWS=----------------------------------

[2009.01.05]

MSXIP21109 & SYS21109(XIP inside) added to "Lego" repository.

-=NEWS=----------------------------------

------Check the time of upload, new version could be there: not the all changes going to the "NEWS" category -------

P.S. Remark for all:

I open this thread for people, who want to make own rom, but don't want spent the time for brutal operations.

Not all components is "mondi's original", - big thanks for

bepe,

swtos,

Niki,

Vic5870,

AVLev,

Prewien,

lexxirae,

and others for ideas and work.

It's only "timepoints" of my kitchen. With bugs, mistakes etc.

Will be glad to see opinions, founded bugs, new ideas.

EVERYBODY CAN USE IT AT ALL, if they use it for private ROM or follow the same "open" politics.
[Touch Diamond, MDA Compact IV ROM Development] Blazeitup123:
i get errors when extracting. winzip says its corrupt and win rar says invalid or corrupt authenticity information. win rar will complete the extration, but i'm not about to flash anything when there are errors. maybe upload again?
[Touch Diamond, MDA Compact IV ROM Development] mondilv:
MD5:

18ebc1fbaaca73df8ff6124ad4296db3 *1.97.20755_Diamond.rar

19befa01daf491d6c838fa8d38d8096a *KITCHEN_20755_WWE.RAR

2bdceea4e5642f9f4066ed858041c086 *1.97.20755.nbh

Check it.

I'm downloading back now. Will see.

Used winrar 3.80

..............

1.97.20755_Diamond.rar has checked: passed

1.97.20755.nbh has checked: passed

KITCHEN_20755_WWE.RAR has checked: passed
[Touch Diamond, MDA Compact IV ROM Development] iXiR:
Thanks man,

going to try it now :)

If I can do anything, just let me know...
[Touch Diamond, MDA Compact IV ROM Development] okokur:
hi,

at first, i have the same problem with extracting (3.8) and authentification,

but it extracts ... i dont know, if some files wouldnt extract?

the second is

"AAAAAAAAAAAAAAAAAAAAAAARGH" !

where you are the last weeks during i flashing my rom with kaiserkitchen

(it's very good, but for beginners its very strong ... with a liitle time spend

and reading here and reading there its gone) ? :)

i cooked my own rom ... i think its 3 houers before ...

its always the same - iam finishing with this one - than an other cooker/flasher puts a new thread and all the works begin at zero.

but that is it what we love i think.

i will use my rom for 3 or 4 houers than i will test/use your kitchen :)

thank you for your work.

okokur

p.s.

my english is not so good and the time its gone to morning,

my comment to your thread means positiv/happy. it dont means any angries
[Touch Diamond, MDA Compact IV ROM Development] mondilv:
Hello!

I repeat: it's not "my" kitchen.

"My" is only changes in OEM/SYS/ROM folders.

I like this kind of kitchen for useful "stepping".

Forgot, where did I find it. Somewhere here:)

Bit later will be update to 20757 (HD ported).
[Touch Diamond, MDA Compact IV ROM Development] pietrucci:
This kitchen seems of no use to me.

It needs .nb, .wrn and other files which are'n present.

Maybe some explanating how to get them, I would like to try it.
[Touch Diamond, MDA Compact IV ROM Development] mondilv:
???

Just press !COOK.CMD.

May be damaged archive? Check the md5 sum to arh.
[Touch Diamond, MDA Compact IV ROM Development] pietrucci:
Ok, sorry it's working now...

Another question: a lot of files are from date 10th of July, for example the manila files. Does this mean these files really are so old???

The latest versions of manila are of a newer date are they?
[Touch Diamond, MDA Compact IV ROM Development] mondilv:
Marked "stable" original Diamond manila.

If you want the alternative - look to the "_OUT" folder.
[Touch Diamond, MDA Compact IV ROM Development] mondilv:
Updated to Blackstone's XIP/SYS 20757.

Manila updated to last "official": 1.1.35097.1_1630.38

Style to gray.
[Touch Diamond, MDA Compact IV ROM Development] dafeke:
I just got my Diamond 2 weeks ago. I cook my first ROM using your kitchen tree but I have some questions:

1. Why the setting up screen is all black ? I thought there were some sort of Windows Mobile 6 background

2. I tried to set up bluetooth but it shows me a message box with something like "No bluetooth hardware"

I follow the instructions by just clicking !Cook.cmd. I didn't change anything in your packages. Did I do something wrong ?

Please advice. By the way, thanks for this kitchen tree.
[Touch Diamond, MDA Compact IV ROM Development] mondilv:
It's just my choice: less using rom/ram memory. And not important at all. You can use yours pictures. It is the kitchen, isn't it?:)

I'll see. I use BT very seldom. Didn't check it, just put the packages.
[Touch Diamond, MDA Compact IV ROM Development] pietrucci:
I coocked my ROM with version 20755: everything's fine here with bluetooth (and all other stuff). I use bluetooth for my carkit, works fine.

I benchmarked this ROM with my usual benchmarks: it's pretty fast compared to others! I left out Opera and Google Maps, but I don't think that makes a big difference in benchmark results.

I will try your Blackstone upgrade this evening, I'm curious if that's faster than the 20755... (in fact I don;t think so).

There is one strange thing in this one: I can't change pagepool. Using pagepoolchanger.exe it says it can't find the right address...

Keep you informed...
[Touch Diamond, MDA Compact IV ROM Development] omaga:
Thank you mondilv for the this kitchens! Great job
[Touch Diamond, MDA Compact IV ROM Development] mondilv:
Agree. I did benchmarks too. (?)

BT fix - in the first post (from 20755 SYS). Works now.

pagepoolchanger.exe don't works to Diamond (use search - don't remember, where is the info). Use hex editor.

...and NB container is reduced by uldr, - only one needed address.

Thanks for cooperation!
[Touch Diamond, MDA Compact IV ROM Development] pietrucci:
I suppose you use the ? because you don't know why I make this remark? Well, if you like take a look at my thread: http://xdaforums.com/showthread.php?t=406640, you can compare this ROM with many others, all tested on the same device, under the same circumstances, more or less.. I will add this ROM's benchmark results later this evening.

PagePoolChanger DOES work on most 'normal' Diamond ROMs, I've used it many times before. But I guess it conflicts with the uldr thing... no problem.
[Touch Diamond, MDA Compact IV ROM Development] suiller:
here friend... like mentioned in a PM sent you this morning... I'm porting some pieces of your base sys/xip for including in my rom (dia duit), of course I'll mention that the base rom comes from your hard work :)

instead of upgrading the whole sys I prefer to choose faster/smaller dlls between different sys :D

anyway also my rom is open, because I strongly believe that this is the only way to proceed to a faster development... by sharing infos each other

but I'll prefer to share the whole kitchen on my 1st stable release, now we are at v08, because till now my rom has some bugs

thx mate!

bye,

davide
[Touch Diamond, MDA Compact IV ROM Development] suiller:
here how to change PP on diamonds:

open final .nbh file with a hex editor (I use pspad)

search the following hex value: 389FE550089FE5

as you find it change next two numbers (in an original rom, these two values are 00 25)

search again for the same hex value, again you need to modify the adjacent two values (in case of an original rom, these two values are 03 25)

values:

for pp 0 Mb: 00 25

for pp 8 Mb: 02 25

for pp 12 Mb: 0C 26

for pp 16 Mb: 10 26

of course I wasn't able to find alone... I found thx to the great & nice Seatone :cool:

have fun :D
[Touch Diamond, MDA Compact IV ROM Development] mondilv:
I was bad surprised too. Quite big diff between close versions. About 5%, isn't it?

After trying several combination of xip/sys me like 20755 at last time.

Or xip757/sys755 - no bad too.

I good know your thread:D

Early, I think. Can't to call its rom stable. Just found more bugs, think not the last for today:) (lighting for missed call is absent; green element in manila)

I return to home now, so new version could be tonight.

May we use different versions?

"My" looks properly worked, but by devhelth.exe - PP didn't changed.
[Touch Diamond, MDA Compact IV ROM Development] mondilv:
It's normal, IMHO.

Info must be free. It's the best way to make good product together.
[Touch Diamond, MDA Compact IV ROM Development] pietrucci:
Ok, I'm still using version 20755 for a few days now.

There are some bugs and stability problems:

- Loosing GPS fix. I'm using TomTom and my GPS fix is dropping all the time, can't get a steady fix.

- Loosing BT connection. I connected my carkit using bluetooth. Every now and then I loose connection with my carkit.

- Threaded SMS: this options doesn't work (I enabled but doesn't work),

These things DO work correctly in other ROMs.

Maybe some problems are solved in version 20757? Maybe I'll try that later this evening...
[Touch Diamond, MDA Compact IV ROM Development] suiller:
here instead... I've ported 757 to my rom (dia duit), but I had to replace most of drivers of 1.97 with the ones coming from 1.96... in my opinion 1.96 still rocks :D

anyway... till now all seems working well, ram managements is definitively better than 755, 8PP is the best balance even if I'm experimenting also with 4PP, so... still investigating but future is really close ;)
[Touch Diamond, MDA Compact IV ROM Development] seatone:
Hey, what do u think! I've spent more than 15 minutes finding out all this stuff and u reavealed it in a second????

Com'on I was just kidding :D

Thank you for the credit, u are as fair as I thought. :)

Happy cooking my friend!
[Touch Diamond, MDA Compact IV ROM Development] pietrucci:
hi suiller,

camera is build 6.00, seems an old build to me... (at least version 6.04 is out)
[Touch Diamond, MDA Compact IV ROM Development] mondilv:
Interesting, will try. I didn't check v. 1.96 serious: 1.97 issued very fast:)

Absolutely agree. I test 6 & 10M too.

At the last moment, 8M PP - the best choice.
[Touch Diamond, MDA Compact IV ROM Development] mondilv:
At "official" Diamont roms I didn't see it.

At Blackstone's rom - 6.06

But I'm not sure, that is the best way.

Up to you:D
[Touch Diamond, MDA Compact IV ROM Development] suiller:
6.00 in which rom? I checked packages ver between 197 & 196 & didn't notice any diff in camera app... :confused:
[Touch Diamond, MDA Compact IV ROM Development] mondilv:
Thanks for feed!

Going to look.
[Touch Diamond, MDA Compact IV ROM Development] suiller:
:rolleyes: I think that thread like this one could help plp to unify their knowledges... anyway thx againg friend... also because I was near to an horrible headache to find the right way to setup the damn PP :cool:
[Touch Diamond, MDA Compact IV ROM Development] suiller:
I'll test GPS with 757 in the next 2 days & I'll give some news here too ;)
[Touch Diamond, MDA Compact IV ROM Development] pietrucci:
For example THIS, it's version 6.6 from Blackstone...

I got it from Noonski's kitchen (hope you don't mind Noonski)
[Touch Diamond, MDA Compact IV ROM Development] suiller:
I ported many apps from HD... but some, as for ex concurrmanager... have older dlls, in fact works better "old" concurrmgr from 1.93 than the "newer" from HD
[Touch Diamond, MDA Compact IV ROM Development] mondilv:
At first, I use 755 now.

So...

After reflash many versions of radio I went back to 1.00.25.05

Result by gmaps (first start): after 8sec - 7 sats, after 20sec - 11.

Tried use it moving car. All OK.

iGo8 works without problems too.

Which kind of radio do you use?

About BT difficult to check situation. At least my handsfree (HTC gadget) works normally. But I use it very seldom - hate this "third ear".:)

About SMS threading:

In config rgu (OEM/xxxconfig) is:

[HKEY_CURRENT_USER\Software\Microsoft\Inbox\Settings\OEM]

"SMSInboxThreadingDisabled"=dword:00000001
[Touch Diamond, MDA Compact IV ROM Development] mondilv:
For package version - look to package/*.rgu

key [HKEY_LOCAL_MACHINE\SOFTWARE\OEM\MASD]
[Touch Diamond, MDA Compact IV ROM Development] ark666:
Hi Mondilv, tried your kitchen and all is ok, nice job.

Have u tried porting new Blackstone build 20764 aku 1.4.3?
[Touch Diamond, MDA Compact IV ROM Development] mondilv:
Good news, but bad time: haven't enough that f* time, now:(

Study.

May be kernel only.

I think we are waiting for new Diamond from HTC now:)
[Touch Diamond, MDA Compact IV ROM Development] ark666:
I tried but sys is hard to port, this blackstone builds are hard to port.

Cheers. :)
[Touch Diamond, MDA Compact IV ROM Development] mondilv:
Yes, sys....
[Touch Diamond, MDA Compact IV ROM Development] mondilv:
Where did you find it?
[Touch Diamond, MDA Compact IV ROM Development] suiller:
personally I test radios using the MS tool fieldtest.exe... it shows you the signal strength of your cell broadcast, so less noise means much power, in fact right now the most balanced radio is 1.00.25.08 (also 07 & bs14 perform well), during these days I'm testing 1.09.25.23

fieldtest is very useful because goes beyond "feelings"... so you can compare signal with different radios but in the same place/situation, for with 05 I have no signal in my lift... instead even if the phone isn't able to call with 08 in the same situation I have a bit of signal... and this is not due to my personal feeling :cool:
[Touch Diamond, MDA Compact IV ROM Development] suiller:
hmm... I'm still having BIG BIG doubts... in adopting 1.97 rom... there is something that didn't convince me, just finished this test: I put the same same pkgs & whatever in 2 EQUAL kitchens... 1st based on 1.97 & 2nd based on 1.96... results are in favor of 1.96

again... newer sys like 20757 "seems" fatter compared to original ones that come with stock rom... & I don't see real speed improvements, it seems just that with 20757 ram leakage is less... but repeat... it seems... after about 1 hour of usage... I can't see if there are real differences

again... if I benchmark both roms also with diff sys/xip I see very very close results... so... why we are frustrating our minds to import newer/fatter sys/xip/roms if results are almost the same??
[Touch Diamond, MDA Compact IV ROM Development] christonge:
I completely agree... I have been using the 1.96 for a good few weeks now and I have to say I´m very happy with it. I cooked up the 1.97 when it came out but it didn´t seem to be as smooth.

The same goes with a lot of the new SYS and XIP I´ve tried.. The diffrence is very very very small... as always newer doesn´t always mean better! ;)
[Touch Diamond, MDA Compact IV ROM Development] pietrucci:
My previous signature was: Newer isn't always better...

If you look in my overview you'll see the superfast ROMs from Swtos and alphazero are 20755...
[Touch Diamond, MDA Compact IV ROM Development] suiller:
yep noticed :)