yashsingh1/xdaforums huggingface dataset:
[One (M7) Q&A, Help & Troubleshooting] likhon02:
i bought a htc m7 few days back . i did not not use it on kitkat i just updated it to lollipop then i started to notice as soon as i hit power button it would not unlock immediately only the back and home button would lit on and it takes a while to display to light on, sometime it just would not lit.and when someone called me there was nothing on the screen.. i became frustrated i searched but found nothing.. only few threads on xda.. but atlast i found the solution

Solution : Just put a colorful bright wallpaper in your lockscreen and homescreen avoid black wallpaper (optional : crank up your brightness or disable auto brightness) this simple solution put an end to my frustration.. press thanks if i helped :)
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] vache:
​

temasek's UNOFFICIAL CM13 BUILDS​

/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/

Clean Install

Download the ROM

Download GApps

Make a backup

WIPE DALVIK/CACHE/DATA/FACTORY RESET.

Flash the ROM from recovery.

Flash the GApps.

Reboot Device

What doesn't work

CMActions FC on ChopChop on first boot. Ok after a reboot.

Tested on :

XT1622

XT1625

XT1640

XT1642

XT1643

Source :

ROM : https://github.com/temasek

Device : http://github.com/boulzordev

Kernel : http://github.com/boulzordev

Changelog :

https://github.com/temasek/Changelogs/blob/cm-13.0/cm_hlte-Changelog.txt

Download

Screenshots

Bug Reports

Feature Requests

Credits :

Thanks to @khaoticking @latibhullar @elandroido @Silesh.Nair @cool_sid for testing

Thanks to @ashwin007 for the bringup and all his work

Thanks to @elandroido @scritch007 @Shreps for the fixes

XDA:DevDB Information

Temasek for athene, ROM for the Moto G4, ROM for the Moto G4 Plus

Contributors

vache, ashwin007, elandroido, khaoticking, Silesh.Nair, latibhullar, yeshwanthvshenoy

Source Code: http://www.github.com/boulzordev

ROM OS Version: 6.0.x Marshmallow

ROM Kernel: Linux 3.10.x

ROM Firmware Required: Unlocked bootloader, TWRP

Based On: CyanogenMod

Version Information

Status: Beta

Beta Release Date: 2016-08-29

Created 2016-08-29

Last Updated 2016-08-30
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] khaoticking:
Woot released working good by the way one other bug is selinux changer causes fc after first use
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] smitharro:
Sorry to be one of the first to react. You may not like me because I 'leaked' a previous release of you. Since you all seem to be the same developers, why are you making a second CyanogenMod?

Anyway, I'll try it!

Send with my Moto G4 Plus with CM13 (XT1642) using Tapatalk!
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] khaoticking:
We are the same team and I hold no hard feelings you at least acknowledged what you did was a little wrong. We made this one because it doesn't experience the blackout bug that the official version has on my variant which is the xt1625
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] romuloxiii:
Wow!! Thank you so much! I have the xt1625 and have been waiting for CM compatible with the single SIM variant. I can't wait.

Cheers!!
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] briatide:
so it doesn't experience the signal dropping issues that were mentioned in the other thread?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] vache:
It has been fixed since yesterday.

That's why it was not released.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] elandroido:
This by the way is temasek not "stock" cm...
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] cool_sid:
Finally, it's here......!!!!

Way to go guys..... super cool. Great work Vache

Its super cool n I'm making it my daily use ROM now.

N yeah, Laser autofocus does work but is glitchy, yet focuses between two un-equally distant objects.

Not with more. Still it's working I see.:cyclops:
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] stehaworth:
Thanks all involved... Confirmed as working on xt1622 single sim... :)... Even sim card
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] khaoticking:
I feel the need to mention of you have a bug please try to present a logcat when posting the issue it makes things so much easier to solve.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] smitharro:
Ok, installed it and everything working fine!

But: as you're telling here, it's clearly not 'stock' CM... It has nice features in the settings, but this rom is clearly deviating from the original CM. No problem of course, but it'll never be official CM like this! (And that's probably why you guys made a second rom...).

Send with my Moto G4 Plus with CM13 (XT1642) using Tapatalk!
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] vache:
You're right man. Cause there is still blackouts on some devices at first boot with CM, we decided to release the temasek one. The goal is clearly not to became official with this.

We just want to release a working ROM.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] khaoticking:
Exactly we felt that the flashing community was chomping at the bit to get off of stock and we as a team are giving them that opportunity. We don't see a harm in having a slightly deviated version of cm released especially in this case where stock cm has huge bugs that keep it from functioning correctly on certain devices. Yes this is temasek but all in all its still a working cm with a few goodies added in the end its a great place to start.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] DJTeeJay:
What's up, no XT-1644 listed :(
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] c_brown93:
Yeah. Does it work on XT-1644?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] briatide:
When pressing cellular networks from settings, phone crashes and signal is lost temporarily. It also pops up a sim select screen. Also when first started, the signal icon switches from LTE to R and stays as R. Roaming status in sim status says roaming as well. Link to logcat below, let me know if it doesn't work, I've never done before. Xt1625

E: the device is not actually roaming though, as my provider does not allow roaming but everything works

https://drive.google.com/file/d/0BzybIIrBaTbCYVJraFdacDJlc28/view?usp=drivesdk
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] hadesluisk:
Working on xt1641 great rom btw
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] khaoticking:
I'll pass the log on and that's strange mine doesn't do that and I'm running the xt1625 as well
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] briatide:
unsure if it matters but my provider is CDMA with the LTE sim rather than gsm. outside of that I have no idea what might be the cause
[Samsung Captivate Glide] uukgoblin:
Hello,

In order to debug the bluetooth problem, I'm trying to compile a kernel for the Captivate Glide. I can't get it to boot properly.

[MENTION=5545101]steadfasterX[/MENTION] 's SediROM is the highest-version ROM I know of on which bluetooth works so I've got it installed (version 2.1.2) on the phone.

The steps I've taken so far:

1. I have sedikernel from https://github.com/steadfasterX/kernel_samsung_i927 at commit 088aa4109ad144c583f32da5ffba7bac200f0575

2. I copied /proc/config.gz from a running phone, which contains CONFIG_LOCALVERSION="-sediKERNEL-v1.0", ungzipped it and saved it as .config . Haven't changed anything in it yet.

3. I ran `make CROSS_COMPILE=arm-linux-gnueabihf- zImage` (also tried arm-none-eabi- (both from Debian Jessie) as well as ~/Android/Sdk/ndk-bundle/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/bin/arm-linux-androideabi- from the NDK)

4. I also made a TWRP backup of the boot partition, and used split_bootimg.pl from William Enck to split it into a kernel and initrd

5. I then ran mkbootimg with the initrd extracted in step 4 and the kernel obtained in step 3 in arch/arm/boot/zImage

6. Finally I flashed this new boot.img onto the phone with odin (Heimdall, specifically)

I see the white "SAMSUNG" logo (which is normal when booting) with a yellow-triangle with an exclamation mark in it. No further boot stage happens (no bootanim from sediROM). If I re-pack the original kernel with bootimg and flash that via odin, then after the next boot the yellow triangle changes into a blue one and sediROM boots correctly.

I'm a bit stuck at the moment, not sure what's going wrong there. Probably the kernel panics for some reason. Is there a way to read the kernel boot messages before android starts? Any help would be greatly appreciated.

Thanks!
[Samsung Captivate Glide] uukgoblin:
Successful!

Thanks to a lot of help from [MENTION=5545101]steadfasterX[/MENTION] on IRC I finally managed to compile a working kernel :D

Here's a list of steps I had to follow in addition to https://github.com/steadfasterX/android_device_samsung_i927/blob/sediROM_CM-ICS/README.md :

1. as discussed on IRC, `repo sync` was not finding a branch. Needed to add

revision="refs/heads/ics-release"

in .repo/manifests/default.xml in the line with

CyanogenMod/android_vendor_qcom_opensource_v8

2. I removed the spurious comma in device/samsung/i927/cm.dependencies

3. In device/samsung/i927/, I changed vendorsetup.sh to point to vendorsetup.sh.nopatching rather than .patching (none of the patches could be applied)

4. lunch target was therefore the one with -eng, not -userdebug

5. I installed java 6 manually (didn't have sudo)

6. I installed schedtool

7. I adjusted the path to Java and my toolchain in build_sediROM.sh (taken from https://github.com/steadfasterX/android_buildtools )

8. I downgraded GNU make from 4.0 to 3.81

9. I installed linux-headers and created a symlink from /usr/include/asm-generic to /usr/include/asm

10. I changed the toolchain prefixes in device/samsung/i927/BoardConfig.mk to have 4.4.3 rather than 4.7

11. I built with

BUILDID=samsung/i927 LOKIFY=0 ../android_buildtools/build_sediROM.sh bootimage

12. I used the original ramdisk I had extracted from sediROM's boot image, rather than the one that was built (we discussed this on IRC too)

This got me a working kernel, yay :)
[Samsung Captivate Glide] bubor:
its really long guide. You have to replace kernel modules, wifi wouldnt work without modules.

Imho best is compile kernel, modules, replace zImage + modules in this

file and flash from recovery. You dont need to compile whole android just the kernel, you dont need java and other special things, this method is much more faster.
[Samsung Captivate Glide] steadfasterX:
You are right for the kernel but we discussed on IRC to build ram disk too then you need all that stuff but most important he wants to build CM too.

However I'm always a fan of making it right so building a ram disk is the correct way of creating a bootimage. But to start its ok replacing kernel and modules first.

.
[Samsung Captivate Glide] bubor:
correct way is rebuild whole android, and reflash everything, wipe data/cache :)

You dont want to make new ramdisk without replace system. System and ramdisk bound together.

I hope you find something, and fix bluetooth or voip audio.

good luck
[Samsung Captivate Glide] steadfasterX:
Well no and yes. I build kernels including ram disk without building system. This is not necessary as long both are compatible. :eek:

But you are right that booting fails when system and ram disk are not compatible so the correct way depends ;)

However [MENTION=2826508]uukgoblin[/MENTION] I hope you get the fix you want :fingers-crossed:
[Samsung Captivate Glide] bubor:
would you tell me an example when kernel doesnt compatible with ramdisk but kernel does compatible with system?
[Samsung Captivate Glide] steadfasterX:
No no my friend that's not what I said. :cyclops:

I meant if you have CM 9 as system you can build a boot image which includes kernel and a CM9 based ram disk without building cm9 system again. :laugh:

.
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] PsycloneTW:
All,

I am a new owner of a used SM-P905V purchased on Amazon. It's a replacement for my old Note 10.1 2012 edition that died some time ago. I am curious as to what the expected behavior is with this tablet specifically pertaining to charging the device. The purchase didn't come with it's own charger so I have been using the Samsung adaptive fast charger that came with my Note 5 phone, the EP-TA20JWEUSTA model specifically. Now, my old tablet came with it's own proprietary charger and nothing I've found seems to indicate the Note Pro needs a proprietary charger.

So with the above in mind, I am trying to establish the known, expected behavior as it pertains to charging the device. I've observed that the battery will drain if I am using the tablet at anything greater than the halfway mark on the screen brightness slider but seemingly only if the device is below 100% charge when I start using it. It seems that if the device is at 100 full charge and plugged in, I can use it indefinitely while plugged in. Additionally, it seems to charge at a normal pace when it is sitting unused and plugged in.

So, is this what everyone's experience is in general? Would this indicate a need for a battery replacement? Is there a proprietary charger that would offer better charging rates? I have installed a charging monitor app and noticed that the output fluctuates greatly between 40ma and 1300ma when it's sitting idle and charging.

I have cleared the cache, which seemed to help but my expectation is that I should be able use this device while plugged in, regardless of activity/screen brightness and expect that it would charge the battery rather than drain it.

Device is full stock, unrooted.

Any insight is appreciated.
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] ShadowLea:
Sounds normal to me.

The problem with tablets like this is that the screen is LCD(instead of AMOLED, which would cost a fortune) and massive. Which means it uses so much power that all the charger can do while you're using it is keep it level. Lower brightness means less drain.

On top of that the hardware is also quite powerful, which drains it even further.

The original NotePro Charger is identical to the Note 3 N9005 charger and the S5 G900F charger. (I've got all three, same product number and specs.)

Also note that Qualcomm Fast Charge, which comes on the Snapdragon versions of the NotePro, requires a USB3.0 cable.

Original NotePro charger specs:

EP-TA10EWE

5.3V 2.0A

The charger that came with the Note 5(and Note 4) has a lower voltage rating, which impacts charging speed. It's 5.0V 2.0A.

(This one came with the German P905)
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] PsycloneTW:
Thanks for the info. Does .3v really make that big of a difference? I was using the usb 3.0 cable at first then switched to the micro usb cable that came with the phone, I thought the cable could handle it. I'll switch back tonight and try it. Do you know what the US model number is for the above charger. All of the equivalent replacements I can find on Amazon are 5.0V @ 2a.
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] Beut:
It doesn't matter if you're using 5 volts/2 Amps or 5.3 volts/ 2 Amps adapter as the charging current is almost the same: around 1.7 Amps.

However, incorrect USB charging cable will draw less current although it's USB 3 cable, so the important is buying the USB 3 cable designed for this model. It usually is larger in diameter so it can draw more current. If you get around 1 Amps, your USB cable is the wrong one unless the tablet is almost fully charged. Under 90% battery, the charging current should be around 1.7 Amps.

Here is the 5.3 volts adapter

[IMG="5.3 volt adapter"]http://www.mediafire.com/convkey/620e/ay96icd2rg22ah76g.jpg[/IMG]

Then I'm using 5 Volts/2 Amps adapter, the charging current is almost the same

[IMG="5 volt adapter"]http://www.mediafire.com/convkey/2cb8/dnu5gz25995kohw6g.jpg[/IMG]

However, the charging current is less when using the wrong USB 3 cable

[IMG="Wrong USB cable"]http://www.mediafire.com/convkey/f26d/iwtnsdlv7ly62zq6g.jpg[/IMG]

So the key is buying the USB cable specifically designed for the Note Pro 12.2 inches. In above picture, the USB 3 cable is smaller in cable size which is for phone, draws only 1 Amp current. You can use the micro USB too, as charging is the same as USB 3 cable which has only faster speed for data transfer but this micro USB 2 cable must have a rate at 2 Amps, micro USB for phone only draws 1 Amp at max.

This is a micro USB charging cable

[IMG="Mirco USB cable"]http://www.mediafire.com/convkey/bedd/qcu9ur0tr12ju0h6g.jpg[/IMG]
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] PsycloneTW:
Any idea where to find an authentic USB 3.0 cable? I did buy this tablet used and it came with a usb 3.0 cable that *looks* legit in that it is noticeably heavier duty than a standard microusb cable and resembles both of the cables that you show in your pictures, you'll agree there is a very slight difference in appearance between the authentic and the non authentic USB 3.0 cable. One might only be able to tell the difference between them if they were side by side.

I have a regular microusb cable that came with my Note 5. The adaptive fast charger does output 2A. Is it a safe/accurate assumption to think that this microusb cable would be able to support 2A for the Note 12.2?

If not, can you link me to where I could purchase a cable that meets the charging requirements?
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] Beut:
The micro USB is working fine as the USB 3 cable has the same rate of 2 Amps, it's only faster by data transfer because it's USB 3. If you're looking closely, the portion for charging of USB 3 is the same as micro USB, the other one for data. USB 3 cable is the same as micro USB for charging but its data transfer rate is 10 times faster.

[IMG="USB 3"]https://images-na.ssl-images-amazon.com/images/I/416lvhgaweL._SL1000_.jpg[/IMG]

Micro USB cable must be 2 Amps cable, it's usually larger than the 1 Amp cable by size.

However, if you want USB 3 cable, try this one

https://www.amazon.com/Samsung-Sync...8&keywords=usb+cable+for+galaxy+note+pro+12.2
[Windows Mobile Development and Hacking General] serialzs:
@all

anyone know how to develop a two software in one appz..

i mean is "magic button + oxios memory"..or same appz..in one application..

that when you click the X button at the upright corner of our XDAs screen..it will really close the apps and then free-up memories..:D

i think it's a great idea for a new application in our xda..

thanks a lot..

-=[serialzs]=-
[Windows Mobile Development and Hacking General] larsuck:
serialzs, what you smokin' dude? You've been on this forum a year, posted almost a hundred times and you haven't seen any software that does this?

You know, Magicbutton already does this actually. Maybe you have an older version. Go upgrade.

Or if you have WM6 and find MagicButton looks like ****, then try wktask
[Windows Mobile Development and Hacking General] serialzs:
i know what i post..have you read it and understand what i want to say??

or you just posting on without reading it..:rolleyes:

btw..for your information the wktask or magic button doesnt really free-up memory it just closing appz..and it's not same as oxios memory..have you use it both at the same time?

click here < is this the appz are you saying..look at it on what it really does before you comment..what a i***t..

and i dont need your help just to say search in here..i need a programmer that can do this..in one application..have you read it:eek:

-=[serialzs]=-
[Windows Mobile Development and Hacking General] KarhU:
So to let the people understand it better:

You want something like Oxios CloseApps (closes all the apps and hibernates to recover some RAM) - though you want it in a form of a task manager - so it will close task or tasks according to your choice (one or all as in wktask, magic button, x button and all this stuff) and then it will try to silently reclaim the memory (it is not a cool to have a nagging info on reclaimed memory popping out everytime you close a program).

It is an interesting idea to put this functionality together in one app. Maybe you can write a feature request to the authors of these apps (waku listens to these and there are more developers with their own task managers in this forum - pBar and so on - try to persuade them - it should be easier to include new functionality than to build a task manager from scratch).

The problem may be to develop hibernation routine because I think oxios apps are not open source.

Just my two cents...
[Windows Mobile Development and Hacking General] nothin:
QUICK MENU has oxios hibernate-like option, and YES, it can close, what most programs cannot.
[Windows Mobile Development and Hacking General] larsuck:
@serialzs,

Whoa. Damn man, sorry.

Its an easy mistake. When a program closes it frees up ram, so this is what I thought you were talking about. Just trying to help out.

Hope you find what you are looking for. I'm gonna go crawl back under my rock.
[Huawei Watch] misterikkese:
I'm looking for a way to disable the function based on accelerometer for turning on the display by the wirst.

I'd like to bring the display just by tapping or pressing the button.

I've set display always on and gestures off.

Is there a way to disable the accelerometer?
[Huawei Watch] str8spir:
Watch connected=> Android Wear App on phone => Tap Gear ??* icon top right => Device Settings up top and tap on Huawei Watch => Untick Tilt to wake screen
[Huawei Watch] misterikkese:
Many thanks!
[Honor 7 Q&A, Help & Troubleshooting] Nexx_:
Hey,

I wanted to do a nandroid backup so I did adb reboot recovery to go to TWRP, now I can't boot into system, I'm stuck in twrp, I can't even power off the phone it keeps booting up again and again. Please help i'm really lost. Thanks
[Honor 7 Q&A, Help & Troubleshooting] Nexx_:
I did boot to System but with another key combinaison (volume down + power) , I think it's all messed up and the phone thinks that the recovery is the default boot option.. idk how to change this
[Honor 7 Q&A, Help & Troubleshooting] memht:
If you can reach the stock recovery, just put update.app file and install it. If you can't, try to flash boot.img and recovery.img manually. After that, try to install rom again.
[Honor 7 Q&A, Help & Troubleshooting] Nexx_:
Okay thank you, I will try flashing them manually because I have twrp
[Honor 7 Q&A, Help & Troubleshooting] Nexx_:
[MENTION=5391886]DigiGoon[/MENTION] Please can you help me with it?
[Honor 7 Q&A, Help & Troubleshooting] DigiGoon:
You were on which system? Stock or any Custom ROM?
[Honor 7 Q&A, Help & Troubleshooting] Nexx_:
I was on stock b371
[Honor 7 Q&A, Help & Troubleshooting] DigiGoon:
Okay follow these step, if you don't understand any step ask again. But follow these:

Download the UPDATE.APP of the Build number you were on before.

Extract system.img, boot.img, recovery.img, cust.img from that UPDATE.APP

Flash all these files via bootloader mode, to boot into bootloader mode, once a loop is over and you see blank screen on your phone, quickly press Vol DOWN button and while pressing it connect your phone to a PC. If this doesn't work and you get into recovery, then in recovery go to option Reboot, in that select Bootloader.

Once in bootloader mode, flash these files by firing these commands from a CMD, make sure files are situated in the same location where you open up the CMD.

fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot flash boot boot.img

Now after your phone boots up normally, put the same UPDATE.APP from which these files were extracted in dload folder of your external SDcard.

Now switch off your phone and press all the three buttons(Vol UP + Vol DOWN + Power) simultaneously.

Flashing process will start.

Hope this helps. :) :D