yashsingh1/xdaforums huggingface dataset:
[Nook Color General] jleecong:
FYI

I just had my Nook "Installing... A new software update is being installed"! I'm thinking my boot count was not being reset, hence why it wasn't running the command.
[Nook Color General] Bemuse:
Is there really a noticeable difference going from 48000 to 68000? I personally haven't noticed any flicker but was just wondering if some one that is sensitive to it saw a reduction in flicker when they made the changes.
[Nook Color General] greenmky:
I just did it on mine and it is noticeable better. I can now only see the flicker on light gray, and barely at all.

Although the setting SHOULD be 66461 ...when you try to set to 68000 it just defaults to this. Makes sense from what I read on one of the TI developer forums (sounds like it defaults to safe maximum if you go over). I wonder if some of the screens are slightly different than others...does anyone actually get 68000 if you check it after? Or does everyone end up with 66461?

I haven't implemented anything permanent yet though. So I'll have to do whenever I reboot it. I can't do the same command from terminal (file is probably locked or something), so far I have to do from ADB.

This isn't a refresh rate setting per se...sounds like a screen timing setup of some sort.
[Nook Color General] likearaptor:
Does anyone think this will impact battery life by changing this to a higher refresh rate? It just seems odd that B&N would set it low to start out with. The refresh rate problem is pretty obvious. You would have thought B&N would have known how to fix it, right?
[Nook Color General] khaytsus:
I'm usually pretty sensitive to refresh rates, but I've never noticed it on mine.
[Nook Color General] joel71:
Thats because it was meant to be an e-reader. When your reading txt you don't need a high refresh rate but when your doing the stuff that we do after we root a higher refresh rate is needed or preferred.
[Nook Color General] tomtbone:
The problem is, that I use my NC for reading and I can see the flilcker on the screen on certain brightness levels.
[Nook Color General] zetlorf:
So, anyone have a permanent solution for the screen flickering?
[Nook Color General] cmstlist:
Just wanted to add, on Nookie Froyo it seems to default to 68000.

Out of curiosity I tried changing it to exactly 60000 because that would mean it matches the flicker frequency of fluorescent lights and thus it might be less perceptible. When I tried that, the screen wouldn't turn on, and I had to hard-power-off and reboot to fix it.
[Nook Color General] greenmky:
bump

for others with the flicker problem, B&N's 1.2 firmware didn't fix it. Still flickering it up. I'm going to a custom ROM for this reason alone. I didn't see anyone post an easy ADB type fix for it after searching....so...

I was hoping B&N would fix...
[Droid Incredible Q&A, Help & Troubleshooting] BaronofBlood:
For some reason no stock music player will read my internal storage anymore! I tried flashing different ROMs but none of the stock music players will read my internal storage, has anyone else ever had this issue? What can I do to solve this? Thanks.
[Droid Incredible Q&A, Help & Troubleshooting] TheWhiteBandito:
Never seen this issue. Do other 3rd party music players such as Mixzing or "3 (cubed)" read it?
[Droid Incredible Q&A, Help & Troubleshooting] BaronofBlood:
Yep Mixzing does read the internal storage... but the stock HTC music.apk is still a no go :(
[Droid Incredible Q&A, Help & Troubleshooting] BaronofBlood:
Hmm, perhaps it was the ROM, it wasn't working on 2 other ROMs but after installing Myns Warm Two Point it seems to be working again! :D
[Android Q&A, Help & Troubleshooting] Thyrador:
does any1 knows how to get rid of the task-manager button in longpress home-menu?

i figured out that i can find the sources in recent_apps_dialog.xml, but every try to change smth will end in a force close of the longpress home-menu

any solutions out there?
[Galaxy S I9000 General] Tehpriest:
Here is the report

http://www.engadget.com/2011/01/05/...ounced-for-atandt-4-5-inch-super-amoled-plus/

This is only one of many announcements to come though.
[Galaxy S I9000 General] fulcrum1971:
What about the S2?
[Galaxy S I9000 General] Tehpriest:
Their keynote from the President is tomorrow.
[Galaxy S I9000 General] yiannisthegreek:
Hmmm... It sure looks like a nice device. I sure hope that Samsung has all the bugs worked out by the time this hits the market and Id like to see it here in Canada as well...
[Galaxy S I9000 General] gtg2:
I've come to really like the physical home button (missing from this new model) on the i9000 as well as that little hump at the botton of the back. Two ways to easily orrient the phone without having to look at it.
[Galaxy S I9000 General] EarlZ:
Would that 50% more subpixels really improve the text quality on the SAMOLED-plus ?

I hope they sorted out the screen burn issues..
[Galaxy S I9000 General] Rawat:
Yes. RIP pentile
[Galaxy S I9000 General] QueenAmy:
I might better start saving today for the release of this model ;-) looks real nice & 8 MP Camera sounds just great!
[Galaxy S I9000 General] zorxd:
8 MP Camera won't change much if the lens and sensor are still of the same size. Anyway always remember that your display is about 2 MP (full HD)

The best improvement is S-AMOLED+. 4.5" is also interesting, but some people will prefer smaller phones. That extra 200 MHz is better than nothing, but I hope that they also added more RAM or the performance will be about the same.
[Galaxy S I9000 General] cantIntoCode:
Hmm I hope something like this hits the UK. I'd love a 4.5" Galaxy S :) Although I'd rather wait for some major dual core phones to hit the market.
[Galaxy S I9000 General] Tehpriest:
[whistle|thinks] Maybe the GSM version will be ;) [/whistle|thinks]
[Galaxy S I9000 General] Korshar:
4,5 inches?? Wow that's just too much, 4 inches are just perfect, but i wouldn't go any larger.. i'd like to see a 3,7 oder 4 inches superamoled+ samsung dual core 8 MP with xenon light and honeycomb android.. everything else would be just a minor upgrade ^^
[Galaxy S I9000 General] EarlZ:
I thought its still using pentile..

NVM, saw it on another article they are getting rid of the pentil in favor for RGB layout for better images.. they should have done this in the first place!
[Galaxy S I9000 General] evil-doer:
gimme a break. the bigger the better, as long as it fits in your pocket. and ive got OODLES of room left with my galaxy s. my wallet is a lot wider and wallets are designed to go in your pocket.
[Galaxy S I9000 General] Mithent:
I'm glad that AMOLED has now got to the point that they can drop PenTile!
[Galaxy S I9000 General] kunjar:
Exactly...i dislike the idea of having a phone bigger than 4". Even when going for the SGS i was a little undecided. Id rather not have a huge hand held game like device as a phone, it should look sleek and professional, but these qualities are compromised the bigger the size. Bigger screen and therefore phone doesnt mean better. Its nice to be able to use the galaxy s with the same hand that is holding the phone.

Bigger size is just a waste in my opinion.
[Galaxy S I9000 General] madpete:
I cant say I see this as much of an improvement over the current sgs, where the hell is Orion? Delayed? Dropped off the radar?

And yeah, the 4.5" screen sounds like a bit much.
[Galaxy S I9000 General] haloimplant:
Not sold on 4.5" here either. Even 4" (as much as I like it over smaller sizes) is a stretch to use with one hand. It is a reach to hit the far side in 'landscape' orientation.

In terms of just looks though it should be a stunner with RGB sub-pixels instead of pentile.
[Galaxy S I9000 General] KLoNe1:
I think this may be classed as a 'middle-man' to the S2.

Not too much will chance, but as I'm completed addicted to this Galaxy S and Android in general, I will no doubt upgrade to the SGS+ :)
[Sony Ericsson XPERIA X10 Mini] Moody:
Hello, I am trying to compile CyanogenMod 5.0.8 (eclair) to the mini pro.

I chose this version because it will probably have almost everything working since the latest kernel on the x10 mini pro supports eclair.

however when I try to compile the eclair branch from the cyanogenmod source I get the following error.

error: revision eclair in CyanogenMod/android_external_webkit not found

I've looked on the internet for a solution and found something about removing a line from manifest.xml, but I haven't been able to locate it. Is there no hope for porting CM5 over then?

Greetings, Mike
[Sony Ericsson XPERIA X10 Mini] owain94:
what manifest.xml do you mean coz every app has an manifest.xml

please give us some information about this

edit:

i think you need the manifest.xml from browser.apk

coz its a problem with the external webkit this is the browser

and if you decompile browser.apk there is an manifest.xml (like every app has xD)

edit 2:

i've attached the original 2.1 SE Manifest.xml
[Sony Ericsson XPERIA X10 Mini] Moody:
Thanks, but this goes beyond my knowledge.

I think I'm going to start up trying to port a nice gingerbread theme including animations and will take a look at porting CM6 over. I have owned an android tablet before so I have some basic knowledge.
[Hero, G2 Touch Q&A, Help & Troubleshooting] s-android:
hi guys

i wanna download elelinux froyo rom v2.0

but itsnt exist in the link and its remove

can any one help me and uoload this rom in the new upload server?

i just need this one.not newer version
[Hero, G2 Touch Q&A, Help & Troubleshooting] s-android:
nobody wanna helps me?

i just need a mirror for elelinux froyo v2.0 rom

hlp plz

someone upload it
[HD2 Android NAND Development] cedesmith:
cedesmith's (L)ittle (K)ernel bootloader v1.3.3

Disclaimer

This comes with no warranties, if you use it you do it on your own risk.

Please read carefully the flowing information and make sure you know what you are doing.

I don't have time or patience for questions and support. If you use it you are on your own (well and this community).

Recovery

- CWM 3.0.1.4

Q&A

Q: What it is ?

A: A bootloader for android like magldr.

Q: Is it better then magldr ?

A1: NO, it is missing tetris :p.

A2: NO, magldr has some nice features like partitioning and rmnet.

Q: Can i use last 24MB of nand with this?

A: NO, SPL will erase them. When i have some time i may try to fix it.

Q: Does battery charge with this ?

A: YES, from version 1.3

Q: Does it boot WP7?

A: NO. I am only interested in android but in can load and execute any program.

Q: Should i install it ?

A: If you had to ask probably not. If has no functional benefits over magldr.

How To

Flash cLK

- make sure you have hspl

- enter SPL by holding VOL DOWN key while powering/resting the phone.

- flash with customruu like you would a windows rom and/or magldr

Flash a ROM

- download android sdk, you will need drivers and fastboot command from there

- fastboot flash recovery recovery.img

- after recovery you can reboot and use CWM or you can flash with fastboot (fastboot flash boot boot.img, fastboot flash system system.img, fastboot flash userdata userdata.img)

Start recovery / fastboot / text console

- holding down any key ( except power ) will show text console

- home key will enter recovery ( if flashed )

- back key will enter fastboot mode

Known issues

RMNET does not work.

Downloads

NBH

- RUU 1.3.3

- 1.3.3 and 1.4 are are exactly the same function wise, only tools used to build them is different (1.4 includes nbgen written by me to replace osnbtool and nbmerge)

- recovery.img

ROM

- see post #3

Source code

git link

compile on a linux machine with wine and codesourcery toolchain in path by executing "sh compile" in root of source

Credits

- codeaurrora for making LK and for making it open

- Martin Johnson for his tinboot witch was a great inspiration

- Martijn Stolk for his kernel segfault solving code and and cotulla for pointing it and his contribution to android on HD2

- all how worked on making linux kernel possible on hd2
[HD2 Android NAND Development] cedesmith:
kernel and recovery patches

17.03.2011

- small fix on get_boot_reason

- cwm off charge fully implemented, inspired by dan1j3l's code (http://gitorious.org/htc-hd2-android-libraries/cmon/blobs/master/cmon.c)

15.03.2011

- kernel patch to save reboot reason so is available on bootloader

- old patched in zip as pushed in most branches

25.02.2011

- CWM patch for charging, unpached CWM code is not properly reading kernel cmdline because /proc/cmdline file size is always 0 resulting in a always empty cmd line. I also changed the code to wait for key press then reboot phone to normal android.

20.02.2011

- cLK_power_clllapse patch adds detection of cLK to kernel and puts the reset vector at 0x11800000 where cLK will jump (+4) at power_collapse_exit

- off_mode_charging just prevents the kernel from BUG() if off mode charging and panel is off ( and not detectable )

- both of this patches are compatibile with current SD and magldr builds, please push them to your git trees
[HD2 Android NAND Development] cedesmith:
ROMS

HyperDroid-CM7 by pongster

cLK for Dummies by stirkac

Froyo Sense revolution 2.5 by arif-ali

CWM 3.0.1.4 with yes/no menu by seadersn

UD 3.1 by crawlingcity

Revolution HD v2.6 & SL v1.4 by arif-ali

TyphoonN 2.6.3 CM7 for cLK

- download cLK

- download recovery

- if you don't have it download fastboot,adb and drivers from here

- download TyphooN 2.6.3 Standard Edition rom from original thread

- download typhoon kernel(tytung_r7) and initrd for clk update

- put rom zip and clk update zip on sdcard

- unzip clk and recovery

- flash clk ruu

- fastboot flash recovery recovery.3.0.1.4_clk_1.3.3.img

- fastboot reboot

- hold HOME key down to boot recovery

- wipe data/factory reset (if not updating from my previous version)

- install zip from sdcard -> choose zip from sdcard -> TyphooN_CM7_v2.6.3.zip

- install zip from sdcard -> choose zip from sdcard -> typhoon2.6.3_tyung_r7_clk_update.zip

- wipe chache

Other?

- drop me a PM to include it on this post
[HD2 Android NAND Development] cedesmith:
clk changelog

1.4

nbgen for making .nb file

1.3.3

small fix on get_boot_reason

cwm off charge fully implemented, inspired by dan1j3l's code (http://gitorious.org/htc-hd2-android-libraries/cmon/blobs/master/cmon.c)

1.3.2

ROMHDR base addr is spl virtual 0x80000000 = 11800000 physical, LK will relocate to correct address (MEMBASE)

save reboot reason at 0x2FFB0000 (ramconsole - 0x1000 (PAGE_SIZE)) and @0x2FFB0004 XOR 0x004b4c63 (cLK signature)

added oem cmd to fastboot and oemcmd.bat for PC. supported commands are:

dmesg - kernel debug messages

smesg - spl messages

pwf addr len - dump memory

set[c,w,s] addr value - set char(1byte), word(4 byes), or string
[HD2 Android NAND Development] jackielo:
Oh, I can't wait to try it.
[HD2 Android NAND Development] icsulescu:
Felicitari !! :)

Congratulation well done!

Regards,

Me
[HD2 Android NAND Development] jamieross:
good stuff il second trying that :)
[HD2 Android NAND Development] norpan111:
How do you flash those roms on that one ?:p
[HD2 Android NAND Development] simax:
can this be used as replacement for magldr?

if yes.. can i finally charge my battery while turned off? :D
[HD2 Android NAND Development] hellfire666:
Nice!!!!!!! downloading..............
[HD2 Android NAND Development] aminclick68:
good job

cant wait to try it
[HD2 Android NAND Development] yamensaleh:
interesting

this is interesting, specially it is from cedesmith, seriously this man work is amazing, i was waiting for him to release his Desire HD2 as a nand build, but he surprised us with this, keep the good work man

cheers
[HD2 Android NAND Development] agarp:
L0L downloading what

he just posted only the video :P

anyway nice to hear another bootloader for our Leos
[HD2 Android NAND Development] ilovemeow:
faster bootloader? for replace magldr 1.11??
[HD2 Android NAND Development] windroidHD:
no offense, but I see "senior members" complaning on how people don't use search in these forums before posting the question, but let's look at this thread...

1. There is absolutely no info on why this software was written and what problems it's solving? I am sorry but most people are not mind readers.

2. Software gets "shown off" and bunch of "senior members" post replies of "thanks...." instead of using "Thanks" button. These posts are not adding any value.
[HD2 Android NAND Development] TheATHEiST:
Errr no your not! There is no download yet wingnut! :confused:

-------------------------------------

I'm all for the HD2 dev growing and its second wind but what does this really do that magldr doesnt, Is there any advantages of using this rather then magldr because as far as I can tell it does the same (boot from nand) but without the extra functionality that we have option for on magldr?

So what would be (if any) the advantage of using this rather then magldr?

That isnt a dig or anything im just curious.
[HD2 Android NAND Development] stony007_de:
hi guys,

sorry for that question but, where is the benefit in this loader?

CLK vs. magldr???
[HD2 Android NAND Development] refuge27:
thanks for what what does this do no info no download link nothing come come on lol this is useless
[HD2 Android NAND Development] criszz:
is nor an replacement for magldr is an updated cmr, or an bootloader + cmr inside .i think that after watching video :D
[HD2 Android NAND Development] Beretta93:
OMG are you serious? :eek:

What about 24mb erasing HSPL issue?
[HD2 Android NAND Development] seadersn:
thx for the info :)

k, compiling works, but not the display in fastboot / console / recovery (it's fading out to black display with background lights on). booting android = no problem. i now will try to find some display informations.

and here's the panel info:

<6>[ 1.296966] Init Panel
<4>[ 1.297027] panel type is 10 :board id is 4 : SHARP

radio: 2.15.50.14

hspl: 2.08.hspl
[HD2 Android NAND Development] Satyan:
i was finally able to compile with codesourcery 2009 and i have similar problem of blank console. here is output of panel

<6>[ 1.596343] Init Panel

<4>[ 1.596374] panel type is 10 :board id is 4 : SHARP

<6>[ 2.471557] msmfb_probe() installing 480 x 800 panel

<6>[ 4.388732] msmfb: turning on panel

<6>[ 4.388763] sharp_panel_unblank

thanks ...
[HD2 Android NAND Development] arif-ali:
2 early observations (but will continue debug and test)

PPP doesn't work in cLK, for some reason (the same config works in the other bootloader)

init script doesn't work in the same way as the other bootloader, I have a /bin/sh script which reads a config.txt, which then calls the main init file once it finishes.

with the first point, this worked for me in 1.1, so not sure what has changed, that has caused it not to work, will continue to debug. Tried your kernel, and mine, which is patched, but neither work

I know the second point never worked in the 1.1, either, so something in the code probably needs revisiting for this to work correctly, will have a deeper delve into the code, and see what I can find (this is not a show stopper, but is very helpful to have, I have a workaround that works at the moment)
[HD2 Android NAND Development] seadersn:
arif-ali, any news regarding ppp...? i'm trying to get the sharp panel work and will test it; the kernel is patched (compiling atm), ppp will be the only thing which could stop me if it isn't working :) (charnsingh's cm7 kernel).

i've edited display.h of cLK with parameters (taken out of the kernels board-htcleo-panel.c, hoping they're right :ugly: and this in general is "the right point" to start with...? no risk, no fun :)), it will be compiled rightafter the compiling is done.
[HD2 Android NAND Development] arif-ali:
No, unfortunetely, I don't have much good news on PPP, I tried many things to trying to get it to work, like running "/system/bin/pppd /dev/smd0 defaultroute", but wouldn't get that far "tcflush failed: Bad file number". and then disconnect.

I never got any pppd processes running, if I left eveything alone. whereas in the other bootloader, I get the device created and I see it in "netcfg" as well with an IP.

I will try again, and post logs today or tomorrow, as this my main business phone (and I don't have a test phone), so can't really test while working hours.

good luck on your SHARP screen tests!!! :D
[HD2 Android NAND Development] Unconn:
Seems there is more life in this thread now. I think you would get even more life if you updated the OP more often. Also, currently it does not really reflect the state of the project and urges the user to flash 1.1.
[HD2 Android NAND Development] seadersn:
the tests weren't sucessfull / satisfying: the screen still fades to black with backlit on :( but: its still alive :D i even don't really know where to set the correct parameters for it. this is atm a book with seven sealings; but two of them are broken already :)

hmm, i will have a look at the "ppp issue" too; this week i don't have much time to look at anything, plus i don't have internet atm :( i hope friday to sunday.

good luck everybody!
[HD2 Android NAND Development] arif-ali:
@cedesmith,

Just noticed in OP, there's no mention of using mkbootimg anymore, I presume that this is still required?? and the fact it can't be totally be done by CWM

correct me if I am wrong
[HD2 Android NAND Development] cedesmith:
sorry i didn't had time to respond...

ppp is working great only catch is to use nand_init on init.rc libhtc_ril_wrapper

service ril-daemon /system/bin/rild -l /system/lib/libhtc_ril_wrapper.so -- -d /dev/smd0 nand_init

i'm using gaunner desire build and i had to replace libhtc_ril_wrapper.so with the one from letelma.

i cleaned #1st post a bit. i removed the mkbootimg because there is a nicer way:

fastboot -c "" -b 0x11800000 flash:raw boot zImage initrd.gz

i would like if someone with a sharp panel to test replacing target/htcleo/include/target/display.h:

#ifndef _TARGET_QSD8250_SURF_DISPLAY_H
#define _TARGET_QSD8250_SURF_DISPLAY_H

#define TARGET_XRES 480
#define TARGET_YRES 800

#define LCDC_FB_WIDTH 480
#define LCDC_FB_HEIGHT 800

#define LCDC_HSYNC_PULSE_WIDTH_DCLK 2
#define LCDC_HSYNC_BACK_PORCH_DCLK 30
#define LCDC_HSYNC_FRONT_PORCH_DCLK 2
#define LCDC_HSYNC_SKEW_DCLK 0

#define LCDC_VSYNC_PULSE_WIDTH_LINES 2
#define LCDC_VSYNC_BACK_PORCH_LINES 5
#define LCDC_VSYNC_FRONT_PORCH_LINES 2

#endif

it is the config from kernel and it works on with AUO panel, i'm hopping it will work with sharp too.
[HD2 Android NAND Development] seadersn:
this is what mine showed up after editing ;) and it doesn't work, unfortunately :(

but to be sure, let me show into my edited display.h. back in five mins :)
[HD2 Android NAND Development] arif-ali:
thanks for that,

I do have that same line in the init.rc file, and actually I took out the stuff to do with rmnet at the end as well to make it work with the other bootloader.

OK, will download letama's and see how I go, thanks for that

wrt the boot.img, that's quite good, but for ROM providers, I think to provide a boot.img from that perspective will be better. (but that's my opinion, others may differ)
[HD2 Android NAND Development] seadersn:
yep, it's the same:

#ifndef _TARGET_QSD8250_SURF_DISPLAY_H
#define _TARGET_QSD8250_SURF_DISPLAY_H

#define TARGET_XRES 480
#define TARGET_YRES 800

#define LCDC_FB_WIDTH 480
#define LCDC_FB_HEIGHT 800

#define LCDC_HSYNC_PULSE_WIDTH_DCLK 2
#define LCDC_HSYNC_BACK_PORCH_DCLK 30
#define LCDC_HSYNC_FRONT_PORCH_DCLK 2
#define LCDC_HSYNC_SKEW_DCLK 0

#define LCDC_VSYNC_PULSE_WIDTH_LINES 2
#define LCDC_VSYNC_BACK_PORCH_LINES 5
#define LCDC_VSYNC_FRONT_PORCH_LINES 2
#endif

i will try

#define LCDC_FB_WIDTH 48

#define LCDC_FB_HEIGHT 80

tomorrow, as it shows up this way in the file taken out of charnsinghs kernel.

but more tomorrow; gn8.

edit: hmm...

static struct msm_fb_data htcleo_lcdc_fb_data =
{
.xres	= 480,
.yres	= 800,
.width	= 48,
.height	= 80,
.output_format	= 0,

this i meant. but maybe bu****it :)
[HD2 Android NAND Development] qukla:
Greate!!! Well done!