yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Q&A, Help & Troubleshooting] bewA:
Just to update you.

Flashed the second file using ODIN for the PDA.

Swapped a fully charged Samsung battery with someone in the office plugged into my work pc which already had Samsung drivers (for my GN).

and now all working!!

Didn't loose any data!

Thank you so much MistahBungle!!
[Galaxy S II Q&A, Help & Troubleshooting] MistahBungle:
No worries guv. Glad you got it sorted & also glad you didn't lose any data as well ;)
[Galaxy S II Q&A, Help & Troubleshooting] bewA:
You've saved me from divorce! :-P

Now i just need to look at doing ICS... after i've fully charged the phone! :D
[Galaxy S II Q&A, Help & Troubleshooting] MistahBungle:
Hahaha :) Hmmmm. Is that a good or bad thing tho ? :D

So far as ICS is concerned, I've tried Miui V4 which is ****e & needs a lot of work. I tried CM9 about two weeks ago & it was fantastic considering how little they've had to work with, and I'm just about to try the 20 March build of CM9 now. Looking at the discussion thread, they've made a fair bit of progress since I tried it previously.

Obviously there are other ICS variants out there & quite a few stock ICS roms floating around. As always, do your homework/research first, make sure you fully understand whatever it is you're wanting to do to your phone, always check downloads (large ones anyways) to ensure they're not corrupt & you should be fine ;)
[Galaxy S II Q&A, Help & Troubleshooting] bewA:
Well i'll be going to a Stock ICS but as far as doing it with Kies that going in the digital bin (to put it politely)!

As the phone is an unbranded one (not fixed to a network) from what i've read there isn't a UK unbranded one yet, i was toying with the idea of doing I9100XXLPQ but i might let the dust settle depending on what i read throughout the day :)
[Samsung Galaxy Nexus] xko:
i want to sell my nexus where should i post the sell

i live in france and i have like new looking nexus

thx for help
[Samsung Galaxy Nexus] bsweetness:
If you want to try to sell it here, you should post it in the Wanting to Sell section of the Marketplace forum on the site.
[Eee Pad Transformer Themes and Apps] megacoolrock:
now introducing a google play theme :) Black and Cyan.

MAKE SURE YOU MAKE A NANDROID BACKUP BEFORE YOU FLASH OTHERWISE YOU MAY NOT BE ABLE TO REVERT

Step 1. download (links at bottom of post)

Step 2. Move to SD Card.

Step 3. Flash via CWM

Step 4. Reboot. This will change the icon and the name to black market.

Download from here

If you dont want the icon included, download and flash this

be sure to leave thanks :)

Credits: camblue, for the awesome theme, Korumera, for the file server.
[Eee Pad Transformer Themes and Apps] philburkhardt:
I really want to use this, but I don't want the icon & app name changed to "Black Market". Is there any way we could get this without the name and icon change?
[Eee Pad Transformer Themes and Apps] Korumera:
Indeed,

Would like to see a version which keeps the name as it is :) Nice job btw :D
[Eee Pad Transformer Themes and Apps] megacoolrock:
I will work on this, give me about an hour or two

done, flash the v2 and tell me if it works, i dont have my transformer to test it right now, i will edit this when i do
[Eee Pad Transformer Themes and Apps] Danzano:
Love it but can't read comments in the market so maybe some little adjustments ??
[Eee Pad Transformer Themes and Apps] megacoolrock:
have you tried rebooting?
[Eee Pad Transformer Themes and Apps] Danzano:
Yeah ofcourse also cleared cache dalvik cache etc

Its fine reading the comments on the app page but once you open the comments section you can't see the writing

Its just a couple little bits that need tweaking but awesome work so far :D
[Eee Pad Transformer Themes and Apps] megacoolrock:
im currently working out some bugs, when its ready i will post it
[Eee Pad Transformer Themes and Apps] Danzano:
Awesome ill be looking forward to it
[Barnes & Noble Nook Tablet] chuckweiss2:
I think I found a problem not in this forum yet!

A few weeks ago, I rooted, installed CWM and CM7, and started enjoying my nook. After about a week of that, it started to crash and shut off randomly (at least randomly as far as I can tell). I went into CWM and tried to install the rom again and start from scratch: factory reset, install rom from sd. The install went quickly and wasn't at all verbose, it just said "Installing" and then "Install Complete" a few seconds later. When I rebooted, nothing had changed. And every subsequent attempt at changing the rom yielded no changes. If I uninstalled or installed any apps or changed any settings, when I rebooted it went right back to the way it was.

What I'd like to try is Adam Outler's Ubuntu Recovery, but I can't manage to boot from the sd card. I've spent the past couple weeks searching the forums in my spare time for a solution, but can't find one that works. I can adb into the nook though, so I've been trying to figure out how to use that.

So, first question: any ideas on what I might have done that would stop it from booting from the sd?

Next: if that doesn't work, can I fix this with adb somehow? (I tried CelticWebSolutions' parted fix, but no booting from sd card makes it tough)

Any chance someone else has a similar tough-to-describe problem?
[Barnes & Noble Nook Tablet] Solar.Plexus:
+1 for the thread title.

Many people aren't able to boot from SD card UNLESS their NT is plugged in to the charger. Give that a shot.

As for the shutting off problem, I'm not sure. I get random reboots every once in a while. I just feel like it's expected in an alpha ROM.

Just be sure that when you flash a new ROM, you always:

-clear Dalvik cache

-install zip from SD

-factory reset

-reboot system
[Barnes & Noble Nook Tablet] chuckweiss2:
After I realized that the nook kept booting to the same state no matter how I tried to kill it I couldn't avoid the reference.

The problem with my random reboots is that I have maybe 2 minutes from when it boots to when it inevitably shuts off.

And yeah, I booted it by shutting it off and plugging it in, as well as just plain turning it on and also turning it on while holding the n.

Thanks for the reply.

Oh, and yeah, I cleared the Davlik as well the second reinstall attempt, I didn't give it enough thought the first time.
[Barnes & Noble Nook Tablet] lavero.burgos:
Today i had a weird issue as well with CM7, i was on MIUI and flashed back to CM7 to continue with a project and i ended up flashing 3 times but could not pass the Team B+ screenshoot to the bootanimation, it got stuck into dark screen. So by accident i formatted my sdcard and that solved the problem. So next time try formatting your sdcard first for those kind of "weird" issues.

~ Veronica
[Barnes & Noble Nook Tablet] chuckweiss2:
What is it you did to format your sd card? If it works, maybe that's the Rita to my nook Phil.
[Barnes & Noble Nook Tablet] lavero.burgos:
Yes i formatted while in clockworkmod but after that i formatted again with SDFormatter as i always format my sdcards with that program on Windows.

~ Veronica
[Barnes & Noble Nook Tablet] chuckweiss2:
So you formatted the external sd card, not the internal partition that the nook calls an sd card?
[Barnes & Noble Nook Tablet] lavero.burgos:
yes external sdcard and the nook does not call it sd card only, there is internal sdcard and external sdcard:

Internal sdcard >> /mnt/media

External sdcard >> /mnt/sdcard

~ Veronica
[Barnes & Noble Nook Tablet] chuckweiss2:
Gotcha, thanks. I don't think formatting the sdcard would be too helpful to me, my problems are definitely internal
[Droid 2 General] johnny2505:
Hello all. I want to say this site has helped me 100 times over and the guides to get stuff like a DROID 2 on MetroPCS is awesome. I did the ESN add and all the MMS and WEB support to EDGE speeds, but just recently saw the new PRL lists and rocking 3G speeds (450-690kbps down) here in Stockton, CA. So another big thank you to the tutorials here..

My only issue, and its a small one but annoying. I tried searching here and google to no avail..

When I send a standard 1 part text it goes through no problem. But if my text goes over and my DROID tells me it will be 2 messages I get a delivery fail. I thought maybe the phone would auto split the message but maybe it is handled different by MetroPCS? I have friends with stock Metro phones that can do 2 even 3 part long SMS texts no problem. Is there a simple fix or something I just have to live with? It's no big deal as everything else works, just sucks to stop yourself mid sentence then continue on.

Thank you so much for this forum!

The Noob :)
[HTC EVO 3D] chamucoliz:
Any one knows if there is a good battery door for the htc evo 3d seidio 4000mah?

my battery door broke from the bottom, so i would like to get another but not from seidio, so i wanted to know if anyone knows or tried other brands of battery door that work, also any crazy mod may help

Thank You
[HTC EVO 3D] Will32:
4000 mah!? Wow, that thing must be ginormous. I have a 3000mah and its huge.

Sorry, can't answer your question.

sent from my downgraded EVO 3d.
[Droid Incredible Android Development] Tribulattifather:
Original APP folder from most current leak::

App Folder

Original Framework folder from most current leak::

Framework Folder

Tiny's One_V Port so far:

(Boots to the Bootanimation.)

Rom Update Utility:

RUU_PRIMO_U_ICS_40A_HTCCN_CHS_1.68.1400.2_Radio_20 .67.30.0831U_3831.15.00.28_M_release_254948_signed .exe

Run the RUU

Wait a bit until the Rom Update Utility lets you press 'Next.'

Don't press 'Next' though,

Go to your Start Menu > Run > type in

%temp%

Now sort the folder by 'Date.'

The first folder will be the folder that has a 'rom.zip' inside of it inside of the 2nd folder.

HTC_One_V_Ramdisk:

V_Ramdisk Download
[Droid Incredible Android Development] Pons:
Porting a ROM is one thing, porting a kernel is something else entirely.

If you've never done a port, look up wildstang83 porting guide. It'll at least point you in the right direction.
[Droid Incredible Android Development] Hero:
I'd like to help you out with this project if you need it. There is a port of this on the DHD forums so maybe we can learn something from it:

http://xdaforums.com/showthread.php?t=1545595
[Droid Incredible Android Development] Tribulattifather:
I thought of that too. But since the DInc is a 'QSD' (1000Mhz Qualcomm Snapdragon) and the Desire HD and the Desire S are 'MSM' (Mobile Station) We can't use their ports to help us :/

Being that the DInc is a qsd8k (8650 to be exact) we'll need to keep an eye out for ports with the same processor.. Oh man I wish the old Desire could get a port of this, lol. We'd have no problem at all..
[Droid Incredible Android Development] nitsuj17:
kernel source wont help you at all for the 3.xx kernel from other htc phones, so dont bother

i ported sense 4 to the inc 2 (admittedly a lot easier cuz its msm7x30 which most of the ports are) and will give it a shot on my og inc time permitting

see inc2 port here: http://xdaforums.com/showthread.php?t=1553357

the hacked .35 kernels from your ics aosp roms *should* be good (only need zimage) and then we d have to hack up the ramdisk from the htc one to work well enough to boot
[Droid Incredible Android Development] Tribulattifather:
When you say

do you mean we'd need the zimage from HTC One V?

Edit: Updated first post with the zImage and Ramdisk that I extracted from the One V RUU.
[Droid Incredible Android Development] nitsuj17:
no, you need the zimage from one of the ics aosp inc roms and the extracted ramdisk from the htc one v
[Droid Incredible Android Development] Tribulattifather:
Okay. Thank you for clarifying for me.

I'm getting down to business now ^>^
[Droid Incredible Android Development] orochi9999:
can u tell the link to wildstang83 porting guide thread?
[Droid Incredible Android Development] Pons:
★wildstang83's Guide For Basic Porting★
[Droid Incredible Android Development] orochi9999:
thank u!:D:D:D:D
[Droid Incredible Android Development] 2012oasis:
I'd like to help if needed, have a lot of experience with ics on Og EVO don't have a inc but been working on sense4.0 Og port and kernel for a bit now..(same chipset) let me know.
[Droid Incredible Android Development] Tribulattifather:
Well, we're at a standpoint of figuring out which files need to be added/edited from the One_v ramdisk so we can make a working kernel.
[Droid Incredible Android Development] tiny4579:
can you get a logcat or pm me a ROM link? I'd like to look. No guarantees of success. Sadly the sense devs that could figure it out I think have left the incredible.

Also a working ramdisk still doesn't mean the kernel is good. The kernel may need some changes.
[Droid Incredible Android Development] Tribulattifather:
I'll upload the ROM port I just made a few days back. It has most of what I thought might work..
[Droid Incredible Android Development] tiny4579:
I'd like to try tonight if I can. I'm hoping that an HWA enabled AOSP ICS kernel works with it.
[Droid Incredible Android Development] Tribulattifather:
I'm uploading now. Been busy all day.

I think the only way that an HWA enabled AOSP ICS kernel will work is if we figure out which parts of the ramdisk we'll need to add to it.

I have the Ramdisk extracted and uploaded on the OP if you need it.

Edit: Upload at 38% - I have a terrible connection speed for upload bandwith, which is at 49Kb/s..
[Droid Incredible Android Development] withbloodskies:
Ahh! Excited.. :)
[Droid Incredible Android Development] tiny4579:
I'm actually stabbing in the dark as much as you. Never messed much with roms. I'm more of a troubleshooter rather than a rom/kernel chef. I find tweaks and adapt for my kernels. But I noticed there's no init.inc.rc in that ramdisk. Other than that my mind's dead so I'll have to look tomorrow/this weekend.
[Droid Incredible Android Development] Tribulattifather:
I apologize for the delay in posting the port link. You'll have to forgive my internet. But, I assure you that the download is as fast as I can get it with my own server that I use.

EDIT: Port is on the next page --->

Just to make sure that everyone is on the same page - This port is NOT a working port.

It will flash to the DInc and it will install properly but it does not boot. And it is obvious why, lol, because we are still missing the piece to the puzzle to make a working kernel.

I hope that this will give you what you need to get this project I started the thrust in the right direction.

As for my method thus far, I am using the zImage from and AOSP ICS port with Ramdisk parts from the One_V.

Post Script - Today is my third year anniversary being apart of XDA. And I can only hope many more years to come.

CHEERS ALL!
[Droid Incredible Android Development] tiny4579:
I wouldn't worry about the ext4 bit honestly. The /data partition mounts, so we're good.

However scanned the logcat and my suggestion is try swapping out the /system/lib/hw folder with the one from evervolv p12. That is, remove the folder and replace the entire folder so we don't have stray libs. Make sure you can revert if needed. I see a lot of hw files in the logcat error dumps.
[Droid Incredible Android Development] Hero:
I'll try that tomorrow when I get the chance. I just tried switching over only the audio.primary.default.so from p12 in the hw folder to see if it made a difference and it removed the error that was associated with it.
[Droid Incredible Android Development] Tribulattifather:
Could you, by any chance, pm me your port so far for 3.6.

I'm back now and can help with the sense 3.6.

As a mod, I suggest we create a new thread or I can turn this thread into the sense 3.6 dev thread.. Which would you all want me to do.
[Droid Incredible Android Development] Hero:
I'd say we make a new thread so we dont get confused with what info belongs to what port. I'll PM you the port when i get the chance, most likely after 4pm pst.
[Droid Incredible Android Development] Tribulattifather:
Okay. I'll gather up all the data for sense 3.6 like i did for 4.0 and make another thread after your upload. Thank you very much.
[Droid Incredible Android Development] jioleight:
is the thread gonna be on the development section or on a diff section? cause id like to know ur progress. :)
[Droid Incredible Android Development] Tribulattifather:
Sorry, haven't been at the computer desk at home for a few days. Not sure if i'll get it up this weekend. I'll try to aim for Tuesday - my day off and pay day ;) -
[Droid Incredible Android Development] jioleight:
as long as its worth the wait. im fine with it. :D
[Droid Incredible Android Development] withbloodskies:
Well, since 4.0 seems like a long shot I'm kinda curious on the development for 3.6.

Any new news or we still trying to boot that bad boy?
[Droid Incredible Android Development] Hero:
We're still trying to boot it. In all honesty, Sense 4.0 and 3.6 are probably the same difficulty, but we still haven't given up lol.

DEV ONLY:

I think one of the reasons we aren't seeing a boot is because the ramdisk isn't correctly configured. The errors we are getting are attributed to audio, which I don't think would have an effect on whether the ROM boots. I believe we are going to have to modify everything after bootclasspath in the init.rc in the ZS/Primo V ramdisk to match that of our ROMs.
[Droid Incredible Android Development] withbloodskies:
Maybe Newt or Joelz can help you two?

I wouldn't think 3.6 would be that difficult, I honestly don't even know what devices it was released for or on.

I just assumed it was a slightly more different from 3.5. I know 4.0 is ultimately different but 3.6 did look to different.

Well I'm glad you guys are still trying on your free time, thanks.
[Droid Incredible Android Development] Hero:
We've already asked JoelZ for help, but unfortunately we weren't able to solve the boot issue. I think our main problem is that Sense 3.6 and 4.0 are both based on ICS, but the DInc does not have an official ICS release, which makes it difficult to port. Sense 3.5 and lower is GB and we have a GB OTA so in that respect, those are easier to port.
[Droid Incredible Android Development] withbloodskies:
Ahh, that's makes more sense. Shame, the way I think of iCS on our device is "I know its irrelevant" like minecraft, spec wise.

Recently it was ported to the Xbox 360 which it was never suppose to be ported because it was said it wouldn't work.

It runs similar to PC, now why does this remind me of ics on our device?

Because the Xbox is old and outdated and running something requiring a lot of resources. What is our device at the moment still trying to run? ICS, while for the most part it is seemingly stable I believe there could have been a custom port for our phone, not through xda but through the manufacturers.

That's how I think of it, I wish they didn't throw new phones into the market constantly. I wished the manufacturers "if that right" would support phones that might be older. Its a shame most phones don't even last at least a year before better new ones come out. Maybe even months..

Anyway.. my rambling lol, I thought that would make sense.

That's how I think of it.
[Droid Incredible Android Development] z3rods:
There's a little bit of a difference there though. The 360, while it is a little old and outdated now, still packs quite a bit of power. It has a triple-core 3.2 GHz CPU with 512MB of GDDR3 RAM and a custom designed ATI Xenos GPU that's pretty capable. Our Inc on the other hand... well, it's antiquated. :(
[Droid Incredible Android Development] Hero:
Does anyone have the faintest idea what this error is or how to fix it? I'm pretty sure it has to do with the init.rc file, but don't really know where go from here atm...

D/dalvikvm( 83): Unable to stat classpath element '/system/framework/core.jar'
D/dalvikvm( 83): Unable to stat classpath element '/system/framework/core-junit.jar'
D/dalvikvm( 83): Unable to stat classpath element '/system/framework/bouncycastle.jar'
D/dalvikvm( 83): Unable to stat classpath element '/system/framework/ext.jar'
D/dalvikvm( 83): Unable to stat classpath element '/system/framework/framework.jar'
D/dalvikvm( 83): Unable to stat classpath element '/system/framework/widget.jar'
D/dalvikvm( 83): Unable to stat classpath element '/system/framework/android.policy.jar'
D/dalvikvm( 83): Unable to stat classpath element '/system/framework/services.jar'
D/dalvikvm( 83): Unable to stat classpath element '/system/framework/apache-xml.jar'
D/dalvikvm( 83): Unable to stat classpath element '/system/framework/HTCDev.jar'
D/dalvikvm( 83): Unable to stat classpath element '/system/framework/HTCExtension.jar'
D/dalvikvm( 83): Unable to stat classpath element '/system/framework/com.htc.framework.jar'
D/dalvikvm( 83): Unable to stat classpath element '/system/framework/filterfw.jar'
D/dalvikvm( 83): Unable to stat classpath element '/system/framework/com.htc.android.bluetooth.jar'
D/dalvikvm( 83): Unable to stat classpath element '/system/framework/wimax.jar'
D/dalvikvm( 83): Unable to stat classpath element '/system/framework/com.orange.authentication.simcard.jar'
E/dalvikvm( 83): No valid entries found in bootclasspath '/system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/widget.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/HTCDev.jar:/system/framework/HTCExtension.jar:/system/framework/com.htc.framework.jar:/system/framework/filterfw.jar:/system/framework/com.htc.android.bluetooth.jar:/system/framework/wimax.jar:/system/framework/com.orange.authentication.simcard.jar'
E/dalvikvm( 83): VM aborting

Everything else seems to work. No lib errors, bin errors (mediaserver, servicemanager), etc. Hardware files load fine as do the EGL files.
[Droid Incredible Android Development] LENINred:
just the link. http://xdaforums.com/showthread.php?p=26082906&posted=1#post26082906 and just answer on your possible question. hi ready and uploading it now.
[Droid Incredible Android Development] amit.shah:
He said it.. He'll do it.. And now finally, Shaky's ROM for Desire with Ice-Cream Sandwich 4.0.3 Sense 4.0 is up here.. http://xdaforums.com/showthread.php?t=1653537
[Droid Incredible Android Development] withbloodskies:
Confused.. I know we use a lot of the desire ports stuff.. but is it possible now we could get this to boot correctly now?

Anyway glad to see he got it to boot, makes me want a desire :) lol
[Droid Incredible Android Development] Hero:
I just sent him a PM to see if I could use his port. I'll work on it later though guys...facing some personal issues
[Droid Incredible Android Development] withbloodskies:
Hey, personal life > Dev work buddy

Hope it works out!
[Droid Incredible Android Development] tiny4579:
It should be much easier now that Desire is working since both Inc and desire are the same SoC. The only thing different may be the kernel, ramdisk, and a few libs (just guessing about that though).

Pure since we're working as a team make sure he knows we'd both be working on it.
[Droid Incredible Android Development] Hero:
Yeah for sure. The one thing that is confusing me a bit is that Shaky's port only works with a specific hboot for the Desire so we are gonna have to look into it. Also an sd-ext partition seems necessary.
[Droid Incredible Android Development] tiny4579:
Not sure if that's the case with the Incredible and no a sd-ext partition shouldn't be necessary as we have everything symlinked so it should fit. Maybe check with shaky on both if he responds. Since it's released though in early stages right now he may have more time to help.
[Droid Incredible Android Development] Newt:
I tell you what guys ill boot this thing for you but you guys will have to support it... I have way to much going on right now to support it, but I will boot it if you want?
[Droid Incredible Android Development] tiny4579:
That works for us. Just remember the dev requested we ask permission to use it first via PM.
[Droid Incredible Android Development] Newt:
Im going to port my Rom for inc2 then you guys can roll from there
[Droid Incredible Android Development] incubus26jc:
Whats up guys!! It's been a long time.