yashsingh1/xdaforums huggingface dataset:
[Chromebooks] SolidIcecube:
I have a Lenovo ThinkPad Chromebook 11e that I want to turn into a Windows machine. The interesting thing with the 11e is that its motherboard is very identical to the Windows Touch Version of the ThinkPad 11e. The case was reused for both models. SO it actually has an empty cut out for a 2.5" HDD. The thing is the Motherboard connection for the HDD is was not soldered on (obviously because it is a Chromebook with built-in 16gb of SSD. Chromebooks never have/need much storage.) [IMG="Windows version 11e"]https://imgur.com/a/u3TVygP[/IMG] [IMG="The 20pin connector I need. Missing on my motherboard."]https://imgur.com/gallery/NkuNNsp[/IMG]

If there is a way to find the connector found in the images and solder it to the empty spot on my Chromebook, I believe I can convert it into a windows machine. I've looked everywhere and can not find the 20pin connector that solders to the motherboard. I have however found the 20pin connector that plugs into the port on the motherboard. If I can't find the port. What is yall opinion of me taking the 20pin to SATA adapter and soldering it directly to the blank spot on the board? Would that even work? [IMG="Where the port is supposed to be."]https://imgur.com/gallery/xuLeZPK[/IMG]

Thanks for any suggestions on this little modding project of mine.
[Chromebooks] MedykPL:
HDD mod

I have 11e yoga (glimmer) and just yesterday drilled a hole in case and now I have HDD inside and a SATA to USB connector outside case, also I want to install additional OS on internal eMMC in case when i forgot to take the SATA>USB connector. It's not very pretty but I think that it's the easiest way to mount a hard drive in this chromebook, also when it's in sleep mode i can unplug the connector and plug in before i wake it up so when i want to take it somewhere it's not a problem.

And what important despite that it's and old HDD it's faster than the eMMC memory.

Sadly because I have new account limitations I can't post any photos how i made it :(
[Chromebooks] LeRobE:
Did you find the connector and did you do it?

I bought a cheap 11e with a 16GB eMMC. It got room for an HDD/SSD but it's also lacking that connector. Was thinking same thing, would it be doable to solder on a connector and attach a HDD or SDD. And which parts would be needed.

I can't see your pictures though.
[Chromebooks] LeRobE:
Would be interesting to see some pics. Do you run one OS from the eMMC and another from the HDD?
[Chromebooks] SolidIcecube:
My current set up is ChormOS installed on the eMMC (I like to switch back and forth) then Windows 10 installed on a Micro SD card in the SDHC slot. I used a Micro SD card to Sata adapter I bought off Aliexpress inserted in my Windows computer so I could install Windows 10 to the 128gb Micro SD using recovery tools USB (The Windows recovery enviroment was fooled into thinking that it was a normal HDD lol). Thats how I am currently running Windows.

Unfortunately It seems the connector is a dead end, as there need be capacitors that route the Sata power. Upon investigating I discovered that the Windows version of the board is slightly different, so its difficult to reverse engineer (at least for me I'm not very circut board knowledgeable lol). I met a user on reddit who also had simmilar request. They were able to Add a SSD by using a Sata to USB 3.0 adapter, which they soldered to the inside contacts of the USB 3.0 of the motherboard. Thus giving them an internal Hard drive (at the cost of loosing the usb of course). I was intending to do the same, however I plan to use a USB 3.0 pcb hub that I found on ebay to retain use of my USB port and gain two additional internal USB ports. Mind you I haven't had time to work on this project as of late, so I'm not sure how it will pan out. Here is a imgur link to photos showing the "Sata to USB 3.0 adapter" soldered to the main motherboard of the Lenovo 11e (as well as a comparison photo of the chrome and windows version of board). The soldering to USB seems to work pretty well for them so I dont see why my hub idea wouldn't work. Only thing in question would be power drain, I suppose.
[Chromebooks] LeRobE:
Thanks for the detailed info and pictures! Interesting! Sounds like a good idea with the USB adapter.

I haven't decided yet which route to go, or if I should continue with this project. I've struggled to get it to boot from USB and I guess it needs to be flashed with RW-LEGACY firmware to make that happen.

Btw. how does Windows 10 run on it?

Is it the 1st gen 11e you have?

EDIT: I did flash it with RW-LEGACY and booting from USB works.
[Chromebooks] SolidIcecube:
RW-LEGACY? You should get UEFI using this guide. Works fantastic!

And yes, I'm using 1st gen Chromebook 11e (the non-touch one, just to be clear)

The Windows 1909 image I use to install works fine as long as I run "windows debloater" or "winslap", and then disable updates. Once I start updating is when it slows down and things get messed up. I should probably configure my own stripped down image of Windows 10, but I just haven't had the time. Upon a fresh install, I can download and play Minecraft and it runs smooth enough. I've had to reinstall windows and start over three times now, however. I probably get too carried away and download too much stuff, and that is what causes massive slowdown to the point It's just faster to reinstall. Besides my clunky storage management and process drain I put on the computer by running programs just a tad to strong for it, Windows 10 runs smoothly when not doing those thing. Overall I'm impressed with what you can get away with on a Chromebook of all things!
[Tilt, TyTN II, MDA Vario III General] JKingDev:
So I have a shiny new Kenwood KDC-BT838U and for a $220 dollar toy it is pissing me off very much. It does not automatically connect or disconnect from my phone when powering on or off. Simple fix for that is an app to manually establish connection. a2dp will be running fine, then a call comes in. After the call sound will not work and I get all kinds of connection issues until I just power down the head unit then turn it back on (sometimes a few times).

I tested my kaiser with other bluetooth HU's and it worked fine. Then kenwood was not in the store but I love all its other features and it looks great. I contacted Kenwood support and they said that it is a problem with my phone's bluetooth protocol. I decided to give Kenwood the benefit of the doubt. I want to try the widcomm stack.

Found it here.

http://xdaforums.com/showpost.php?p=1072773&postcount=72

I have read that it works with the kaiser. True? After installing the cab, do I need to delete the MS bluetooth reg key or do anything special?

Any Kaiser widcomm users out there? Can you comment on any issues you have? Thanks!
[Tilt, TyTN II, MDA Vario III General] JKingDev:
I went ahead and installed the cab linked above. At first I was getting the out of memory error on boot. I changed the baud rate ([HKLM\Software\Widcomm\BTConfig\SerialTransport]) to 115200 and it appears to be working now. Will report more findings later. If anyone else is using it please share your experiences here. Pretty much all the threads I found by searching were people with the same question and they pretty much all went unanswered.
[Tilt, TyTN II, MDA Vario III General] JKingDev:
Wellit only thinks it is working. Kasier would not find any bluetooth devices near by and my computer cannot find my kaiser. I guess I will give up now but if anyone else got it working please let me know.

Oh BTW, don't install the CAB unless you don't mind a hard reset. I was prepared for that of course, but just a heads up.
[Samsung Galaxy A7 (2018) Guides, News, & Discussio] JHAM2005:
Download the Samsung firmware for the Galaxy A7 2018 SM-A750G with product code CPA from Panama (Claro). This firmware has version number PDA A750GUBS6BTE1 and CSC A750GOWA6BTE1. The operating system of this firmware is Android 9 , with build date Fri, 15 May 2020 03:19:56 +0000. Security patch date is 2020-05-01, with changelist 16854835.

Model... SM-A750G - A750G/DS

Model name... Galaxy A7 2018

Country... Panama (Claro) (CPA)

Versión... Android 9

Changelist... 16854835

Build date... Fri, 15 May 2020 03:19:56 +0000

Security Patch Level... 2020-05-01

Product code... CPA

PDA... A750GUBS6BTE1

CSC... A750GOWA6BTE1

INSTRUCTIONS * 5 Files *

1.- Download Odin 3.14.4 - Install Samsung USB Drivers

2.- Extract the firmware file you just downloaded. You should get 5 files:

AP (System &Recovery)

BL (Bootloader)

CP (Modem / Radio)

CSC_*** (Country / Region / Operator)

HOME_CSC_*** (Country / Region / Operator)

3.- Add each file to its respective field in Odin v3.14.4. Use CSC_*** if you want to do a clean flash or HOME_CSC_*** if you want to keep your apps and data.

4.- Reboot your phone in Download / Odin mode (make sure your device is off) with the following button combo: POWER + VOLUME DOWN + BIXBY

Other options in case first option did not work or isn't possible.

Option 2 VOLUME DOWN + VOLUME UP then USB cable

Option 3 POWER + VOLUME DOWN + VOLUME UP

Option 4 POWER + VOLUME DOWN + HOME BUTTON

Option 5 (Note9) USB cable + VOLUME DOWN + BIXBY

Option 6 (Note10) POWER + VOLUME UP

5.- Once in download mode, connect your phone to the PC, preferably using the original USB cable you got with your phone. Odin should detect your device and a BLUE box will show up with the COM port number. (Be sure, the SAMSUNG-drivers are installed on your PC!)

6.- Do NOT tick any extra boxes. The only options to be ticked are F.Reset Time and Auto-Reboot.

7.- Click the start button, wait for Odin to say 'PASS' in a GREEN box. Once the flash is complete, your phone will reboot, and you can disconnect your phone from the PC.

Download Samsung USB Driver for Mobile Phones

https://developer.samsung.com/mobile/file/68b2dc40-3833-4a8b-b58e-32f7aca25c00

Download Odin 3.14.4

https://dl2018.sammobile.com/Odin3-v3.14.4.zip

Download Firmware

https://samfrew.com/download/Galaxy__A7__%E2%91%A7__/sw2m/CPA/A750GUBS6BTE1/A750GOWA6BTE1/

Or

Download Firmware

https://www.sammobile.com/samsung/galaxy-a7-2018/firmware/SM-A750G/CPA/download/A750GUBS6BTE1/340041/

Root + Recovery

https://xdaforums.com/galaxy-a7/development/recovery-twrp-3-2-3-1-galaxy-a7-2018-t3876798
[Samsung Galaxy A7 (2018) Guides, News, & Discussio] rogersrafols:
thank you for this sir....
[Samsung Galaxy A7 (2018) Guides, News, & Discussio] vaidhy2007:
Hi, In the indian version of a7, I am unable to downgrade from 10 to 9. The phone is showing that binary is mismatching. How to downgrade ?
[Samsung Galaxy A7 (2018) Guides, News, & Discussio] Flydie2:
Downgrade from 9 to 8?
[Samsung Galaxy A7 (2018) Guides, News, & Discussio] Johannj22:
If the binary is mismatching it's not possible to downgrade.
[Samsung Galaxy A7 (2018) Guides, News, & Discussio] chrisssj2:
Why would you downgrade from 10 to 9? anyone?
[Samsung Galaxy A7 (2018) Guides, News, & Discussio] VineVince:
tysm sir salute
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this ROM.

Try this build at your own risk. It's likely to have bugs and is EXPERIMENTAL as it is a work in progress. It boots and seems to work fine on my SM-T350, but I have only tested it for 24 hours. Problems will likley surface later?

BACKUP YOUR FILES and have a copy of your working image BEFORE trying my build.

What works.

1. bluetooth

2. wifi

3. brightness

4. external audio

5. GPS

6. audio through headphone jack

7. Google play store - use pico apps

8. flip flap smart cover

9. audio over bluetooth

Note: first initial boot takes a bit longer, be patient.

Known problems.

1. Home screen text may look fuzzy.

Text on home screen looks funny/fuzzy. This only seems to affect the home screen and nowhere else. I have seen the same problem on the SM-T350, SM-T560NU, SM-P550 and Nexus 7 2013.

Problem is with stock trebuchet launcher and/or its fonts. I tried rootless pixel launcher from fdroid as a quick and simple test and see no problems with home screen text. Rootless pixel uses a different font though. A future LineageOS update could resolve the problem?

Rootless Pixel Launcher | F-Droid - Free and Open Source Android App Repository

F-Droid is an installable catalogue of FOSS (Free and Open Source Software) applications for the Android platform. The client makes it easy to browse, install, and keep track of updates on your device.

f-droid.org

OR you can use nubianprince's crdroid 10.0 build for this tablet. He used his 9.0 repos and has no problems with fuzzy fonts/text. See

https://xdaforums.com/galaxy-tab-a/development/rom-galaxy-tab-8-0-t4158163

OR you can use a fairly recent 16.0 build which doesn't have the problem.

2. The stock Jelly browser crashes a lot. Use a different browser. There's lots of better options that are more stable and reliable than the built in Jelly browser.

3. FM Radio is not support since this device doesn't have the LTE functionality.

4. Stock camera does not take picture on front facing camera. Use open camera instead. I don't know when stock camera was broken, but when I tested the March 7, 2021 build, it doesn't work.

Open Camera | F-Droid - Free and Open Source Android App Repository

Camera App

f-droid.org

5. BOE panel

For people who get black or blank screens when trying to flash TWRP 3.3.1 or LineageOS or crDroid SM-T350 roms, it's likely you have a BOE sourced panel.

adb root
adb shell cat /proc/cmdline

The very last parameter will be mdss_mdp.panel. If you see BOE anywhere in that string, then you have a BOE panel. For example,

mdss_mdp.panel=1:dsi:0:ss_dsi_panel_S6D7AA0_LSL080AL03_BOE_WXGA:1:none

There is a fix as documented at

https://xdaforums.com/t/rom-sm-t350...galaxy-tab-a-8-0.4158163/page-3#post-83488241

Thanks/Credits

Thanks to @nubianprince and @lividhen99 for ideas and suggestions on getting this build to work. I used one of nubianprince's repos for this build.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
FAQ - I spent hundreds of hours building this rom. The least you can do is spend a few minutes reading everything before posting.

Q1) Does the build work on xyz?

A1) I have no idea. I only have the SM-T350. You can try it on variations, but don't be surprised if you get bootloop or bricked hardware. In addition, I won't build it for the 355 (LTE) version.

Q2) Application xyz doesnt' work. Can you fix it?

A2) I only fix what I use. If you use app xyz and it doesn't work, then try 16.0 or going back to the last rom that worked for you.

Q3) My tablet hangs or crashes with 17.1. This build is slow and buggy. Can you fix it?

A3) Go back to the last working stable rom for you. 17.1 is a work in progress and will have bugs and frequent changes.

Q4) Do you plan to update the rom?

A4) Yes as long as I have high speed Internet, I wil try to release the rom monthly to incorporate the security patches.

Q5) What TWRP should I use?

A6) TWRP 3.3.1 or 3.5.0.9. Get it from

https://xdaforums.com/galaxy-tab-a/development/rom-galaxy-tab-8-0-t4158163

Q6) What is the difference between this rom and crdroid?

A6) Use this rom, crdriod or stock. It's not a popularity contest, so use whatever fits your needs. I only offer this as an option for those who want or need a new rom. Most of the code is the same between this rom and crdroid, however, the way we implemented the fixes might be slightly different. In addition, if there is a bug in this rom, it may not be in crdroid due to coding differences and how it's fixed.

Q7) Can I turn off the on screen navigation keys?

A7) To turn off on screen navigation, go to settings, system, advanced, gestures, system navigation, gesture navigation.

Q8) Can I build this rom? Where are the source and kernel source files?

A8) Yes. I have uploaded the repo diff and roomservice.xml file. The kernel source files are at

Samsung MSM8916 Devices

Samsung MSM8916 Devices has 68 repositories available. Follow their code on GitHub.

github.com

The repo diff is what I changed compared to "stock" msm8916 code. The majority of the repo diff is because there's a bug in 17.1 WiredAccessoryManager.java and I reverted back to the 16.0 code. The bug prevents audio through the headphone jack. See

https://xdaforums.com/showpost.php?p=83445681&postcount=13

Q9) Where can I download this rom?

A9) You can find the 2020 17.1 and 16.0 builds at

Downloads for : Samsung Galaxy Tab A 8.0 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

androidfilehost.com

I'm moving to sourceforge for all 2021 uploads. The main reason is that I would like to see the stats of where this rom is being downloaded from worldwide. All 2020 builds will remain on androidfilehost.

2021 builds found at

retiredtab - Browse /SM-T350/17.1 at SourceForge.net

sourceforge.net
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
TODO

1. document and upload long list of fixes you need to build 17.1 if you want on your own.Done.

2. mirror nubianprince's repo in case it gets deleted.Done.

3. upload some files, fixes and documentation to github for future.Done.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Oct 8 build released. See post #4 for changes.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Hexrotor:
I set the time to Oct 18 but it was changed to Jan 18 after reboot, then October 9. I remember that crdroid have the same issue.

See this logcat:

01-18 08:52:10.608 680 680 I SystemServer: StartAlarmManagerService
01-18 08:52:10.611 680 680 D AlarmManagerService: Kernel timezone updated to -480 minutes west of GMT
01-18 08:52:10.611 680 680 I AlarmManager: Current time only 1471930611, advancing to build time 1602188073000
01-18 08:52:10.611 680 680 D AlarmManagerService: Setting time of day to sec=1602188073
10-09 04:14:33.001 680 680 W AlarmManagerService: Unable to set rtc to 1602188073: Invalid argument
10-09 04:14:33.006 680 680 D SystemServerTiming: StartAlarmManagerService took to complete: 10ms

Backlight problem is still in my BOE device. I don’t know which logs are necessary, so I kept most of them. The logs about BOEpanel of crdroid are same with Los, but may be different in other places.

:)Hope it could be solved.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] reukiodo:
Which TWRP image are you using? I've seen a couple different ones, but since there's no official support over at http://twrp.me/ I'd prefer to use the same one you're using to test this ROM installation...
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
I'll take a look, but right now I have a big project that I need to get finished by mid November so my time for building and troubleshooting roms is limited right now.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
TWRP 3.3.1
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
These messages

D modemanager: Panel Name: S6D7AA0_LSL080AL03_BOE_wxga_video_mode_dsi_panel

E modemanager: readXMLOp:Couldn't open OEM XML file!

E modemanager: retrieveMode: Failed to enumerate modes

E modemanager: instantiateModeMgr: Failed to update default cache!

E modemanager: readXMLOp:Couldn't open OEM XML file!

E modemanager: retrieveMode: Failed to enumerate modes

E modemanager: in applyDefaultMode fail to retrieve default mode!

I modemanager: in applyDefaultMode ret = 0 mCurMode = -1

are from the proprietary module (which is why I couldn't find them in the AOSP code)

system/vendor/lib/libmm-qdcm.so

If you search for those keywords above, they all appear in this module.

At this time, I have no idea what the libmm-qdcm.so does and how it controls the backlight, if at all.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] spiramedia:
can someone provide link for twrp 3.3.1 for t350? i just can't find it.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
From

https://xdaforums.com/galaxy-tab-a/development/rom-galaxy-tab-8-0-t4158163

TWRP 3.3.1 is at

https://drive.google.com/file/d/14T99LQaKtEhGeglFxrUm0kMRw_RKopP5/view
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] spiramedia:
me t350 just shut's down on his own. clean install.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Works fine for me and others.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Hexrotor:
[MENTION=4052504]spiramedia[/MENTION] Maybe your device is using BOE panel, try to Illuminate the screen with a flashlight.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] spiramedia:
mine is BOE. But i have no problem with this. The tablet just shuts down when using it. Maybe it overheats.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
[MENTION=4052504]spiramedia[/MENTION], when asking for help, it helps us if you provide maximum information. For example,

1) What are you running when the tablet shuts down? High performance gaming? Watching youtube?

2) How long does the tablet run before shutting down?

3) Maybe your battery is really old and weak especially if you used it daily for 5 years?

4) If you think it overheats, you can download several CPU apps that tell you the temperature of the CPU like

https://f-droid.org/en/packages/com.kgurgul.cpuinfo/

5) If the battery is old and weak, does it shutdown when you have the AC microusb adapter plugged in all the time?

6) When it shuts down, what is the battery percentage at?

7) Is your battery guage calibrated properly? If it says 30%, maybe it's really 0% and you have to discharge/recharge 2 or 3 times to recalibrate?

As you can see, I asked a lot of questions. The more info you can give, the better.

PS. If you have a BOE panel and backlight works, then I have no idea why my rom works with yours and not Hexrotor.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
@Hexrotor, does this happen if you date and time setup to "use network provided time".

If I turn "use network provided time" off, then yes, the tablet doesn't keep time properly. I think it's due to the Qualcomm RTC being read only? Searching the Internet, a possible fix might be

https://github.com/LineageOS/android_hardware_sony_timekeep

I might try incorporating that into the next rom build which will likely be sometime mid Nov when the next security patches are released.

I think it's defaulting to Oct 9 because the build date is Oct 8, but in your timezone, it might be Oct 9.

The error messages for the BOE panel are just before the system stops the boot animation and gives the 3 dots and says LineageOS. I find that to be confusing because I would think the kernel would enable BOE backlight at the very beginning so you can see what is on the display. It makes no sense to have the backlight completely dark and then enable it just before the 3 dots that says LineageOS.

And if spiramedia's BOE backlight works with my rom, then I don't know why it doesn't work with yours. Maybe there is something persistent in one of the persist partitions where a prop is set?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
@Hexrotor, you didn't specify in this thread or the original crdroid thread whether you tried downgrading the stock to marshmellow and then try crDroid 10 or LineageOS 17.1.

Apparently, it fixes the no backlight for some people? See

https://xdaforums.com/showpost.php?p=83488241&postcount=41

It's possible the marshmallow firmware has something coded into the file system partitions that fixes the BOE? Maybe someting in the aboot partition?

Let me know if you have tried downgrading or not as per above.