yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] sgspluss:
In one point you are right its an forum, but most of the questions can be answered on they own.

In your case, you asking if they wanna publish an testbuild.

Now its time to think, testbuild what means its just for testing if all working that it needs to.

IF all working as it needs, then you can expect an release which NEVER called "testbuild" or else they will called "beta" or in this case simple "FML xxxxxxxx". And i am sure you dont wanna use an testbuild where not quite sure if its working as it needs to.

Look in other forums like samsung galaxy s plus or lg o2x, they dont have offical CM or else its just ported to work on this devices.

The members they wanna use the roms needs much more time to wait, because the dev's are testing each build and dont publish any beta like here. So be always happy for that what you've got and just wait for that what you can get ;)

Ah and i will answer as always, i am who i am dont wanna change me, my mind or my personallity to sounds friendlier.

If you dont like me or my postings, ignore me which are the simple as possible :D
[Samsung Galaxy Nexus] RoadToNever:
The devs will release builds when they decide the time is right. Requesting builds is irrelevant to the process so why waste your time?
[Samsung Galaxy Nexus] revanmj:
[ROM][5.0/LRX21T][AOSP] FML: Fork My Life (11/16/2014)

This low RAM / too aggressive LMK is serious - I just noticed that I often don't get text messages until I open SMS app and keep it that way (missed messages seem to be lost forever).
[Samsung Galaxy Nexus] ScardracS:
The problem of the low memory killer isn't a problem of FL, but is an AOSP's related problem, so we need to expect a Google fix for that type of problem
[Samsung Galaxy Nexus] titof174:
I don't understand cause yesterday i sent sms less than 160 caracter and it worked but today i all my sms aren't send and i haven't change anything
[Samsung Galaxy Nexus] revanmj:
Not really - we have sources so developers can try to fix this by themselves.
[Samsung Galaxy Nexus] Haik0:
>> "And i am sure you dont wanna use an testbuild where not quite sure if its working as it needs to." <<

You are sure ?? But are you really ? Nah, of course you are not,, it's physically/mentally impossible to be sure for someone else but you (specially if you have never even meet that person in your life),, cuz that would basically mean you can read that person's mind, right ? or how else can you be Sure ? What you are doing, is that you are simply assuming, that's it! :)) and your assumptions are are not valid as long as they are not verified, but did you even try to verify ? No! You just talk too much ; )
[Samsung Galaxy Nexus] Reptilez_DK:
Being a developer forum, people should know that not every build works, as originally intended. Just my 2 cents. :)
[Samsung Galaxy Nexus] Suxsem:
I have read that too
[Samsung Galaxy Nexus] sgspluss:
Just to say it clear as possible TESTBUILD ARE CURRENTLY UNDER TESTING FROM DEVELOPERS!!! They never will pubished them (maybe to few selected tester but not public), because those testbuilds can contains new bugs which aren't present befor and which needs to merge down befor they will published an official release (of course if they will have some free time...).

So as you can see, this has nothing to do with physically or mantally reding anyone mind, this are just thinking as developer do it day by day build by build (stable enought to publish it, maybe i have to merge down this and this bug befor and so on). As i saied, here on gnex you can be happy to have this very early beta which also will get more updates soon as possible, in other forums they need to wait much much longer or some other get nothing and have also deal with it. So deal with the situation here, and be happy what you have got and what you will get in future!

And please to be honest, i dont need to talk so much if some member use their brains and begin to think befor they writte anything! ;)

Now, lets close this topic, dont let us disscuse about testbuild and release (which are two different shoes), let us keep this section clean for developing and helping to report bugs we'll find that they can fixed soon as possible...
[Samsung Galaxy Nexus] freshgiammi:
oh f*ck i think i might have just dropped a bootimg with ~38MB more to Ram...

Also, please stop flaming :o
[Samsung Galaxy Nexus] aliesz:
excuse me, what is the usage of this boot.img file?
[Samsung Galaxy Nexus] freshgiammi:
how to flash, you mean? Well, use the app "Flashify" from Google Play or run "fastboot flash boot boot.img" from bootloader.
[Samsung Galaxy Nexus] AbhishekS:
Any LMK optimizations or just a 38mb increment as of now?
[Samsung Galaxy Nexus] revanmj:
Thanks. It seems to be improving things - updating official Facebook client finally didn't force close everything (including the launcher, previously I always ended up in empty multitasking view).
[Samsung Galaxy Nexus] aliesz:
thanks but I mean what is this file exactly? it is a file for fixing anything and must flashed over the latest build or another use?
[Samsung Galaxy Nexus] flip360:
"a bootimg with ~38MB more to Ram"
[Samsung Galaxy Nexus] freshgiammi:
BOOTIMG: Kernel with Ramdisk.

Flash on the lastest build.

---------- Post added at 09:49 PM ---------- Previous post was at 09:48 PM ----------

Just 38mb. The LMK optimizations are now done ROM side, also. That's were we want to work. Kernel LMK is fine.

The faulty thing is LMKD
[Samsung Galaxy Nexus] thetakerfan:
Is this boot.img maguro only or would it also work on toro?
[Samsung Galaxy Nexus] Master94ga:
Thanks [MENTION=4986658]freshgiammi[/MENTION], now the phone work a bit better :D
[Samsung Galaxy Nexus] revanmj:
Oops. This new kernel seems to break root. It stopped working after I installed new boot.img. So I reinstalled SuperSU from the newest beta ZIP (2.30) and I'm still getting this error:
[Samsung Galaxy Nexus] piterdemon:
The same pronlem here :/
[Samsung Galaxy Nexus] freshgiammi:
Hm.. i actually got that too now. I'm going to investigate, thanks for the quick response. For now, to everyone using root, don't flash the boot.img.

You can switch back by flashing the one in the lastest rom zip.
[Samsung Galaxy Nexus] wbedard:
I have been having a bear of a time combining FML 11/16, the new boot image released today and SuperSU (rel .30 or .35). I have tried several different installation paths trying to combine these elements but all paths have led to SuperSU saying that su is not installed and SuperSU is not able to install it. The problematic part of this trio looks very much like the new boot image. Is anyone else having similar trouble and/or has any tips on a "best practices" workflow to get all these installed and working happily together?

R/

wbedard
[Samsung Galaxy Nexus] freshgiammi:
You could try to flash back the bootimg from FML's ROM ZIP, and check if SuperSU works again.

If it does, extract the zImage from my boot.img and flash it with "fastboot flash zimage zImage". That way i can be sure it's ramdisk related.

All that because my kernel has no major changes and is pretty much a fork of MW's. So, i don't get why it should break SuperSU...
[Samsung Galaxy Nexus] wbedard:
Since I already new that the 11/16 build of FML works with the newest versions of SuperSU, I went straight for isolating the ramdisk by flashing just the kernel, as you indicated. Sure enough, that worked fine. I don't know how closely you've been following Chainfire's work with SuperSU but he indicated some new methods were being used in .27 and .30, which could even cause bootloops in some cases. If you're not following his "bleeding edge" releases, it might be worth a look at the release notes for his latest builds to see if your ramdisk is somehow confusing the SuperSU installer. It's not like FML is a widely used ROM that he has to ensure he supports...:>)

Thanks again for you help with this!

R/

wbedard
[Samsung Galaxy Nexus] sohailazam:
Got that Sweet little Battery percent on 5.0 with the help of this app ??

-https://play.google.com/store/apps/details?id=de.kroegerama.android4batpercent

------------------------------------------------------------------hit thanks if it helped!
[Samsung Galaxy Nexus] freshgiammi:
Hm, so it's a ramdisk problem..

I'll see if I can track it down. Thanks!
[Samsung Galaxy Nexus] pvkiniyan95:
Yep, zImage flash works
[Samsung Galaxy Nexus] kennyngo:
Guys I do not know why, but sometime I cannot send sms, it hang out then I also can not make a call as well. I have tried to call myself back from my friend phone, I can hear the phone ring through the speaker, but nothing happen on my phone, this cause me 2 -3 times per day, I have to power off, and restart the phone again. is there any way to solve this issue so far - BIG THANKS to DEV
[Samsung Galaxy Nexus] rajputrajat:
I definitely observe better multitasking with this kernel..

Thanks
[Samsung Galaxy Nexus] xXrawrXx:
So after flashing the zImage are you still left with the extra ram and root?
[Samsung Galaxy Nexus] rajputrajat:
Yes
[Samsung Galaxy Nexus] Whiskey103:
Let me remind you the "xda ethos" .. do not ask for ETAs and dont swear.

It will come when its ready.

Whiskey

Forum Moderator
[T-Mobile Samsung Galaxy S 5] diablo009:
When I turn on power save mode, I notice that it reduces both screen refresh rate, and brightness too.

Is there any way to allow reduced screen refresh rate, but NOT reducing brightness. Is this even possible?

Reason being that the screen is kinda too dim even in wee bit darker than normal light conditions. Right now I am toggling between auto and manual brightness based on where I am.
[T-Mobile Samsung Galaxy S 5] aooga:
Refresh rate? How can you tell that it does that?
[T-Mobile Samsung Galaxy S 5] diablo009:
It says that in the info about the power saving mode.
[T-Mobile Samsung Galaxy S 5] aooga:
XDA is somewhat down right now. I've been trying to reply to you, but it keeps hanging. All power saving mode does is lower the CPU clock frequency. The refresh rate is never changed. The frame rate is, however. If you're rooted, you can reduce the CPU clock yourself with a number of apps on the play store.
[T-Mobile Samsung Galaxy S 5] diablo009:
That's strange. Check the attached screenshot. It says it reduces frame rate.

What I finally ended up doing is install YAAB for brightness control (includes night mode too). This disabled the auto brightness n things worked out well.

Thank you very much for trying to reply. The very thought is appreciated a lot.
[T-Mobile Samsung Galaxy S 5] aooga:
Yeah, frame rate. You said refresh rate :)
[T-Mobile Samsung Galaxy S 5] diablo009:
Oops. My bad.
[Nexus 4 Q&A, Help & Troubleshooting] blueandwhiteg3:
Hello,

I left the land of iOS a while back because I was sick of the cat-and-mouse game around jailbreaking. I assured that I could root my Nexus 4 and install whatever I want. The problem is that everything I keep finding about rooting my phone is like *massive* overkill.

I'm used to iOS where jailbreaking simply unlocks the phone so I can do whatever I want. I basically want to achieve that same effect on my phone. It would be ideal if I could even still somehow get system updates from Google after rooting but that might be asking too much.

I've had my phone for some time now and there are only two reasons I want to root it:

1) I want to enable LTE

2) I want to be able to install AdBlock fully

I don't want to install a customized ROM. Everything about my phone is fine. I just want to do the two above things. In fact, I almost don't even care that much about AdBlock. Enabling LTE that is most important to me.

Is it necessary for me to locate a new ROM to do this? If so, where can I find a ROM identical to the one currently installed (everything is up to date) but simply 'unlocked' so I can install the LTE enabler? Is there another way to enable LTE without rooting?

Sorry if this question has been answered, I've searched around, but I seem to be finding lots of not very useful answers.
[Nexus 4 Q&A, Help & Troubleshooting] taodan:
I read you post and I think you are asking for something (i.e., LTE) but you don't want to get your hands dirty. So here is my suggestion for you, sell your nexus 4 on swappa and then buy the Nexus 5 which has LTE by default. The price of Nexus 5 has come down very much that you can recoup some by selling the Nexus 4.
[Nexus 4 Q&A, Help & Troubleshooting] blueandwhiteg3:
I never said I'm unwilling to get my hands dirty. I am just trying to find the simplest, cleanest way to do this. Once I identify that, I'll execute.
[Nexus 4 Q&A, Help & Troubleshooting] chada77:
Two main steps really:

1.	Root your phone (involves unlocking your bootloader):

a.	This will destroy all data on your phone, so back up what you need to

b.	This is a great guide to getting it done: http://community.giffgaff.com/t5/Blog/Google-Nexus-4-Unlock-and-Root-Guide/ba-p/6983918"

It uses the graphical toolkit which if you dont want to get your hands dirty makes it much easier than messing around with the command line

c.	In summary the process is Download toolkit on PC -> Enable usb debugging on phone -> Install Drivers on PC (from toolkit) -> Unlock Bootloader -> Install Root and Flash Custom Recovery

2.	Flash a custom Modem. This enables the LTE/4G:

a.	This basically overwrites the radio software with one which has 4G Unlocked

b.	bpear96 has written an App that you can get from the Play Store which makes it easier for you to do this: http://xdaforums.com/nexus-4/themes-apps/app-nexus-4-modem-flasher-lte-enabler-t2607221)

c.	This is a good guide to do so (http://www.ibtimes.co.uk/how-enable-lte-google-nexus-4-e960-1447403), follow the bit that says ‘How to enable LTE on Nexus 4’. You have to choose a LTE Hybrid Modem, flash this (will reboot) and then go back into the app and Say Enable LTE.

At this point your phone should be able to pick up the LTE Signals and should show 4G.

Since you're rooted, you can simply download the AdAway apk and install it.
[Nexus 4 Q&A, Help & Troubleshooting] chrisrozon:
Use the Wugsfresh toolkit to get root, then the LTE Flasher to get LTE.

The hardest part will be getting the right Windows drivers to install, but that's Microsoft's fault not Google :)
[Galaxy Note 3 Q&A, Help & Troubleshooting] Kevind_444:
My friend gave me a Note 3 of his for free before he left to thailand (he was helping me out because mine took a drink). So I was sooooooooooo excited to get off this lame nexus s. Problem is he has a passcode unlock and he didn't tell me it. He will be gone for 6 months and I don't know when or if I will be in contact with him (he's there for work). So my question is :

How do you take the passcode off the phone so I can use it for myself? I tried flashing the stock Samsung firmware from sammobile, and it worked like a dream, but it STILL has the passcode. This is such a headache I was really excited to have a good phone once again :(

if anyone could help me out this would be GREATLY appreciated, it's stressing me the hell out!!!
[Galaxy Note 3 Q&A, Help & Troubleshooting] vndnguyen:
I dont know how to bypass the lock screen, and it may be illegal

But FYI, the Note 3 has 26 partitions, but when you flash the stock firmware, only 12 partitions have been flash. So the rest of partitions may store the passcode... ;)
[Galaxy Note 3 Q&A, Help & Troubleshooting] Misterjunky:
re: lockscreen

Put the phone into stock or custom recovery, whichever you have and then

do a "Factory Data Reset" and reboot the phone.

Once that's done you will no longer have problems with lock screen.

But you will need to add your own gmail account and so on.

Good luck!
[Galaxy Note 3 Q&A, Help & Troubleshooting] hhai2pth:
You try factory reset. I have the same problem and it solve for me
[G2 Q&A, Help & Troubleshooting] tasty_boy:
Well, after a brick... i could make my phone live again

but... to solve the issue i had to install the Vodafone Stock rom

and that Vodafone logo in bootscreen is poor...

can i change it to stock LG one?

tried some... but didnt worked in Recovery...

thanks
[G2 Q&A, Help & Troubleshooting] xenix96:
Stock LG bootanimation.zip and shutdownanimation.zip

Hi your lucky cause i just changed my Bootanimations.

So i attach you below the 2 backuped LG Stock animation files

Instruction:

1- You need root!!

2- Get root explorer

3- Put the 2 files on your phone

4- Open root explorer an navigate to root/system/media

5-

Backup your Vodafone bootanimation.zip and shutdownanimation.zip on your sdcard

6- After backuped just delete the Vodafone bootanimation.zip and shutdownanimation.zip from root/system/media!!!

7- Grap the Stock LG bootanimation.zip and shutdownanimation.zip and just place it on the same folder root/system/media

8- Set permission to rw-r--r--

9- Reboot and enjoy!

Cheers
[Moto G Q&A, Help & Troubleshooting] slimshady76:
Hi folks, I've been trying to get a simple sound recorder app to work in the stock Moto G KitKat ROM without success. I tried installing the CM Sound Recoder app from the CM Apps Installer, copying it from /system/app to /data/app, etc. and I couldn't make it work.

I just want a simple app to record my son, and I can't get the darn thing to show in the app drawer.

Any help will be much appreciated.
[Moto G Q&A, Help & Troubleshooting] Quasar:
You can download smart voice recorder from play store
[Moto G Q&A, Help & Troubleshooting] slimshady76:
Thanks for the tip! I'll give it a try.
[General Accessories] jwzg:
IMHO this rates as the greatest Google find ever...well almost. Thanks to rayray987123 from www.motorolafans.com.

I just flashed my HT820 with new firmware to fix the skip problem. According to the info, any HT820 with designation SYN948A, SYN948B or SYN948C inside the headset band may have the skip problem. Mine is a 948A and the flash indeed fixed the problem. The flash instructions I in the attached .RAR file are in English.

NOTE: The headset MUST be turned off. As you are plugging USB cable into the headset, you MUST keep the forward and back buttons depressed. It will not go into flash mode otherwise.

I've been listening to my headphones for the last 30 minutes and they only skipped when I cupped my hand over the earpiece. Sound is as good as the original without the skipping of course. I'm happy!!!!
[General Accessories] Jainoxi:
Flashed my HT820 with this patch succes! Will keep you posted!
[General Accessories] Wiz:
Hmmm mine is not recognized, but also is a SYN948D .... any clues?
[General Accessories] jwzg:
I'm not sure if you can flash this firmware to any other models. This is for A, B or C only. You may try to contact Motorola to see if there is an upgrade patch for your set.
[General Accessories] jwzg:
Shameless bump on the front page. This is not a registry hack...it's new headset firmware and it flat works.
[General Accessories] scr6:
Just did it to my HT820 Part number SYN0948A. Seems not to have completely aliviated the problem completely but its a great great improvement. Where I was getting skipping/chopping every couple seconds I know can through a couple minutes of music. I'll update once I test it out a bit more since it has been only a couple minutes ha ha . Sorry I was just anxious to say Thanks and confirm that it does work. Now I dont know if its just me or it seems like volume is a bit lower and distorst when I put the Media player to 100%. But I dont know if its me like I said. Well I stop ranting and showing my excitement since now I feel like I didnt throw money away on my mda and ht820's since thats one of the major reasons I switched from my sk3
[General Accessories] jwzg:
Try the priority256 hack on the registry and see if that doesn't bring it in line. This morning I was trying o listen to Resco Radio and it was skipping all over the place. I did that registry hack and Barry Damn White is coming through seriously clear.
[General Accessories] shogunmark:
well i have an asian knockoff from ebay... and numbers have worn off on it so i cant tell if i have one that can be updated or not.. when i press down the back and forward and insert the mini-B nothing happens for me, just charges... at any rate i did a reg hack on my 8125 and got rid of the skipping anyway..
[General Accessories] jwzg:
First of all, the Asian versions on Ebay are typically not knockoffs. They are the same headphones produced for the Asian market with different firmware. Knockoffs are out there, but if the headphones are coming in the box with paperwork, most likely they are not. I do live in China and believe me it's easy to find the fakes.

Second, the cab that shogunmark posted also has a bad key. Check the registry after installing and you'll find the key AD2P instead of A2DP. That does exactly squat. In addition, the various registry hacks on this board do little or nothing if the firmware on the phone is faulty. Believe me, I used all of the registry hacks and nothing kept them from skipping until I updated the firmware. If a reghack alone fixed your skipping then you have good firmware already installed. The only reason mine were skipping this morning was that the wifi was running at the same time and the priority256 hack gives higher priority to the A2DP dll.

Third, you MUST follow the directions to the letter, or the headphones will not enter flash mode as you plug it in.
[General Accessories] shogunmark:
First of all thanks for the flame :roll:

second i never said i didnt like my asian version, works great for me, dont care if its asian or a fake or both. Its definitely poorly made, but i dont care, for $50 on ebay after shipping im happy with my purchase.

3rd, i didnt make that reg hack, all i know is that i tried everything.. Mine was skipping every 10-15 seconds when playing music and it drove me nuts.. i finally came across that reg hack somewhere on this board (dont remember the thread) and bad key or not it fixed my problem..

And finally, i did follow the instructions to a T.. next time i will post that i held the 2 buttons down, plugged in the mini-B and "waited 3-5seconds" and still nothing, just a solid blue charging light, no flashing blue light..

so excuse the f*ck outta me for giving my 2 cents on what worked for me, im just trying to help others on this board just as much as others has helped me.
[General Accessories] jwzg:
No flame intended. Just be careful what you post. Not that the cab would brick your device, but posting any old cab without knowing its source or what is in it is not what makes this forum great.

I certainly didn't mean to flame you, but was trying to separate fact from fiction. Perhaps I sounded harsh and for that I apologize.

Better?

One last thing; the buttons on the right earpiece are the correct ones. It should go into flash mode if it's the real deal. Again, sorry for being assuming, but I don't give up easily.
[General Accessories] jordanmills:
This ain't working for me either. I can't get it to go into flash mode. I turn the head set off, hold the buttons, plug in the cable, and wait . . . and the light just stays on. Nothing changes when I release the buttons.

So, if it worked right for you, did the lights turn on as soon as you plugged in the cable, and did it start flashing before or after you released the buttons?

I have PN SYN0948A so blah on me.
[General Accessories] jwzg:
The light will not begin to blink until it has been plugged in for a few seconds. Keep the buttons depressed until it does. Once again the buttons on the right side earpiece must remain depressed while the cord is inserted. As long as the lights are blinking, you can run the .exe in the patch and just follow the instructions from there.

I'm certain it does work. However, this seems to be a problem with more than one person, so I have no idea if its the way you are doing it, or the headsets.