yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] waffull:
Anyone find YouTube fc'ing upon system startup? It's been happening for the last 4 or 5 builds. YouTube is a system file, so I've just been ignoring it since I reboot so rarely. But I've started having to reboot every morning after using Songza during the night. I assume that is a memory leak issue.

Anyway, I uninstalled it just now and rebooted and found the startup much faster. The unlock responded to the first touch. So clearly YouTube was trying to do something at startup which slowed it down bc it was fc'ing.

I checked aLogcat, but that shows a blank log, not sure why. I only have a chromebook right now, so now Windows to get log with.

I'm currently on the newest build and before that the experimental build and every twa build since the first JB build.
[Kindle Fire Android Development] YaKillaCJ:
I can't officially confirm your suspicions but can say from my own experience. I have not had any force close messages on any of the CM7 and CM9 roms granted the app is (generic). Facebook, Pandora, Netflix, Youtube, Maps... Pretty much the apps that should run across all devices. Well time Im going to move from CM9 (GedeRom) to this now since it seems stable enough. Is there anything I should kno thats a well known issue or suggested additive?
[Kindle Fire Android Development] merwin:
I had to move away from the ROM temporarily. Weird freezing issues in Temple Run. Anyone else have an issue with that game on the latest ROM?
[Kindle Fire Android Development] bluSCALE4:
I had been running Hashcode's version released a month ago and though this adds more features, it is a lot buggier. Most of the issues I've noticed have to do with the stock launcher or any other launcher. Considering you use the launcher often, it's something that'll have me updating to the next version or better rom asap.
[Kindle Fire Android Development] wolf45801:
i been using this rom for alittle while now and havent had no problems except for twc tv app crashing cause of codec problems
[Kindle Fire Android Development] twa_priv:
Just ignore people like bluSCALE4 who have absolutely nothing useful to add besides *****ing.
[Kindle Fire Android Development] wolf45801:
oh trust me i ignore alot of people like that lol
[Kindle Fire Android Development] webdroidmt:
My apologies for a useless post but I had to say that the "Thanks" I just clicked for twa equaled his post count. :D

Mike T

---------- Post added at 02:33 PM ---------- Previous post was at 02:19 PM ----------

Figured I'd try to make my post more useful. LOL You mention You Tube being a system app, sounds like you have an older gapps from maybe 7/11 or 7/17. The newest gapps from 7/26 no longer includes You Tube, as it's downloadable from Play Store. Since you uninstalled it, have you tried to d/l You Tube from Play Store? Also, if you haven't flashed 7/26 gapps, might be a good idea. You Tube works great for me.

Mike T
[Kindle Fire Android Development] jstrom23:
I agree with everything that's been said about the awesomeness of this ROM and the Devs, twa_priv and Hashcode. I also agree that all of the funky issues are fundamentally app related, whether it's a buggy app like FB, or too many apps using up the RAM. Fresh install of this ROM is just about flawless.

I appreciate the support and generosity of the devs and the community.

I will try the zram setting mentioned above (thanks for the tip) and if it works great, and if not, who cares. I'm running JB on a Kindle Fire...what could be better than that.

---------- Post added at 03:22 PM ---------- Previous post was at 03:12 PM ----------

Both work great. I generally go back and forth between them for variety. One of the benefits of using a custom ROM.
[Kindle Fire Android Development] soupmagnet:
I can't agree more. If you can't do it better yourself, and you're not paying for it, don't ***** about it. If you can't offer something constructive to the conversation...GO AWAY.

@twa_priv...Kernel issues aside, this ROM is flawless. Thank you very much for for the work you put into it. Devs like you are why this community is so strong. Keep it up.
[Kindle Fire Android Development] twa_priv:
Thanks for the support guys.

Here's a new build. Compiled using the old kernel sources to workaround the wifi and flickering issues until they are fixed (see below).

20120828-1622-Linaro (Old Kernel)

* Old kernel build

* Trebuchet replaces Launcher2. Because both CM10 and SGT7 are now using Trebuchet as the default launcher.

* Latest SGT7 / CM10 changes

NOTE: The launcher change means you will have to setup your homescreen(s) and widgets again. Sorry about that but I had to switch eventually.

-----------------------------------------------------------------------------------

Here are some comments about the issues that came up recently.

* Wifi sometimes does not reconnect after wakeup.

Only happens on new-kernel builds. Also happens sometimes on vanilla new kernel CM10 builds using just hashcode's local_manifest.

Workaround: Disabling/enabling Wifi re-establishes the connection.

* Blank apps screenshots in Plays Store.

Happens on old and new kernel builds as well as on complete vanilla CM10 builds without any customizatons, linaro, sgt7 etc. The reason is a dalvikvm out-of-memory error when loading an app screenshot.

* Flickering of certain popup menus.

Only happens on new kernel builds. Not sure where exactly the issue is yet. But interestingly it goes away if I either build using the old kernel OR use the framework, settings CM10 repos instead of the SGT7 ones.

* TWC app streaming issue.

Seems to be a CM10 issue because it works on AOSP builds.

@wolf45801 - please test the latest 20120828-1622 build and let me know if any of the (quite many) recent CM10 changes had a positive effect :)
[Kindle Fire Android Development] pbailey212:
Thanks for giving us a chance on the new kernel. Though its not quite ready for prime time, it has potential. I'm downloading your new build right now, I'm sure there won't be any real issues, but I will let you know if i find any.

sent from my Nokia 5110
[Kindle Fire Android Development] webdroidmt:
Wow! Thanks for the new build and thanks for troubleshooting all those small issues. I'm debating if I should install the new build, or just stay with what I have for a while. The only issue I do have in that list is the blank screenshots in Play Store and it really doesn't bother me. Wifi has been solid for me and I have yet to see any flickering on the recent apps popup menu. Maybe it's happening elsewhere and I'm just not catching it??? Anyway, great work as always. Thanks.

Mike T
[Kindle Fire Android Development] twa_priv:
The flickering issue is reproducable by adding a Settings Shortcut widget -> right after dropping the icon to the homescreen the available options popup menu flickers a few times.

But yes, pretty much all but the wifi issues are minor. Even there is an easy workaround.

The blank app screenshots seem to be a generic issue even on older builds, old and new kernel, vanilla and custom. I played around with different dalvikvm settings but without any luck so far.
[Kindle Fire Android Development] webdroidmt:
On the flickering, I'm not seeing it??? I use Holo Launcher HD and I couldn't reproduce it. I also just tried adding widgets with Launcher 2, including settings shortcut and still was unable to reproduce the flickering.

Well, I just finished d/l the new build, I'll probably make a nandroid and give it a flash. Can't resist those flashaholic tendencies. :laugh:

Thanks,

Mike T
[Kindle Fire Android Development] twa_priv:
What build are you on?
[Kindle Fire Android Development] webdroidmt:
The last one, 0824-2036.

Mike T
[Kindle Fire Android Development] wolf45801:
ok let me charge kindle to 100% and ill flash it and report back
[Kindle Fire Android Development] pbailey212:
After playing with today's build for a couple hours, I can confirm all previous issues are gone. (I don't know about twc) bravo! Thanks for keeping the kindle fire burning
[Kindle Fire Android Development] portezbie:
TWRP still gives me errors three or four times before working when trying to install this rom. I was hoping the last update to twrp would fix that, but doesn't seem like it.
[Kindle Fire Android Development] duncakes:
Jus switched over from jandycane yesterday, no issues so far, sure do miss the quicknav but I can deal with it. Since this ROM is so snappy. Good work guys.
[Kindle Fire Android Development] wolf45801:
ok i just flashed and tried twc and its still giving me the error so no it dont work and i have to redownload xda app it wouldnt open afterwards lol
[Kindle Fire Android Development] webdroidmt:
Since you're still having issues with TWRP, have you tried COTR? It's been working well for me, only thing it seems to take a little longer to backup/restore. You can get it in smirkis' smirkit installer thread. http://xdaforums.com/showpost.php?p=22608974&postcount=1

Mike T
[Kindle Fire Android Development] twa_priv:
I have one more test build for you to try if you want.

This build is a non strict-aliasing build - and in case this one works at least I know the issue is with the linaro strict aliasing fixes.
[Kindle Fire Android Development] wolf45801:
ok let me get that flashed ill report back

PS still does it
[Kindle Fire Android Development] twa_priv:
Ok, thanks for testing.

I can't recall now ... but did you ever get twc working on any other jb rom?
[Kindle Fire Android Development] wolf45801:
Yes it works great on jandycane

I never tried hashcodes
[Kindle Fire Android Development] twa_priv:
Right ... that means I'm pretty sure now this an issue with the CM10 frameworks/av repo then and it will get fixed sooner or later.
[Kindle Fire Android Development] wolf45801:
Yeah thank you for trying u know the funny thing is it does the same thing on cm9
[Kindle Fire Android Development] twa_priv:
Actually ... I was just reading the reviews for the TWC TV app - and people are complaining there that it doesn't work on rooted devices.

Can you go to Settings -> Developer options, click on Root access and select Disabled. Then try the app again - worth a shot....
[Kindle Fire Android Development] wolf45801:
Same thing I bypassed what it looks for on root. The live TV will start then error out after it tries to buffer
[Kindle Fire Android Development] waffull:
I have not tried installing from play store yet, but was about to. I have been using the 7/26 gApps, except for gallery, which I took from the ics gApps. I have no explanation for why it was a system file. I used to back up with my backup root and do clean installs and the restore all apps and data. Maybe somehow it got mixed up in that? But I have only dirty flashed at least the past 5 or 6 builds. Maybe bc i gave the alien rom a try for day and that had gApps pre-installed. Who knows. Its gone now and I will report back after I install from the play store.

Btw, thanks for the reply.

EDIT: OK, so with YouTube uninstalled, I booted into recovery, updated to the newest TWRP, 2.2.2.1, booted back into system, booted into recovery, wiped cache and dalvik/cache, flashed 0828 build, wiped dalvik/cache, booted back into system.

A couple of odd things happened. 1) YouTube automatically "updated" from the play store. But updated what is my question, I had uninstalled it. And why? I did not flash gApps again. 2) rom manager, which I had uninstalled since I have no use for it, installed itself from the play store. Why?

I'm going to cycle through a few reboots now to see how YouTube acts. Will report back only if it causes a problem.
[Kindle Fire Android Development] pbailey212:
This might be a long shot but go to performance and turn off surface dithering and turn on 16bit. Its native to cm9 and its not on aosp.

sent from my Nokia 5110
[Kindle Fire Android Development] wolf45801:
Thanks but nope same thing
[Kindle Fire Android Development] webdroidmt:
You're probably right if the Alien rom had gapps preinstalled, most likely You Tube was one of them. Generally, if I'm coming from a rom that has preinstalled gapps, I always wipe system along with cache/dalvik, then flash the new rom and gapps. It's like giving your KF a laxative. LOL

Mike T
[Kindle Fire Android Development] waffull:
Hah.. I'll try to wipe that visual from my brain ;) I just added an edit to my post above..
[Kindle Fire Android Development] saulob:
One noob question, do I need to update TWRP? I have 2.0 installed, should I update to the latest one (2.2.1)?

Or it's all ok?

Tks
[Kindle Fire Android Development] pbailey212:
Old twrp will work just fine

sent from my Nokia 5110

---------- Post added at 07:58 PM ---------- Previous post was at 07:55 PM ----------

I can't find the weather channel streaming app, can you send me the market link?

sent from my Nokia 5110
[Kindle Fire Android Development] wolf45801:
Weather channel app? I don't use it lol
[Kindle Fire Android Development] twa_priv:
He is using the Time Warner Cable streaming app :)
[Kindle Fire Android Development] wolf45801:
Yep we will figure it sooner or later lol I also wish this keyboard wouldn't miss on the typing lol
[Kindle Fire Android Development] pbailey212:
That makes more sense, I'm an idiot and was thinking twc (the weather channel) I thought you were really in to weather lol

sent from my Nokia 5110
[Kindle Fire Android Development] wolf45801:
Lol nope
[Kindle Fire Android Development] pbailey212:
http://xdaforums.com/showthread.php?t=1604776 have you tried this? Also I read that it won't work if you have adb and USB debugging on.

sent from my Nokia 5110
[Kindle Fire Android Development] wolf45801:
Yep the live TV is working just there's a codec problem on cynogenmod. It works great on jandycane
[Kindle Fire Android Development] webdroidmt:
If I were you, I would definitely wipe system and reflash the rom and gapps. Also, be sure you are using the correct gapps version for 7/26, they released two packages, one had YT as a system app, in the second one it was removed. Here's a link to the current 7/26 gapps with YT removed, just scroll down and read the release notes. You may still have some leftover stuff in system from the preinstalled gapps in the Alien rom, wiping system and reflashing the proper gapps package should square it away.

http://wiki.rootzwiki.com/Google_Apps#20120317

Also, if you're restoring apps with Titanium Backup or similar, you don't want to restore system apps, just user. Restoring system apps will just continously put back the YT app, as well as Rom Manager, which was a system app in the previous 8/24 new kernel version of this rom but not in the new 8/28 version. Good luck!:)

Mike T
[Kindle Fire Android Development] Tim4:
Just saw an interesting effect about the flash bug, which happens before the boot animation after every cold boot.

Usually it looks like a 1 second long white splash.

But few minutes ago, i was surfing on facebook, and this time the goddamned app has a lot of strange things. Im sure its facebook itself cause it happened to me before, on other phone with 2.3.

But it was so pissing me, so i called the power menu and powered off the kindle. after few seconds i turned it on, the boot bug appeared again but this time it wasnt a white splash, it was a screen with facebook and power menu over it, in other words exactly same screen i saw before i turned the kindle off.

Hope it can give you some help about the bug, your rom is real monster!
[Kindle Fire Android Development] imtoomuch:
Why is ROM Manager installed? We don't use CWM. Or has it always been installed and I just missed it?
[Kindle Fire Android Development] twa_priv:
Because I have not yet taken it out yet on new kernel builds. Old kernel builds (e.g. the last one) don't have it.
[Kindle Fire Android Development] saulob:
So, we can uninstall/remove it without any problem from the new kernel build?
[Kindle Fire Android Development] al mon:
Is anyone else having problems flashing 8/28? In TWRP - it says the zip cannot be opened.
[Kindle Fire Android Development] pbailey212:
I had no problems. Check md5 and download it again if needed

sent from my Nokia 5110
[Kindle Fire Android Development] Ixthusdan:
It may be my imagination, but the display in the previous build (new kernel) seems sharper and more vivid than this build ( old kernel). Is that possible? Nothing wrong with either, just an observation.
[Kindle Fire Android Development] jyesucevitz:
question about the 0824 build

i've had problems with the last several builds. screen flickering. freezing. systemui crashing. after a

full wipe and reinstall of the 0824 build i have not had any of the problems. since the 0828 build seems

to be just a launcher and kernel change, am i better off not flashing the new build?
[Kindle Fire Android Development] Ixthusdan:
The 8/28 build reverts to an older kernel which is more stable than the new kernel present in the 8/24 build. If 8/24 was working without issues, could just stick with it. With the bugs worked out, the new kernel will be better.
[Kindle Fire Android Development] lukitas12:
I've been using the latest new kernel build and so far so good. Battery drains only if Wi-Fi is left turned on.
[Kindle Fire Android Development] twa_priv:
See this post for a list of issues and which kernel build they affect. If you can live with them there's no reason to install the latest build.
[Kindle Fire Android Development] a1exus:
I'm just curiose why newer build has old kernel?
[Kindle Fire Android Development] kevindiehl:
10
[Kindle Fire Android Development] lukitas12:
I disabled hw overlays, is it OK? I don't want to force the CPU. Ty
[Kindle Fire Android Development] pavanmaverick:
Didn't have to change the model, but changing the JB version from 4.1.1 to 4.0 worked like a charm. Interestingly, it also got DropBox working!

The ROM is now officially amazing! I cannot believe how quick and responsive the whole UI is. Absolutely terrific! :good::good:
[Kindle Fire Android Development] twa_priv:
When I first installed a JB ROM (the one from hashcode) adb wouldn't recognize my device. I had to reinstall the drivers (using the KFU install_drivers batch file).
[Kindle Fire Android Development] pavanmaverick:
I had the same issue, on Windows 7 x64 (but I suspect that the fix might work for all versions of Windows). Here's how I fixed it:

Turned off UMS on the Fire (that is, I clicked on the Disconnect USB Storage, so the Fire was not trying to connect as a drive).

I opened up Device Manager on my computer and found two items: The Android phone/composite device and the Portable Storage item. Uninstalled both WITHOUT deleting the drivers/software.

Disconnected and reconnected the Fire. Now, when I tried to connect as USB storage device, it showed up in Windows. Hope this helps you. I found this fix on another thread, but cannot for the life of me remember which one, or who suggested it.

---------- Post added at 07:45 AM ---------- Previous post was at 07:43 AM ----------

Had this happen too. Try wiping cache/dalvik and reinstalling the ROM and GApps (without any other wipes). Fixed the issue for me.

Good luck.
[Kindle Fire Android Development] webdroidmt:
My machine is Win7 64, my USB Storage worked perfectly on Hashcode's builds and works perfectly on this rom, as does ADB. The very first time I connected to my PC while on Hashcode's JB build, Win installed new drivers automatically.

EDIT: Just a suggestion for those having issues with UMS. Try flashing Hashcode's most current JB rom, make sure UMS is working and then flash this rom over it with gapps. Just wipe cache & dalvik when flashing this rom over it, nothing else.

Also an FYI, Goo located & downloded a new gapps for me today, 20120717. I just flashed it and it broke Google Now, restored my nandroid from last night and all is well. I noticed that the Velvet apk in the newer gapps was a different filesize from the 20120711.

Mike T
[Kindle Fire Android Development] Krunk_Kracker:
That fixed it! Excellent!
[Kindle Fire Android Development] twa_priv:
Seems like sbrady is looking into the System UI FCs ...
[Kindle Fire Android Development] vita10gy:
I did. I flashed over a 7/17 build and reflashed gapps. Holding home doesn't do anything special anymore. No one else has said anything though, except for one person thinking maybe their gapps were too new (though I flashed the same gapps on the working 7/17 one and the "not" working 7/18 build, so I doubt that's it.)

I'll try redownloading later tonight I guess.

Edit: and just to be clear, as far as what the OP says. Google Now doesn't FC, it just appears gone altogether, at least as far as getting to it via holding the home button is concerned.
[Kindle Fire Android Development] Krunk_Kracker:
I was coming in to report that my Google Now is no longer working either. I've reflashed gapps, wiped cache/dalvic cache and still nothing :( This is on the 7/17 gapps. Gonna go back to the 7/11 gapps.
[Kindle Fire Android Development] webdroidmt:
Yeah, if you read my post above #145, you'll see that I tried the 7/17 gapps and it broke GN. FYI, when I tried reflashing 7/11 gapps , it still force closed. I had to restore a nandroid for it to work again. As always with this stuff, YMMV.

EDIT: It may require that you reflash both the rom and gapps again, which I didn't do and that's why I had to restore my nandroid.

Mike T
[Kindle Fire Android Development] twa_priv:
Where did you get the 7/17 gapps from?
[Kindle Fire Android Development] webdroidmt:
If you have Goo Manager on you Fire, it reports a newer gapps version and d/l it. This is the link: http://goo.im/gapps/gapps-jb-20120717-signed.zip

Mike T

---------- Post added at 01:05 PM ---------- Previous post was at 12:37 PM ----------

It looks like Teamwin put this gapps out. I'm gonna' try it again, this time I'll flash the rom and the gapps package and report back.

Mike T
[Kindle Fire Android Development] Krunk_Kracker:
GET OUT OF MY HEAD!

I was coming back to say that exact same thing, lol.

I am now reflashing the rom and gapps with only a cache wipe.

---------- Post added at 01:10 PM ---------- Previous post was at 01:10 PM ----------

Goomanager popped up and told me I had an update.
[Kindle Fire Android Development] webdroidmt:
LOL Just flashed both at the same time, no go! I even tried clearing cache/data from GN and force stop, still no go. Just restored my nandroid again and everything's back. Guess I'll stick with 7/11 gapps for now.

Mike T
[Kindle Fire Android Development] Krunk_Kracker:
Yup, same thing for me...I wonder what changed?
[Kindle Fire Android Development] vita10gy:
I flashed the 2nd 7/17 and gapps and google now worked fine, later I flashed 7/18 over it, reflashed gapps, and google now is gone. (Not FC on open, no option to even open it.)

I'm 99% sure I flashed the same gapps both times, so that's probably not the issue. Maybe 18 can't be flashed over 17, or maybe I screwed something else up. I didn't toy around with it because I wanted to wait to confirm if it was just a me problem or not.
[Kindle Fire Android Development] twa_priv:
I would stick with one gapps version (best is probably 7/11) until all these issues are resolved and/or an "official" gapps is available on http://goo.im/gapps
[Kindle Fire Android Development] tedr108:
I'm guessing that the dev(s) did something to really improve I/O here...

I have a real-world app which does a major text file search. This ROM really does well on it, so the I of I/O is quite fast here. At first, the KF JB roms were pretty slow on this search ... you devs must have figured something out, because this ROM now beats ICS/GB roms by 15-20%. Would not have expected that. Many thanks.
[Kindle Fire Android Development] webdroidmt:
+1

I even tried replacing the Google Now (Velvet.apk) in gapps 7/17 zip with the one in gapps 7/11 and it still forced close. Hey, things are working very well as is, so I'll leave well enough alone...for now. :D

Mike T