yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] chairshot215:
Thanks that is exactly what I was looking for. I do remember having one issue setting the theme in the b.p. Think I did this,

PRODUCT_PROPERTY_OVERRIDES += \

persist.sys.themeId=Themexyz\

persist.sys.themePackageName=themepackagename

The lines had been added to the build.prop but above the lines referencing the Cyanbread theme so booted using Cyanbread. I know its not hard to just open in 7zip and edit but would like to learn the correct method.

At home now and am about to start a build. have one actually 2 more questions,

First I also have the Galaxy Nexus boot animation I have been adding via 7zip and was wondering what would happen if I used the same method of adding apps like the below example and would I either get a build error or would it overwrite the cm7 animation and use the Nexus animation?

PRODUCT_COPY_FILES += \

device/amazon/otter/prebuilt/animation/bootanimation.zip:system/media/bootanimation.zip

Second is that I am also removing unwanted APK's like say Bluetooth via 7zip and would like to learn how to just build without.
[Kindle Fire Android Development] Sblood86:
If you have a large set of APKs that you want to be able to build easily without having to add them all into the make file individually you could create your own directory (anywhere is technically fine but an example would be 'vendor/chairshot/' in that you could place all your APKs and an Android.mk file with the included copy commands than simply add that make file to otter.mk or cyanogen_otter.mk

include vendor/chairshot/Android.mk

As for removing APKs from the build checkout the squisher in the device folder (this is where cmstats etc is being removed from instead of using a custom make file like the old tree)

Lastly for the bootanimation it will overwrite it, assuming your change comes after the cyanogen make file in the load order.
[Kindle Fire Android Development] chairshot215:
Hay Sblood sorry to be such a noob but decided this morning to start over with a clean slate but running into an issue downloading the source. Never mind this, just wrote up this long question about the issue but before sending I decided to try one more thing. Also just downloaded the source for my phone in a directory named Android and a bin folder with the a Repo file on the root directory, still not sure how that all works but anyhow I created a Kindle directory and placed the new Repo file in a second bin directory I created inside the Kindle directory along with the CM7 directory inside and am now able to download the source. Just figure I would share as I'm still trying to wrap my head around this stuff. That and don't have much else to do why waiting for the download to finish. When finished I plan on trying to add my apps using the method you have described above and thought I would take the time to insure I'm understanding correctly.

1, Create a directory, will call it chairshot for now.

2, Place Android.mk with copy command inside chairshot directory,

3, add (include vendor/chairshot/Android.mk) to the otter.mk. assuming chairshot directory is inside vendor directory,

4, place my APK's inside (vendor/chairshot)

Will look at some other .mk for an example but am not sure what the copy command should look like on the Android.mk that would be placed in the chairshot directory or would I still need to do each app individually like the copy command I had used for them in the otter.mk?

Otherwise could probably figure it out by poking around but don't have much else to do why Source is downloading and figured this could possibly help other noobs like myself trying to learn how to build their own CM7 Rom.

Edit,

Done so going to try the following in the Android.mk

# APK's

PRODUCT_PACKAGES += \

app \

app2

only because I see this in a few other .mk's referencing some cm apps and also the theme apps. basically I opened a bunch of files and if it contained (include whatever.mk) I found the whatever.mk it was referencing and I saw what is listed above referencing what I know is an app. Guess I will find out in about 2 hours.lol
[Kindle Fire Android Development] Sblood86:
Sorry for slow response... That should all work fine yeh.
[Kindle Fire Android Development] Sblood86:
New recovery up; should work for all ICS and Gingerbread Roms.

Big thanks to Drew Walton of Team Hydro for helping me squash the bugs that were keeping this from being released.

This does fully support Rom Manager, I'm currently looking into adding support for GooManager as well.

The reboot functions should support all versions of FFF however newer Roms will not properly boot into recovery without FFF 1.4 or above.

As always hit the second post for a binary.

-IngCr3at1on

PS.

-Bacon is also served in the first post.
[Kindle Fire Android Development] smirkis:
Works great. Awesome work n nice update.
[Kindle Fire Android Development] portezbie:
I'm getting an error trying to install today's (June 13th) update.

The error in TWRP says:

format() expects 4 args, got 3

E: Error in /tmp/sideload/package.zip

(Status 7)

Any idea why it's not working?

Thanks!
[Kindle Fire Android Development] Sblood86:
Honestly I haven't tried flashing cm7 in twrp; I would venture a guess they have updated something though.

Here's the deal with the format line in the updater-scripts:

Edify scripting was originally introduced with Gingerbread; it removed the need for having a way to parse the update scripts directly in the recovery by including a binary with the updater-script to parse it for them, brilliant idea in theory but it's created a few issues in practice.

First and most apparent is that different binaries do not work properly with specific recoveries and or packages; we've all seen the (apparent) random need to swap a binary from a rom we know will flash to make something cooked up in a kitchen or similar flash properly.

Those issues become more apparent with the introduction of the use of the 3.0 kernels and other ICS changes; the first and foremost being the ability to maintain a filesystem size from the format command, in most cases the variable remains untouched and sits at 0 but what it also does is adds a 4th argument to the format command in the updater script. Now the binary that's included with the script can parse it no problems but the recovery itself has a check before issuing a command like format; to make sure the appropriate number of arguments is provided. In CWM it appears to fallback and flash as it should with 3 arguments in the case of gingerbread (or at least it did with the last build I flashed), not having tested TWRP I have no way of knowing what it does in this instance.

You can't swap the binaries around or add an extra 0 to the end of the format command in the updater-script cause the extra 0 would require the binary and the binary is going to fail to properly parse everything gingerbread related if it's from ICS (I tried, I was bored).

You can; comment or remove the format system line from the updater-script and format system manually before flashing the zip (I'm not going to actually recommend you do this, but it would work).

I hope that explains the issue a little better; I should point out I didn't actually flash the ROM from last night (nothing was changed since the previous release), can someone do me the small favor of confirming I'm not insane and it does properly flash from within the recovery in the second post?
[Kindle Fire Android Development] smirkis:
I flashed it from cwm last night. no errors on my end. ill try again later today, but the new cwm recovery flashes cm7 and cm9 now. no borked partitions possible on this one as it used the older kernel as usual.

once it supports openrecovery scripting I'm sold. but still use it daily
[Kindle Fire Android Development] portezbie:
I'm pretty sure I flashed the june 1st update in twrp without any problems, weird.

So you think It's something with twrp and I should try going back to cwm?
[Kindle Fire Android Development] smirkis:
damn, I guess I was the june1st I flashed. the june13 zip gives the errors ,mentioned? weird. sorry sblood86
[Kindle Fire Android Development] Sblood86:
Interesting... Well I'll dig into it.
[Kindle Fire Android Development] portezbie:
Thanks a lot for maintaining and developing this rom SBlood, it's really fantastic and the best rom I've used for the KF.
[Kindle Fire Android Development] Sblood86:
Well it seems something failed or similar somewhere in the compiling the script for example looks perfect, I just built another build and it flashed fine; I had the sudden epiphany to sync my repos after having done so lol, I'm gonna build from this fresh sync before I upload so everything's nice and fresh from CM.
[Kindle Fire Android Development] portezbie:
Just flashed and booted the June 14th build without any problems.

Thanks for the quick fix SB!
[Kindle Fire Android Development] Sblood86:
As Smirkis and at least some others may already be aware last night I patched up ORS support for both the LS670 and the Kindle, everything appears to be working fine but I've only had a limited time to test it on either device. Drew went ahead and released the LS670 recovery after having tested it himself, I'm still waiting on confirmations from Smirkis on the kindle recovery (there are some substantial differences but everything should be fine).

Assuming no bugs have been reported by tonight expect a new release early morning with full ORS/Goo Manager support.
[Kindle Fire Android Development] Sblood86:
New build is up in the OP:

There is a known issue with the reboot function in ORS.
[Kindle Fire Android Development] Pkt_Lnt:
OK I guess I need your contributions on both my devices. :D

Kindle Fire w Hashcode ICS ROM + 3.0 kernel & Tapatalk 2

edit -

Ok, flashed. What exactly is the reboot issue?

Does that mean if I choose a ROM in Goo IM to flash, it will not boot to recovery.

Or do you mean after the ROM is flashed, the recovery will not reboot back to the newly flashed ROM?

Still getting my head around the whole ORS thing here.
[Kindle Fire Android Development] Sblood86:
Small issue where the 'script engine' itself didn't have anything actually assigned to happen if a reboot command was included in the script.

It will be fixed in the next release, as will a few other things.
[Kindle Fire Android Development] smirkis:
can u set the recovery to remember the selected choice as far as sig check? even if i disable it, and reboot to OS to see if it will flash unsigned zips, when it boots back into recovery to flash it, sig check is re-enabled again and unsigned zips just fail. i understand why you enabled it, but without the option to disable it when using ORS, or the recovery remembering that i disabled it, its not quite working, as not every rom posted, is signed.
[Kindle Fire Android Development] Sblood86:
We can probably make the signature switch permanent (for some reason I thought it was) otherwise you guys know the source tree is public right? :p

commit
[Kindle Fire Android Development] Sblood86:
Please see Post 2 for special information regarding the recovery.

On a separate note I'll be uploading a new rom build soon with Goo Manager support as well; not tonight, I'm going to bed, but soon.
[HTC Sensation] m.sfm:
HI i am stuck in the bootloader. I tried to go into recovery but it doesnt let me or cant flash the PG58IMG. I think i messed up by deleting my files on the sd card. Does anyone know how to fix this?
[HTC Sensation] tommeke19:
Pull out battery and try again.. or have did this already?
[HTC Sensation] m.sfm:
already tried that and i previously attempted to put a custom rom on and it froze have way through the progress and rebooted. The phone is stuck on the HBOOT and nothing is loading.
[HTC Sensation] m.sfm:
Also if this helps...The bootloader screen has Revolutionary on top and the recovery just shows three androids when pressed.. Are their any files I need to put on the sd card?
[HTC Sensation] big_sw2000:
Take the PG58IMG file of the sd card. Or pop the sd card out of phone, then try to accsess recovery. If it works, the deleate PG58IMG of sd card

Steve
[HTC Sensation] gol_n_dal:
Sounds like you need to flash a Custom Recovery (e.g. CWM).

Depending which HBOOT you have you can either use an appropriate PG58IMG.zip with the recovery, or fastboot flash it.
[HTC Sensation] m.sfm:
I have the 1.27.1100 HBOOT. What file am I suppose to get for this? I tried to load recovery by taking out the sd card, it didn't work. Also the rom I attempted to flash was the Virtuous Rom ICS.
[HTC Sensation] big_sw2000:
I wouls start again.

Have a look at this

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

Steve
[HTC Sensation] m.sfm:
I took a look at it and the only thing I can attempt to do for now is try to put the PG58IMG. When I attempt to do that, it doesnt ask if I would like to update but just parsing and then just goes back to HBOOT. Is it bricked?
[HTC Sensation] EddyOS:
Do you have the RUU for your phone? If so, which RUU is it?
[HTC Sensation] big_sw2000:
If you can get into hboot, then no its not bricked. Something will work, but what.

Steve

---------- Post added at 03:51 PM ---------- Previous post was at 03:50 PM ----------

What dose it say on your hboot screen

Steve

---------- Post added at 03:54 PM ---------- Previous post was at 03:51 PM ----------

Silly question, but dose the rom load, or do you get boot loop

Steve
[HTC Sensation] m.sfm:
This is exactly what it says:

-Revolutionary_

PYRAMID PVT SHIP S-OFF RL

HBOOT-1.27.1100

eMMC-boot

Jan 13, 2012, 17:33:34
[HTC Sensation] m.sfm:
Also rom does not load and I really dont know the RUU except its Tmobile US and got the phone recently like a week.
[HTC Sensation] EddyOS:
OK...first, turn the phone off and download this firmware file:

http://goo.gl/Jupb3

Once downloaded, copy it to your SD card. Then put the SD card back into the phone and turn it on holding the down button. It should read the file and ask you to update. Follow the instructions.

Once complete, press power to reboot and as soon as it starts to reboot pull the battery. Remove the SD card and delete the PG58IMG file from the card. Put the SD card back in the phone.

Download this RUU:

http://www.filefactory.com/file/c19...00U_10.14.9035.01_M_release_223976_signed.exe

Once downloaded, turn your phone on again holding the volume down button and once it stops scanning for files in HBOOT press power to change to FASTBOOT. Then connect the phone to the PC. If the drivers install correctly, it will say FASTBOOT USB on the phone. At this point, run the RUU

This should reflash the stock T-Mobile US ROM - you WILL lose all data doing this

Once flashed, and the phone boots correctly, reset the CID if you need to. The T-Mobile US CID is T-MOB010
[HTC Sensation] big_sw2000:
Pritty much as above

Steve
[HTC Sensation] m.sfm:
What if your battery is too low? Does the phone still charge when plugged into the wall outlet when in Fastboot?
[HTC Sensation] m.sfm:
Also when trying the P58IMG it says parsing fail-pu Update failed!.... is there any way to put the clockwork files on the sd card without the zip installer? Or I am running the cmd fastboot and my device does not show up but still allows for options. What can I put for the cmd fastboot?
[HTC Sensation] jaysun3000:
You know there was a lot of talk of failed-pu on the HTC Mytouch4G forums about how the eMMC chips would fail I never experienced that before and I don't know if its common on the Sensation like it was on the Mytouch wish I was more help check out the discussions they have concerning failed-pu:

http://xdaforums.com/showthread.php?t=1086403&page=2

from my HTC Sensation Z710e using XDA App
[HTC Sensation] big_sw2000:
Have you tried a diffrent firmware pg58img file.

Maybe the latest ICS firmware.

Stve
[HTC Sensation] EddyOS:
Trying which PG58IMG? You need to be a lot clearer what you're doing to avoid confusion
[HTC Sensation] big_sw2000:
please deleat
[HTC Sensation] m.sfm:
Sorry but can you tell me how to delete a thread? I am new to this....
[HTC Sensation] big_sw2000:
Sorry not the thread lol. I did not mean you lol. I meant my post. I wrote a load of crap.

Steve
[Samsung Galaxy SL i9003] anna0811:
Guys i am going to make a icon set for miui rom. Can someone give the steps to make a icon set?

What should be the size of png ?

Guys help me on this
[Desire Q&A, Help & Troubleshooting] jaavaa:
Okay, I tought i just could RUU my phone using RUU file. So I downloaded RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4. 06.00.02_2_release_126984_signed.exe and booted to fastbood mode -> connected USB -> ran RUU. Anyways, all wen fine and the gray HTC logo appeared on my screen but after few seconds the RUU gave me "Bootloader version error [140]". After that my phone is just dead. It wont turn on or anything, I cant get ADB to my phone. Screen is totally black. The phone just randomly vibrates when i plug it in the charger or press the power button after taking the battery out. But its just random. The charging led indicator wont even turn on.

I Had few weeks old XJ's MIUI installed, CWM 4.X.X.X and hboot 6.93.9999 (if i remember right, 6.93.XXXX it was anyways). After failing the RUU, I googled and found out that i shuold have downgraded hboot first? I recently bought a new phone so actually just didnt give s*** Im having proximity sensor problem in my old Desire, so I would like to return it to the shop after flashing the default rom.

So folks, how do I proceed? Totally bricked?

Thanks!
[Desire Q&A, Help & Troubleshooting] eddiehk6:
sounds like wrong RUU file meant for SLCD/Amoled.

try the first post in Q&A which should deal with this...it's a sticky for a reason;)
[Desire Q&A, Help & Troubleshooting] kotag82:
It looks like slcd brick look for droidzone slcd brick guide
[Desire Q&A, Help & Troubleshooting] jaavaa:
Thanks, but as I already said, the phone cant be detected by PC. The phone wont even turn on. I tried again starting the phone to fastboot mode, but the phone wont even vibrate or show any signs of life. The only thing is that when i randomly plug the phone to the charger, it might vibrate and start warming up.

And yes, I've tried charging the phone over night assuming the battery would be empty.
[Desire Q&A, Help & Troubleshooting] eddiehk6:
so holding down back and power to get straight to fastboot doesn't work at all? i'm only referencing the troubleshooting guide

droidzone's slcd brick guide is more comprehensive, if that doesn't work then i dunno unfortunately...:(
[Desire Q&A, Help & Troubleshooting] jaavaa:
Whoa, got some life to my phone! Started it somehow with usb plugged and vol down and i got it to recoverymode! ADB Devices gives me following:

List of devices attached

HT07XPL06736 recovery

Dont want to boot the phone again, what do i do now? tried running a RUU for SLCD spotted in the sticky thread here, but it gives me 170 USB error.

EDIT:

So I'm in this situation now? (taken from droidzone's guide)

Well, is there a correct RUU for me?
[Desire Q&A, Help & Troubleshooting] kotag82:
as you are in recovery fastboot commands will not work try adb ones:

adb reboot bootloader

download fastboot commander you can find info there
[Desire Q&A, Help & Troubleshooting] jaavaa:
Okay entered the command and now the phone cant be recognized in any ways again. Tried running RUU right after boot but still error 170. Cant get the phone visible to ADB again..
[Desire Q&A, Help & Troubleshooting] kotag82:
do you have goldcard? download WWE RUU 2.29 and try do it blind google some videos as pb99200 method is shown, how to use pb99200 method see bortak guide from stickies... im off now till wednesday
[T-Mobile myTouch 4G Slide] Kanerix:
There are a lot of roms out there for our phones, now, but tracking down an OC kernel for many of them is quite a pain. Do we have a compiled list of kernels and download links? Thanks!
[T-Mobile myTouch 4G Slide] AgentCherryColla:
Give me a couple hours, I'll have a list. :D
[T-Mobile myTouch 4G Slide] AgentCherryColla:
http://xdaforums.com/showthread.php?p=22789976

Done!!
[T-Mobile myTouch 4G Slide] Kanerix:
Thanks man! You rock!
[Galaxy S II Q&A, Help & Troubleshooting] M1ch43lk:
Hi Everyone,

Anyone having experience with how to get bluez to work reliably with the "Renault RadiotSat Bluetooth"?

I'm running now "Resurrection Remix ics v9.0" with XXLPH kernel and it works but very unreliably. :(

When I start my car It get paired with the phone but if I won't use the phone for a minute or two it will disconnect and then I can't get to reconnect again.

The only way is to turn of the car and start again :mad:

I tried to changing the:

/system/etc/bluetooth/audio.conf

By adding the:

Autoconnect=true
HFP=true

But that did not improve the quality of the connection.

Any hints how to troubleshoot this?

My plan is to run "adb shell" and check while connected to the Radiosat and maybe see why

it gets disconnected...

Does the /system/bin/bluetoothd log it's information to any logfile?

The bluez version I'm using is 4.93... noticed that the latest is 4.98... Will that make any difference?

I've tested the "Renault RadiotSat Bluetooth" with my old Nokia E52 and my old HTC desire and with both of them it works much better. I do not get disconnected and I can even access my phone book/phone log and get information from the music player on which song is playing....

Any hints which settings in bluez to get that running as well?

Thanks in advance,

Michael
[Galaxy S II Q&A, Help & Troubleshooting] jozwis:
galaxy s2 and BT in Renault Radiosat

Hi,

I have lot's of problems with BT on my SGS2 that uses official FW. You can find on the Renault website that this phone is not supported.

But I also found that even supported phones give problems (my radio is restarting).

So this is problematic for all devices - I have no idea why - but BT stack in galaxy is too good/new (fast) for such Sagem based device.
[Galaxy Note GT-N7000 General] KingVekxin:
Ok I have an infuse (using Inspire now until replacement comes in) and I have seen a galaxy note, read specs and seen... I don't know why so many are jumping ship... It is just a bigger screen really, already with GB... Not a true upgrade at all, just a way to get a few hundred dollars out of people.... That's why many devices wont get true updates because people will always act like the slightest change is the biggest upgrade when it isn't.... Im just saying people be smart and wait for a TRUE BLUE UPGRADE and not just an overblown phone
[Galaxy Note GT-N7000 General] bradbusa:
how is it not considered an upgrade? it has a dual core processor, and a gigabyte of memory... not to mention almost double the battery. plus all the features the S pen provides over normal touch screen. you may as well have just condemned all the current galaxy s2 devices because they arent TRUE BLUE upgrades.. wtf mate

oh ya, those devices should also be getting ICS, which so many people are looking forward to

if you dont like it, dont buy it bro. different strokes for different folks
[Galaxy Note GT-N7000 General] mariusvt:
^+1

The note is definitely an upgrade hardware wise. That being said it doesn't interest me at all because there is no way a 5.3" screen phone will fit comfortably in my pants pocket. The infuse is boarderline, most of the time it is fine but sometimes it is just annoying in my pocket.
[Galaxy Note GT-N7000 General] Axiomkid:
A complete waste of an upgrade due to phones coming out with 2gb of ram and Quad Cores. Why jump the boat on Dual Core and 1gb of ram? A complete waste for those just wanting the phone for the big screen.
[Galaxy Note GT-N7000 General] CheesyNutz:
im waiting to see what coming form the Sgs 3 or htc leaked quad core phone before upgrading
[Galaxy Note GT-N7000 General] MikeyFTL:
Some of us want the bigger screen. I've gone from flip phones, to the iphone, to the Infuse all in search of the biggest screen...and the Note will be the king of the biggies for awhile. Sorry, but the Infuse is an antique in comparison. Not fitting in a pocket is the least of our concerns and no reason to create a thread to DO NOT DO. Find a better reason to bad mouth the new bad boy.