yashsingh1/xdaforums huggingface dataset:
[7" Kindle Fire HD Q&A, Help & Troubleshooting] jscombs91:
Yep 100% sure. I believe it came with 7.4.6 out of the box. and I tried the 2 latest versions of that the 1.3.0 and 1.3.5 ones. an I believe it was running 7.4.6.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Jserrano56:
I'd try flashing 7.3.0 or anything higher, try using tool from the previous link I posted first, or anything else available and if it boots use KFFA to downgrade to 7.2.3 and I'd use FireFlash to flash the 2nd bootloader and recovery

When it boots is it useable for 30 secs or is it just frozen during those 30 secs and then crashes back into a boot loop?
[7" Kindle Fire HD Q&A, Help & Troubleshooting] jscombs91:
I tried the latest version which is 7.3.0 (That's the newest one I can find) and it just goes into a boot loop. and it's usable during that time then freezes and crashes.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Jserrano56:
Okay well to be honest I never used recovery until I need to use twrp so I'm not sure how stock recovery is set up but try booting into stock recovery and see if you have to option to either

1. Wipe cache and data

Or

2. Factory Reset

Let me know how it went
[7" Kindle Fire HD Q&A, Help & Troubleshooting] jscombs91:
I believe the screen with the red triangle is the stock recovery (I am unable to get to it through normal means just have to wait for it to randomly boot to that) and if it is then the reset to factory defaults button doesn't do anything to fix it.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Jserrano56:
If you've flashed anything since your last post go back to the one that kept boot looping holding down the power button for 20 secs will reset it and that should fix the boot loop? Report back to me when you've tried it
[7" Kindle Fire HD Q&A, Help & Troubleshooting] LinearEquation:
No, a bootloop cannot be fixed by powering off and on.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Jserrano56:
That's not what I meant?

shouldn't resetting the device fix it?

Wiping cache and data fixes boot loops?

So resetting it should do the same right?

Is the hard reset key combination something different?
[7" Kindle Fire HD Q&A, Help & Troubleshooting] LinearEquation:
Well, until you get the stock OS to actually boot and "cook" that reset won't do anything really. Only flashing through bootloader can do anything. I'm scratching my head myself over this one. Everything shows that it should be working. *shrugs *
[7" Kindle Fire HD Q&A, Help & Troubleshooting] jscombs91:
You and me both. I actually was able to get it to boot into the amazon os but like on the TWRP after about 30 seconds or so it froze with green pixels and restarted itself into a bootloop. It's very inconsistent. I could do the exact same steps I did to get it into the amazon os and next time it wouldn't. but 3 times from now it might.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Jserrano56:
Wait... What? What did you say about TWRP?
[7" Kindle Fire HD Q&A, Help & Troubleshooting] jscombs91:
Oh whoops. I must have edited that out of a post earlier by mistake. I was able to boot into TWRP earlier for about 30 seconds but it crashed and restarted into a bootloop. I'm trying to get it into it again to take a look around the file system and see if anything looks odd but I'm not having any luck getting back into it.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Jserrano56:
It all makes sense now!... sort of

Okay so after all these attempts to return to stock somehow twrp survived? Something isn't right? But maybe that's what we've got to get rid of? And get the proper stock recovery img in for it to boot up without boot looping

Or

Maybe you could sideload or that adb push a rom onto it? I know that boot loops are a problem if you installed the 2nd bootloader on anything higher than 7.3.0?

Do you have enough time in twrp to wipe the cache and dalvik cache, I'd say wipe data too but I'm not sure how your Kindle will respond to that?
[7" Kindle Fire HD Q&A, Help & Troubleshooting] jscombs91:
Well I flashed TWRP just to see if I could get into it by chance and poke around. I tried sideloading but it crashed and reboot right after I hit it. Does anybody know if the kindle outputs data by UART? I know I saw RX and TX pins on a picture of the board. Maybe I could read data from UART and see if it's throwing any errors or such.

EDIT: I hooked up a FT232 to the TX pin and got the following data with stock images using system restore tool: http://pastebin.com/NbEQk4JJ (Warning: A LOT of text)
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Jserrano56:
[MENTION=1898996]jscombs91[/MENTION] try this

Substitute the KF2 files with the KFHD7 files?

http://xdaforums.com/showthread.php?p=5937
[7" Kindle Fire HD Q&A, Help & Troubleshooting] LinearEquation:
Did I miss him using KF2 rather than KFHD7 files? That would not be good if this is the case.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Jserrano56:
No but a guy in the KF2 thread had a similar problem and was able to fix it and he posted his method on their KF2 threads, I'm suggesting he try it and report back to us, we have equivalent files that were used in the tutorial we just need to substitute them
[7" Kindle Fire HD Q&A, Help & Troubleshooting] jscombs91:
Well I just went ahead and got rid of the kindle since it looked like it wasn't getting fixed any time soon. Thanks everyone for your help. :)
[G2 Q&A, Help & Troubleshooting] sujith4nair:
Hie

Lg G2 a brand new phone hardly used for 2 weeks. i am in love with this phone. i always like to click pics. although it seems lg g2 camera is decent, however i feel camera quality can be improved a lot. Later i found Jishnu's Camera mod. i wanna try it.

1) before that like to have some questions. any easy way to both Root and Unroot? can i use this mod with temp root?

2) after unrooting what about warranty? will it be void? can those service center people find i had previously rooted G2?

3) On the other side kitkat OTA will be released, so can i update? will i have to unroot and update OTA?

4) any one provide me links for above query?:confused:

please dont complain this questions had been asked many times etc etc.. Am asking just for my satsfaction
[G2 Q&A, Help & Troubleshooting] Plain Water:
Rooting: theunlockr.com/2013/10/25/root-lg-g2-versions-video/

Recovery flash: theunlockr.com/2013/11/03/flash-custom-recovery-lg-g2-versions-video/

Unrooting: theunlockr.com/2013/11/01/unroot-lg-g2-versions-video/

---------- Post added at 07:50 PM ---------- Previous post was at 07:49 PM ----------

About warranty, I'm not sure.

---------- Post added at 07:54 PM ---------- Previous post was at 07:50 PM ----------

If you want to receive ota updates when you are rooted, remember to backup your stock recovery via flashify, then install custom recovery to install your camera mod. When the ota is out, reflash your stock recovery via flashify and download ota root keeper. Then from there choose protect root and backup root. Then start the ota update
[Samsung Galaxy Nexus] randommmm:
I like the idea of reclaiming GN's reserved RAM, but we all understand there is no free lunch, those threads only mention 1080p record or playback support, what drawbacks of those RAM hack brought to us exactly?

I don't think most users who flash those kernel or even some kernel developer was acknowledged that. (especially who don't own a GN themself)

I keep seeing phase like "no known negative effects", "The ram being freed comes from things like 1080p playback/recording and other such things that keep ram even when not being used" .

They are wrong.

I test with a few video, show that all RAM hack has more or less backfire to GN's HW play-back ability, quick conclusion:

1. ASRAM is better than BigMEM. ( I just quote them by name, which I read in kernel thread, not pretent knowing what they are...).

2. Stock 693MB is better than ASRAM.

Two chopped video is attached,

When I said "better", I mean the kernel can allow more video files decode in hardware acceleration mode, aka, HW or HW+. Basically there is no video can play in HW mode with BigMem kernel. ASRAM can't play output.mp4 in HW mode, while outputb.mp4 is fine.

If by any chance you don't understand what is the difference between HW & SW playback...

Well, in short, HW will use less CPU to play a video, which lead to better battery performance, much better. I also tested that, it depends on you screen backlight and specific video parameter, in my test, SW mode will consume 2-3 times battery compare to HW mode.

Final conclusion:

If you watch video a lot (most online video is code by AVC1 ), avoid BigMEN hack kernel like superRAM, it's up to you whether use ASRAM though.

NOTICE: all 4.3 or later ROM may need another fix to play video without lag.

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

This fix was discovered by [MENTION=5208741]oubeichen[/MENTION]

For the record, none of the test video is 1080p
[Samsung Galaxy Nexus] Mach3.2:
So that's why some videos won't play smoothly on my gnex..

I guess i'll reserve such functions to my n7.
[Samsung Galaxy Nexus] Ashtrix:
But when i was using no ASRAM/BigMem types like Trinity Kernel the HD playback was choppy too, since the 4.3.x + update everything messed up :rolleyes: .
[Samsung Galaxy Nexus] seriousia:
Exactly.

I have a 1080p video and it was playing smoothly on 4.2.x but it shutters in 4.3+ Roms. :confused:
[Samsung Galaxy Nexus] randommmm:
That is another issue, and the fix is in the OP too, please refer to this link:good:

http://xdaforums.com/showthread.php?t=2559138
[Samsung Galaxy Nexus] randommmm:
No, not exactly. The decoder binary has problem since Android 4.3, there is a fix by reverting to 4.2.2 binary, as I said in OP or you can refer to this link:

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

SW does the decode thing all by CPU, and GN's 1.2G CPU is OK to deal with many video, you won't notice difference between HW from SW except the battery drain in most of the case.
[Samsung Galaxy Nexus] randommmm:
I've read the source of BigMEM and ASRAM, they are the same thing. They just used try & error way to "find out" that took 50MB from the heap_tiler instead of the more aggressive 70MB will keep the carama 1080p work, nothing sophisticated. Those developer didn't realize this heap not only relates to the ability video can play or not, but also hardware decode ability.

Honestly, I hope they don't realize that, or they were lying and put the blame on application
[Samsung Galaxy Nexus] akash3656:
How did you come to a conclusion that they were lying? And some developers DID realise that video playback is also broken and even has that mentioned in their threads. Or indirectly mentioned that things may break by making different variants for different users.

And by the way if you want 100% stable and working phone, xda or any other place that encourages you to tweak your phone is a complete no-no for you.
[Samsung Galaxy Nexus] antypas:
Most devs mention that this "hack" breaks "things".

The matter is how important to a certain user is the ability to play flawlessly every video available.

Most users aren't bothered at all...

"Bigmem" and "ASRAM" and bull****. They aren't anything special.

They do the same thing to a different amount. "Bigmem" reclaims more than "ASRAM" and "SuperRam" reclaims even more than "Bigmem".

Mpokwsths invented the technique and others just decreased the amount of reclaimed RAM.

The source is available, you could build your kernel with less RAM reclaiming and try to find the sweet spot for you.

Or if you are a hotshot try and build a kernel that gives back 900MB of RAM and keeps the video playback perfect.

Otherwise ... seal your lips and be more kind to the "developers".

[MENTION=1662773]mods[/MENTION]: This thread should be closed or at least moved to the appropriate section.
[Samsung Galaxy Nexus] randommmm:
Do you read? I said If they know what they're doing, still claim "just some rare app will not work" , that is a lie in every definition. Did you ever read a line of source of any kernel or rom? Please shut-up before you've finished reading.(thumb down)
[Samsung Galaxy Nexus] randommmm:
double post
[Samsung Galaxy Nexus] randommmm:
Thankyou, XDA need more retard like you two, rate the thread 1 star? I don't care, did you read? Did you know the 4.2.2 fix? I post this topic is for those who read those OP like great CM, say goodie, goodie, and backfire? Sorry, we don't cover that, or we won't get some "donate", wow, bravo.

The most interesting thing is someone who don't own the phone can "create" a kernel for it :D, and still some stupid stand in the defense line for them. I like it. It worth a watch.:laugh:
[Samsung Galaxy Nexus] randommmm:
[MENTION=1662773]mods[/MENTION]

I am totally fine if you feel like you should close this thread, I feel sorry for those user who using kernel not function as they'd expected. I feel even sorry for those developers who follow these BigMEM, ASRAM commits, making kernel they believe their kernel breaks nothing or just something rare use( like 1080p).
[Samsung Galaxy Nexus] antypas:
I did know about the 4.2.2 Ducati engine fix... It was posted a few days ago.

So that doesn't make me a retard after all???

You are not only ungrateful to the devs that do things for free but you are a ***** that calls names as well...
[Samsung Galaxy Nexus] doomed151:
I suggest that devs make memory-reclaimed kernel versions optional, and the stable version should use the stock ROM allocation to avoid any function impairment.
[Samsung Galaxy Nexus] antypas:
Or the users that don't want the extra RAM can build whichever kernel they desire from source after changing the RAM reclaiming values...

Simple as that.
[Samsung Galaxy Nexus] akash3656:
Even if I have read, android is God knows how many million lines of code and thousands of commits. They (kernel developers) never mentioned some rare app, they say it as a general thing. And please, even if I do not read github like a story book, I read OP and try my best to follow threads. And clearly most if not all made variants without RAM hacks or made variants that worked with most things. If that weird app doesn't work, screw it flash a kernel that doesn't mod with RAM. Or go fastboot flash to stock 4.3.

As pointed by others, you could make your own ram hack that is *better* or appreciate their work and accept the fact Galaxy Nexus sucked from day 1 in terms of RAM.

Seriously, if you're gonna rant you're also at the wrong section of the forum too. Have you read xda rules?
[Samsung Galaxy Nexus] oubeichen:
I think kernel with 40MB RAM reclaimed is safe for most 720p video.

Kernel with ASRAM(50MB) cannot play 720p video that ref > 7 with HW nor HW+ decoder.

And with 40MB declaimed can up to ref = 9.
[Samsung Galaxy Nexus] Nephilim:
This whole thread is just a giant ragefest, honestly it should be removed. I don't feel OP is correct in outright calling people liars, it's just not the appropriate way to get a point across in an adult developer community. Just because one individual has an issue with a particular app or a certain function properly working does not mean others will guaranteed have this same issue. With android we all do different tweaks, use different apps, kernels roms etc. This means that just because the particular apps you choose to use are not working because of Bigmem, Superram ASram blah blah blah, it doesn't mean it's an epidemic on all of our devices.

I have had no issues using MX Player or Youtube on HQ video setting with Superram, I haven't had a single reboot, freeze, app fc or anything else do to the SuperRam kernel, I've been using it since it first was released on 4.3. I use my custom settings with it as well. I am not trying to bag on randommmm, what I am merely doing here is saying that no one is right or wrong and the developers are certainly not liars.

On my custom kernel thread I have a poll on which kernel people prefer the most, as of right now 49 out of 73 people on there are using MPOkang superram kernel, none of them are complaining about it causing all these issues.

The OP of the Kernel clearly states that 1080p video playback/recording will not work, that is the only thing that is guaranteed to not work for sure, if you need 1080p on your device then simply do not use the kernel, quite simple.

With any kernel there is a chance of issues, but guess what? With any kernel settings there is a chance of problems too, just because people have certain issues with SuperRam kernel flashed does not mean it's superram, not everyone knows what they are doing when adjusting the kernel settings. Not to mention not every rom, especially 4.4.x roms, are going to work perfect.

I read randommmm's post about this on whatever thread he posted about it on, I personally do not feel this subject warranted it's own thread.

randommmm, I am in no way saying you don't know what you are talking about but..... until you have developed a kernel yourself you really should not be namecalling people that have. If this were as extreme of an issue as you are making it out to be there would not be so many using SuperRam kernel without complaint and there certainly would not be the vast amount of other kernel developers adding free ram modifications to their own kernels.

I sincerely mean no offence to anyone on this thread. I've been following it for a bit now and felt it was time to put my opinion in.

That is all.

Neph
[Samsung Galaxy Nexus] randommmm:
It's not about that. Who don't want more RAM? The point is some "great NAMEs" like the below [MENTION=2853378]Nephilim[/MENTION] claim it's safe, it's won't hurt anything except 1080p record or playback, without really looking into the problem. And, make some weird statement like "rare app won't work", but the truth is the kernel broke thing, not RARE app, it's universal. And, that is why quite some kernels follow this innocent looking ASRAM.

I just trying to tell the truth to the developers mostly, I surely can build a kernel myself, in fact, I am always using kernel built by myself.

I just don't won't people suffer from a bad battery performance because of flashing bad kernels.

At last, I don't try to hide my dislike to some dev. who themselves don't even own the phone.... that is ridicules.
[Samsung Galaxy Nexus] randommmm:
So you think know what are you saying? HAHA, funny, one of the quote is from you,:D when [MENTION=5208741]oubeichen[/MENTION] the first person said that superram will bring bad effect to HW playback. And you choice of phase is not that polite in my opinion. Just because you has more posts and "thanks" don't make you correct.

That is weak defense saying no one complain... people won't know before they were told or discovered by themselves. Somehow you want a thread deleted because it is telling the true, what are you afraid of ? Do you gonna shout " you can't handle the truth" next:laugh:
[Samsung Galaxy Nexus] randommmm:
Thanks, you help me more than any big name in the GN forum. (well, some of them turn out wrong though)

I'll build one tonight and see how it goes;)
[Samsung Galaxy Nexus] pattyboi:):
one of the most mature comebacks i have ever seen neph,very mature man,major props.:good:
[Samsung Galaxy Nexus] AgentSmith:
Ignoring the endless politics going on here I can gladly report this fix finally made 720p and even some 1080p video smooth again on my GNex. This is nice because I used to use my phone a lot for watching series and the OP made that possible again for me. A million thanks. :)
[Samsung Galaxy Nexus] Sik-1:
Google broke HW playback in 4.3, obviously why you posted the revert to 4.2 files. Smfh

---------- Post added at 04:54 PM ---------- Previous post was at 04:54 PM ----------

Also what good is watching a 1080p video on 720p screen???? Plz do tell
[Samsung Galaxy Nexus] Nephilim:
Good point on the 720p screen. As for the "fix", its really just workaround using old files, technically swapping outdated vendor files isn't fixing anything.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] Sik-1:
Exactly what I'm tryna say
[Samsung Galaxy Nexus] Exnor:
Why would one try to watch 1080p video on a 720p screen?

From my Galaxy Nexus yakjuxw
[Samsung Galaxy Nexus] AgentSmith:
You really can't come up with even one possible reason?? How about quickly checking a new download on your NAS? Or watching a movie on the road that you only happen to have in 1080p? I even hooked up a full HD screen once in a hotel to watch a movie in HD. Worked perfectly! This phone's hardware can do it so why should the software hold it back? Or in other words: why are you willing to cripple your phone?
[Samsung Galaxy Nexus] Nephilim:
No one told you that you have to use any of the kernels with free-ram mods. And as said twice now, how exactly are you able to view 1080p on the Galaxy Nexus' native 720p screen? If I wanted to watch an HD film at a hotel I'd connect my laptop. You are just grasping at straws right now. My device is in no way crippled. I am able to use every function on my gnex that I need to use and as said above, since the screen is only 720p it is asinine to need to view a video in 1080p since its automatically downscaled to 720p anyway.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] AgentSmith:
How is giving factual examples equal to grasping at straws? All these things I actually did my presumptuous friend. I suggest you read my previous post again, slowly, without jumping to conclusions, because you might then pick up that resolution is not my priority. And again, I don't get involved with politics. All I said was I'm happy HW acceleration works flawlessly now, with the stock cm kernel.
[Samsung Galaxy Nexus] Nephilim:
Actually, your example of watching a 1080p video on your phone is irrelevant seeing as the screen resolution is only 720p. Most people do not bother downloading or transferring 3+gb of 1080p movie onto their 720p resolution 4.7 inch screen smartphone just to stream it on a hotel television so that's almost completely irrelevant as well, and I'm not sure what you mean by "check a new download on your NAS". As I said in my past posts, you don't have to use kernels with free-ram modifications but it surely is not hindering anything I need to do on my device. You are still grasping at straws, there is really no day to day relevance on anything you posted on your previous comment and my reasons are stated at the beginning of this post.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] oubeichen:
We should not fight about this issue.

And maybe developers dont watch videos as much as we are.

Anyway, I am just hoping they can release multiple versions to meet different demand, only to change one line of code before compile(of course we can build the source ourselves,but you know we love mpokang).
[Samsung Galaxy Nexus] Sik-1:
Bokang has 3 options exactly what you asked for lol
[Samsung Galaxy Nexus] AgentSmith:
Amazing how some keep repeating themselves just because they like their personal beliefs a little too much. Sarcasm aside, everyone uses their phone differently. That you don't need a certain function doesn't mean someone else doesn't either. I used the full HD output of my phone several times already in the past year. It's there for a reason and I particular like to make use of it from time to time. It saves me from hauling a laptop with me when all I need is to display audio and video. And the NAS story, let me rephrase. When there's a new video download on my NAS it's nice to be able to quickly check the file with my phome without having to grab my laptop. This is just one of those things that makes life a little easier and I sure as hell never thought I would have to explain it in this many words...
[Samsung Galaxy Nexus] bsmitty83:
I don't think neph understands your acronym for network attached storage , and again for the millionth time , we don't get the reason for this thread , its useless , just flash another kernel . its pointless to argue this topic . funny , but pointless .

It may as well be a "best ROM thread "

Your explanation could have been a lot shorter if you just said network attached storage next time