yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] xxprowler:
forgot to mention that im on stock kernel.
[Vibrant Android Development] VICosPhi:
Thanks Bruce, awesome site...great find.
[Vibrant Android Development] mike216:
my expieriences with JL1 and JL4 basede modems

in my opionion.JL1 by master flashed through CWR has been the best for me.Im running nero v1 that came of course JL1 based but after i flashed masters JL1 modem i seem to have better data speed.I live in cleveland ohio and we do have hspa support.I also flashed the new JL4 modem and it seems to have worked great for a lot of folks living on the east coast but i got around the same speed i had with the JL1 that nero comes with.
[Vibrant Android Development] BruceElliott:
Nero v1 is deodexed, but is not the same framework-res.apk as JL4. So, DO NOT use the flashable that I posted. You will need to do the "cooking " method as described in OP.
[Vibrant Android Development] BruceElliott:
Nero b3 is deodexed, but is not the same framework-res.apk as JL4. So, DO NOT use the flashable that I posted. You will need to do the "cooking " method as described in OP.
[Vibrant Android Development] BruceElliott:
That is correct, WILL NOT WORK with odexed ROM. Just flash a deodexed JK6 posted on this forum somewhere.
[Vibrant Android Development] seojuhwan:
I am doing UOT Kitchen cooking method for Nero v1.

Is it "twframework-res.apk" or "framework-res.apk"? I tried both, and I am getting "SHTF". What am I doing wrong?
[Vibrant Android Development] BruceElliott:
It is "framework-res.apk."

Did you upload the "framework-res.apk" from your /system/framework folder? Note that the upload function on the website is a bit ambiguous. DO NOT click on the bubble that may pop up that says "download." That would invoke a framework-res.apk from the website rather than your own.

Are you on a deodexed ROM? (Should be, from Team Whiskey.)

Otherwise, I do not know what to tell you. You might ask Team Whiskey, though. It may be that they are calling "twframework-res.apk" at some point from some script. The UOT Kitchen method assumes that your ROM is actually using framework-res.apk. If Nero v1 is not, then you would obviously not expect this method to work.
[Vibrant Android Development] seojuhwan:
Has anybody successfully done this to Nero v1???

I have tried both apk files and the same result comes out. :(

EDIT: nvm, it is being developed by jocelynmallon at TW forum.

http://board.teamwhiskey.com/viewtopic.php?f=27&t=653
[Vibrant Android Development] jcc332006:
I flashed this mod on ginger clone 2 and it soft bricked my phone. Ginger is based on jl4 but for some reason it doesnt work. Flashed with CW.:(
[Vibrant Android Development] seojuhwan:
I just tested jocelynmallon's Nero Accurate Battery Mod. It works great! (This is for Nero v1.)

http://board.teamwhiskey.com/viewtopic.php?f=27&t=681
[Vibrant Android Development] seojuhwan:
Just cook it from UOT because it is not a complicated procedure at all.
[Vibrant Android Development] BruceElliott:
[MOD] Blue Segmented Battery Indicator FOR STOCK JL4, CWM-flashable**12/18/2010**
[Vibrant Android Development] mr.orange303:
What he said.:-)
[Vibrant Android Development] jcc332006:
Dude did you take the time to read my post? I said JL4. Whats up with your bold red response. JL4 JL4 JL4!! Read the post!:rolleyes:
[Vibrant Android Development] slighpcs:
While your ROM is based on JL4, I assume the framework has already been customized. Hence, the issues you've encountered. Correct me if I'm wrong though as nothing is for sure. ;)
[Vibrant Android Development] BruceElliott:
Yes, I read your post very carefully. Here it is:

"I flashed this mod on ginger clone 2 and it soft bricked my phone. Ginger is based on jl4 but for some reason it doesnt work. Flashed with CW."

The problem, I deduce from your posts, is that you are inexperienced and do not understand the difference between a "stock" ROM and a "modded" ROM. A ROM that is "based on" xyz stock ROM is not stock by definition. Your problem is not that you failed to match up "JL4," but that you failed to match up "stock" vs. "non-stock."

I suggest that you read up a bit more on these forums, at least until you understand basic concepts such as "stock" vs. "modded," before you attempt further modification of your phone. Your situation is somewhat akin to giving the car keys to a 12 year-old. Bad things will probably happen.

In these forums, the "car keys" are thrown out there for anyone to use. There is no parent, so you must take responsibility for understanding what you are doing. Although the devs and mod'ers try to make things as "cookbook" as possible, the fact is that ramifications of firmware modification are complex. Read-up, bud; I know you can do it!
[Vibrant Android Development] BruceElliott:
That is correct. The first thing that the devs do is hack at framework-res.apk.
[Vibrant Android Development] gilcimar9:
how to i remove it if i want to???
[Vibrant Android Development] BruceElliott:
(1) Replace /system/framework/framework-res.apk with the original JL4 framework-res.apk using root explorer or adb.

(2) Reboot.

The original framework-res.apk is attached, below. :)

WARNINGS!!!

(a) The attached file IS NOT flashable. Use root explorer or adb to move the file to /system/framework.

(b) This post is applicable ONLY to

STOCK

JL4.
[Vibrant Android Development] opentofalling:
nevermind...
[Vibrant Android Development] rorycs:
Is anyone updating this Mod for JL5?
[Vibrant Android Development] leungda:
How about Nero 3 JL5 version?
[Vibrant Android Development] opentofalling:
The instructions in the OP are simple enough for anyone to follow. Get to it!
[Vibrant Android Development] Yellow C6:
Thanks, OP. With your excellent instruction, I made the exact same one for the stock JL5. Very easy and works great. :)
[Vibrant Android Development] BruceElliott:
I will be, probably tomorrow.
[Captivate General] Delgoth:
I've been trying out all the captivate roms in the past few weeks. And all of them seem to have their quirks. I'm hoping that with all this 2.3 developing going on, captivate development will go in a new direction. Especially looking at battery life.

Every rom I've tried has battery life problems. probably due to overclocked kernels designed for a totally different phone. Assonance seemed to have the longest life for awhile but it seemed to get worse over time.

I've never had GPS problems. I've walked around my yard a few times and it follows me around to a tee. The lagfix did seem to do the trick.

And the backlight notification is a cool feature, but I can't seem to get it to turn off, even after I disabled it from clock work recovery.

I'm not trying to rag on anyone here, I'm just trying to say that now that development for our amazing phone is being given a break with official source code from the nexus hopefully features and roms won't to be for other phones that just happen to work on the captivate. I understand that these new things will be based on the nexus s, but is imagine that with the firmware leak from samsung, a real captivate version could be made some where down the line.

Thank you, and I wish you the best in development.
[Captivate General] Ryukeima:
Battery life, along with many of the items you listed, is relative. I for example get amazing battery life with many of the roms I have used, much better than stock. I am using the OC/UV kernels too without any undervolt. I am not saying the problems dont exist, but that I dont expect the issues that others are having to be fixed because of the Nexus material flying around. Mileage just varies by make and model. I am actually not sure what my point is, but then again, I am not sure what the point to your post is either haha. No offense.
[Captivate General] h8rift:
I understand what you are trying to say.

To summarize "stop putting i9000/Vibrant ROMs and re-orient kernels on Captivates and calling it a Captivate ROM".

If we lived in a perfect world where a certain manufacturer would release source code instead of breaking GPL licensing rules...it maybe easier. But for the time being...we still are going to be the bastardized cousins of the great, almighty i9000.

So...if you want to do something about it...call Samsung :). The devs are working with the tools they have...even if that means they have to borrow from the neighbors :).

Thanks

-h8
[Captivate General] flashman2002:
Please explain what this has to do with development? Be happy these guys are doing things to make the phone better than stock 2.1.

This is my captivate. There are many like it buy this one is mine.
[Captivate General] sold1erjjt:
Some users have done tests, it shows that the stock jh7 has a lot better battery life then all of the custom ROM's mostly in part that the ROM's were made for different devices... just sayin...I don't mean to bicker, but golly has Samsung been... lazy? I don't even know what to call it. The Captivate hasn't got a good leak in sometime. but Samsung could at least be more specific with their ETA on Foyo being out.. I understand AT&T has a thing to do with it but still...
[Captivate General] shaolin95:
+1

I rather would like to see people stop posting non development related threads on the Development forum.... :rolleyes:
[Captivate General] ritchmonty:
Is this non development due to the fact that there is not a rom to download? I've read through thousands of posts on the Captivate Android Development section of the forum and I really don't see the difference so why are picking on this thread in particular? Your post has absolutely nothing to do with development ....
[Captivate General] designgears:
2.2 for that captivate hasnt been officially released, so they don't have to release the source until then.
[Captivate General] shaolin95:
First learn what development means so you can understand the point.

Second, just because you have seen thousands (hyperbole much?) of non development threads does not mean they were posted in the right place....the MODs can barely keep up with people that cannot read or lack reading comprehension.

Thirds, my post has nothing to do with development? Was that a joke...am I supposed to turn a non development thread into one? :rolleyes:
[Captivate General] MikeyMike01:
In summation: more pewpew, less QQ.
[Captivate General] gtg465x:
I don't notice much difference in battery life between using Captivate ROMs and reoriented i9000 ROMs. I get great battery life with both (usually about 40 hours with moderate use). Maybe you're seeing poor battery life because most ROMs posted for the Captivate use Setiron's kernel, which is overclocked and has all sorts of other tweaks built in. Lagfixes don't help either. If you want decent battery life with an i9000 ROM, try xcaliburinhand's no voodoo kernel (JPU and JPX ROMs don't need a lagfix) or disable overclocking, lagfix, and tweaks on Setiron's kernel.
[Captivate General] Smallsmx3:
40 hours doesn't even seem possible unless u put your phone down and don't touch it.....I have used vibrant and i9000 roms and noticed since switching back to cronus (jj4) and voodoo stable (jj4) which are all captivate parts that my battery life has almost doubled. Im going to stick with this setup for awhile and see what happens.
[Captivate General] Delgoth:
I wasn't trying to to start no fight here! Like I said I wasn't trying to call anyone out, but yes I probably did post in the wrong forum. I had chosen Development, because that was what my post was aimed at.

I appreciate the work being done one the Captivate, because without it our phones would be pretty boring don't ya think?

Really, all I'm trying to say is that I hope we see some new kinds of ROMs in the upcoming future. Something similar to Ultimate Droid would be crazy, with all of it's extra phone settings.
[Captivate General] gtg465x:
I can go a lot longer than 40 hours if I put it down and don't touch it... 70+ hours. With really heavy use (couple hours of tethering, a little gaming, couple hours of browsing and reading xda, lots of texts and gtalk, couple calls, hour or so of music listening, random time and email checking) I can only go about 14-16 hours, but it's still enough for a full day.
[Captivate General] rpicaso:
The Captivate source has been released.
[Captivate General] Smallsmx3:
Source for what?
[Captivate General] avgjoegeek:
lol +1 10 Char
[HD2 Windows Mobile 6.5 ROM Development] flattit4:
hi guys short story i try to send my fone back to htc for service cause the vibrate doesn't work. but i have the hspl on so i try to uninstall it and is end up not working ( still can boot into the boot loader ).

it keep give me something like 00028002 not allowed

after that ruumbh

pb81100 hx-bc

spl-1.42. 0000 xe

microp(led) 0x05

microp(touch) 0x40

upgrade rom code error

please try again

help pls i already download like 5 of the original asian rom still could not uninstall the hspl

thanks in advance
[HD2 Windows Mobile 6.5 ROM Development] flattit4:
i just wondering if we hack the htc memory from 4 something to 512 is that mean we need to use the us rom?
[HD2 Windows Mobile 6.5 ROM Development] flattit4:
sorry guys i figure out already apparently 5 of the rom that i try to download may be error the last 1 i download is working find

can some 1 delete this thread

thanks
[EVO 4G Q&A, Help & Troubleshooting] sferrin:
I'm trying to understand what I'm seeing on my display. The EVO has a display resolution of 800 x 480 yet when I make a wallpaper 800 pixels tall and try to assign it as wallpaper it pops up a selection area substantially smaller than the full resolution wallpaper and crops the display of it. Also, when I assign images to contacts it crops those as well. What gives? I end up with jaggy contact avatars (from being cropped then stretched to fill the required space) sitting right next to 1-to-1 resolution graphics, the end result looking horrible. This would seem to be an Android problem as my Imagio running Windows Mobile 6.5 (*gag*) does not have this problem. Is it something I'm doing wrong or is it an inherent Android flaw? If the latter does Google intend to fix it? If the former what do I need to do differently?

Thanks.

Nevermind. Finger on green box, drag arrows. :o

2nd edit: It appears that while it also works on the avatar pics they always revert back to the low res crap. :(
[EVO 4G Q&A, Help & Troubleshooting] nuggyunlimited:
I have the wallpaper problem how can I get the entire 800 x 480 as the wallpaper.

Swyped from Eva running Myn's RLS4!
[EVO 4G Q&A, Help & Troubleshooting] sferrin:
When you select your wallpaper a green box will appear. Touch on the green box and arrows will appear letting you strech the selected area to the full size.
[EVO 4G Q&A, Help & Troubleshooting] nuggyunlimited:
Farthest mines go.

Swyped from Eva running Myn's RLS4!
[Nexus S Q&A, Help & Troubleshooting] jdm_cars:
picked up 2 Nexus S on release day, went home happy. Preoccupied with work, so I only powered them up last night.

To my Surprise, both phones have dust under the glass! WTF Samsung? Removed the plastic sheet on the front to make sure, and yes, it's under the glass.

on one phone the dust was smack in the middle, while on the other phone it was a little left of the middle.

Can't be seen on a dark screen, but once you switch to a white background like the web or texting you can see it.

I know I am probably being OCD and anal about this, but heck I paid over $1k for both phones out of contract.

Went back to BestBuy and returned them promply, of course now they are sold out, and I have to wait for the next shipment.

Just wondering if others have similar experiences? BTW, I also had a Galaxy Tab and before returned it, it also had some dust specs under the glass...

I also own an HD2 and G2, seems HTC is better at QC.

Shame, really want this phone but WTF samsung?
[Nexus S Q&A, Help & Troubleshooting] slowz3r:
Nope you sure its under the glass?
[Nexus S Q&A, Help & Troubleshooting] BlackOtaku:
No dust under the screen here.

It seems that this first batch of phones is a rather mixed bag; some have defects and others are fine. It was a good idea to return them, hopefully your replacements will be free of issues.
[Nexus S Q&A, Help & Troubleshooting] profanum429:
My first S had a little speck of something. I initially thought it was a dead pixel, but I could see it when the screen was off also so I assumed it was dust. I returned it and checked the next one out before I left the store and it seems to be good.
[Nexus S Q&A, Help & Troubleshooting] jdm_cars:
100% sure, remove the screen protectors on both of them and rubbed the area where it was, thought it was a dead pixel too, but no it was fine on a dark background, but on a white background could see it easily.

sold out at my local bb, but still available online might go that route.

just wanted to see other people's experiences or maybe they didnt notice yet, lol.
[Nexus S Q&A, Help & Troubleshooting] ll_l_x_l_ll:
this happen when you have 2 layers for the screen. the internal part and the upper part where you touch.

there is an advantage for this. if god forbid you dropped and broke the screen, only the upper part gets replaced. and wouldnt cost you much to do so " and you wont get another screen with dead pixel and being OCD whatever the new screen is good or not. because the actuall inner screen isnt touched.

the bad thing about is what you said. dust can enter in the middle between both layers of the screen.

even if you get a new nexus S without dust under the screen, if you leave it in the open area with sun and wind always hitting it, you will get a dust somehow inside as well. so make sure your phone is in a pocket most of the time.

the only phone i remember right now that had both layers of the screens touched as 1 part is the iphone 2G and the iphone 4 " i am sure there are others but i dont know "

this result to no dust under the screen no matter what " unless the dust came from factory while they were attaching both screens on top of each other and glue them "

but if you break your screen in the iphone 4.... god help you.
[Nexus S Q&A, Help & Troubleshooting] Shockie:
Yeah, after about a week and couple of days of usage, I've got my first spec of dust in the top left area of the screen. Really, it's nothing noticeable but I do have some sort of OCD with my phone (god help me if I get a visible scratch on the screen).

I don't think it's really worth taking it back to get it changed as this Nexus S I have currently has no problems whatsoever, I don't even have the pink or yellow screen issue with this one. I think I'm just gonna have to live with that one spec of dust for now...
[Nexus S Q&A, Help & Troubleshooting] princeasi:
I think this may be just bad QC. I looked at ifixit taking apart the NS. Basically they said the trickiest part to the disassembly was the screen, and they had to use a heat gun to soften the glue just to separate the 2 screens. So dust entering between those 2 screens would be pretty difficult unless the glue wasn't properly applied from the assembly line.

Sent from my Nexus S
[Nexus S Q&A, Help & Troubleshooting] boonkoh:
I don't have dust under my Nexus S screen... but I do have dust under my front facing camera! And its only recently just got there - I remember playing around with it extensively when I first got it 6 months ago and the camera was really clear and sharp.

Now it is all fuzzy and white haze. And I can see all the dust particles on the underside of the glass. Annoying!

Anyone know if there's an easy way to clean it? Or is it a case of back to Samsung?
[Desire Android Development] python08:
Sorry but I have a pooor internet connection and I try to fix a bug : the device is re-running boot sequence when 3g get activated :/
[Desire Android Development] MrTequila:
nice man, maybe we can help u to fix the bugs. i could give u a mirror!
[Desire Android Development] python08:
Thanks a lot !

My current (and only for now) problem is in frameworks, with NetUtils..
[Desire Android Development] xvfzms:
Is it flashable zip, or have we flash ROM through fastboot (cant you delete recovery image then, to avoid overwriting it ?)?
[Desire Android Development] tasty_boy:
nice try!!, hope u have success!!!!

have u twitter or an irc channel?

so we can see how the development is going!

and we could help with anything!

nice job guy!
[Desire Android Development] python08:
There are two methods : fastboot (boot.img & system.img) without erasing recovery and flashing via recovery, but you lost your recovery.

Twitter : @renandroid

I have actually little issues but the ROM is not really useable.. I'm gonna try to release a .zip as soon as possible :)
[Desire Android Development] hugesea2008cn:
very nice.thanks !!!
[Desire Android Development] mdeejay:
python08 can you upload gralloc.qsd8k.so & copybit.qsd8k.so for bravo?

if you have.

Thanks
[Desire Android Development] python08:
m-deejay : I took gralloc.qsd8k.so from a Nexus One build and I think I'm gonna upload the update.zip in a few hours or minutes I don't know. So just wait a little bit and I'll upload also the copybit.qsd8k :)
[Desire Android Development] mdeejay:
with nexus one gralloc we have "white screen transitions" :(
[Desire Android Development] zahashingo123:
hope you get this soon!
[Desire Android Development] python08:
Yes, you're right :( I'll keeep this one for the moment but I'm gonna work to fix that.

We could send informations by PMs about our progressions :)
[Desire Android Development] AdamG:
I already made a copy yesterday, its not really usable until we get the new blobs from the nexus ota because of the gfx bug.
[Desire Android Development] 10lexik:
Hi frenchie friend :D

I can upload your rom on a mirror if you want ^^
[Desire Android Development] python08:
Yeahh it's great to see french solidarity :D When my ROM will be ready, I'll ask you :) Thanks a lot!
[Desire Android Development] kszxcvbnm:
oh good !
[Desire Android Development] monoblur:
You have to ask yourself "if Adam did not do this there should be a reason"
[Desire Android Development] 10lexik:
Can't he just try and can't we just test ? ;)
[Desire Android Development] Flashmaniac:
I thought the same =D

could you tell us already what is working and what is not? :)
[Desire Android Development] python08:
@cigga33 I'll add it ;)

But for now, I'm gonna quickly release RC5 (in a few hours).

Changelog :

- Switched to CFS vorkKernel

- Smooth battery icons (thanks to ClassicalGas)

- Reverted graphic changes (definitely SMOOTH, as smooth as previous releases =D)

- Added options for trackpad wake/unlock and menu unlock

It's just a quick fix of the RC4, new features will come in RC6 ;)
[Desire Android Development] cigga33:
With this features, Amethyst have no lack now!

Woah! Can't wait for RC5! :D:D
[Desire Android Development] simonthor:
Very awesome! Defienitly my default rom. Works great with the oxygen hboot.

Now you just need to make your own boot-animation. (Not important :))
[Desire Android Development] python08:
RC5 is available :)
[Desire Android Development] simonthor:
Thanks! Is wipe Cache enough?
[Desire Android Development] peppesgd:
app2sd+ are added or not? tnx for wonderful rom
[Desire Android Development] python08:
Wipe cache Should be enough.

No A2sd+ for now, sorry :/
[Desire Android Development] python08:
Little bug with power widget in statusbar.. Will fix it asap.
[Desire Android Development] revthanki:
Hey, loving the updates! (looking forward even more to when the N1 OTA comes out).

Now the widget settings are there, coudl I ask again for USB tether? :D
[Desire Android Development] tasty_boy:
Think that i got an issue...

my Market didnt opens the main screen

wiped everything

and didn't works

that's a little issue, but is so nag!!!
[Desire Android Development] Fancois:
Got the same problem on WiFi, but I was too far from my routeur ^.^

Now everything find :) Expect I didn't find the option for the OJ
[Desire Android Development] python08:
The option for the OJ is under Settings > Accessibility ;)

For those who have this issue with Market, please post a logcat because I haven't this issue :/

I will upload a fix for status bar widget settings soon.