yashsingh1/xdaforums huggingface dataset:
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] theorioles33:
Its probably the update to NJ7. Yes, you can root afterwards.
[Samsung Galaxy S Relay 4G] Lippen:
Hi.

I have a problem with my Relay 4G : when I*slide the keyboard, the screen turns off, and I*can't switch it on except if I*close the keyboard, and press power button twice.

It is not a rom problem as I*have the same behaviour in the recovery.

Has anyone ever had the same problem ? Using the Relay without its keyboard is a bit shameful...:crying:
[Samsung Galaxy S Relay 4G] demkantor:
My guess is the main flex cable has a small imperfection where midway in the slide it turns off

But either full open or close it works, so this would need to be replaced, not a terribly hard task and you will find a great breakdown of the relay in these threads as well as a few threads of others buying and fixing the cable themselves

Best of luck!
[Samsung Galaxy S Relay 4G] Lippen:
I'll try to open it thanks to the Hardware Guide topic and see if it is broken. I'll also buy a new cable, it's cheap.

Thanks
[Samsung Galaxy S Relay 4G] demkantor:
Thank the guy who made the guide, he deserves it!
[Micromax Canvas A1] ruhez:
Can Anyone give me modern combat 5 blackout 1.0 normal apk file

I had installed 1.0.3b apk but its crashing and if I install any older apk it ask me to update to latest version

Please guys help me

Thank you… .
[Micromax Canvas A1] ruhez:
sorry its 1.0.3 not 1.0
[ONE Accessories] trdspectacoma:
Hi All they have announced that they will make the case for the OPO if we can get 1500 pre-orders. lets do this!!

Heres the link

https://forums.oneplus.net/threads/rhinoshield-crash-guard-bumper-case-preorder.161731/
[ONE Accessories] abhi08638:
Done

sent from my amazingly awesome OnePlus One

don't forget to hit thanks!
[ONE Accessories] paiktaras:
25 + 5 dollars !!!!!

too much
[ONE Accessories] trdspectacoma:
30$ not really for what it is
[ONE Accessories] A Guy Called Revive:
Are you sure? There is no other solution if you want a bumper case for the OPO and if you see the video it's worth it...
[ONE Accessories] Zealotki11er:
Yeah considering its just a bumper. I don't remember the last time i send more then $15 for a case. If it was some high end case with good material i might pay $30.
[ONE Accessories] coltlacey1:
How many are already on the preorder?
[ONE Accessories] 1/4 Life:
Shows it on the preorder page. Currently 87/1400 with 30 days to go.
[ONE Accessories] ASSMO:
JUST PREORDERED! #89!

This is going to be the case that keeps our ONEPLUS protected but gives us our precious back which we all love to feel!

PREORDER PEOPLE!
[ONE Accessories] ucantak3dis:
Idk if we'll get enough people to pre-order to even get this bumper made. I mean It's still in the double digits.
[ONE Accessories] ASSMO:
There is 30 days left and they will give you a refund if they dont get enough. This is by far the most beastly case you can get for our phone. PREORDER SO WE CAN GET THIS SICK CASE! There is no reason not too!

If they reach 70% of there goal they start production so lets get there!
[ONE Accessories] TatesMan:
#96 here
[ONE Accessories] reverenddak:
You have nothing to lose, money will be returned if they don't make the 1400. Plus it's only day 3, and there are 30 days left! That's on track for 3000+.
[ONE Accessories] alex1301:
There is a big reason not too purchase this case. Look at the damn high price! With this money I could purchase fuel for my Simson bike to drive it over a half year!
[ONE Accessories] ASSMO:
Well if you look at an Otterbox they start at $40 bucks. This is a premium case for our beautiful phone. The company has incredible screen protectors and there cases have proven to be really protective.

I want to protect my device but still have the back open. This is the case to do that.

If you don't want a one of a kind case for our device than don't purchase. This is basically the only high end case from a high end company, I pre-ordered right away.
[ONE Accessories] akarol:
1500 pre-orders... lol...
[ONE Accessories] GTCC:
So they want you to pre order a bumper for $30 without seeing it.
[ONE Accessories] KeyperOS:
You know you CAN see the one they made for the iPhone.

Personally, I am not a fan of bumper cases, I do realize that the bulk of the damage on a phone happens on its' sides but I just can't help it, I want a case that covers the back too. That's why my favorite kind of cases are the hybrid "TPU on the sides + a hard back" type.

I can however understand the guys that want to see and touch the back too, especially one as unique as the One's.

If this bumper came fused to a hard back too I could prolly see myself paying the 30+ USD price.
[ONE Accessories] L2_n19h7m4r3:
Use a rubber band.
[ONE Accessories] Hzu:
This is NOT a casing, it's a mere bumper. An Otterbox is a fully protective casing.

$30 for a bumper only; or,

$40 for a fully protective casing.

Which do you think is more valuable? Unless Evolutive Labs show us the design and prove that their bumper really works on this device, I'm not buying this. You cannot believe them right away by watching their iPhone demo. The iPhone is thicker and is easier to get protection from the bumpers. The OnePlus One is very thin and how do you think a bumper (unless bulky), is going to protect the device?

And no, they have NO cases sold or made and used by the consumers. There is nothing to be proven. The iPhone crashguard is still in the Kickstarter stage. Nobody have used it, nobody have proved that their crashguard actually works. This is Evolutive Labs's first take on a bumper.

While I do like their screen protector, but there are still some things that I'm not satisfied but I'm not going into that here. Well, it's up to you. It's your money after all. Okay, how about you prove it to us that it works when it gets on your hands (IF this thing actually make it into production)? For science, of course.
[T-Mobile, Samsung Galaxy SIII] rwfnetworking:
Awhile back I recall reading that the SGH-T599 (4.12) could be unlocked by entering ServiceMode *#197328640#, but on my phone I navigate through the menus and the last screen has no enteries. Does anyone know an alternative free method?

Robert
[T-Mobile, Samsung Galaxy SIII] ShernDog:
This is the Galaxy SIII thread, or SGH-T999, so wrong thread.
[T-Mobile, Samsung Galaxy SIII] rwfnetworking:
I know, but I could not find a thread for the T599 and i frequent this thread. I was just hoping someone might have some idea??

Robert
[General Questions and Answers] edchou3:
Pantech 8010 died while on car charger.

Will not power up. Tried all available suggestions without success.

Cannot be seen by PC if unable to power up.

Need

Contacts and SMS

messages from phone.

"Can't be done" not acceptable "answer".

Took to shops and manufacturer who were not willing or able to recover data.

Need DIY or super cheap method due to budget constraints.

Please,

Working answers only!

Idle banter wastes everybody's time.
[Galaxy Note 8.0 (Tablet) Q&A, Help & Troubleshooti] kunefge:
S-pen does not work on a large portion of the screen, it only works approximately on the 1/8th of the screen (approximately drawn in the attached thumbnail). Within the area, I am able to write, and call shortcuts using the S-pen (such as screenshot, note-taking etc) but outside it there is no response, I cannot even see the pointer when the S-pen is outside this area. (Moreover, there is a very small region (point-like) within this area that when I hover the S-pen over there, the pointer occurs far away outside the box). The touch responses (without a pen), are OK for the whole screen. The problem is only when I try to use the S-pen. My initial guess was that it was a calibration issue, so I tried to reset the s-pen calibration with the Reset Spen app in the Play Store but to no avail. I also tried different S pens, the problem persists for all of them. And the S pens I used, function correctly in other tablets.

The problem occurred after I replaced the display flex cable (as seen in the attached thumbnails). To replace it, I had to remove the motherboard and disconnect some connections . Is the problem because of the different flex cable (that needs re-calibration), or is it that when changing the cable I may have introduced another problem (because I had to remove the motherboard and so)? Can I solve it using a software hack? I would appreciate any help.

Thank you.
[Galaxy Note 8.0 (Tablet) Q&A, Help & Troubleshooti] seedrom193:
I have the same problem but on a smaller scale , about 1/10 of the screen is not responsive to S-pen ,

I will be very glad if someone could help :(
[Galaxy Note 10.1 (2014 Edition) Original Android D] Andmoreagain:
I thought I'd post an update since some progress has been made, though there are still some things missing.

The current plan is to make a unified kernel for all Universal 5420-based devices, including our Note, the 12.2, and Tab S. I've managed to forward-port a lot of the necessary drivers to Linux 3.14. Most come from Samsung's Universal 5422, 5430, 5433 and 7420 kernels (Linux 3.10), while other stuff such as the Mali GPU drivers were taken from one of Linaro's 3.14 kernel trees along with Mali platform support for the Exynos5420-based Arndale Octa board. Currently I have only been focusing on SM-P600 support since that's the tablet I will be testing it on, but once I make sure it runs I'll be adding in support for other devices as well.

What's done so far:

* Maxim max77802 drivers (PMIC, regulator)

* Maxim max77888 drivers (PMIC, MUIC, LED, regulator, haptic)

- These will be used as a base for max77803 support since it's essentially the same driver

* Samsung's TN extension features

* Samsung's USB notify layer

* Samsung's battery/charger/fuelgauge drivers

Also:

* The sii8240 driver has been pulled in, though it doesn't compile yet

* The sensors are all supported in mainline so their drivers can easily be cherry-picked

Todo:

* Port over the LCD driver (LSL101DL01 / LSL122DL01)

- It needs to be adapted to the new display port driver (exynos-dp) instead of the old s5p-dp driver.

- It also requires device tree support, which is absent in 3.4, whereas board files are not supported in 3.14.

- This is beyond my skill and knowledge so if there's anyone reading this who can- and is willing to help please contact me.

* Write a board-specific DT blob.

* Probably a few more things that I'm forgetting.

Source/changelog: here

Feel free to fork this if you wish to help with development, just make sure to notify me if you do. :D

Original post:

XDA:DevDB Information

Unified Exynos 5420 Kernel, Kernel for the Samsung Galaxy Note 10.1 (2014 Edition)

Contributors

Andmoreagain

Source Code: https://github.com/sigma-1/universal5420-device-tree

Kernel Special Features:

Version Information

Status: Testing

Created 2014-10-31

Last Updated 2015-08-27
[Galaxy Note 10.1 (2014 Edition) Original Android D] hitman1376:
Well ... Wish you luck with the Development ...

Dear friend , maybe [MENTION=5529656]xluco[/MENTION] can help us get the device tree so that we can clear a way for AOSP and such ROMs to our SM-P600/1 ... Good Luck

With Best Wishes

Hitman1376​
[Galaxy Note 10.1 (2014 Edition) Original Android D] Andmoreagain:
Thanks, unfortunately I'm not that familiar with the android source code. At least it will probably be easier to gather all the device information once we get everything into a single file.

But anyway, I did an adb pull of the /dev, /proc and /sys directories from my p600. Found lots of useful info, especially for calculating some of the interrupt values. The gpu node is also complete, although I have yet to update my repo.

I'm also going to grab myself a development board tomorrow in hopes of getting a better picture of what I'm doing. I need to be able to visualize things as I work on this stuff.
[Galaxy Note 10.1 (2014 Edition) Original Android D] hitman1376:
Well ... Finally Good news ...

Well ... seems like you know what to do ( And managed it out well :good: ... I took a look into the GitHub ;) ... Good work :good: ) ... but , if there were any problems , I would be glad to help ( I own a P601 but it doesn't matter ... their almost the same ... ) ...

Wish you luck with the Development

Hitman1376​
[Galaxy Note 10.1 (2014 Edition) Original Android D] xluco:
Excellent project mate, good luck! :D I'd offer some support but I don't know a single thing about device trees :P
[Galaxy Note 10.1 (2014 Edition) Original Android D] davidtwood:
So as far as I can tell, Samsung have decided that despite having five free I2C ports, they're going to move four of their I2Cs to be bit-banged on GPIOs. I think this should be sufficient for those four (11, 17, 22 and 24) in a device tree:

i2c_11@0 {
compatible = "i2c-gpio";
gpios = <&gpd1 4 0 /* sda */
&gpd1 5 0 /* scl */
>;
i2c-gpio,delay-us = <1>;
#address-cells = <1>;
#size-cells = <0>;
};

i2c_17@0 {
compatible = "i2c-gpio";
gpios = <&gpb3 6 0 /* sda */
&gpb3 7 0 /* scl */
>;
// i2c-gpio,delay-us not specified?
#address-cells = <1>;
#size-cells = <0>;
};

i2c_22@0 {
compatible = "i2c-gpio";
gpios = <&gpa1 5 0 /* sda */
&gpa1 4 0 /* scl */
>;
i2c-gpio,delay-us = <2>;
#address-cells = <1>;
#size-cells = <0>;
};

i2c_24@0 {
compatible = "i2c-gpio";
gpios = <&gpa2 2 0 /* sda */
&gpa2 3 0 /* scl */
>;
// i2c-gpio,delay-us not specified?
#address-cells = <1>;
#size-cells = <0>;
};

The addresses of the other ports appear to agree with the existing code in exynos5420-pinctrl.dtsi:

s3c2440-i2c.0 = i2c_0@0x12C60000
s3c2440-i2c.1 = i2c_1@0x12C70000
s3c2440-i2c.2 = i2c_2@0x12C80000
s3c2440-i2c.3 = i2c_3@0x12C90000

exynos5-hs-i2c.0 = hsi2c_4@0x12CA0000
exynos5-hs-i2c.1 = hsi2c_5@0x12CB0000
exynos5-hs-i2c.2 = hsi2c_6@0x12CC0000
exynos5-hs-i2c.3 = hsi2c_7@0x12CD0000
exynos5-hs-i2c.4 = hsi2c_8@0x12E00000
exynos5-hs-i2c.5 = hsi2c_9@0x12E10000
exynos5-hs-i2c.6 = hsi2c_10@0x12E20000

-d
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stevethegreat:
Well, HMP is trully what's left missing from this tab. I mean we've got good roms, AOSP support, having its hardware completely unlocked would be the last piece of the puzzle at it were ... Personally it would give me smooth Linux via framebuffer, at it stands it's CPU (core) limited, often maxing all 4 cores, having 8 cores to stretch its legs even with throttling in place (it) would be a blessing. Smooth desktop OS on a Note tablet would be a first.

Hmmm, having no (significant) kernel experience my support would be confined to that of encouragement ... oh well. Good luck to you sir!
[Galaxy Note 10.1 (2014 Edition) Original Android D] Kryptocid:
Hi mate!

I really want to help you but I don't know how to programming in Linux(for the moment) and I know little bit in Android. My hoght school profile is based on IT and programming but unfortunately i don't make on these langage, I'm making only C++ and C#.The point is: I want to help you and the CM devs to resolve the bugs. I'm waiting response form Sand Pox.

If u find me useful pm to me and I will try to help u. Good luck !;)
[Galaxy Note 10.1 (2014 Edition) Original Android D] SamsungGalaxySamsung:
Good luck!
[Galaxy Note 10.1 (2014 Edition) Original Android D] Andmoreagain:
Hey! I just sent you a PM :)

I just put up a new repo with the current progress. I'll add more reference stuff later on, but here's the link to the repo: https://bitbucket.org/sigma-1/exynos5420_lt03wifi_dts
[Galaxy Note 10.1 (2014 Edition) Original Android D] SamsungGalaxySamsung:
Hallo?
[Galaxy Note 10.1 (2014 Edition) Original Android D] Andmoreagain:
So, I think it's time to declare my research on the flattened device tree officially over. What I have thrown together so far gives me a good idea of how the fdt should eventually look like, although it's not completely accurate.

What should happen now is basically device driver development. Since I'm aiming for Linux 3.18.y there are some things that need to be considered. The SM-P600 relies on certain drivers that are exclusively present in the stock kernel, but some of them can also be found in other Samsung kernels which range from v3.4 to 3.10.

Some of these drivers can be swapped out for generic drivers, while others need to be ported over. My current plan is to start by compiling a system with only just the minimal hardware support to make it boot.

Android's branch of the 3.18 kernel has much of the required support already, but there are at least two major drivers that must be implemented, namely the LCD driver and drivers for the max77803 pmic from Maxim Integrated. The latter does not play that much of an essential part as the max77802 pmic which is already supported in the kernel, but one of the things it controls is the charging mechanism which I believe is pretty much essential.

Also, there is no support for the proprietary battery/charger/fuelgauge drivers from Samsung. Hopefully the generic driver works just as well even though I literally have no idea how it will work out.

Our max17050 fuel gauge is already supported, it's just the max77803 "charger" part that needs to be figured out.

Once the device boots, the rest of the drivers can be implemented one by one as kernel modules once they have been adapted to linux 3.18. That's also where device tree overlays come in, which is one of the cool features of the device tree implementation.

So, I guess I'm off to learn how to write linux device drivers. Guess I'll just write the LCD driver from scratch. The Maxim drivers all look very similar so the 3.4 verson can probably just be upgraded in accordance with the ones already present in Linus' tree.

Another thing to note here is that the ARM Mali GPU drivers are not present in the upstream linux kernel. On the other hand, they have been reverse-engineered and implemented into the Direct Rendering Manager (DRM). What that means though is that the proprietary libs will no longer work. Instead, libdrm would have to be implemented into the android source along with its exynos-specific support libs.

The Mali/Midgard drivers could be implemented into the kernel source, but I personally like the open source alternative better as long as it works.
[Galaxy Note 10.1 (2014 Edition) Original Android D] SamsungGalaxySamsung:
Keep it up! Good work (y)
[Galaxy Note 10.1 (2014 Edition) Original Android D] xda_nikita:
Is it worth considering a possible arm port of Ubuntu? How about Ubuntu Touch to make use of SPEN?

So far it looks as though your effort has the depth and scope ... is it something you would consider worth exploring?
[Galaxy Note 10.1 (2014 Edition) Original Android D] Andmoreagain:
I actually intend on starting with building a regular Linux rootfs with a desktop distro such as Ubuntu before jumping on to a full android build. In regards to s-pen functionality, I won't be focusing on that until everything else is working as it should. I hope it can be supported eventually though. I myself would love to be able to draw directly in GIMP or InkScape with the s-pen.

My first aim is to get the u-boot bootloader up and running. That alone would open up a lot of possibilities for future development as well as true multi boot.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Andmoreagain:
So I've been tinkering with this a bit, and I'm currently pulling in some Samsung drivers to a linux-linaro v3.13 tree. I decided to go with this particular kernel base since it's not too different from linux 3.10 and because it has native support for exynos5420 which upstream android/linux-3.10 doesn't. My original thought was to use linux 3.18, but it just presented me with too much incompatibility with the 3.10 drivers.

I've also found a suitable driver for the max77803 PMIC. It's actually for max77888, but our stock driver is based on the max77888 driver and they're almost identical for that matter. Pulled it in from a 3.10 tree along with the battery+motor drivers and a driver for the sii8240 chip. I'm still fixing up some missing includes before I start diffing it against the stock drivers. I'll post an update once it all compiles without an issue.

Edit:

Fixed up some build errors with the sec_battery driver, now running into some "field has incomplete type" error with max17050 fuelgauge driver. Not sure what to make of this so if anyone has any ideas it would be greatly appreciated.

LD drivers/base/built-in.o
CC drivers/battery/sec_battery.o
CC drivers/battery/sec_adc.o
CC drivers/battery/max17050_fuelgauge.o
In file included from drivers/battery/max17050_fuelgauge.c:15:0:
include/linux/battery/sec_fuelgauge.h:60:19: error: field 'fuel_alert_wake_lock' has incomplete type
struct wake_lock fuel_alert_wake_lock;
^
scripts/Makefile.build:308: recipe for target 'drivers/battery/max17050_fuelgauge.o' failed
make[2]: *** [drivers/battery/max17050_fuelgauge.o] Error 1
scripts/Makefile.build:455: recipe for target 'drivers/battery' failed
make[1]: *** [drivers/battery] Error 2
Makefile:816: recipe for target 'drivers' failed
make: *** [drivers] Error 2

Source code: https://bitbucket.org/sigma-1/linux-linaro-3.13-2014.01

I also find Samsung's 3.10 kernels a bit odd looking in some aspects. They still use deprecated macros such as __devinit and __devexit that shouldn't be present in 3.10 at all. Anyway, I'm gonna continue to try and sort this out.
[Galaxy Note 10.1 (2014 Edition) Original Android D] peterpan07:
Hi not a developer (so far) but did someone read about this device here?

There is a Linux running on an Samsung Exynos5422 Cortex™-A15

Its maybe helpfull to get some stuff thats not supported from Samsung opensource

http://www.hardkernel.com/main/products/prdt_info.php?g_code=G143452239825
[Galaxy Note 10.1 (2014 Edition) Original Android D] Andmoreagain:
Yeah, the Exynos series of SoC's are all supported upstream, including Exynos 5420. The current kernel base I'm using comes from Linaro and not Samsung OSRC and it has most of the required support already. The upstream kernel actually has much better and advanced support for the Exynos series than any of Samsung's stock kernels. They just seem to be more interested in actually providing upstream support for the development boards while end-user devices such as phones and tablets get no such support. It's understandable and in most cases this doesn't really make much difference to the end-user. Exynos 5420 is a special case though IMO because our stock kernel still doesn't properly support all the capabilities it has to offer.

The issue we're facing is basically that Samsung's phones and tablets rely on hardware that isn't entirely supported upstream. Like I've mentioned before, an example would be the PMICs that are commonly used in Samsung's products. Usually these are chips manufactured by Maxim Integrated and while a handful of these chips have upstream kernel support, most of them don't and their drivers are exclusively found in Samsung OSRC kernel trees. Thankfully the PMICs are the least of my worries in this context because these drivers are all based on one another and all look pretty similar for that matter. Basically the only thing that truly needs to be worked upon in this early phase is the driver for our LCD (LSL101DL01). If simply adding OF/Device Tree support to the driver doesn't work then it may have to be rewritten in order for it to work properly with linux v3.10 and higher. I simply haven't started looking into it enough to be able to say anything about it at this point. ;)

The PMICs are my current priority, since support for max77802/803 will also be needed for the u-boot bootloader as far as my understanding goes. Otherwise it doesn't seem like u-boot requires much driver support compared to the kernel.

Current todo list:

- Apply upstream patches for max77802 support

- Get max77803 (muic, motor, leds, charger), max17050 (fuel gauge) and Samsung's battery drivers working

- Forward-port the LCD driver to play nicely with Linux v3.10 or higher

- Add device tree bindings for all of the above

Again, any help would be appreciated. I'm personally just learning things as I go along so if there's anyone here who has experience with C/kernel programming and might be willing to contribute to this project or even just provide some insight or ideas, then please let me know! The more, the merrier! :)