yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Core.] nand.96:
How is ur device showing when u power on? There is only 1% chance to be hard bricked!
[Samsung Galaxy Core.] h.d.z:
Ah how u hardbricked? That's never happened to me

SENT FROM..... HMM IDK SORRY WAIT I ASK MY MOM...DONT KNOW SORRY
[Android Q&A, Help & Troubleshooting] dantezyates:
custom kitkat rom for gt-s7262 and how to flash it ? i have cwm recovery and my phone is rooted :confused: phone is galaxy star pro gt-s7262 latest stock frimware J1 india
[Android Q&A, Help & Troubleshooting] sai66666:
OP
[Android One (First-Generation) Cross-Device Genera] KunalKene1797:
♦ScreenShots♦​

​

♦More ScreenShots♦​

Click Here​
[Android One (First-Generation) Cross-Device Genera] DC07:
Great work bro.I'll put this up on the sticky once download links are up. :good:

Thanks for this.

btw Dual Sim?
[Android One (First-Generation) Cross-Device Genera] KunalKene1797:
Yes Bro Dual SIM! :fingers-crossed:

Though Still Under Testing! ;)
[Android One (First-Generation) Cross-Device Genera] Akshatk:
as it is based on CyanogenMod.

does it support data on sim2?
[Android One (First-Generation) Cross-Device Genera] KunalKene1797:
Data on Sim-2 Is Still Not Fixed In The Device Tree By Varun...As soon as it is fixed....All My ROM's Data on Sim-2 Will Be Fixed! :fingers-crossed:
[Android One (First-Generation) Cross-Device Genera] Shreesha.Murthy:
Awesome Work............... Nice Job........... :) :) :) ...................... Expecting MIUI from You! ............. :p :p :p :p
[Android One (First-Generation) Cross-Device Genera] varunrocks17:
Grt work tthak u so much
[Android One (First-Generation) Cross-Device Genera] Shreesha.Murthy:
BUG FOUND : Can't Sign in with Google accounts ...... :( :( ............. Tried with multiple Gapps .... :( :( ........... Can't judge this Rom without Google advantages :( :(

Edit : Can create a new Google account ........ And use the services
[Android One (First-Generation) Cross-Device Genera] KunalKene1797:
Sign In Bug Will Be Fixed In The Next Build! Tha'll Take A while! Now Exams! :fingers-crossed:

Hope You Guys Can Understand! :rolleyes:
[Android One (First-Generation) Cross-Device Genera] startracker:
I gotra fix

Is it saying can't establish reliable network?
[Android One (First-Generation) Cross-Device Genera] KunalKene1797:
The Sign In Just Force Closes, "Google Account Manager Has Stopped"

But The Same Process SignUp Is Buttery Smooth :rolleyes:
[Android One (First-Generation) Cross-Device Genera] startracker:
Gapps problem .try another latest gapps
[Android One (First-Generation) Cross-Device Genera] KunalKene1797:
Got Some Help From Other Too they Asked To Use PA Gapps [FULL]

CrDroid Users Download PA Gapps!
[Android One (First-Generation) Cross-Device Genera] startracker:
No need of full pa minimal will work
[Android One (First-Generation) Cross-Device Genera] Faiyaz5yaz:
many apps getting closed even before launch..

eg : default browser , HTML viewer , and user apps like MX player , adobe , opera . etc ..

is it only me ?,

I made a clean install
[Android One (First-Generation) Cross-Device Genera] startracker:
U gotta change the ROM

Or

Go to cm and come back
[Android One (First-Generation) Cross-Device Genera] Faiyaz5yaz:
Thank u .. and also I don't find Most of the features listed Here .. like pie , hover ,halo and many more .. will they b included in future builds or am missing it ..
[MENTION=5587411]Kunal.Kene.1797[/MENTION] can u help me solve the above problem?
[Android One (First-Generation) Cross-Device Genera] KunalKene1797:
Yes CrDroid Has Updated Its Sources on Git! Future Updates Will Have More Stability and features!
[Android One (First-Generation) Cross-Device Genera] GeekyNoobyGuy:
i am able to sign up but sign in fails, google account force closes :rolleyes: hope it gets fixed soon!
[Android One (First-Generation) Cross-Device Genera] ApriliaM3:
I've cleaned this thread of the disrespect and stupidity (except for the post above).

Please just report the matter in future, so that a moderator can deal with the offender and not have to cleanup pages of retaliation :good:
[Android One (First-Generation) Cross-Device Genera] KunalKene1797:
Thanks a lot! Sir, Can i have the above post deleted (disabled his account)! thanks,

Regards! :)
[Android One (First-Generation) Cross-Device Genera] Ravx:
Hi seems like a nice ROM other than the Google apps bugs.

Is the development continued or is it stopped.
[Android One (First-Generation) Cross-Device Genera] KunalKene1797:
It Is Going On And It Will Be Updated Today Hopefully:o;)
[Android One (First-Generation) Cross-Device Genera] KunalKene1797:
CrDroid Updated​

Download Links Are In The OP​

(Most Probably Fixed All The Bugs, Report Bugs If Any)​
[Android One (First-Generation) Cross-Device Genera] suyash14993:
Awesome bro

Downloading it right now

---------- Post added at 05:57 PM ---------- Previous post was at 05:44 PM ----------

Bro, have you done anything to speed up download speeds...cz i am getting low speeds on stock in spite of having 5 mbps internet connection
[Android One (First-Generation) Cross-Device Genera] karanrajkapur:
Google sign in bug is the only thing keeping me from this awesome ROM which is a daily driver on my Nexus 4!

Expecting a workaround soon. :)
[Android One (First-Generation) Cross-Device Genera] KunalKene1797:
Find a Bug, Report It Will Be Fixed soon! ;)
[Android One (First-Generation) Cross-Device Genera] suyash14993:
FC

systemui fc encountered as soon as the rom boots

cant even go through the setup steps

please fix
[Android One (First-Generation) Cross-Device Genera] KunalKene1797:
Oh sorry i've updated the wrong link...links will be updated soon!:p
[Android One (First-Generation) Cross-Device Genera] Ravx:
Yeah last time I installed this Rom .I came to know that it was cm 11 instead of crdroid. The version prior to this update.
[Android One (First-Generation) Cross-Device Genera] suyash14993:
crdroid

Please upload the link fast and let us know... Eager to use this rom;)
[Android One (First-Generation) Cross-Device Genera] GeekyNoobyGuy:
We All are waiting bro!!! Thanks! ;) [MENTION=5587411]Kunal.Kene.1797[/MENTION]
[Android One (First-Generation) Cross-Device Genera] KunalKene1797:
I am still working on the crdroid fc...its still not fixed, links of R-1 are still available in the OP to download, R-2 will be uploaded as soon as the systemui fc is fixed!
[Android One (First-Generation) Cross-Device Genera] suyash14993:
Update

When will the update link be displayed..?
[Android One (First-Generation) Cross-Device Genera] karanrajkapur:
Please don't ask for ETA. :)
[Android One (First-Generation) Cross-Device Genera] GeekyNoobyGuy:
yeah bro don't ask for eta's! :p

He said that he is fixing bugs in the rom. and he also said that he will release it as soon as they are fixed.

Never ask a developer ETA! ;)
[Android One (First-Generation) Cross-Device Genera] suyash14993:
Sorry

I never asked the developer in arrogance or something

Even I'm a developer and I know it's not that easy

It's just that I'm eager to use R2 of this rom and that question was out of my eagerness

If you guys feel that, that was wrong, well then I'm sorry for that.
[Android One (First-Generation) Cross-Device Genera] KunalKene1797:
Sorry Bro's For The Delay But i am simply not getting time to fix it due to studies...(ma 12th) :p

I'll try to fix it soon later!
[Android One (First-Generation) Cross-Device Genera] -xCeeD-:
Hey bro,

Any progress? :confused:
[Android One (First-Generation) Cross-Device Genera] deccan451:
Latest crdroid chages in kitkat gives FC's and project stopped by developer no more lollipop based crdroid ...:(
[Android One (First-Generation) Cross-Device Genera] -xCeeD-:
Ohh, that's sad. I always wanted this rom. :rolleyes:
[Android Q&A, Help & Troubleshooting] :
Q&A for [AIO] ROOT, CWM RECOVERY, CUSTOM ROM GIONEE E3 CWM v6.0.3.3, XPERIAHD ROM

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [AIO] ROOT, CWM RECOVERY, CUSTOM ROM GIONEE E3 CWM v6.0.3.3, XPERIAHD ROM. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Android Q&A, Help & Troubleshooting] paulspp:
Hi,

confirm that Recovery img being over written do not work for me ,can you tell me how exactly you did root.

I solved -kingoroot
[Android Q&A, Help & Troubleshooting] paulspp:
cwm e3 kitkat

hi,

I did update to version kitkat from gionee and do not find a CWM that works. anybody knows how can put a CWM.

thanks
[Android Q&A, Help & Troubleshooting] kuchuk:
Im using the Indian firmwire, can u please port the touch version for indain one as my volume rocker is badly messed and can't be fixed
[Android Q&A, Help & Troubleshooting] dharmeshdj:
Problem with cwm

i have rooted E3 device...its rooted via frameroot and its k root...but the problem is that via mobile uncle tool the CWM doesnt work...its not getting in to recovery mode...its getting normal boot mode and restarts..dear,... please help me... i had an E3 before this one...now i have bought thi new E3..but not working set up...please help me... and also doents getting it factory data reset...
[XDA Assist] Ahmer Jamil Khan:
Unicode is built into our phone ROMS.

Recently new emoji characters have been released as part of the Unicode 7.0 standard.

So my question is, is there a way we could force our phones to update and get the new emoji without waiting for our ROMs to be updated? Is there a way to install or add it with some app or Xposed Framework?

? ? ?

P.S. I can see them without any additional support on Windows 10.
[XDA Assist] Razvan:
Hi,

I'm afraid you can't do that, without a ROM update.

Sorry
[8125, K-JAM, P4300, MDA Vario Software Upgrading] herzzreh:
Hi,

Running PDAViet3, no issues 'cept for one - softbuttons do not respond when pressing the corresponding hardware buttons. Sometimes it works, sometimes it doesn't (tapping the button on the screen works fine).

Anyone have this?
[G3 Themes and Apps] kadett-k2:
Anyone using HKThemeManager with cm11 thmes on G3? Does it work or not? Thanks
[G3 Themes and Apps] Benny Alex:
Test it by yourself and tell us if it works :)

Gesendet von meinem LG-D855 mit Tapatalk
[Xperia Z1 Q&A, Help & Troubleshooting] QA Bot:
[Q&A] [ROM][UB][4.4.4][Z1]GZR Team Validus Tesla Rom official builds {Linaro+Sabermo

Q&A for [ROM][UB][4.4.4][Z1]GZR Team Validus Tesla Rom official builds {Linaro+Sabermod}

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [ROM][UB][4.4.4][Z1]GZR Team Validus Tesla Rom official builds {Linaro+Sabermod}. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Xperia Z1 Q&A, Help & Troubleshooting] DMondi:
Chrome, hosts

Hi great developers! :)

I`m really like Tesla ROM, but:

1. Chrome browser is running in window mode (how can I fix this?)

2. Can You include full \etc\hosts in next builds?
[Xperia Z1 Q&A, Help & Troubleshooting] abbychauhan:
Its not ROM issue its Chrome issue.
[Xperia Z1 Q&A, Help & Troubleshooting] DMondi:
Chrome

Problem in this

AOSP Lollipop:

public static final int FLAG_ACTIVITY_RETAIN_IN_RECENTS = 0x00002000;

about this write many peoples
[Xperia Z1 Q&A, Help & Troubleshooting] 301stSpartan:
Pocket mode

Hey - I'm facing a slight annoyance, and not sure if it's my fault or a small bug. Thing is that I can't seem to be able to disable pocket mode. Every time I take the phone out of my pocket, the screen turns on. I've disabled it everywhere I've seen it in options, but it is still popping up. I've disabled it:

Notification services => Active display. I've turned this entire feature off, as well as disabled pocket mode and bypass mode.

Lock screen => Notifications on lockscreen => Disabled notification peek and pocket mode

Is there somewhere else I should be looking? Or is it just not disabling like it should be?
[Galaxy S II Q&A, Help & Troubleshooting] QA Bot:
[Q&A] [ROM][4.2.2][AOKP/CM/PA] GT-I9100 Vanilla RootBox [04/08][v4.2][DEVELOPMENT TH

Q&A for [ROM][4.2.2][AOKP/CM/PA] GT-I9100 Vanilla RootBox [04/08][v4.2][DEVELOPMENT THREAD]

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [ROM][4.2.2][AOKP/CM/PA] GT-I9100 Vanilla RootBox [04/08][v4.2][DEVELOPMENT THREAD]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Galaxy S II Q&A, Help & Troubleshooting] steveleeb:
Miracast / Wireless Display

Hi, ive only caught onto the rootbox phenomenon, very nice ROM.

but, the only reason i gave it a go was because i need my S2 to give me the option to use Miracast.

I updated to the 3.9.1 vanilla rootbox after reading an article on it (4.2.2) , i can't find wireless display / miracast anywhere.

where is it?

( i checked settings - display, daydream is there but no miracast.)
[Moto 360] Cr4z33:
I just saw that Ultimate Shield (UK based) released finally a total body protection for our Moto 360 too!

Personally I consider their product quality better than Spigen at a fair better price.

Use their product for both a Samsung Galaxy S4 LTE+ and a LG G3.

http://www.ultimateshield.co.uk/motorola-moto-360-screen-protector/

Disclaimer: I am in no way affiliated blah blah blah <puttexthere> :D

Sent from my Samsung Galaxy Tab Pro 10.1
[Upgrading, Modifying and Unlocking] steadfasterX:
Changelog

sediKERNEL v2.0 (build28)

Enhancements:

Busybox (busybox_nonselinux_1.23.1) added to initial ramdisk (to get all the commands needed for the magic recovery boot keys)

Toolbox added (to get a working reboot command for the magic recovery boot keys)

added magic key press detection for booting into recovery! This superseedes all the problems regarding how to reach the recovery mode when the system is damaged!!

Usage instructions:

Power on the device

when you see the LG logo the first time do

NOTHING

!!

When the screen goes black THEN press Volume UP + Volume DOWN. Both

the same time and hold them

pressed.

Release the buttons

when the screen goes black again

Wait. You will see the LG logo a third time and then you will see the recovery screen!

If you see a kernel crash then you have pressed the magic keys too early! Read and follow the above steps carefully and you should be fine.

ing those keys and be happy!

AROMA flashing ZIP file available! This will flash the sediKERNEL into the right place (boot partition of course ;) ) and wipe dalvik cache for you. Enjoy

Fixes:

sediKERNEL version string was not optimal

Version was "Unavailable" at "About Phone" --> "Software Version" --> "Kernel Version". This was because the regex awaits "()" to filter out the correct version string. So the fix was to add build details into brakes and double escape CONFIG_LOCALVERSION string. Using EXTRAVERSION within the Makefile brakes Kernel module build when used.

Download:

USE THAT ON YOUR OWN RISK!

ZIP flashable file (see instructions at the OP thread):

sediKERNEL v2.0

DD Image file (see instructions at the OP thread): open the ZIP and use the /kernel/sediKERNEL...lok file

sediKERNEL v1.5

Enhancements:

removed all kexec patches and kexec support because we do not need it atm (I want to avoid issues)

added version string to kernel (uname -a)

Fixes:

may fixes kernel crash in rare situations (kexec related)

Download:

USE THAT ON YOUR OWN RISK!

DD Image file (see instructions at the OP thread):

sediKERNEL_JB-v1.5_build6.img

ZIP flashable file (see instructions at the OP thread): N / A

sediKERNEL v1.2

Enhancements:

Will ignore crappy LG bootloader args

Will not do a factory reset when kernel panics occur

Will not enforce LG signed image

Fixes:

This may fixes LG security errors (need feedback..)

May fixes a problem booting custom ROMs

Download:

USE THAT ON YOUR OWN RISK!

DD Image file (see instructions at the OP thread):

sediKERNEL_JB-v1.2_26.img

ZIP flashable file (see instructions at the OP thread): N / A

sediKERNEL v1.0

Enhancements:

Same as stock but build from the sources

Compatible with the locked bootloader (means loki'ed)

XATTR enabled

KEXEC patches applied !

SELinux capable

Booting successful (tested on stock ROM)

Wi-Fi (tested on stock ROM)

Fixes:

TWRP is not unhappy anymore because of missing xattr and selinux ;)

Download:

USE THAT ON YOUR OWN RISK!

DD Image file (see instructions at the OP thread): sediKERNEL_JB-v1.0.1.img
[Upgrading, Modifying and Unlocking] steadfasterX:
Reserved 2

IN THE MEANTIME YOU COULD USE THIS POST FOR ANOTHER THANKS CLICK ;) :D
[Upgrading, Modifying and Unlocking] OfficerJimLahey:
I appreciate all the work being done.

Would this be a solution to "Security Error" bootloops I am getting with my de-bloated ROM?
[Upgrading, Modifying and Unlocking] steadfasterX:
Possible but if you still getting security error bootloops when using this kernel then it may has something to do with a removed LG app.

It depends at which stage that security error occurs. If it appears directly when booting up it should not occur with sediKERNEL but if it booting up and you see the error then first it should be app related.

-----
[Upgrading, Modifying and Unlocking] OfficerJimLahey:
Yeah, the error I received using the stock kernel threw before the boot animation occurred, but after the LG logo.

I read somewhere that the Security Error comes up when you even remove Videos.apk. Hopefully that is kernel related and will go away with sediKERNEL.
[Upgrading, Modifying and Unlocking] steadfasterX:
Well there are 2 stages where the LG logo will be displayed:

1) When powering on the device -> that is a static LG Logo and is shown shortly after powering on

2) When booting the Kernel -> that is the same looking LG Logo but there is a little little animation on it

I think that you will receive that Security Error after stage 1 and before stage 2 so when booting the kernel and that should be fixed using sediKERNEL.
[Upgrading, Modifying and Unlocking] OfficerJimLahey:
Oh okay. It must be ROM based then. Because I think I did get to stage 2 before the security error threw.
[Upgrading, Modifying and Unlocking] steadfasterX:
nevertheless it would worth to try the sediKERNEL ;)
[Upgrading, Modifying and Unlocking] OfficerJimLahey:
Agreed. I will hold off until v1.5 is released since that one looks more promising. :D
[Upgrading, Modifying and Unlocking] steadfasterX:
Latest available version

sediKERNEL v1.2

Enhancements:

Will ignore crappy LG bootloader args
Will not do a factory reset when kernel panics occur
Will not enforce LG signed image

Fixes:

This may fixes LG security errors (need feedback..)
May fixes a problem booting custom ROMs

Ok no appologies anymore try it ;)
[Upgrading, Modifying and Unlocking] OfficerJimLahey:
So I noticed a couple things over the past few days with the kernel.

The first is minor. When doing a reboot from recovery you need to make sure the USB cable is disconnected. The impact is that the phone goes to charge mode if the cable is still connected.

The other, well, gives a real good reason to have the really bulletproof method with TWRP. The hotkeys to the bootloader no longer work. I was testing an AOSP keyboard with my ROM (think I know what to do now) when the setup wizard crashed continually, leaving me soft bricked. Luckily download mode still works.

So tonight I am using the spare, until I get the F3Q rooted, recoveried, and restored (again).

Not to complain, I really appreciate all the work done, thought you would want to know any drawbacks with the current version.

Sent from my MyTouch 4G Slide
[Upgrading, Modifying and Unlocking] steadfasterX:
Many thx for your feedback!

Hm interesting. I use method 2 and the hotkeys are still working. AFAIK those hotkeys are integrated in the bootloader and that one will never be touched by any method. Strange..

-----
[Upgrading, Modifying and Unlocking] OfficerJimLahey:
There are so many hotkey variations across brands I lose track of the combo (keys pressed, how long). But I did try pwr +vol-dn, pwr + vol-up, even the three finger salute. Sometimes holding until the first LG logo shows, other times until the boot animation comes up (that's when I know I am screwed). I could still be doing it wrong...

Where is the bootloader stored anyway? Could it be that the opportunity for loading the bootloaders factory reset is during the kernel loading stage? TWRP kernel could still have those functions/flags. With a flipped boot and recovery image noted in method 2, that would make sense why your setup works.

Sent from my MyTouch 4G Slide
[Upgrading, Modifying and Unlocking] steadfasterX:
The trick is to take out the battery , pressing vol+down and power while putting back the battery again. This will work 100%.

Any tries without putting out the battery may not work.

The bootloader is in "aboot" partition and i do not think it will have to do with the kernel. The reason why I can say that for near sure is that:

I tried to grab the key pressed while booting up which will be done in the init process. You can define things within an init script also key presses but they do not work while _booting_! They will work when booted up only so I tried to find out any other methods. The most meaningful would be to do that manually by writing a program to grab the key events. But at least I can say that I found no ressources about doing that other then described.

Because of that and because the bootloader steps into factory reset before kernel loads I do not think that there is anything kernel related. I think that the battery pull out will work in any case...

-----