yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] buhohitr:
If you are running stock ROM you need to make a backup of your stuff, then Odin factory ROM. If you using custom rom wtth cwm you need to wipe sd then reflash the ROM.
[Verizon Samsung Galaxy S III] BadUsername:
Pretty sure you're using safestrap.

I'm not sure, but maybe if you increase the size of a custom rom slot you'd have more space. I really have no clue though.

Try to ask this in the safestrap thread also if you think it's related to that.

Edit: I asked for you, I want to know how this works too.
[Galaxy S III Mini Q&A, Help & Troubleshooting] shervinkh:
Hi.

i was wondering if there's a way other than downloading the whole ROM and flashing it everyday for updating nightly roms (maclaw's)?

and if there isn't other way does flashing rom too often harm device?

how often do you update yours?
[Galaxy S III Mini Q&A, Help & Troubleshooting] Carlyle_f:
I think the download and flash method is the only way for now and I don't think it harms your device, I flashed mine everyday for weeks without problems, but I don't update it everyday anymore, I wait a few days or for a changelog with improvements I wanted, whichever comes 1st. There's not much difference in the day to day changelog.
[Galaxy S III Mini Q&A, Help & Troubleshooting] eswarvf:
no never think that rooting or flashing will harm device if u think like that ull be panicked when it wont boot and we have nightlies if only cm or any other aosp roms are official and no we all dont want it official as maclaw cant do his changelog after it ill flash it in week or any great changes

so no need to flash everyday
[General Omni Discussion] Matthias.87:
... to the latest nightly 02/12, it has a broken kernel / recovery mode!!

If you did, flashing via Odin will be necessary.
[General Omni Discussion] sundna:
;( can u help me? i've flashing via Odin but it doesn't start :( boot loop
[General Omni Discussion] sirskull:
I tried the version of today : 20140213 and also that one seems to fail.
[General Omni Discussion] Entropy512:
Was this via OpenDelta, or a complete ZIP downloaded from dl.omnirom.org?

None of the developers can reproduce issues with locally-build ZIPs, and I think xplodwild flashed a nightly ZIP with no issues too.
[General Omni Discussion] Matthias.87:
My 20140212 got flashed via opendelta
[General Omni Discussion] -Furion-:
It came with OpenDelta.

my post here can help :

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

Entropy, I can make test with my spare i9100 if it can help ! Just tell me what do you need;)
[General Omni Discussion] GidiK:
I had the issue with a locally build zip. And also with an OpenDelta update.

It gets fixed (the bootloop that is, there are other issues) by just replacing the kernel. Between the previous nightly and the broken one, there's only one commit in the kernel project: https://gerrit.omnirom.org/#/c/5019/.

But here's the mystery: most people, including me, seem to be able to solve the problem by installing the latest gustavo's kernel. But that one also seems to have that code... However, even though I saw no one reporting problems with the latest gustavo's, I did in one of my many trials have issues with it dumping back into TWRP instead of booting. I never had issues with older omni or gustavo's kernels and the 0212 rom.

Because of the other issues (Settings.apk not being loaded starting from 0212) I'm still on pre-0212 and experimenting...

Update: build a current zip, with 5019 reverted to its PS2, which I think didn't have trouble yet. However, it still bootloops. (Of course I may be doing something wrong however; I'm not very experienced with this sort of thing).

Update 2: build a zip with 5019 fully reverted: no boot loop! I am currently verifying whether including 5019 again will break stuff again.

Update 3: yes, it does. I took great care to follow the exact same install procedure. So this confirms https://gerrit.omnirom.org/#/c/5019/ as the culprit.
[General Omni Discussion] p_star:
The 2014-02-12 update for OpenDelta has also caused my i9100 to boot loop.

Hoping the post by -Furion- will fix it.

will test after work.

Edit:

Works fine when done with odin ver3.04
[General Omni Discussion] Entropy512:
OK this is really weird. I9100 and I777 have 100% identical displays (the only differences between these two devices are the touchkeys, call audio, and NFC. In fact I9100 kernels will boot on i777 although the above items will not work correctly of course...) and my i777 is booting fine even with that patch.

wtf?
[General Omni Discussion] GidiK:
We're definitely in the land of weirdness here. Judging by the SII I9100 thread, some people with i9100 also have no problem...

I don't know what I'm talking about, but could it be an issue unrelated to the code? The way it's build? The resulting kernel size? Maybe any other change would also have caused problems?
[General Omni Discussion] Entropy512:
OK that's REALLY weird if not all I9100 users have problems. Great. I'll check when I get home if xplodwild has tried this on his device, hopefully he can reproduce the problem.

stupid unified kernel/recovery approach, makes it damn near impossible to get a last_kmsg of a failure.

OK, here's a question: Can one person who is having issues with the newer kernels and one person who isn't please run the following command and put the output here, including whether or not you're having problems with the newer kernels on your device. (People who are having issues with the new kernels need to flash an older kernel to do this, people who are not having issues can get this from a newer kernel.)

cat /proc/cmdline

Please only post this information if you have results that differ from results already posted, specifically:

Look at the lcdtype variable (if present) or (if present) the ld9040.get_lcdtype variable

If you have the same lcdtype as someone who has already posted results AND you are getting the same results, don't post your results as they are unnecessary

If you have the same lcdtype as someone who has already posted results AND you have different results with new kernels, quote the other person and post that you're getting different results
[General Omni Discussion] GidiK:
Issues: yes. ld9040.get_lcdtype=0x0.

Not exactly from an older kernel, but with the patch reverted so effectively the same; I hope that isn't a problem. Redacted the serialno just in case:

console=ttySAC2,115200 consoleblank=0 androidboot.selinux=permissive loglevel=4 console=ram androidboot.serialno=*** sec_debug.enable=0 sec_debug.enable_user=0 c1_watchdog.sec_pet=5 sec_log=0x100000@0x4d900000 s3cfb.bootloaderfb=0x5ec00000 ld9040.get_lcdtype=0x0 consoleblank=0 lpj=3981312 vmalloc=144m
[General Omni Discussion] _mikey_:
Issues: no. ld9040.get_lcdtype=0x2

running 20140212 nightly
[General Omni Discussion] Entropy512:
Not a problem. I pretty much meant "any working kernel"

Thanks.

So, so far:

People with 0x0 have failures

People with 0x2 do not have failures

No need to post results if you have results that match the above.
[General Omni Discussion] GidiK:
I don't pretend to understand anything about the code, but the patch moves initialization code from one file to another, and this initializes equally for lcdtypes 1 and 2, but differently for lcdtype 0. Was "&u1_panel_data", is now "&s2plus_panel_data" for lcdtype "LCDTYPE_SM2_A1", i.e. 0. No idea what this means, but I don't have an S2plus.
[General Omni Discussion] Entropy512:
Yup, got it, found the same thing. Also, s2plus_panel_data was an uninitialized struct.

https://gerrit.omnirom.org/5569
[General Omni Discussion] Hammerhand.17:
I've had no issues, and my results matches those posted.
[General Omni Discussion] rabiny:
Works on 20140215 NIGHTLY

Thank you,

The issue was resolved for me with nightly build 20140215
[General Omni Discussion] Bobacco:
For me, too! Thx for tracking this down!!
[HTC Sensation] pdbc:
Hi everyone,

this is my problem. I use almost always a very good quality headphones set (but without mic): obviously if I need to answer/make a call I have to talk into the phone's mic. Well, very often I'm not able to send my speech...I'm receiving very well, but the listener on the other side is not able to hear me, or at least he listen a very-very-very low sound. I did myself a test, calling me from an other mobile phone, and obviously I tried more than one headset.

I wrote "very often": actually, at the beginning after a reboot, this is not happening. It starts happening after a while, usually one hour after reboot: if you have a call, you are able to talk for 5 maybe 10 seconds, then there is the issue.

I thought it was a ROM bug (I was using Viper 3.1.4), then I tried Viper 5, then Elegancia, then Revelation...same problem... so I think it could be a kernel related bug ( [MENTION=2212152]SebastianFM[/MENTION] Kernel). Actually, no AOSP ROM has the same issue (Albinoman, Sultan, bilal, etc.).

Please, someone with these ROM can check if it is true?
[HTC Sensation] pdbc:
Sorry for bumping it up. Anyone has experienced same issue? [MENTION=2212152]SebastianFM[/MENTION], could it be ROM related issue, or I must search in a different place? Take in account that it happens only in ROM powered with your kernel...
[Galaxy Note 3 Q&A, Help & Troubleshooting] gatubatu:
Dear All,

Am new to this forum and my apologies if I am posting out of place/context.

Would like to request help on the following issue. I have a N900 Exynos 4.4.2.

Baseband version N900DDUDNA1

Kernel 3.4.39-376474

Build KOT49H.N900XXUDNA6

Whenever I activate Mobile data, I get a pop up message every 2 - 5 seconds "You've used 0.00 Kbytes".

Any advice /suggestions on what is happening and how to solve this would be highly appreciated.

regards, gatubatu
[Galaxy Note 3 Q&A, Help & Troubleshooting] jdomadia:
It seems like popup is from carrier,better to ask carrier.
[Galaxy Note 3 Q&A, Help & Troubleshooting] stanley08:
[MENTION=5093728]jdomadia[/MENTION] is probably right, but try this however. Messages > Settings > More. Untick Push messages and CB activation. Maybe not the solution but give it a try. :)
[Android Q&A, Help & Troubleshooting] insomniacno1:
Hi guys, I took a search on XDA but couldn't find a thread about this so here goes:

I like to hear your experiences with Pipo in general and the level of their service, also if you should own a S1 Pro then I like your opinion if its good choice to buy.

Also has anyone experience with Pipo store - delivery on time, delays, excuses etc.

Hope to hear from you soon

JBJ

EDIT: not valid anymore since i bought another brand:)

Moderator please delete this post:)
[MDA III, XDA III, PDA2k, 9090 General] nunompsg:
just installed wm5 Tuma v1.3 on my Qtek9090

had (some) hope that mic problems would dissapear, but no luck att all :(

besides that, all is working like a charm, even performance is not as bad as i thought it would be :)

btw, GREAT JOB keep up the good work, it is appreciated ;)

i've read in some forum (not sure if it was on XDA) that someone had solved the problem by putting a extra hole next to mic :roll:

i'm decided to try it out since i'm tired having to use a headset when speaking on the phone with everyone :?

i'm used to open up/repairing laptop's at my work so how hard can it be, right? -WRONG! -i cant find the damn mic!! :shock:

i opened up the BA but i cant find it anywhere...

next to the reset and hardreset buttons theres nothing that looks like a mic...

does someone know where is it??

thx much
[MDA III, XDA III, PDA2k, 9090 General] s_thilkumar:
Its just next to the reset button at the bottom of the XDA IIs. When you open the cover, the mic is fixed in a kind of slot, just in the same spot where you see a hole next to the reset hole in the cover.
[Sprint Samsung Galaxy S III] jcl123389:
Hello, I'm new to these forums. I bought a Straight Talk Samsung Galaxy S3 (SCH-S960L). And i am pretty new to rooting, custom ROM's, etc. And because of that reason, along with the fact that i bricked my last Straight Talk phone after incorrectly attempting to root it, I am now quite apprehensive to go about rooting. I am not too keen on the idea of rooting my Straight Talk phone with any root that is specified to Sprint, T-Mobile or another carrier/model of phone, at least not without being sure that i am able to with no problems. I would like to have the most knowledge i can gather about rooting this specific model of phone before i go about with actually doing it. So recently i have been looking through any information i am able to find online and through the forums about how I was going to go about with rooting. However, I cant seem to find hardly anything on how to root this specific model of phone, and any information i do find seems to be iffy with reliability for my carrier, and i would really hate to mess something up. So my question is, could ANYONE help guide me through this process so i can successfully root my device without messing something up and having a $399 dollar brick on my desk. Thanks in advanced.
[Samsung Captivate Glide] aminmasa:
regarding my concern,

I request for a guide manual booklet regarding the cyanogen rom (android 4) on my device.

I have unlock (rogers network) device with stock rooted 2.3.5 rom .

Regards
[Samsung Captivate Glide] stormdude124:
Have a look at my signature! Everything you need to know is there,if you need anymore help post there!
[Sony Xperia P, U, Sola, Go] mohamadamin323:
Well I do not know how to speak English, sorry!

I have a Smartphone Xperia Go

I could not detect any SIM card went down some time ago and after-sales service, Sony is also trying to fix someone could just help me get
[Sony Xperia P, U, Sola, Go] mohamadamin323:
Plese
[Sony Xperia P, U, Sola, Go] waqar89:
What was actually happened?

Have u done something wrong?
[Sony Xperia P, U, Sola, Go] xperia_hero:
I think this is not a Q&A forum DON'T POST QUESTIONS IN GENERAL FORUM
[Nexus 5 Q&A, Help & Troubleshooting] OuncE718:
I recently purchased 2 of these Qi capable chargers and I want to know is it possible to rewrite the NFC that's built into the charger or if there's a hacked app that can allow it to work?

I'VE SEARCHED ALL OVER GOOGLE WITH NO RESULT.

sent from my neXus 5
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
Oooh I don't know. I have one though. But I guess if you have them already there is nothing additional I can add...
[Nexus 5 Q&A, Help & Troubleshooting] OuncE718:
I downloaded an app called "NFC

Tools" that's supposed to erase tags and write them, etc but of course Nokia locked the NFC tag specifically for the use with Nokia phones. I'm pretty sure it can somehow be hacked to work with the N5. I just don't know how.

sent from my neXus 5
[Nexus 5 Q&A, Help & Troubleshooting] PhilipTD:
You try Retag?
[Nexus 5 Q&A, Help & Troubleshooting] OuncE718:
Thank God!!! You are a lifesaver. This app works. It says it can even reprogram hotel keys. That's scary. Lol

sent from my neXus 5
[Nexus 5 Q&A, Help & Troubleshooting] PhilipTD:
Awesome.
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
How did you do it? I can't figure it out
[Nexus 5 Q&A, Help & Troubleshooting] OuncE718:
First make sure that NFC is turned on, on your phone in settings. Once NFC is turned on then touch the tip of your phone to the base of the Nokia DT-910 similar to the sample picture of the yellow Lumia below.

sent from my neXus 5
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
Awesome thanks. Its the first picture I didn't know ;)
[Nexus 5 Q&A, Help & Troubleshooting] OuncE718:
You're welcome. I just wished Nokia would have incorporated the NFC tag into the Qi instead of the base of the stand. It's a bit annoying to use the tag that way.

sent from my neXus 5
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
Oh right so even if I programme it, I wont be using it unless I "tip it"?

Its not much use to me if simply placing it on charge won't activate it
[Nexus 5 Q&A, Help & Troubleshooting] OuncE718:
Exactly! I was stoked to find out the charger had NFC but quickly didn't care for it much once I realized it wasn't built into the Qi.

sent from my neXus 5
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
Ah well. Wasn't sure what I was going to use it for anyway ;)
[Nexus 5 Q&A, Help & Troubleshooting] ascsa:
Hi, you could use the Retag Power Trigger (--> "more" Button or new trigger Button) to use it without touching the nfc tag ...
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
Hmmm interesting. How does that work?
[Nexus 5 Q&A, Help & Troubleshooting] ascsa:
it´s magic ...:D ...i´m just kidding ....

It adds a "power" tag (plugged or unplugged) and this is triggered by plug or unplug a charger ... no matter if this is a normal charger or a Qi charger ...Have a look at the additional triggers ... you could have a lot of fun with the wifi or bluetooth triggers as well :cowboy:
[Nexus 5 Q&A, Help & Troubleshooting] OuncE718:
Thanks, I seen the trigger setting before but didn't look into it much. That's cool to know. I'll try it. Thanks.

sent from my neXus 5
[Droid RAZR M Q&A, Help & Troubleshooting] toroloco73:
I gave this beautiful phone to my wife like a present christmas, I had done the root and deleted the blotware verizon ...

These days unfortunately the device has been updated to 98.18.94, build 9.8.1Q-94 and lost root privileges ...

you can redo the root?

thanks
[Droid RAZR M Q&A, Help & Troubleshooting] lem22:
Yes, it's all here.
[Galaxy S III General] srv.abhishek:
Hi

XDA is planning to include Micromax, Carbonn etc as actvie devices to the forum.

I am sure that Indian users will benefit a lot from this.. Here is the link

http://www.xda-developers.com/announcements/xda-india-support/
[Galaxy S III General] koolshubh:
K
[AT&T Samsung Galaxy Note I717] huhine:
Because of my job I use my phone(AT&T Galaxy Note I717) a lot and sometimes it drains my battery like mad. I am curious how much it could improve so just ordered a 7000 extended battery several days ago. My only concern is going to be the added thickness.
[AT&T Samsung Galaxy Note I717] shayneflashindaily:
Who is the manufacture.?

*S.O.F.A*2SHAYNEZ*K.C.C.O*
[AT&T Samsung Galaxy Note I717] huhine:
The sticker on the battery written mpj:/
[AT&T Samsung Galaxy Note I717] shayneflashindaily:
Give it a whirl

*S.O.F.A*2SHAYNEZ*K.C.C.O*
[AT&T Samsung Galaxy Note I717] ournewhero:
did you get this? how does it work? was the added thickness an issue? would the back cover still fit?

inquiring minds want to know :)
[AT&T Samsung Galaxy Note I717] beastlykings:
OP please deliver! Very curious here!
[Verizon Samsung Galaxy S 4] Jupiter683:
Hello everybody! Just got a Galaxy S4 from Verizon with the evil 4.3 update & I want to root the heck out of it, but when I follow all the instructions to the letter, absolutely NOTHING works...no SuperSU, no terminal commands, nothing...this is very tedious and rage inducing.and I also would like to know if it's possible to downgrade back to 4.2. Really not liking 4.3...stupid Knox...

ANY help put into layman's terms would be greatly appreciated.
[Verizon Samsung Galaxy S 4] decaturbob:
what root instructions did you follow?
[Verizon Samsung Galaxy S 4] k1mu:
No, of course it's not possible to downgrade. Please learn what you're doing before you brick your phone.

Start here.

After that, post DETAILS about what you tried and why it didn't work. You didn't tell us what model phone you have, what build it's on, what you tried to use to root it, what you observed, etc. How is it possible for anyone to help you?
[Verizon Samsung Galaxy S 4] Jupiter683:
You are quite right. Forgive me, I was 80% asleep when I wrote that post...Sleep deprivation is truly a cruel mistress... I was, however, able to successfully root my VZW Galaxy S4 with the help of this extraordinarily helpful video via youtube: http://www.youtube.com/watch?v=K5mCsDyW-TI

Now, I just need to find out which apps are bloatware & are safe to freeze.
[Verizon Samsung Galaxy S 4] hexitnow:
Any of the Verizon apps, sdm.apk (so phone won't update), aether pal .apk it allows Verizon remote control of your phone, callid or w/e it's called, cityid anything you won't use.

Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
[Verizon Samsung Galaxy S 4] Jupiter683:
Great! Thanks a heapload! I'll do a little perusing around to see what's safe to freeze. Thanks again!
[Galaxy S III Mini Q&A, Help & Troubleshooting] Davian64:
I play around with my phone, testing roms, kernels and tweaks until google maps stop working on my phone. the last time it work was when i'm using Maclaw's CM11.

I decided to return to stock rom and recovery using odin and thats when the problem started. I followed the steps from here.

The phone reboot each time I start Google Maps. I tried going back to CM11 but the phone reboot each time I start Camera (previously it was working fine). (I may hare to try CM11 again to see if Google Maps working in CM11)

Then I try to revert back to Original Stock Rom With Kies following the steps here but the problem persist.

Any idea to solve this problem?
[Galaxy S III Mini Q&A, Help & Troubleshooting] DjWacko:
Hi,

Maybe a corrupted data partition.

Do a real format data + media in recovery.

After that, try again flashing :).

Greetz

Hopes it works
[Galaxy S III Mini Q&A, Help & Troubleshooting] Davian64:
Hi,

Is real format data + media in recovery means wipe data/factory reset in recovery? I believe i did that before flashing stock rom using stock recovery.

I had an idea just now and I try several apps from play store, compass apps and any apps that uses compass and each apps reboot my phone upon starting. Logically Google Maps also use compass. So this might be the problem but strangely i could use Waze with no problem at all.

If compass related app is the problem, how do i fix this?

Thank you
[Galaxy S III Mini Q&A, Help & Troubleshooting] DjWacko:
Hi

real format isn't the same as wipe data/factory reset.

Real format = In recovery go to mounts and storage --> format real data and media :)

Strange that the compass isn't working. Try to uninstall non standaard compass apps from your Phone. And try google maps again.

Install app one by one, and see what app is causing the problem.

If not, it's recommend to do a full clean install again at your Phone.:)

Greetz
[Galaxy S III Mini Q&A, Help & Troubleshooting] Davian64:
Thanks.

I will try and report later as I'm currently doing offline charging. I'm a newbie, do you mind telling me the steps for full clean install?

Thank you
[Galaxy S III Mini Q&A, Help & Troubleshooting] Davian64:
I did format real data and media. still not working. I also install Maclaw's CM10.1 using steps from here, Camera is working, unlike CM11 but Maps still not working.

I also tried several compass app. Result are the same. Non of the apps works and phone reboot as soon as the apps start.

Thank you
[Galaxy S III Mini Q&A, Help & Troubleshooting] DjWacko:
Mmm, really strange it doesn't work :(

I'm on carbon rom now for some testing. The only app with gps needed on this rom is Google earth.

I tested that app, and all is working fine here.

Maybe a dead gps at your Phone?

Greetz
[Galaxy S III Mini Q&A, Help & Troubleshooting] Davian64:
Yes, it is strange. How to know a dead gps? But Waze is working fine. I haven't try Carbon. Tried slimrom but same as CM. Maps on stock browser and chrome also working fine. Only Google Maps apps giving me reboot.
[Galaxy S III Mini Q&A, Help & Troubleshooting] DjWacko:
Hi

I thought that GPS wasnt working on any app :)

Dead GPS = if you dont get a lock anymore and the phone isnt searching for signals.

Maybe you can try GPS locks software.

https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2

This will help your GPS to update the location off the sateliets.

When app opened. Use the icon in the right below corner.

Tools --->> calibrate both option.

If its taking to long , use the third option in tools and download

After that calibrate again

Greetz