yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] lopestom:
Hello guys, I wanted to help our friend from Brazil nicamel to transform your model D910A for the D910i to be a process as reported earlier. And it worked like our friend dynamiclynk. All questions have been resolved. The BLU Products email saying that the exchange was possible happened. So I believe our friend Ctibor doing something wrong. What knot did was save the recovery folder in the SD and thus creating the folder as I reported in another post of recovery. Example: H: \ clockworkmod. After entering CWM ---> backup and restore ---> restore -> 2012-11-17.07.23.13 /

Perform the restore, Go Back -> power off. Power on the phone and ready.

I asked that nicamel put screenshot of your settings. And I ask you to do the process Ctibor to know if there are other factors that are giving error and report it to us.

So people who bought the wrong model can now trade without fear thanks to the help of everyone here. Congratulations to all of us, Happy Christmas and New Year.
[Android Q&A, Help & Troubleshooting] lopestom:
I read on facebook the BLU (http://www.facebook.com/BLU.Products) the same problem. And asked to contact them by e-mail. Do not know if you're the same person, but if not, check the site.
[Android Q&A, Help & Troubleshooting] aguscaba:
gps issues

Thank u for your response lopestom, i saw the facebook page but i dont found anything about the GPS; i had already sent an email too without any response (yet) (sent to service@bluproducts.com)

The question is kind of urgent because i bought the handest at walmart, depending if it is a common problem i would ask for money back or handset replacement in warranty.
[Android Q&A, Help & Troubleshooting] lopestom:
"Nelson Martínez hello there, I recently bought this phone but the compass app is not working.

That's normal or it's just my phone? Thanks 25 de novembro às 20:39"

"BLU Products Hi Nelson Martínez, please write us an e-mail service@bluproducts.com Thank you"

-

Really is something wrong. I believe it is better to try to replace the unit as is warranted. A friend of mine had a phone with the same problem and changed, of course it takes to return, but it's better than having other problems. It may be something related to antenna. Anyway, the rest I can not help if you have tried other resources.
[Android Q&A, Help & Troubleshooting] lopestom:
Sad news. :crying: Our friend nicamel with their new D910i, in the beginning until the 3G signal was good. But something really strange this. The signal becomes unstable between Edge and 3G (H). We are doing everything we can in terms of knowledge about it, until researched more about problems in modem and found this post: http://xdaforums.com/showthread.php?t=1881994

I can not contact Gionee on GN868H or Micromax model A90S to know which model specifications or download the modem. Would be the same entity Gionne and BLU VIVO 4.3? In short, I could not get any information about.:confused:

II ask that MacGyver1138, dynamiclynk, Ctibor, williegomezt and others with more knowledge might try swapping the RADIO MODEM as described in the above post. Meanwhile, here we are trying other simple processes.

Does changing the RADIO MODEM of BLU for a SII or S3 ICS would be compatible?
[Android Q&A, Help & Troubleshooting] dataspill:
I have successfully rooted, installed CWM and ran a nandroid backup with successful boot afterward! I'm guessing you guys just need the system data?
[Android Q&A, Help & Troubleshooting] lopestom:
We already have that for all 2 models. You say change something in the script system data? The system data on files download recovery in other post.
[Android Q&A, Help & Troubleshooting] jcarlos1993:
Como instalo el clockworkmod recovery???

How do I install clockworkmod recovery???
[Android Q&A, Help & Troubleshooting] lopestom:
Se você escreve em português, mande—me um email privado.

If you write in Portuguese, send me a private email.
[Android Q&A, Help & Troubleshooting] celesus:
Hi, I'm from Venezuela, I write because I mistakenly bought d910i and I tried to change the rom to d910a, however I have the following questions:

1. How do root the device? (I tried the steps http://xdaforums.com/showthread.php?t=1886460 ) but without effect.

2. How do you install the CWM?

3 How do you install the "D910a backup system" provided by MacGyver1138?

Please Help!!!!
[Android Q&A, Help & Troubleshooting] celesus:
How to install the rom d910a?
[Android Q&A, Help & Troubleshooting] dataspill:
Oh, okay. Thanks for the info! Yeah, just some minor build.prop tweaks. It's nothing I can't undo, but if I did it's good to know I have a backup.

---------- Post added at 11:44 PM ---------- Previous post was at 11:33 PM ----------
[Android Q&A, Help & Troubleshooting] lopestom:
Hey, your see this http://xdaforums.com/showthread.php?t=2060482

http://xdaforums.com/showthread.php?t=1971058

I need options and opinions if this correct on our telephone.
[Android Q&A, Help & Troubleshooting] celesus:
d910i to d910a
[Android Q&A, Help & Troubleshooting] celesus:
CyanogenMod in Blu Vivo 4.3

another question, is it possible to install a CyanogenMod rom in the Blu Vivo 4.3?
[Android Q&A, Help & Troubleshooting] lopestom:
Know a colleague who tried to install the ROM Micromax superphone Pixel A90S unsuccessfully. According to him, did just that when installing the unit will restart it stays on the screen and does not come from BLU system for home screen.

I'm researching the files and are compatible with the BLU to install the CM10 official - JB [4.1.1] CyanogenMod 10
[Android Q&A, Help & Troubleshooting] malimal:
any reviews on this phone. i cant seem to find any.
[Android Q&A, Help & Troubleshooting] lopestom:
Specify what kind of comments or reviews.
[Android Q&A, Help & Troubleshooting] malimal:
lol..guess those questions would help.

how is the battery life and camera?

does blu have a track record of providing updates?

I guess a general comparison to other similar models phone. i wont put it up against a SGS 3, but how about against something like a SGS 2.

I really want a dual sim phone, and this seems like the best that is out there for GSM/GSM support.

I did see some reviews on youtube, but not in English.
[Android Q&A, Help & Troubleshooting] celesus:
CM10 in the Blu Vivo 4.3

Then, in theory, the CM10 rom could work in the Blu vivo 4.3, even though I find the best way to root the phone, does anyone know?
[Android Q&A, Help & Troubleshooting] lopestom:
Well, The duration of the battery is good, depends on what you use many apps, wifi and gps make any cell 1600mA consume much energy. Then another backup battery is interesting.

The native camera is not good, so use app Cam360, and HDR + lgcamera.

To learn about updates you should read all the previous posts. However, to date, as is the recent launch of the phone, help developers and custom kernel file 're making attempts. By the time it got many advances and other areas.

For comparisons visit website gsmarena and make your analysis.

Actually, the reviews are generally in Portuguese of Brazil, but if you're looking for a dual sim phone for private use, has my reference as 8.5 to 9.0, plus the cost benefit in general for what it offers in hardware. If you are looking for professional use, a choice will be yours alone.

---------- Post added at 08:50 PM ---------- Previous post was at 08:41 PM ----------

Yes we know the root causes carry time! Just read the previous posts.

After the root can talk better about the CM10. So williegomezt and MacGyver1138 are best to answer about development than me.

I'm traveling.
[Android Q&A, Help & Troubleshooting] Breto:
MIC problems

Have anyone solved the low mic volume problem?

Thanks
[Android Q&A, Help & Troubleshooting] aguscaba:
Mic volume problems

im having the same problem very low mic volume...
[Android Q&A, Help & Troubleshooting] antivirtel:
Blu Vivo 4.3 true Dual-SIM

Hi!

Can someone tell me if this phone has true Dual-SIM solution for the dual things? (So when I use one SIM (eg. for call), the other also could be called, or receive SMS.)

Thanks! Happy new year!
[Android Q&A, Help & Troubleshooting] malimal:
Yes. Both Sims are active at the same time.

Sent from my Nexus 4
[Android Q&A, Help & Troubleshooting] RemoWilliams:
Couple of questions

Hi, couple of questions i posted on a different site recently, but got no replies. I hope u guys don't mind me posting them here:

Anyone experienced the same issues or know a solution? Plz let me know:

1. When I select a contact from the Call Log to call him/her back, I always get "Unfortunately, Contacts has stopped", forcing me to go into Contacts everytime I want to call a person.

2. NoLED app (I): I got this free app from the Play Store. When starting NoLED app, it says "You must enable NoLED in Acessibility Settings. Do you want to do that now?". When I click "yes", it takes me to "Accessibility" screen, but I don't see anything in that screen about NoLED. What's the deal here? (PS: this is my first Android phone). I am able to start the app though.

3. NoLED app (II): Every now and then, the app will stop running, and I need to restart it. Why does that happen? I would like for it to stay running all the time. I found a setting 'Force close apps on low memory' (or similar) in the phone's menu, and I unchecked it, but that didn't help. Anyone know what the cause is and how to resolve it?

4. Sometimes the phone will do a spontaneous little reboot-kinda thingy (I get the Startup Blu-logo & the tune, and a bit later the phone is operational again, without me having to re-enter SIM pin-numbers). I haven't been able to figure out yet what triggers it. Until now, it looks like a random thing.
[Android Q&A, Help & Troubleshooting] MacGyver1138:
I haven't seen #1 happen with me.

#2 Does it need root? Is the phone rooted?

#3 I use automatic memory managers and task killers, plus I replaced/removed the launcher that comes with it (GoEx?) with Trebuchet (the one from Cyanogenmod) and its tiny, so I'm less prone to crashing anyway.

#4 See #3 above, but also Android doesn't like to kill Apps when you press Home, they just kind of freeze and wait for you to come back, I don't like this, so I setup a task killer to kill anything not needed to make or receive calls, and I try to exit out of every app every time I'm done with it. My phone lasts about a week or more before something misbehaving has me rebooting.
[Android Q&A, Help & Troubleshooting] RemoWilliams:
Thanx MacGyver..

#1: Interesting. Happens to me EVERY time. Would like to hear from others as well.

#2: Checked the info in Play Store just now... Doesn't say anything about it needing root. Furthermore, rooted my phone a cpl weeks ago, but I still get the same result. While I was in Play Store, I saw an update. So just now, I updated from 6.0.14 to 6.0.15. Checking now.. Nah, still the same. Would like to hear on this issue from folks who actually run NoLed on their Blu Vivo.

#3: Ok, thanx. Anyways, as I already said in #2: Just now, I updated from 6.0.14 to 6.0.15. Let's see if it's gonna stop running again. Would like to hear on this issue from folks who actually run NoLed on their Blu Vivo.

#4: Aight, will keep that in mind. Which taskkiller is that? And it auto kills apps when you click home or what?

Update 20120104: The NoLED update 6.0.15 didn't change a single thing. Still shuts down every now and then, and still won't auto-start after reboot, even though I set it to 'Auto-start after reboot'. Sux.
[Android Q&A, Help & Troubleshooting] lopestom:
Install ROMs JB

I believe some people here have tried, but I will report to avoid duplication.

Yesterday I tried to install three ROMs in JB BLU VIVO 4.3. The first and second are from Micromax 110 (two different ROMs) and the third A90S Micromax. All without success, the Micromax A90S just sits on the home screen and BLU Products not leave this and the Micromax 110 ([MMX_A110] [ROM] DrBhokali_v1_mujahidali.zip) almost worked, as only enters the home screen keeps appearing and BLU Products and disappearing without starting the android.

I saw the files inside the zip file, but so far do not know what the incompatibility, though suspicious of settings, since they also do not know much about development. So is the story for those who want to try to install too.
[Sony Xperia P, U, Sola, Go] XPF:
Hello,

i habe a Problem with my Xperia U:

Today i have flashed the Dynamic Rom, for U.

Because i find this rom not so good i have flashed again to Stock ICS.

The Problem, now i dont can Root my Phone (i have use binary and Flashtool).

Then i would flash the Stock Rom again, and what happens?

I dont can flash anymore..

What the hell is doing wrong?
[Sony Xperia P, U, Sola, Go] XperianPro:
Please think before posting.
[Sony Xperia P, U, Sola, Go] corsav6:
Agreed, after reading the post(4 times) I still dont know what your problem is.
[Sony Xperia P, U, Sola, Go] :
Well this thread isn't going anywhere and it also does not belong in general.

Thread closed

Sent from my Nocturnalized One XL using Forum Runner
[Asus Transformer TF700] wolfman87:
Maybe I'm the only one confused (I doubt that though :P) but there is a lack of clarity on different elements in the Development section (and others) about what is what. :confused:

To clarify (from what I understand:

Asus Firmware Updates

(things you get OTA if you're not unlocked and have nothing to do with Android per se., but Asus's implementation)

.22 was the release

.26 updates the scheduler and a few other things

.30 updated the camera

Was there a different JB release or is that only ROM dependent? There is a lot of talk about moving between .30 and JB.

Some ROMs/Recoveries are for ICS, others for JB, some for both. Which are which?

ex. CM10 is JB based, but will it work on an ICS BL and .26? From what I understand it will. If that is the case, what would be the advantage of updating my firmware? Does the Firmware update the bootloader as well? If I update firmware should it be to .30 and then to JB (see previous question about this)

Now, lets pull in the bootloaders:

TF700 ICS BL

TF300 BL

TF700 JB BL

There are also different guides for updating certain things, but not others. It's all generally confusing.

I'm not trying to piss and moan, I just think that there is a lot of information out there in specific pieces but not all of it connects. Lots of great options exist, but those of us who want to flash better ROMs and different Recoveries also need to understand how they are connected so we don't brick.

Thanks for anyone who can put this all together. I have a feeling it would be a pretty long post :(.
[Asus Transformer TF700] _that:
I am also confused, but at a different level, so I can at least clarify some of your points and ask others for more clarification. :)

The ASUS firmware consists of everything your tablet needs - bootloader, Android kernel, recovery kernel, Android apps and custom apps. Some updates may not include new versions of all components. The combination of everything except the bootloader is what most would call "ROM".

The version numbers in your list are 9.4.5.x, and all are based on Android 4.0 (ICS).

The ASUS JB release (Android 4.1) is firmware version 10.4.4.16.

Now it gets interesting. First of all, starting with the bootloader released with 9.4.5.30, Asus changed something in the bootloader that disallows - if I understood it correctly - flashing an unsigned bootloader even on unlocked devices, and that means no downgrade to the .26 bootloader, and more importantly, no way to flash the AndroidRoot bootloader that enables us to create the initial blobs for wheelie and NVFlash.

And there appear to be some incompatibilities between versions of bootloaders and kernels - I would also like to know why exactly.

Also, some recoveries are incompatible either with specific bootloaders, or with some changes in the Android system partition introduced with JB. If anyone could shed some light on this, it would be very appreciated.
[Asus Transformer TF700] pbrauer:
I can't speak for the other guides, but I do try to organize the ROMs by what version they are (JB or ICS), and if there are specfic limiations for recoveries or kernels, i try to note those items too.

As for the moving between JB and .30, or downgrading for various reasons, there were a lot of things people did to port the TF300 ROMs to work on the 700 at the same time a patch came out for the 700 (.30). The combination of these things happening at the same time meant that people had bootloader issues, or had ROMs that limited what they could do long term. I know that does not clarify what they do, but hopefully helps explain why it happened.

I try to keep the directory i maintain updated every day M-F and once during the weekends. If there are specific things you would like to see, please feel free to PM me with details.
[Asus Transformer TF700] wolfman87:
Thanks for writing all of this amongst a busy schedule - it's happening to me top (XDA is a nice short release during the day when I have a free minute )

When you say both ICS and JB Bootloaders, do you mean .26 and .30 respectively (since those are the ROMs that came bundled with them)?

numbers v. names is another thing we can add to the confusion pile ;)
[Asus Transformer TF700] Nebucatnetzer:
It's suggested buy the dev but it doesn't actually need the Jellybean bootloader.

I'm running .30 and it works without a problem so far.
[Asus Transformer TF700] MartyHulskemper:
Ouch -- managed to get Nvflash beforehand or have we lost you? :fingers-crossed:

---------- Post added at 02:36 AM ---------- Previous post was at 02:25 AM ----------

Good point! Actually, the answer would be 'no' -- I updated my reply above to answer this; I'll add it here for the sake of chronology and readability -- the first three (.22/.26/.30) contain ICS bootloaders, and the first (and as of now only :) ) JB bootloader is .16, so, as above:

.22 = ASUS firmware version 9.4.5.22 = ICS

.26 = ASUS firmware version 9.4.5.26 = ICS

.30 = ASUS firmware version 9.4.5.30 = ICS

.16 = ASUS firmware version 10.4.4.16 = JB

Note that the confusion stems from us having called the first few firmwares by their incremental build number -- this is what is currently shooting some people in the foot. :) If, however, you look at the full build number, the difference is quite evident. ;)
[Asus Transformer TF700] pbrauer:
Marty and Wolfman, thanks for the question and thanks for the summary. I try to keep the links in one place, but also see all the confusion! I have taken liberty of referencing this thread, and copying part of it into the Directory thread that I maintain.

Hope that you don't mind!
[Asus Transformer TF700] NeoGodSpeed:
Thanks Alot for this very helpfull post :)

Can this post be added to a sticky and be updated when new roms are released, this info would help so many searching for answers
[Asus Transformer TF700] okantomi:
I would say that some of that guidance is a bit out of date, but it is very nicely organized!

First, think whether you will want to go with stock-based roms. CleanROM Inheritance v2.5.1 is the latest and greatest version of the TF700 Infinity's stock-based offerings and this has the Aroma installer and has Clemsyn's overclocked kernel as an option during the install process. For this ROM, it is a good idea to use the latest TWRP recovery (install through Goomanager) but CWM is OK too. Another offshoot of scrosler's original CleanROM is being supported through the original CleanROM thread. The ROM I had tried was very nice.

If you would rather go Cyanogenmod-way, then you have the official CM ROM, you also have CM based Paranoid Android, Baked Black Bean and LiquidROMs. You also have Clemsyn's CM kernels, and CWM recovery. I think it's best to stick with CM/AOKP/AOSP--or--stock-based. They're like complete systems. There are other offerings too, and I don't mean any disrespect if I've missed any currently supported ROMs here, but there are a few that don't appear to be current anymore.

Good luck!
[Galaxy S III Q&A, Help & Troubleshooting] CalInTheZone:
I have this problem with XXDLIB after first upgrade from ICS I had the problem that more settings under settings crashed I solved it with at clean install! But now it's back! Been running for weeks without any problems until this morning when the problem reoccurred. How do I fix it WITHOUT a clean install?
[Galaxy S III Q&A, Help & Troubleshooting] slaphead20:
Try a fix permissions in recovery if you are rooted
[Galaxy S III Q&A, Help & Troubleshooting] CalInTheZone:
Already tried that without result.
[Galaxy Note GT-N7000 Android Development] Phil3759:
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

PhilZ Touch 3.0 Recovery

(Clockworkmod v6.0.1.5 based recovery)

Galaxy Note - N7000 Version Only

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *​

This is the temporary version of my custom clockworkmod recovery

For permanent one, look here

WARNING: flashing some update.zip files with format commands

can still brick your phone until you use a safe kernel, like PhilZ-cwm6.

New in v3.00

Completely revised new touch code

Much more user friendly touch experience

Lots of new features

Video Teaser:

Main menu at height setting 5 and 1

PhilZ Settings menu

Backup / Restore EFS and kernel

GUI Touch Settings

Aroma File Manager

Source code

coming soon...

Read in my kernel thread post 2 for instructions to use PhilZ Touch features like aroma and ors support[/SIZE][/B]

Why a temporary recovery?

Flashing instructions for stock recovery

You are done

If it fails with black screen after successful flash:

Change log

15 nov 2012

:Update to new custom touch 3.00 recovery included in PhilZ-cwm6 kernel

Read full change log in kernel thread

08 oct 2012

:Update to new custom touch recovery included in PhilZ-cwm6 kernel

20 Sep 2012

: Update non touch version to 6.0.1.4 ** Recommanded Update from previous 6.0.1.4 attached here **

19 Sep 2012

: Update non touch version to 6.0.1.4

Touch version stays at 6.0.1.2: if you know about a kernel with touch 6.0.1.4 or source changes for touch cwm6, let me know please

17 Sep 2012

: Update non touch version to 6.0.1.3

Touch version stays at 6.0.1.2: if you know about a kernel with touch 6.0.1.3 or source changes for touch cwm6, let me know please

28 Aug 2012

: Update to 6.0.1.2 - Touch (ICS only) and non touch versions

Download link and warning at post 2

Credits

Chenglu for his great unpack / repack tool: MAJOR CREDITS

kbc-developers for the base semi-touch code :good:

Gokhanmoral@Siyah for his touch source and great support over PM in fixing dual USB mount: MAJOR CREDITS

Tallustus from Team Skyfire for his great support over IRC: MAJOR CREDITS

sk8erwitskil for his recovery source (ors support, aroma file manager and efs backup/restore), a great place to start learning: MAJOR CREDITS

shoe63 for his testing and great help in porting to the N7000 Big thanks

dr.ketan for his precious help in porting to the N7000 (I don't own one), for support in the thread and for his faster mirrors: Big thanks

utkanos for his great and kind support over IRC

gweedo767 @ #Koush for sharing his new touch code source (not yet used)

myfluxi for his xxRecovery source in fixing dual usb mount

Koush for his great work on CWM6 and CM

Cyanogenmod for their scripts / initramfs

Chainfire for his support (stock recovery flash) and all his work for the Android community

superatmos and Dharam_Maniar for their great guides on unpacking/building custom kernels