yashsingh1/xdaforums huggingface dataset:
[Xperia SP Android Development] sadique_shiblee:
Seems like same ROM with better features and porting...
[Xperia SP Android Development] whitemamba:
Downloading... The AROMA version should be up by tomorrow. ;)
[Xperia SP Android Development] ruchirtrehan:
Few extra stuff to come, main is framework, it's a bit messy, coz framework gives bootloops after decompiling it once wether edit or just recompile, but I got some great devs helping in this, so framework shall be the biggest feature in this ROM ;)
[Xperia SP Android Development] Rajeev:
Not only in this ROM. The whole SP thread...

Btwn Reboot , Reboot To Recovery and blah blah is available in Power Menu Option ? Because i dont see that in Change logs...
[Xperia SP Android Development] ruchirtrehan:
Oops, in a hurry to release this I forgot to add them :p
[Xperia SP Android Development] Rajeev:
Ha ha ha i like it... No problem., An addon will b perfect.. Can get one now... ? Its the must needed one... :good:
[Xperia SP Android Development] whitemamba:
Are you porting the full Honami framework or just theming it?

If you are porting the full framework (with all the new stuff and infinite small apps) directly from the Honami ROMs (of Xperia Z or Z1), then I can't help you. :(

Refer to this if you have bootloops even with just recompiling: http://xdaforums.com/showthread.php?t=2321207

Also, you have to install SemcUxpGenericRes.apk first before decompiling framework-res.apk by using

apktool if SemcUxpGenericRes.apk

By the way, use the framework-res.apk from here: http://xdaforums.com/showthread.php?t=2405874

It did not give me bootloops while recompiling. :)

Hope this helps
[Xperia SP Android Development] ruchirtrehan:
Sure, will give it's add-on soon, cant now, it's raining hardly here and my net is screwed up, using mobile now :p so by tomorrow I'll give it.
[Android Apps and Games] pgunning1:
hi guys quick question. I have android ICS 4.0.4 which unfortunately can't use the swipe cards that Google now provides even with xda hacking.

I'm looking for an app that's similar to the cards Google uses ie weather, calendar, location if possible. I have metro which is very cool but no where like Google now.

Is there any app that is similar in api from the top menu with swipe.

Any recommendations welcome as from my searching the threads on xda Google now is not possible on rooted 4.0.4 due to Google restrictions - there not much fun are they lol.

Atb
[Android Apps and Games] GuyInTheCorner:
A great app is utter! which can be found on the Google Play https://play.google.com/store/apps/details?id=com.brandall.nutter

Its pretty good imo

- Sent from Guy's Super Duper S3
[Android Apps and Games] pgunning1:
hi thanks for the reply, I have utter and agree it is good, but it's not quite what I meant, it's the drop down cards that give info is what I'm looking for like the later versions of Google now.

Thanks
[Android Apps and Games] t0kgrumps:
Are you sure that you have searched xda for a working Google now for ics? http://xdaforums.com/showthread.php?t=1983337
[Android Apps and Games] pgunning1:
Hi yes I did see this thread but if you check the thread below from which its sourced it no longer works from what I can understand...

http://xdaforums.com/showthread.php?t=1747224&page=685

if I'm mistaken then I'd love to know as it's just what I've been looking for but I thought google had blocked it??
[Android Apps and Games] pgunning1:
I trust the above is correct but is there an app that is similar to the google now.

Atb
[HTC One X] Frexxia:
I'm posting this thread in case anyone else has had the same issue.

After the official android 4.2.2/sense 5.0 update, my WiFI router simply could not be detected by my HOX. After trying various things like factory reset, I discovered that the issue was that my router was set to channel 13. Changing this to the 1-11 range fixed the issue. It seems like this update removed the support for channels 12 and 13 (which are not used in the US).
[Sony Xperia P, U, Sola, Go] Dutch9177:
I tried to resolve this problem in general help discusion but no luck.

Here's the problem:

I have xperia sola white - really unhappy with very slow laggy stock rom .54, so I flashed ultimate rom v11.

First time I did it, I had no problem but keyboard which is after few minute after restart started to keep disappearing... I found out, that I'm not the only one having this problem, tried to solve with locking it in memory, change OOM after restart to -17,.... nothing so far helped.

Now I tried second shot, fresh ftf stock .54 and everything carefully flash again, guess how it end up. At first I was really happy, because it looked like problem solved, but today I'm chating on fb and that piece of... started to do it again.

Maybe it started to do this problem after I changed QWERTY to QWERTZ and downloaded czech vocabulary. Dunno, today I'm gonna experiment with it.

Maybe the problem isn't in ROM, maybe the problem is keyboard it self. Is there any way (maybe in terminal,...) how to figure out, why the process crashed?

Or please is there anyone who experienced similar problem and solved it? When I was listing xda, I found out, there are many of us dealing with this :(
[Sony Xperia P, U, Sola, Go] ChikeD:
Did you try to replace the keyboard to stock?
[Sony Xperia P, U, Sola, Go] Dutch9177:
Actually it¨s what I¨m trying to do right now, but there is another problem (as allways), root explorer won't let me mount as R/W in system folder. Trying to bypass it somehow.... with something ... I let you know, thx for (any) respond :)
[Sony Xperia P, U, Sola, Go] ChikeD:
Won't let you mount RW why? Does it has root privilages?
[Sony Xperia P, U, Sola, Go] Dutch9177:
I don't know, this phone is killing me :/

Yes, app aks for permission root, I give it access and still it shows that I'm in R/o mode :(

->

This is interesting, I can't even mount /system/ in cwm, wtf?

edit:

Tried different kernel, now it let me in :)
[Sony Xperia P, U, Sola, Go] ChikeD:
Anything else that needs root works?

This custom kernel or stock?
[Sony Xperia P, U, Sola, Go] Dutch9177:
I was using Phantom kernel, different kernel did the work... So now I deleted old kb and replaced it by stock kb from ics and guess what happend :D. I guess I need JB keyboard. Looking for it right now :)
[Sony Xperia P, U, Sola, Go] Dutch9177:
So honami kb deleted, installed stock kb and google kb. If the problem was the keyboard, you probably won't hear from me anymore :D

Thank you for help :)

note:

please don't lock this topic, I have this feeling that this is not the end
[Sony Xperia P, U, Sola, Go] Dutch9177:
I'm on stock kb and google kb... Problem remains, any idea?

I'll try to dump some log later, maybe someone would be wise from it.
[Google Chromecast] tchebb:
This thread is for FlashCast image developers ONLY. If you are not developing a FlashCast image, please do not post here. Post in the main thread instead.

Hello developers! I hope that this thread can serve as a place for you to ask any questions you may have about FlashCast development or internals, make feature requests, and report issues you're having. I will edit this post with FAQs as they come up. Until then, take a look at my documentation on GitHub, which contains documentation and sample code to help you create FlashCast mods.
[Google Chromecast] ddggttff3:
So far its working great! Plan on releasing a rooted 13300 system image with this soon, but I was wondering, is there a possibility you could create a partition backup option? so like

backup_mtd_partition 'rootfs' 'system.img'

Where it will make a folder called backup on the jump drive, and store the rootfs file system with the name of system.img? also a md5 for each file would be nice. I know I could just have a script dd the mount point, but would be nice to see a function to call.
[Google Chromecast] tchebb:
This would definitely be a useful feature. I can see a few implementation details that would need to be worked out in a non-obvious fashion, though:

There is currently no way for a imager script to directly access the root of the user partition. This is intended to prevent multiple scripts from having access to the same filesystem and possibly overwriting each others' files. Instead, scripts are executed in a temporary directory whose contents are discarded on device shutdown. It seems like the solution to this would be to create numbered backup directories, like there are numbered logs now, for mods to place their backups in.

It wouldn't be desirable for a mod to take a backup every time it was flashed, as not everyone cares about backups and they take up lots of space. There would need to be some way for the user to decide whether or not they wanted backups. Maybe another flag file?

Finally, taking a backup of an MTD partition using nanddump (dd should not be used to image NAND partitions, since it is not bad-block aware) images the entire partition, when (in the case of squashfs) only a small part actually has a filesystem on it. This means that a single rootfs backup will take up 400MB on the USB drive. I would want to implement something which can back up only the part of a partition which squashfs is using before I release backup functionality.

Obviously, this is a prime candidate for a new helper function, because of these non-trivial complications. I'll see if I can make the necessary changes to FlashCast and release backup functionality as part of v1.1. Thanks for the suggestion!
[Google Chromecast] ddggttff3:
One more suggestion, if you do not mind. :p

How about the ability to flash multiple zips at once? So, if I have 2 files I want to flash, first one will stay eureka_image.zip, and then the next one would be eureka_image1.zip, or some similar process to allow multiple zips.

The issue here would be a naming scheme that would be easy for users to use and understand. so maybe if you flash a single file, just use eureka_image.zip, and if multiple, each would have a number added, starting from 1 and counting up in the order you want them flashed?
[Google Chromecast] tchebb:
This is something I intend to implement. My current plan is to support a eureka_images directory, which can contain any combination of zipped and unzipped mods which will be flashed in alphabetical order. Mod authors can distribute their mods with a prefixed number, so, for example, you could distribute 00_13300_rooted.zip and 59_unlocator_dns.zip. I'll write a standard for how to determine the numbers (e.g. full system images get 00-09, major/minor filesystem changes get 40-49/50-59 respectively depending on how many files they affect, etc). It's not perfect and there can still be conflicts, but it should allow most mods to be flashed in a mostly sane order. I'm open to any suggestions or improvements you might have.
[Google Chromecast] ddggttff3:
Sounds great to me! Only other suggestion I have is to add another flag file which would allow Flashcast to continue flashing the multiple zips, even if one errors out.

So, by default if multiple zips are going to be flashed, and it errors on the first, it would stop, get a red LED, and then reboot.

with a flag file present, maybe ignore_errors, even if it errors out on the first zip, it would continue down the chain of zips until it finishes all of them.
[Google Chromecast] bormeth:
Anyone got any idea how to get started with some themes for the chromecast? :) Will be more than happy to help, as soon i know where to start.
[Google Chromecast] tchebb:
Most of the resources seem to be kept in the .pak files contained in /chrome. The first step to theming would be figuring out what format those are in and how to unpack and repack them. You might want to start by taking a look at the content_shell source code, as it might have some documentation or scripts for working with .pak files.
[Google Chromecast] bormeth:
Im gonna dive into it :)
[Google Chromecast] ddggttff3:
Have a little bug report.

If a person has more then 85~MB in their eureka_image folder, and then they start a SquashFS File system edit, flashcast will report an error saying out of space. Now, here is the error part. Even though it failed to mount with an error, the imager.sh file will continue to run, and will then attempt to flash back a corrupt file, causing a non-bootable chromecast until the system partition is re-flashed.
[Google Chromecast] ften:
The first script on THIS SITE will unpack the .PAK files, although it unpacks everything as a .png as it was made for a different Chromium device. So you would have to manually go rename all the files to their correct extension for the files, but because it expects everything to be a .png it won't pack back properly. The second script, technically should unpack/pack as proper file extensions, but I never got it to work right as I have little to no knowledge of Python.
[Google Chromecast] chemicaldave:
The chromium source has a script,data_pack.py (which I can't link to since I'm a new user ATM) which can be used to pack and unpack .PAK files. The script posted above seems to be lifted from this source and modified to detect a few filetypes and write the unpacked files. But if you want to modify or add images and need to repack them, this script will help you figure it out. I'll work on adding and making some changes to the theme and give some instructions.
[Google Chromecast] hiep256:
how to mount usb drive

Haven't used linux in years. Thanks!
[Google Chromecast] tomg09:
Hey, want to do some poking around in the flashcast .bin file...how do I go about doing that? What is the file format, and is the image mountable in linux? Even better might be to extract files/folders from the image...what tool can I use to do that?
[Google Chromecast] tomg09:
Ok, so I'm doing some dinking around...I've looked into buildroot, and I think for the most part I understand what is going on. I also tried building from source, and it appears to have worked. So, from this poking around I have a few assumptions I've made and a few questions. Correct me if I'm wrong anywhere but.......

Basically, you've built a generic bootloader for the device using buildroot. This is not related at all to the stock CC bootloader (although maybe you borrowed a few drivers, etc). I would guess that the buildroot bootloader has just what you need to display a picture on the TV and do some basic file system operations, and I would also guess that the buildroot bootloader is missing a few features that the stock bootloader has - therefore, it wouldn't be possible to run a full-fledged ROM off of this bootloader. Am I right so far? If so, what is missing from the buildroot bootloader? Libraries? Binaries? No idea?

Also, to access something like USB storage, the buildroot bootloader is able to include the required /dev devices, whereas it wouldn't be possible to include this on CC's stock bootloader without the source. So, doing something like accessing a ROM from an external flash drive isn't feasible because of these limitations? Basically, all that is possible with the current bootloader (of course, the insecure one which allows for unsigned code to run) is to add a few binaries to the stock CC ROM (things like adb, dropbear, etc), maybe add some access to those binaries through Web GUI, etc.

Am I on the right track? Is there anything you would add/correct? Thanks for the help. I'm trying to understand :)
[Google Chromecast] ddggttff3:
Buildroot does not let us build a bootloader, it lets us build a custom linux distribution that runs on the chromecast. The reason it is unable to do anything "graphical" minus the static image is due to licensing of the marvell GPU driver the chromecast uses. It is currently closed source, so it is unable to be compiled. We can use the blob from the stock OS, but ATM there is no need, and this can cause licensing issues.

Also, you can still access /dev and such on the stock OS. The big thing is the stock OS has usb input disabled at a kernel level, so it doesn't mount or detect any devices plugged in when the OS is running. This is circumvented though if you build and use your own custom kernel. For the features Eureka-ROM adds to the stock OS, we add those by using googles open source cross compiler for the device to build supported binaries.
[Google Chromecast] tomg09:
Hmm...interesting. So, if I understand the booting process properly, upon power-on, a small bit of code called the bootloader is run, loading the kernel into memory (where, among other things, the graphics driver is located). From there, other components of the operating system are loaded on "top" of the kernel. So, it's not the bootloader that's rebuilt - but the kernel - with buildroot. Now, what sort of things would be possible if an open source alternative for the graphics driver were available (bear with me in the hypothetical), or even if one were to take the blob from the stock CC kernel? Turn CC into an android stick, complete with USB input device compatibility maybe?

Now on another note. I want to learn about cross-compiling. I am thinking of trying my hand at cross-compiling samba for the chromecast. Now if I understand the buildroot compiling process correctly, the right compiler for making chromecast-runnable binaries is compiled (or do you include it externally), and in theory, it should be possible to compile samba, right? I've been poking around the buildroot directory tree with the chromecast source superimposed over the top, and as of yet, I havent found the compiling binary (gcc, maybe?). I will look in a bit more depth. Once I find this, it should be as simple as specifying host and target architecture, putting the compiler for the CC in PATH, and compiling, right?

Thanks again for your help, and if you feel this isn't the appropriate place to post this, let me know.
[Google Chromecast] ddggttff3:
If we had a fully working open source graphics driver, lots could be accomplished. Full custom linux distributions could run x11 shells, we could have xbmc working with hardware decoding, and yes android would technically be possible if enough people wanted to put the time and effort into it. You can take the blob from the rom to do some of this, but things like hardware accelerated decoding will still not be possible due to the fact there is no documentation on how to use the blobs properly for things like that. (this is my understanding so I may be off on some small details, [MENTION=2789381]tchebb[/MENTION] can probably explain it more in depth.)

As for cross compiling, you just need to use googles prebuilt toolchain as the compile source.

Link: https://code.google.com/p/chromecast-mirrored-source/source/browse?repo=prebuilt

Mind if I ask why you want to compile samba? do you want to host media or files from a chromecast device? I actually have CIFS added to the eureka-kernel configs on our repo, so if you compile our kernel from source, you can mount samba shares on the chromecast device using the CLI.
[Google Chromecast] tomg09:
Cool. Thanks for the link. Basically, I'm just looking to learn about cross compiling for mobile devices. I figure samba seems easy enough. It was the first thing that came to mind. Any other ideas for something to cut my teeth on? Other binaries that would be well suited to CC, but are easy to compile?
[Google Chromecast] tomg09:
One more question...I've looked through the toolchain...the way it's set up is somewhat confusing. In the root directory of the toolchain: bin=gcc, g++, everything else I need to compile. What are the two folders entitled "arm-unknown-linux-gnueabi" and "target-arm-unknown-linux-gnueabi"? They seem to have relevant stuff (one has gcc, g++, etc except without the arm-unk... prefix, and other binaries which seem important). How do I use these/should I use these/why are they kept separate?

Thanks for the help.
[Google Chromecast] xredjokerx:
Cool! First :)
[Google Chromecast] ddggttff3:
Oh yeah, finally we can update kernels! Thanks for this, got some work to do now.
[Google Chromecast] cj_000:
tchebb, awesome work. Your flasher seems so much more flexible than what we put out (but hell, we did it in 3 days), and it's never a problem to help out. In fact, we LOVE it when someone actually picks up on what we did and makes it so much better.

Can't wait to give it a try, once I get some free time!

CJ
[Google Chromecast] stewwmann:
vulnerable bootloader ?

How do I know if I have A Chromecast with a vulnerable bootloader ?
[Google Chromecast] twist:
Looks super cool man, I am about to check it out and update my chromecasts now! Great work!!
[Google Chromecast] SOHKis:
just flashed over, working great. thanks so much!
[Google Chromecast] tchebb:
The initial software which the Chromecast shipped with, build 12072, had a vulnerable bootloader. In all following software versions (12840, 12940, and 13300), the vulnerability is patched and FlashCast can't be used. If your Chromecast has been allowed to access the internet, it will have updated itself and will not be vulnerable. If you have not set up your Chromecast and it still has the software from the factory, it may or may not be vulnerable, depending on when you bought it. To check, you can plug it in (but not set it up), and check its "Build" in the Chromecast app. Alternatively, you can simply try to boot FlashCast on it. If it's patched, nothing bad will happen; the USB drive will simply fail to boot.
[Google Chromecast] twist:
I just got 2 units this week from Amazon and they have not been updated from the factory and thus, vulnerable.
[Google Chromecast] raydekok:
damm, i have this 13300 version. and this will never happen or is there a way?
[Google Chromecast] gerald410:
Updated 3 Chromecasts, thanks for the excellent work!
[Google Chromecast] ddggttff3:
Currently there are no other known exploits.
[Google Chromecast] raydekok:
that is to bad. i'm hoping that it will not take to long.
[Google Chromecast] tvall:
[MENTION=4247376]cammykool[/MENTION] has been hoping that since Google forced 12840 upon him. He has given up hope.
[Google Chromecast] twist:
I just finished using FlashCast on 2 ChromeCasts and everything went smooth and great! I could really see FlashCast evolving into a full blown recovery for ChromeCast!

I am thoroughly impressed with FlashCast, amazing work man, well done!
[Google Chromecast] siratfus:
Hey guys, what's the purpose of this? Does it mean we can then use 3rd party developed apps? Apps that allow us to play local videos, etc.?
[Google Chromecast] stewwmann:
Thank You, Thank You very much....

Thanks for all the responses, I found a local Best Buy that has one, and I have put it on in store pickup for tomorrow. So if I do end up with one that has original fw, and am successful in installing flashcast, I can use the device as normal after that? no worries of it being locked back down? if we are not sure ,I just will continue using my updated one until then
[Google Chromecast] tvall:
If it comes with the original version, and you install an image that doesn't update, you can use it as normal and not worry about it being locked down.
[Google Chromecast] stewwmann:
cool

:good: *fingers crossed*
[Google Chromecast] thatdudebutch:
So if my Chromecast had been connected to my TV since release date I'm screwed huh
[Google Chromecast] tchebb:
It means you never attempted to root it. FlashCast is simply a way to mod the Chromecast; it won't root the device on its own. To root and disable updates, you need to flash a rooted system image, such as the one made by [MENTION=2212097]ddggttff3[/MENTION]. I apologize if the original post didn't make this clear enough. I've updated it so as to remove confusion in the future.
[Google Chromecast] JPHCCFC:
So now it's updated from what I have read there is no way back. Is there any future potential of being able to root?
[Google Chromecast] ddggttff3:
Not currently as the current root method relies on a exploit in the bootloader.