yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] ItinerAecus:
Yes, the manufacturer sent me a replacement SD card after the original became stuck as read-only and could not be formatted.
[Android Q&A, Help & Troubleshooting] iXaidyiu:
What's your manufacturer? SanDisk or Toshiba or others?
[Android Q&A, Help & Troubleshooting] ItinerAecus:
This was a Lexar SD card. The RMA process was very straight forward.
[Xperia SP Q&A, Help & Troubleshooting] rcallmann:
Hello fellows.. Yesterday my Xperia SP updated for cm-13.0-20160625-NIGHTLY-huashan and google play service has stopped.. How can i fixe it... I tryied install gapp pico but the problem is increase no setup wizard has stopped also like google play serviceT... hanks a lot
[Xperia SP Q&A, Help & Troubleshooting] penn.gwyn:
Start post of the CM13 Q&A answers this
[XDA Assist] mohamed thebear:
:silly: delicious matter for xda-developers [!!help me!! my bricked device keeps reconnect and disconnect quickly 3 sec with my pc ;so I can't restore stock rom on my device]

hi guys,since two day I've flashed my device with wrong rom :angel:{I'm not know about flashing wrong rom because I browsed a lot of porting roms subject in some forums then I've become able to flash my device and I've knowledge about this operating but I believed like this "now I owned the world " :laugh:after installing custom recovery cwm and backuping overall the device}.

however I flashed three rom adapted with my tablet before porting the wrong rom.

in abbreviately,after wrong rom the tablet is in boot loop 5 sec and restart,is it stuck in manufacture lego:eek:

which are mayhem picture after flashing the wrong rom then restart again .

I try and try again to booting into custom recovery

but is unuseful the tablet not reach custom recovery with pressing (vol.up button +pwr.button)

or reach factory mod with pressing (vol.down button+pwr buttton).

now,I try to fix the problem when connect the tablet with my pc via usb cord

,my bricked device reconnect & disconnect with pc quickly almost 3 sec ,usb cable otg is perfect functional though

is it occurring (I able to driving the tablet but I am not able to flashing with flashing tools such as : sp flash tool & mtkdroid tools)

the trouble is not fix when pressing (vol.up or vol.down or both these or both these with pwr or pwr alone ) before plug otg cable with my pc.:eek:

I searched and watched solved mtk problem on youtube but my trouble is not similar anything of this problems

and nothing about this on sites and forums.:crying:

in addition to :

I disassembly the case of my tablet and disconnect the battery connection with tablet motherboard

but same result. :(

!!!!please tell my how to fix this trouble!!! and able to flash stock rom

detail device :cowboy:

name :CCIT A799W (china tablet)

cpu :mediatek 6572

intsd: 8G

RAM : 1g

ANDRO: 4.2.2 (jellybean)

board: HX-M706-MB-V1.1.0

N.B: the wrong rom is Lollifox_MT6572_Kitkat_Ajit_mtkroms-com exactly. they say: for mt6572 only (not mt6572 running kitkat ):mad:

for more info tell me and :cool: good luck for every body :cool: .
[XDA Assist] GuestK0087:
Greetings,

Thanks for using XDA Assist.

There are no specific forums for your device so I ask that you post your questions here:

Android Q&A, Help and Troubleshooting

The experts you'll find there may be able to help you.

Good luck!
[Android General] Team Pusa:
Reminders:

Always give CREDITS to us!

The rom is already rooted so DO NOT ROOT IT AGAIN!

There is a flashable DSB fix for Unsupported devices below, Do not flash it if your device is already DSB supported!

The Bugs that we know is already stated in Changelogs section so don't complain if your camera is not connected or no phone storage! Blame your porter!

Features:

* Xperia Yellowpop User Interface

* Added ABS Tweaks

* Added Greeting on Lockscreen

* Added Delete Screenshot

* Added Settings on Recent Panel

* Added Task Manager on Panel

* Added Battery Usage on Panel

* Added Rom Banner

* Added About FazFap

* Added Credits

* Added Changelogs

* Added Music Visualizer on Lockscreen

* Added Music Visualizer on Panel

* Added Tinted System Bars

* Added Battery Styles

* Added Carrier Label

* Added Carrier Logo

* Added Clock Style

* Added AM/PM Style

* Added Brightness Control

* Added Double Tap to Sleep

* Added ListView Animation

* Added App Circle Sidebar

* Added Gesture Anywhere

* Added Network Speed (stock)

* Added Omni ScreenRecord (NonAPK)

* Added Hideable SimName on Lockscreen

* Added Enable/Disable Navigation Bar

* Added Navigation Bar Size

* Added LCD Density

* Added Omniswitch

* Added Toast Animations

* Added Font Chooser

* Added CPU Control

* Added Dolby Atmos

* Added System App Remover

* Added Partition Info

* Added Shake to Clear Ram

* Added Ad Blocker

* Added 3 game Nutella Platlogo

* Added Team ***** Members Menu

* Added History of Team *****

* Added Build.prop Editor NonAPK

* Added AOKP System Animation

* Added 2-way Reboot

* Added Xtreame Booster

* Added HeadsUp Notification

* Delete Some Bloatwares

Credits:

Individuals:

• God

• Josiah Viola Tingzon

• Klark Luis Peralta

• Villas Felimon

• Renan Boriga

• Zane Flores

• Adi Aisiteru

• Sejajr

• Gurpreet Singh

• Leo Villasenor

• Aryan AR

• Bamzzz

• Danilo Sarmiento Caballero

• Vasily Ivan

• Jonacx D Greyt

• Dhenz Aquino

• Kent John Jordan

• Venkat Kamesh

• Droidbuster

• Tenten Ponce

• Octo O

• Muhammad Abdusy Syukur

• Fiqih

• FUAD

• Rahul Sehgal

• Rio Hutabarat

Groups/Team:

• Maximum Dev/Port Team

• Material Android Development Team

• Mediatek Android Art and Dev Reborn

• Nameless Porting Team

• Alliv OS

• Resurrection Remix

• AICP

• PAC Rom

• FMD

• Cyanogenmod

• Dolby

• Sony Mobile Communication

• Hidden Developers

• XDA

• Google

• Github

• Stackoverflow

• MakAndTheGank

• Xenon

• Hyperion

• Maxwen

• SlimBean

• ParanoidAndroid

• Carbon Rom

• LiquidSmooth Rom

• Omni Rom

• DU Team

• Team28devs

• AMD Team

• ChurOS

• XDA

Links:

Link removed

#WeAreTeamPussy
[Android General] Yeasir-ya:
Nice rom
[Android General] mr_Kronnus:
Help with firmware

Hi Team Pusa

I tried to port your firmware on Dexp EL350 (CPU sc7731). And faced with the problem of mobile network - it does not exist, and constantly appears com.android.phone error. And if you go to settings "on the phone", then in the "communication module firmware" is missing in the line ... :(

I ported in this way:

Procedure:

1. Download Rom or (PAC FILE)

2. Load PAC File in Research Download

3. Get the system.img

4. Extract System.img Follow this tutorial on how to extract here

5. Replacing Files (from base to port)

Base-Stock

Port-Custom

Boot.img

bin> sensorservice

etc>Bluetooth

dhcpcd

wifi

permissions

fallback_fonts.xml

lib>egl

modules

libsurfaceflinger.so

libsensorservice.so

libmedia_jni.so

libEGL.so

libGLES_trace.so

libGLESv1_CM.so

libGLESv2.so

lib>hw>Camera.sc8830.so

sensors.so

all usr > except keylayout

Your firmware is very interested in, and for about a month trying to fix the problem, but not successfully. Please help, can tell me how to fix it or tell me what needs to be replaced.

Thank you.

Add screenshots can not, because limit for beginners...

where to send screenshots?
[Android General] Saber5311:
This is not Android 5 this is android 4 look at built prop SDK 19
[Android General] Sudarshankakoty:
Will this ROM will work on Micromax Bolt Q370 ? Its a sc7731 device.
[Android General] Sudarshankakoty:
I have cross ported a lollipop ROM (Fazfap) for my sc7731 device, and the ROM boots fine. But the two major issue found in the device.

1. Touch not responding properly. I mean I click somewhere and it opens other items. Like I click calculator but it opens an app right below it etc. A touch point circle shows and moves as I move the finger across the screen, but I am unable to scroll up down left right completely.

2. SIM cards not detecting, no signal showing.

All other working great, including Bluetooth, wifi, sensor etc.

Anybody knows what are the files to be replace from base to port to fix these problems ? ROM was not booting until I change the Boot.img. This ROM is available on Google by searching "sc7731 Fazfap" and sound output of this ROM is great

Edit : I replaced system/usr from stock and touch working fine. Still useless because constantly getting error message as Unfortunately the process com.android.phone has stopped. Whats the fix ?
[Android General] Saber5311:
Is was android 5?
[Android General] Sudarshankakoty:
5.1
[Android General] Saber5311:
Error with script

I can't flash this
[Android General] sudroidtech:
Has lots of fc and bugs

The design is looks good but it has many bugs such as systemui fc.
[Android General] skella:
Thank you Guys for your time and effort dedicated in helping people,,,, i salute and respect your hard work,, keep up the good deeds Guys,,,,, Thank you so much....... just wanna ask if its possible,,, My huawei device is a M9 D-horse,,,, i think it is a clone SPD device,,,,, it is completely dead, can i flash it with this ROM?
[Xperia Z2 General] Brandon Nel:
Hi everyone. Today I'm just sharing some work from someone else. No one has tested the Audio mod on their Z2 yet, (according to the Original thread) so I tried it and it worked like a charm! :)

Features that I experienced on my Z2...

-Click sound is much more clear.

-Music in general is a bit more louder, with deeper Bass and much more richer sound.

-Overall sound & music sounds overall more natural and vibrant.

Downloads and info is from this post: http://xdaforums.com/android/software/mod-htc-beats-audio-beats-xperience-t3281603

This is NOT my MOD. I'm just sharing his awesome work to you guys and confirming that it does work with Z2 devices.

Any, thanks to [MENTION=5954096]androidexpert39[/MENTION] for this amazing MOD. You rock. :)

If you want to include this MOD into your ROM or Tweaks MOD, then be sure to ask him first. (I really want to! :D)

Be sure to give him some thanks on the original thread! :good:
[Xperia Z2 General] sniper63:
this wont cause any bootloops or anything ?

as the op doesnot mention anything about sony z2 or any of the sony phones ! Really curious to know ///
[Xperia Z2 General] Brandon Nel:
No. Not at all. I tested it on my Xperia Z2 Marshmallow 570 firmware. No bootloops at all.
[Xperia Z2 General] zBLacKy:
Works for cm12.1?
[Xperia Z2 General] abeyruma:
thank You!!!! :)
[Xperia Z2 General] yenero:
Working with Z2 existenz v3.5, Abricot kernel v8.1
[Xperia Z2 General] ratasana:
Worst audio mod for phone speakers
[Xperia Z2 General] Brandon Nel:
Yes. All ROMS 4.4-6.0.1
[Remix OS for PC] modaifallah:
My laptop has:

1) AMD Athlon QL-62 dual core 2.00 Ghz

2) Nvidia 8200 mg 256 mb VRAM

3) 3 GB ram

4) Broadcom Wireless driver

It has a weird thing that occurs in remix, Phoenix and Android x86. After some time the laptop suddenly 'dies', it freezes completely without any input or output changing and ALT+SHIFT+F1 doesn't open the terminal. It only will work after hardware reset. In Android X86 Marshmallow specially, it doesn't occur if the Wifi isn't connected as my wifi card doesn't always load upon boot.

How can I debug the issue? If it's Wifi related or video card related how can I debug it?

Thanks!
[Nexus 6 Q&A, Help & Troubleshooting] sam008:
Guys

I'm on n preview 4 and occasionally my phone just freezes our becomes very slow to respond. Is there any debugging app that can show me which application on the phone is taking a lot of processing power or memory even though it's running in the background?

Thx
[Nexus 6 Q&A, Help & Troubleshooting] zelendel:
Start with a logcat.
[Nexus 6 Q&A, Help & Troubleshooting] NLBeev:
Maybe 3C Toolbox Pro. Don't know if it works on N preview.
[Galaxy S3 Neo Q&A, Help & Troubleshooting] darkavix:
Before flashing custom rom, my phone charges good with usb cable and power-bank , but now it doesnt work. Is a problem of kernel? If it is, which kernel can i install?
[Galaxy S3 Neo Q&A, Help & Troubleshooting] Arsal7R:
Try another cable and charger. I don't think that it's a kernel problem.
[Galaxy S3 Neo Q&A, Help & Troubleshooting] darkavix:
i test with rom based on 4.4.4
[Xiaomi Redmi Note 3 Questions & Answers] stephendt0:
Alright, well I hope I haven't buggered up here.

I'm doing some work for a business that needs no less than 17 new smartphones for their sales team. They wanted something that had a decent sized screen, awesome battery, and fingerprint reader. I immediately thought of the Xioami Redmi Note 3 Pro. I showed them my Note 2 and they were impressed and said they would be keen on the Note 3 with the fingerprint reader for the price. I thought it was a no-brainer. I knew MIUI would confuse the existing sales team (they use Nexus 4's and 5's currently) so I figured CM12.1/CM13 would be the way to go, and I did notice that there was a bootloader unlock process required. I didn't think much of it at the time.

Now I realise there is a somewhat painful bootloader unlock code application process. Hmm. Would I experience difficulties getting unlock codes for this many devices? Luckily I only ordered one so far to test, but I am worried whether Xiaomi will be happy to hand out codes like candy. If they reject me, I'll be holding the bag and be required to get them a different phone, probably something like a Nexus 6p, which is more than three times the price and doesn't have as great battery life.

If anyone has some insight to this process and how it would play out if I tried to get a heap of codes that would be great.
[Xiaomi Redmi Note 3 Questions & Answers] shaanyt:
Tell them to use MIUI.

Firstly, you shouldn't replace a stable STOCK ROM with a development AOSP ROM like CyanogenMod, which usually has undocumented bugs and issues. Companies usually prefer security and stability over "the look of vanilla android". I don't believe people cant learn to use MIUI. Why? Because MIUI is still android, just with CUTER icons and a different launcher. If you are so worried about the launcher, force all of them to use google now launcher or Nova Launcher. Confusion due to different launcher is never a good excuse to sacrifice security and stability.

Secondly, unlike MIUI, which pushes stable updates every 1 or 2 months for security patches, CyanogenMod updates are not guaranteed, worse still, CM updates are never extensively tested and are released almost every god damn day (along with randomly added experimental features/changes, which might suddenly break something, or randomly removed features/changes, which again, might break something). You can't expect them to update today, find out there's a bug, update again tomorrow, OMG BUG NOT FIXED ? Patch again the next day. OMG bootloop from bad update / bad flash? OMG OMG OMG ! What to do? OMG OMG OMG WTF Another bad flash? No signal, no wifi? What to do? Wait til next update? See the problem here? Not everyone knows what to do with a ROM that needs that much tinkering. Then, there's another problem, what if somehow the maintainer call it quits? The ROM gets abandoned. What happens then?

Conclusion, for work use, NEVER EVER flash AOSP ROMs or whatnots, always stick with stock for security, stability and support from the OEM. Also, it saves you the trouble when **** happens, imagine a bug causes the whole team to miss a meeting or screw up an email which causes business loss, the management would certainly like to know whose idea it was to unlock a secured bootloader, replace a stable MIUI stock ROM with an unstable ROM.

EDIT : Extra info : I am using CM13 now, it has a lot of weird bugs, like GPS not working for some devices (depends on region) and some people have random "no signal" issues, or no data, or sim not detected. And after flash, some of us needs to edit files it root directory to get capcitive buttons working again, otherwise menu key wont work properly. Some get random reboot. Some get bootloop after update. So on. Seriously, DO NOT FLASH FLASH CM FOR OFFICIAL WORK USE IF THE PEOPLE USING THEM ARE NOT TECH SAVVY PEOPLE WHO KNOWS HOW TO DO A LOT OF ANDROID ****.
[Xiaomi Redmi Note 3 Questions & Answers] stephendt0:
I totally get where you're coming from, but I think you're overreacting and ROM stability or updates isn't the problem here. This isn't going to happen for a couple of months at least, and I would use one as my own device and make sure there isn't any bugs before giving it to anyone else. I'd be handling updates manually as well. You make it sound like stock ROMs don't have bugs either, and they get updated forever. Lol.

Really not sure I'm sold on MIUI though. It is quite a departure from AOSP. I tried it for a week and I couldn't really stomach it, but this was about a year ago now. I feel I'd get complains for sure. I also don't see development for CM13 stopping anytime soon either.

Even if I did use MIUI, I'd need to flash a modified stock ROM via fastboot, which again would require an unlocked bootloader. I sure as hell am not going to sit around and setup 17 phones by hand, so let's get back to the original question. Is getting bulk bootloader unlock codes a problem?
[Xiaomi Redmi Note 3 Questions & Answers] agambhandari:
Bulk unlocking won't be a problem, since you only need to get the permission for a MIUI account.

Basically,when you get the permission, you can unlock any number of Mi phones linked to your account.

Although I would recommend sticking to the stock MIUI since it is much more stable and supported because in your use case, stability would be paramount.
[Xiaomi Redmi Note 3 Questions & Answers] balazs312:
Hire me too, and I'll unlock for them. :highfive:
[Xiaomi Redmi Note 3 Questions & Answers] macgyver_classic:
Via mi tool and getting official authentication to get unlock code? Yes it's a problem because xiaomi will only allow to unlock one device per month using same mi account, you'll need different mi accounts to get codes at a time...

Also, it takes quite a long to get unlock code from xiaomi around 2-3 weeks, if unlocking is mandatory for you, I'd suggest you to manually unlock those devices.. search mi forum or Google, you'll get process to manually unlock your device...

But still, i don't think it'll be a good idea...

Unlocking device and installing custom rom for personal use or experiment? it's really good.

But for bulk or commercial use? I still don't think it'll be a good idea... best of luck anyways.. happy unlocking! :)
[Xiaomi Redmi Note 3 Questions & Answers] stephendt0:
Alright, cool. I thought that would be the case - pretty annoying. Not keen on the manual unlock method, it seems like a good way to brick a device via an OTA update.

The only other way I could use MIUI is if:

- I could disable all the MI services such as Mi Account, Mi Message, Mi Cloud, and any other junk / optimiser apps that might be preloaded

- I could pre-load around 20 user apps (some which need to be pre-configured with data, such as launcher) that would be needed

- I could disable the stock launcher permanently and have it replaced with Nova launcher

- I could install some kind of AOSP theme

- I could improve the RAM utilisation somehow

If I could do all of that, and clone this configuration to 17 devices without unlocking the bootloader, then I might be able to stick with MIUI... otherwise it's gotta go, or I gotta pick a different phone.

Edit: Had another look at the unofficial unlock method. It appears that as long as you aren't on a MIUI base, it should be fine. Looks like I might not have to unlock official after all.
[Xiaomi Redmi Note 3 Questions & Answers] shaanyt:
1. MIUI has bugs too, yes, but usually minor + documented. It doesnt break GPS nor does it randomly make major capabilities of the phone fail. This is where CM falls short, sometimes. You'll never know when CM will change something because they think it will work, which winds up giving you bugs or bootloops.

2. MIUI won't get updated forever, but it will certainly be supported for a longer time than other OEMs. Look at how many phones will be getting MIUI 8 soon. Also, let's not forget, CM won't be updated forever either. Sometimes, it even gets abandoned. Then there's the part about CM where some (well most, but i don't blame them) maintainers are like "logs or it didnt happen" when it comes to bug reporting, and there arent that much people using CM, so, less likely they will get logs. Some even give you the middle-finger by saying "can't reproduce LOLL you're on your own." ***By no means am i implying that the maintainer/developer for RN3 CM13 is an asshole.

3. Aside from launcher, MIUI is not that different from other "flavoured" android UIs like touchwiz or whatever-LG-calls-their-UI. Mainly, icons are different, that's about it. The "not sold on MIUI" is not really a solid reason to use a ROM that isnt stable/secure. Just change the launcher then, use themes. Humans can adapt. With time, users will adapt to it. The same goes to iOS-->Android or Android-->iOS, that's why it's not very common (but not exactly rare either) for users to switch, because within a week or two, they give up, swap back.

4. Flashing using MiFlash with locked BL you mean? Hmm, perhaps you could try using adb reboot edl. This sends the phone into emergency download mode (only for qualcomm version), which allows you to flash fastboot ROMs, but only STOCK fastboot ROMs. Never tried on a modified ROM version, but i don't think that would work.

Note : I am not advocating for/against MIUI nor am i here to argue with you. I am just trying to help you make a decision clearly. By looking at security and stability. Not by judging how lamely cute MIUI is (which i agree, looks childishly weird, it's like an iOS reject made out with touchWiz and gave birth to a mutated UI).

By the way, sometimes xiaomi ignores unlock requests, sometimes they reject them cuz you account doesnt have enough "posts". Plus, you'd need like 17 accounts. Personally, i would suggest getting another phone, one (or 17 :P) that looks closer to Vanilla and is friendlier to the Open Source Community (which obviously, xiaomi isn't, they dont walk the talk) as this would greatly reduce bugs and problems on ROMs like CM, should you choose to go there. But at its price range, RN3 is just about the best. Other phones are like 2x more. The next best thing would be Nexus 5x. 6P is too expensive.
[Xiaomi Redmi Note 3 Questions & Answers] Grantius:
Why not suggest Nexus phones. I wouldn't use Xiaomi phones if I had to support them afterwards?
[Xiaomi Redmi Note 3 Questions & Answers] stephendt0:
Price and battery life mainly. They're just so hard to beat for the money.
[Xiaomi Redmi Note 3 Questions & Answers] stephendt0:
Good points. The thing that I really want to focus on is the user experience though. The extra "features" will definitely cause some headaches. Sure, they can adapt, but I'd probably have to train them which isn't what I want to do. I've setup devices with CM ROMs for people in the past with great success (setup quite a few K3 Notes earlier this year on CM12.1) as they have been cleaner, faster, and much easier to use than the stock ROM. I figured I could do the same thing on Xiaomi devices. I also want to create training videos for them and I was hoping that if I could use CM it would apply to those who still have Nexus devices as well since they will look and feel the same.

It's a classic case of awesome hardware (with snapdragon SOC) at an awesome price held back by irritating software. The K3 Note was similar until CM12.1 was stable - the stock ROM was really bad.

I'll have to think long and hard about whether I would want to continue or if I should just start looking at other devices. I just can't think of anything else under 250USD that will fit the bill.
[Xiaomi Redmi Note 3 Questions & Answers] stephendt0:
Others have said you can only unlock one device a month per account.