yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] donsveto:
Friends, can you help me to setup Call meter 3g widget, to show only minutes of outgoing calls. For example I have 500 free minutes per month, and I want Call meter to show me how many free minutes I spent. If Call meter can count from 500 to 0 it would be great. Thanks in advance
[General Questions and Answers] :
Here is one you can try out.

Call meter 3g

A Hero Can Be Anyone. GENERAL HELP THREAD
[General Questions and Answers] YMH:
Out of my depth.

Hi All. I know I'm out of my depth here. I downloaded Call Meter 3 G because I am having massive problems with overcharging by my pre paid mobile service provider and thought this app would help me keep tabs on them. I thought I would be able to understand the set up, but alas, I don't. I so admire you young people who are very savvy with technology. Unfortunately, I am an older woman (nearly 60) and I'm overwhelmed with trying to figure out how to set up the Call Meter 3 G app. Is there an idiots guide for setting up this app for people like me who just do not have the technical skills of younger people please?

I am also sorry to gate crash this thread with my question, but I didn't know how to start a new post either (!).

Thank you in advance for your understanding.
[7" Kindle Fire HD General] rhodri11:
Hi does anyone know of an app that is available for android that allows multiple apps to be active on the screen at the same time?
[Galaxy Tab Q&A, Help & Troubleshooting] pushkardua:
I Have Glaxy Tab P1000, installed cm10.1 in it..

i tried to restock my tab with odin and battery ran out in the middle of flashing...

now the state of tab is

it shows phone-computer link screen.. only when i am charging it MOstly It keeps on blinking

removing the charger would turn off the screen imidiately.. 1 in 50 times it stays and can be connected to computer but it wont get recognized by pc

tried to use one click unbrick and odin..( pc just dont show any device connected)

i just cant power on the tab without a charger.. no matter how many keys combinations and time durations.. :/

all i can see is the screen i am posting below
[Galaxy Tab Q&A, Help & Troubleshooting] nirvana97:
Try to boot to download mode (after reinstalling the drivers)

Reflash firmware you are looking for via kies or odin. I ADVISE to look for stock firmware, before flashing any custom roms.

Sent from my tab
[Galaxy Tab Q&A, Help & Troubleshooting] pushkardua:
I am not able to put it into download mode.. the most i can do is just wait for it to stop blinking and quickly put usb into pc... but any software niether oneclick unroot nor odin would show any sign of connection of new device!!
[Galaxy Tab Q&A, Help & Troubleshooting] geno93n0:
The drivers are probably not installed, or need to be reinstalled.

First, you should try using the zadig.exe driver installer that comes with the Heimdall bundle (just Heimdall, not OneClickUnbrick). Plug in the Tab, Click Options -> List All Devices, then click Samsung USB Composite Device and install the driver. That should most likely make it detectable by OneClickUnbrick.

If that doesn't work, try downloading the Samsung USB Driver for Mobile Phones or Samsung Kies to install the needed drivers.

Finally, you can try getting the drivers to install automatically by plugging in the Tab, then going to your Windows system tray, right-clicking Safely Remove Hardware and opening Devices and Printers. From there, you should try to find your Tab's device listing (it's usually Samsung USB Composite Device), right-click it, and select Remove Device. Then unplug the Tab and plug it in again.
[HTC Rezound] Monk12314:
Just sold my ReZound and got a DNA. Selling a bunch of stuff including a charging/syncing dock with extra 1500mHa battery and external battery charger, case able dock, a Sedio Active 2 piece case (Red), an OEM MHL cable and OEM wall plug, another wall plug (not OEM, came with the dock), and an Insten glossy screen protector.

If you're interested, i'll be putting all of this up on ebay later today in a bundle (probably for around 100 bucks). I'll update the link here as soon as it's up.

PM me if you're interested in anything in particular.

EDIT: Also have a 2750mHa extended battery with cover for sale.

EDIT 2: Have the link to eBay, Free shipping, everything for $125 (will accept for $115 if offer is made, special discount for fellow XDA'rs : http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=230973465537

EDIT 3: PRICE LOWERED TO $80.00
[Chromebooks] opieum:
DISCLAIMER: For advanced users ONLY!! Not responsible if your chromebook gets bricked, struck by lightning or eaten by a pack of wild boars or attacked by crab people! Anything you do strongly recommended it be done on an SDcard to ensure easy rollbacks and no destruction of firmware.

Here are the first downloads of the rootfs and ramdisk (both of which are needed for a working android install on chromebook) These are based on AOSP. More files will be coming as I am compiling. Basic instructions on how to set up uboot will be posted above as well as how to properly flash an SDcard. This assumes you know how to get your chromebook into dev-mode. Please note this is strictly for anyone with android system experience. The system may not even boot properly at this point. This is pre-pre-alpha at this point. There is alot of work to do before it even comes close to being usable. But if you get it working, please make a DD image (instructions above) and post it for all to use and work from. FOSS means sharing and sharing means caring. This will speed up the work needed to make this work for all of us.

aosp-ramdisk.img

https://mega.co.nz/#!sZgVmIQY!M9ANXXEJYAWR0TlRxV_mC3CdEXkTKC_Tgr1PdOD0Hxo

aosp-rootfs.tar.bz2

https://mega.co.nz/#!ZNgAFYqR!HkXcLxead3Zgm7lNcUzjb0YlfzEbbogTL5CnZDuUtIA

arndale-kernel

https://mega.co.nz/#!gIQXVLRC!U_L0WSutAXdGzdqhFrlzD1ij750Q8lTlKwHVoC28C14

arndale-ramdisk.img.ub

https://mega.co.nz/#!RB4XBAjS!JtNgciYJrLL_TDmjXjnZkTouPKwAhva26b7U9zvBYA0

arndale-rootfs.tar.bz2

https://mega.co.nz/#!xJwBVALa!QnwJRjQzhC218tcjMtKnimKZE2kn73sGs8XgeC75fDU
[Chromebooks] afrojoc:
I'm super excited that you're working on this Opieum. This would be absolute dream come true. I'd love to help out but I can't be a tester lol. After I get my next few paychecks I'd love to send a donation to you sir!
[Chromebooks] opieum:
Im still working on it. Its a bit tricker than I thought to get it working. Not impossible tho. I just lack the experience and knowledge to get this up and running. I figured I could do it over the weekend lol. Humbling experience. Once I have something working that is moderatly usable I figure I will take some donations to support other types of chromebooks, for now tho I will just do this cause I want to get android working on the samsung chromebook series 3.
[Chromebooks] moocow1452:
May want to wait for IO until after if Chrome and Android get close enough to jump from one to the other.

Also, I guess you could try and use the Cyanogen Mod port tool to try and get Android on it. It's what I used to try and get Ubuntu-Phone on my Nook. Nearly have it, but got the black screen of doom.
[Chromebooks] opieum:
Thanks moocow, I appreciate the advice. I had not considered the Cyanogen tool. I know google IO is right around the corner but I want to see if I can get it working. Part of it is as much a technical exercise to see if I can do it as much as it is just doing it.

Do you have a link for this porting tool? I was looking for one. If its just porting from the git I guess I can do that too. I was just wondering if there was a specific tool do this with. I was not aware there actually was a tool.
[Chromebooks] awacker89:
I'm so excited someone is trying to make this work! I'm no dev, but I'd love to help in anyway. Subbing now.
[Chromebooks] moocow1452:
http://wiki.cyanogenmod.org/w/Doc:_porting_intro

This might help also.

http://wiki.cyanogenmod.org/w/Development
[Chromebooks] vampirexhunter:
Amazing! I wish you the best of luck on this :)

I've seen some great development for the ARM Chromebook over on the Linux side, so anything is possible :)

Hope your efforts will be fruitful :)

Thanks!
[Chromebooks] musical_chairs:
I'm excited to see some effort being put into this!

I don't think you need to worry about flashing procedures just yet, and I certainly would forget about messing with uboot until way later in the game. It's pretty easy to get a dual-boot setup on the chromebook, getting the files in place is way easier than it is on a typical Android device because you can write them to an sdcard from inside ChromeOS, then reboot to the sdcard. We can worry about booting Android from the internal storage later, shouldn't be too hard. And to do anything with uboot, you're going to need to physically disassemble the chromebook and remove the write protect screw/sticker, IMO it would be best to avoid that.

Maybe we should start by adapting this procedure, but putting an Android filesystem and kernel on the sdcard instead of Linux?

http://blogs.arm.com/software-enablement/848-running-linux-on-the-series-3-chromebook/
[Chromebooks] opieum:
Thanks. I have been hitting wall after wall with u-boot so yea I am working on the dualboot method for now. That post is great! I had not seen it before. Bookmarked among many. Hopefully I can find the issues keeping me from making this work.
[Chromebooks] musical_chairs:
The first obstacle I am seeing is that while ChromeOS uses a pretty standard Linux kernel and no ramdisk (and that is what uboot will be looking for), Android uses a kernel and ramdisk on a /boot partition. I don't know enough about Android to know if it's possible to boot it with a different configuration, but I've got a hunch that if we're going to get Android to boot on this thing, we're going to need to do it a lot more like the Android x86 people do it than like a typical Android ROM.

Two exercises that I think will be very helpful here:

1. Install a Linux (Ubuntu, Debian, Arch, Fedora, whatever) on the sdcard of a chromebook without using a script like chrubuntu

2. Install Android x86 on a 'normal' computer.

I have almost done the first (I cheated and ended up using a script to install Ubuntu), the second I may eventually do if I can find the time.

...and like I said, I think the best approach here is going to be a x86 style Android installation, but with an arm build.

---------- Post added at 01:42 PM ---------- Previous post was at 01:27 PM ----------

...or maybe this is what we need - chainload uboot:

https://plus.google.com/117557107585466185396/posts/hVWc5EE9EK6

---------- Post added at 02:09 PM ---------- Previous post was at 01:42 PM ----------

Okay, this looks to be the official documentation on using nv-U-boot (chainloading uboot):

http://www.chromium.org/chromium-os...using-nv-u-boot-on-the-samsung-arm-chromebook
[Chromebooks] musical_chairs:
Upon further reading, I believe that this is the correct method:

1. Pack nv-U-boot as a signed kernel and dd it to a chromeos kernel partition.

2. nv-U-boot then boots Android using a typical Android boot command.

For the time being, I'm pretty sure it will be better to keep nv-U-boot and all the Android partitions on an sdcard, as it is no harder to boot from there than from the eMMc, and it's a whole lot safer to test stuff this way. Once we've got it working, we can repartition the eMMc and install everything there so it's faster and all that good stuff.

Bear in mind this is pretty much just academic at this point, I tried to chainload nv-U-boot but haven't actually gotten it to work. I'm pretty comfortable mucking around in Linux systems, but this uboot stuff is all new to me.

What I've done so far:

1. Set up partitions on my sdcard (including two kernel partitons) as per the first link I posted.

2. Got a working Lubuntu installation on the sdcard (cheated and used a chrubuntu-derived script).

3. Got a working Crouton (chrooted) Lubuntu setup on the internal storage (doesn't really apply here, though it comes in handy for some of the tools needed for manipulating files and stuff)

4. Tried the nv-U-boot image from opensuse:

http://download.opensuse.org/repositories/openSUSE:/12.2:/ARM:/Contrib:/Chromebook/standard/armv7hl/

5. Tried the nv-U-boot image from the Chromium Projects:

http://commondatastorage.googleapis.com/chromeos-localmirror/distfiles/nv_uboot-snow.kpart.bz2

In both cases, the process is the same. Pack nv-U-boot as a signed kernel, something like this (both commands are run in a shell from within ChromeOS, in dev mode):

vbutil_kernel --pack newkernel --keyblock /usr/share/vboot/devkeys/kernel.keyblock --version 1 --signprivate /usr/share/vboot/devkeys/kernel_data_key.vbprivk --vmlinuz u-boot.img --arch arm

write it to the sdcard with dd, something like this (remember you can hose almost anything with dd if you point it at the wrong place, so use with care:

sudo dd if=newkernel of=/dev/mmcblk1p2

(this writes it to partiton 2 of my sdcard, partition 1 is my good Ubuntu kernel.)

I haven't seen nv-U-boot yet but I think I'm close.
[Chromebooks] opieum:
Yea the u-boot stuff is real new to me. I have no issues either with linux its the bootloader stuff with android I am struggling with. I'm going to look at the arndale instructions as it uses similar hardware on how to load it from SDcard. The documentation there seems to show how to load the system. I already built and compiled the code from arndale seeing as it uses the exact specs needed. Since we have the ability to boot from SDcard on a chromebook this should be easily doable. The build will be the hard part. I am going to see what i can do with that method, I'm adapting from various sources. Ideally if I can come up with a simple image that can just be DDed over to a 32GB SD card that would be best for all to start and test with until a much easier method can be adapted. I had read elsewhere that the android method had been tried using the linux methods and it did not work. Hence why I havent looked as deeply into it. But I think at this point it seems like looking at this with a mixed methods might be the better approach. I'll post my results tomorrow as I am trying this out now.

UPDATE: I got some promising news. I am following this guide I have built android according to those instructions. http://www.arndaleboard.org/wiki/index.php/WiKi#How_to_Flash_a_Device (ignore the dipswitch references here as we got the ctrl-U option to boot and devmode)

The uboot install part is automated via a script which saves some time. Easy enough to break down the script to see how its done manually. The build will have 4.1.1 That said arndale provides pretty much all the tools to do this simpler. I think if we get this working then all we need to do is further automate the process OR provide an image with a simple script to image an SDcard with. Additionally I suspect (I have not confirmed) that the wifi and other components on the arndale are also the same on the chromebook.
[Chromebooks] musical_chairs:
Hmm, I wonder if the uboot from the arndale board will work on the chromebook? The chromebook's uboot doesn't have fastboot, and there's no way to interrupt it either (as in, hold down a key to access the uboot menu). BUT, if we put the arndale's uboot on the sdcard, as in, this:

http://www.arndaleboard.org/wiki/index.php/WiKi#Prepared_micro_SD.2FMMC_for_ARNDALE_bootable.

...that looks rather promising.
[Chromebooks] opieum:
Yea that was the idea and portion I was looking at. I'm trying it out now to see if this will work.
[Chromebooks] moocow1452:
I thought something similar might be done with Plop, the most awesomest boot loader in the world when Chrubuntu was first finding it's feet. Booting into a bootloader might be the answer for not just Android, but Windows 7.
[Chromebooks] opieum:
But this is booting on ARM. So Win7 would not work here as there is no ARM capable version. The work now is being done for the Samsung Chromebook ARM version (series 3) which would also work on the Acer version that is also ARM based as well.
[Chromebooks] moocow1452:
Nuh uh, Acer C7 is x86 based. RT can play on ARM, but a Chrome bootloader might be worth it.
[Chromebooks] opieum:
You are correct sir on the Acer being intel. That being said. This project is to get android on the samsung chromebook (series 3) which is an arm EXYNOS 5xxx series CPU. The methods developed here would also likley apply to any other arm based books on the market.
[Chromebooks] musical_chairs:
Here's an interesting read:

http://archlinuxarm.org/forum/viewtopic.php?f=27&t=4016&p=29341&hilit=nv+u+boot#p29341

I especially like the part later in the thread where one guy bricks his chromebook by flashing a custom uboot, and recovers by soldering around on the mainboard.

That thread has some good info though on actually using nv-u-boot though.
[Chromebooks] opieum:
THat looks great! I am actually trying a build based on the arndale instructions and just going to boot from SDcard.I keep running into issues compiling. I am working past the issues since that seems to be the area I am having the most difficulty. I am using ubuntu 10.04 as is recommended to do the build. I might look elsewhere for uboot building and android building since arndale seems to be poorly documented and supported.
[Chromebooks] musical_chairs:
Well I finally made it to the nv-u-boot command prompt (and managed to freak out ChromeOS enough to cause it to reset itself and wipe all local data, but that's a minor detail). I wasn't making it to the nv-u-boot prompt before because I misunderstood the priority settings of the ChromeOS kernel partitions (higher number means "boot from me first" - oops). I finally 'got it' while reading the instructions and the script downloaded from this page: https://www.berrange.com/posts/2013...fedora-18-arm-on-a-samsung-google-chromebook/

Anyway, you can boot to the nv-u-boot command prompt either from an SD card or by overwriting one of the kernel partitions on the emmc. I chose to use the SD card for now, for safety reasons. nv-u-boot (google's version at least) needs the /boot partition to be ext2, so I need to do some repartitioning to my sdcard before I can boot my Ubuntu again. But for now, how to get the nv-u-boot command prompt:

(This assumes your Chromebook is in developer mode and has dev_boot_usb enabled.)

1. Partition your SD card using parted vaguely as described on this page: (On a Linux machine with an SD card slot)

http://blogs.arm.com/software-enablement/848-running-linux-on-the-series-3-chromebook/

We need at least one ChromeOS kernel partition, and as far as I can tell, GParted does not know about those, so we need to create the kernel partition from the command line. We will also need an ext2 partition for /boot in order to use nv-u-boot, this is not part of the partitioning guide but you can do it with GParted later.

2. Download nv-u-boot for 'snow' from here: (On the Chromebook now)

http://commondatastorage.googleapis.com/chromeos-localmirror/distfiles/nv_uboot-snow.kpart.bz2

3. Hit Ctrl+Alt+T for a terminal and enter:

shell
cd ~/Downloads

4. Extract the uboot image:

bzip2 -d nv_uboot-snow.kpart.bz2

5. Write nv-u-boot to the SD card:

sudo dd if=nv_uboot-snow.kpart of=/dev/mmcblk1p1

Replace 'p1' with the approproate partition number if you are not writing to the first partitition of the sdcard.

6. Set partition flags:

sudo cgpt add -i 1 -S 1 -T 5 -P 15 /dev/mmcblk1

(where -i is the partition number, -T is the number of tries, and -P is the boot priority, higher number boots first.)

Now, when you reboot and hit Ctrl+U, the system will attempt to boot with nv-U-boot. Immediatly hold down the spacebar to interrupt uboot and be given toe command prompt (warning - if you don't hit any keys, uboot gets confused, ChromeOS gets scared, and next thing you know, it has reset itself and you'll need to re-enable dev mode. Believe me, I know...)

From the uboot command prompt, you can make changes, save them, and boot in lots of interesting and creative ways. Now for figuring out uboot commands...
[Chromebooks] opieum:
Well u-boot commands are on http://git.denx.de/?p=u-boot.git;a=blob_plain;f=README;hb=HEAD. I have been building android. I have been hitting wall after wall with the arndale builds and they apparently have poor support and documentation. So I am rebuilding using AOSP or CyanogenMod since they now support the samsung exynos5 CPU. I have been working on the SDcard as you have as well. I haven't made much progress this week due to personal commitments but I plan on spending some time this weekend and hope to have results. The post is useful for the bootloader. However I did read (trying to find the original post) that there is some formatting issue with the rootfs that would keep android from booting. However I think having the u-boot working would be a great first start. We just have to figure out where to go from there.
[Chromebooks] musical_chairs:
Thanks for the link. For now I'll focus on getting more familiar with uboot, get Ubuntu booting from it, etc. I'm not going to be attempting any android builds at this point but I'd love to try booting one of your builds once you get one to where you are comfortable sharing it. Keep up the good work!

Edit / update: I did get Ubuntu to boot from uboot on the sdcard. Copying what the Arch guys did:

http://archlinuxarm.org/forum/viewtopic.php?f=27&t=4016&hilit=protect&start=80#p29341

Booted by passing the following commands to uboot:

setenv bootargs root=/dev/mmcblk1p2 rootwait rw
mmc dev 1
ext2load mmc 1:1 42000000 vmlinuz-3.4.0-5-chromebook
bootm 42000000

(posted here for my own records)

A little more tweaking uboot, then I think I'll switch gears and install android-x86 on my big laptop to see what I can learn there. Fun stuff!
[Chromebooks] opieum:
I'm attempting to get a build going today based on the arndale stable build once I convert the cyanogenmod to a rootfs I will use that. I got uboot going I just need to ensure it works.

I am getting close if I have a working image I will upload it for SDcard use. Its a starting point for ROM modders to work with on the chromebook and might convince google to use android as a desktop OS alternative

http://forum.insignal.co.kr/viewtopic.php?f=6&t=62
[Chromebooks] vampirexhunter:
I'm excited to see this happen :D

Keep up the good work!
[Chromebooks] awacker89:
GOOD NEWS! Android for Chromebook is... near?
[Chromebooks] moocow1452:
Would totally be in there with you guys, but my sister would kill me if I touched her laptop.
[Chromebooks] vampirexhunter:
:D Would she still kill you if you told her Android OS might be coming to the Chromebook soon? XD
[Chromebooks] musical_chairs:
Well I got sidetracked and have been trying to build my own kernels for Ubuntu on the Chromebook. I still haven't gotten around to digging into how Android builds and packs things like kernels, but for the Chromebook, the kernel image file needs to be packed differently than for the Linuxes I am used to. To quote Olof Johansson, a ChromeOS dev:

It seems the kernel needs to be packed like this before uboot can recognize it. So far I've gotten uboot to load the kernel I built, but it doesn't boot yet. But I have a feeling this information could come in very handy in trying to get an Android kernel to boot. Here's the full post:

https://plus.google.com/109993695638569781190/posts/34PYU79eUqP
[Chromebooks] skim0322:
Maybe you can contact cyanogen mod team. They have knowledge on Kernels and they might be interested working on chromebooks.
[Chromebooks] opieum:
musical can you post your process (howto) for having setup u-boot on the sdcard? I would like to try that method. I think I actually have the other part with android installed but the uboot part is where I am sure I am messing up. Since the u-boot part you have already works, maybe then we can post notes here to get that working. If I have success on my end then we can put our heads together and get this working. Least get a working dev build for rom makers to play with and tweak and enhance.

I think I might have the trick for getting the kernel on there and working.

EDIT: NVM saw your post detailing the steps. I am trying those out.