yashsingh1/xdaforums huggingface dataset:
[XPERIA X1 Android Development] Ronniebiggs:
Thanks for the update! I will try it now.

What I am wondering is how the people here are setting up their SetCPU (for good battery) I myself only set a maximum while on standby, for I set it at like 19MkHz but that took me ages to unlock, so now I put the minimum at 19 MHz and the max at 112 MHz (on demand). Seemed to work and battery life was ok.

As for the new build: I will report shortly
[XPERIA X1 Android Development] whycry:
19 MHz minimum and 112 maximum? Thats way too low..

You basicaly just need to instal setCPU and run it. It will control frequency on its own.

It should be like 652max / 19min. But believe me, that is not the main power consumer. So it doesn't really matter so much.
[XPERIA X1 Android Development] needo:
just put the maximum to it's end ..

minimum to 112 or something like that .. (with normal kernal)

...............to 19 with high performance one (as it support that)

make sure that it is working when you see the freq changing ..

it saves battery by keeping freq. at minimum when the device is not used ...
[XPERIA X1 Android Development] morocomolr:
Test new Build

Some information about the new build:

- Installation: ok (normal kernel);

- Login Google (Gmail, Calendar, Contacts): all right;

- Wifi: ok;

- 3G Data: ok;

- Applications, Foursquare, Twitter (2.0), ES Task Manager, ES Explorer: all right;

- Google Apps, Maps, Marketing, Laitude, translator, Gmail, GPS, Voice Search: all right;

- Facebook Application: clash and close;

- Change wallpapper only after restart ADW (but this problem is common in SuperFroyo);

- Wake up screen show "noise" image, only show correct after touch screen.

I liked the change to SuperFroyo and not come pre-installed applications.

Thanks for the build. :)

Sorry my bad english.
[XPERIA X1 Android Development] needo:
Good news .. but i have tested facebook for about 5 minutes .. it was working very well with no crash !!

- wallpaper problem may be due to ADW application as it's not bug free app till now .. but it has nice themes ...

- what about performance (speed) ?!

thanks for feedback ...
[XPERIA X1 Android Development] Olleman:
Could this harm the battery or at least shorten it's life span in any way?

BTW my phone just turned of after using it from full battery with this new version. W-LAN has been on the whole time and the installation process of the rom was also during this time, when I turned on WinMo it said I had 12% of battery left. So this basically means that we get about 85% of the battery power. Think it's still good though, I should last me a whole day with normal use which doesn't include W-LAN for me. I'm now recharding in android to see how if it will charge to 100% or stop at around 80% as other builds do.

Also, I tried to make a call a couple of hours ago and had no luck, it just told me "call ended" some seconds after I had hit "Dial". After I had recieved a call I could make outgoing calls again...

About speed, I got 18.4 in NeoCore with no sound which is exactly the same I got when using advanced+keyboard_fix kernel from this package with faryaab's ROM.

All internet apps including gmail working like a charm :)

,Olle
[XPERIA X1 Android Development] needo:
i have no idea if this harm the phone or not .. , but i don't think so ..

BTW it is due to The kernal ..

- have you installed SeTCPU .. & changed sampling rate to 250000 ?!

if you did that you'll get 19.5 or more ...

ok thanks for feedback ..
[XPERIA X1 Android Development] morocomolr:
Benchmark new Build

With Fix Kernel Normal:

Quadrant: 591 pts.

Neocore: 21,6 fps.

With Kernel High Performance:

Quadrant: 483 pts.

Neocore: 18 fps.

The normal kernel is better than the optimized kernel. (!?)

- Facebook app, crash and close when I try to open some photos on neewsfeed.

I think it's bug of the app, not the build.

- Launcher Pro change wallpaper no problem. ADW not.

X1a, SD Card 8GB, Radio 1.17.25.09.

Thanks.
[XPERIA X1 Android Development] Ronniebiggs:
I am trying this build with the normal kernel +keyboard fix.

The stability is better than the previous build, but the device does feel more sluggish.

When switching apps or starting them, I often get the error screen that asks me to kill or wait for the app. Battery seems very solid with the current build, been a whole afternoon and part of the evening without ac and still plenty of juice left.
[XPERIA X1 Android Development] electrified:
installing the SuperFroyo Modded Build

:)
[XPERIA X1 Android Development] whycry:
Please change this ugly status bar to default one.

This is probably not the first priority, but you can easily access themes from other builds.

You could change it to something like this:

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

heres full theme. I do not understand rom building so i cannot help with this. But maybe you are able to combine e.g. this theme to your builds?
[XPERIA X1 Android Development] needo:
What .. i can't believe 21.6 ?!!!!!! really it is a great news .. !!!

i was busy in developing these roms so i didn't try to see benchmarking ..

i was searching for smoothness and stability ...

please morocomolr give me some more info ..

was it the normal with keyboard fix .. ?!

have you changed the sampling rate .. ?!

thanks morocomolr ... :)
[XPERIA X1 Android Development] needo:
ok thanks for feedback .. i haven't experienced any of these errors ..

nice to hear that about the battery ...

ok thanks too much for this help .. this really great theme ..

but the problem is that the time in this build is colored by default to black ..

& changing it's color will take much time from gingerbread & Sense developing ..

BTW .. i will work on new build more stable and faster FROYO build & try to change the clock colour ...
[XPERIA X1 Android Development] electrified:
just a quick question, how to get the old launcher like the one this pic: (the launcher on the bottom)

and the menu, not this right left scroll, i want the old up down scroll, if that is possible

thanks in advance
[XPERIA X1 Android Development] needo:
ok would you like to wait for me to change the theme .. ?!

i'll do that today ...

or you want that now ?!
[XPERIA X1 Android Development] electrified:
can i install that on my own? or do you have to change something in the installation files?

EDIT: on the picture above, without the black bar on the bottom, it should be transparent, as it used to be until now
[XPERIA X1 Android Development] needo:
SuperFroyo - NEW THEME

Theme changed .. Fonts .. everything changed ..

hope you love this theme ..

To make it fully themed ..

change the adw theme to the one provided ...

Delete the old npkinstall folder .. and put this one ..

and make a fresh installation ..

http://www.mediafire.com/?8ga038n7vlo4l8v
[XPERIA X1 Android Development] Ronniebiggs:
I forgot to mention something!

I experienced a loss in carrier at one point. The system still showed a 3G connection and my carrier's name, but my gf tried to call me and she could not reach me. It also seemed that my whatsapp messages were not delivered. I could easily reset this to switch off the radio (flight mode) and then reenable. But might be something worth to mention.

Also I got a low charge error at 50% battery (in winmo) and my phone turned off. So although te charge was good (standard SetCPU settings), below 50% it is error prone. But I guess you already mentioned it that it is a common problem with the current kernels. Fingers crossed for a fix soon from kernel developers :)
[XPERIA X1 Android Development] Olleman:
Had some problems yesterday with this build :(

When in the middle of recharging I tried to open GoSMS and the device suddenly rebooted. After this it took 3 attemps at starting Android again before it would boot. The 2 first times it rebooted in the middle of the android booting process. When I finally got Android running again I was constantly bombarded with msgs like "Unexpected shut down of android.processes.acore" these pop up all the time now even after a couple of reboots making this android install unusable.

Any ideas on what could be the cause of this needo?

,Olle
[XPERIA X1 Android Development] manishsharmasz:
+1...i got the same issues.

I am using the fixed kernel. overall great experience.

I also found the issue of not being able to see the incoming call info if the phone is on stand by...but i am able to answer the call using the hardware key.

Thanks for the great work.
[XPERIA X1 Android Development] whycry:
SuperFroyo Normal Fix without Keyboard fix, I experienced my device not waking up few times. Sometimes it just shows this ugly artifacts screen, which is acceptable, but most of the times screen doesn't even wake up.

I'm considering turning back to CyanogenModded, which despite numerous bugs was more stable.

Electrified, I'm not sure if thats what you're asking but isn't that a difference between ADW and LauncherPro ? Such icons are with LauncherPro if I'm not wrong.

Needo, do you have access to other skins? This one is.. dimplomaticaly speaking, childish :)
[Nook Color Themes and Apps] DatterBoy:
I've searched all over the web for this and all over XDA and there has been nothing conclusive. Hoping we can find something usable here.

Basically, market hangs on starting downloads and does not progress. I can tie the failure only occurring after I install the V1.1.0_r2 update and ensuring top to bottom I have met all the requirements. I work on about 4 NCs for family members and one of our has gotten V1.1.0_r2 working with Market fully functional. 2 of the NC's fail Market and have not tested the 4th since generally, only Market fails but all other functions on the NC work perfectly.

My system:

- 1.0.1 Auto Nootered

- Gingerbread keyboard

- Sideload hack

- Telephony Hack

Here are the symptoms I have found:

- All worked fine on 1.0.1

- Initial install of 1.1 worked for a bit but crashed on adfree host file update and did not work thereafter

- First notice was on Facebook download

- market.android.com can still push installs

What has not worked:

- Clearing Market data

- Clearing download manager

- Starting and stopping downloads

- ejecting or unmounting SD card

- fixing permissions does not work

I've seen this happen on 2 different Nook Colors but not on a 3rd and my personal SC I've repeated the failure across 3 complete factory wipes and resets with the same end result of a working Market that gets stuck on Download Starting.

Any ideas?
[Nook Color Themes and Apps] khaytsus:
You don't have an Android phone, do you? This happens on every device recently, something with the market, has nothing to do with the Nook.
[Nook Color Themes and Apps] DatterBoy:
I disagree. I have a DINC and several nooks and I can force this to happen on the nook where the market works fine until I update to 1.1
[Nook Color Themes and Apps] iconoclastnet:
I was having the same market download behaviour you describe the first few times I attempted a 1.1 upgrade. The thing that finally did work for me was doing a complete wipe of all data, all cache and complete factory reset, even back to the stock recovery partition. Then walked through the upgrade setting things up by hand and not restoring anything from backup. The market has worked fine for me ever since.

You mentioned doing complete factory wipes and resets, and if they were this kind of thorough wipe-everything back to out-of-the-box state reset and not just a restore from an old backup... then I don't know what to tell you. I assumed there must have been something buried in my data that was somehow causing the problem in 1.1, but maybe I just got lucky that last time.

fwiw, here's what I did in case you spot any differences that might help.

- "Erase and Deregister Device"

- wiped dalvik cache and cache partition from clockwork recovery

- used dd to rewrite boot and system partitions to stock out-of-the-box state (1.0.1 version)

- rebooted and went through B&N "first time" setup process, registered with my B&N account.

- auto-nootered

- rebooted and went through google's "first time" setup process.

- performed the whole youtube -> gmail -> google talk -> market setup dance

- installed clockwork rom manager from the market

- followed the 1.1.0 upgrade process

- rebooted and tested everything (including the market)

- started manually loading books and apps back on, avoiding backups made before the upgrade

I don't know if this is of any help, but it worked for me. And I hope someone figures out where the problem actually is before the next B&N upgrade, because I'd rather not have to do all that again.
[Nook Color Themes and Apps] DatterBoy:
I did the same thing as you but I did not wipe the dalvik cache. Weird thing was that I was able to get market to work immediately after the update but it stopped working after a bit. Couldn't tell what triggered it and I was only doing hard installs from market. No backups.

I restored to factory via 1.0.1 image several times to try and isolate the problem. It was not decisive since I do have one nook that competed all updates including an overclock and all functions seem to work perfect including market.
[Nook Color Themes and Apps] capnron65:
issues and FCs with V1.1.0_r2 update

Keep in mind I am a noob at all of this and am barely able to keep up with you guys, but I had problems with FCs and general instability after using the V1.1.0_r2 update and flashing one of the more "stable" overclocked kernals. In general I didn't like the direction my NC was heading and decided to begin again.

I went back to stock using this: http://xdaforums.com/showthread.php?t=945838

and then applied this: http://xdaforums.com/showthread.php?t=922870

and so far everything seems stable.

The people on these forums amaze me with their technical know-how.
[Nook Color Themes and Apps] paleh0rse:
Having the EXACT same problem here after doing a wipe and upgrade to auto-nootered 1.1.

After successfully downloading and installing roughly 20 apps, any new downloads now stop at the "Starting Download...." stage. Ive also tried everything short of replacing vending.apk to fix the problem -- nothing has worked. Ill be trying that next... I'll report back after.
[myTouch 3G Slide Q&A, Help & Troubleshooting] Virus1x:
Flashing a New Recovery EXAMPLE 3.0 for clockwork ported to SLIDE.. breaks S-OFF?

example from this... thread

http://xdaforums.com/showthread.php?t=933131
[myTouch 3G Slide Q&A, Help & Troubleshooting] etu_aty:
Nop it wont break your s-off, actually you need s-off to be able to flash a new recovery...

the only way u can break it is by changing the bootloader which is done by unrooting, re-rooting or flashing a stock rom (esprimg.zip) so yeah, flash it and try it dont worry ;)
[General Topics] mirzaei1:
Hi my friends

I have searched the forum several days about "streaming audio to mono bluetooth headset in wm 6.5" but I did not find a solution that works for me.my device is acer betouch e101 with windows mobile 6.5.

if anyone have a solution,please help me.

best regards
[General Topics] Hookani:
There is an app that worked for me on a Touch HD. I think it was called BTaudio.

Ho'okani
[General Questions and Answers] mbroch89:
I've tried rooting my htc aria many times and I can never get unrEVoked to recognize my phone. I've tried installing multiple bootloaders but none appear to be any different than the others. I have no idea how to uninstall HTC sync so I fear that may be conflicting with it. Basically I'm just wondering if any more experienced users had any insight. Any help is greatly appreciated.
[HD2 General] kevinwebster83:
Hi All,

For the past few months I've been running a DFT NAND build of Android. Yesterday, the phone was running extremely slowly with some odd behavior in the Android menus. When I restarted the phone, loading got as far as the DFT splash screen but then nothing else would happen.

I have since used MAGLDR (1.11) to attempt to boot a fresh Android image from SD card but this hasn't worked. Have managed to use the USB Loader to attempt to flash another NAND build (both Android and WP7) but even though the download process completed, this still didn't work and am stuck in MAGLDR now.

Have read through the forums here and have tried most (if not all) of the suggestions, however nothing seems to be working.

Can anyone offer anymore advice?

Thanks,

Kev
[HD2 General] paradox2313:
As MAGLDR gets removed if you flash a stock winmo rom I suggest you to try that!

Before you install the winmo rom you can also use Task29 to completely wipe the nand.

good luck
[HD2 General] kevinwebster83:
Thanks,

I shall give that a try this evening.

Kev
[HD2 General] kevinwebster83:
Unfortunately none of the suggestions have worked. I'm unable to flash a stock WM6.5 ROM as the RUU doesn't detect the phone.

The device does show up in Windows as a Microsoft USB Sync device, however.

Task 29 does not work either due to the same problem.

I've attempted to flash a new Android ROM release but when the phone reboots, it gets stuck on the green HTC logo screen and won't proceed any further.

I don't seem to be able to get MAGLDR 1.13 on the phone either, as DAF.exe complains about some "Config load failed" error.

Any other suggestions?

Thanks in advance,

Kev
[HD2 General] ASCIIker:
*sigh*

you need to read up on "how to flash stock rom from sd card". no need for RUU i believe; sd card method involves copying a file extracted from the stock RUU and placing it in the root of your sd card and letting bootloader detect and flash the file. search for a tutorial or see the stickies.

once you've done that, make a special note about the part that says you need to boot into bootloader (hold down volume down + turn on phone + keep holding volume down until a 4-color screen appears). i suspect you are not doing this step, this is why windows, mtty, etc are unable to detect the device.

if you have already done the above, ignore my post :D
[HD2 General] kevinwebster83:
*sigh* too.

I've already tried flashing from the SD card but I have the same problem. I get to a green HTC loading screen and nothing else happens. I just get stuck in a reboot to MAGLDR and try again loop.

I've read through plenty of posts on flashing custom ROM's and troubleshooting but nothing has helped.

I don't get a 4 colour screen when holding down VOL-DOWN and the power button, the phone just goes into MAGLDR.

Kev
[HD2 General] kevinwebster83:
Just to add to that, Windows DOES detect the device but the RUU doesn't. Only the DAF applications find and can talk to the device.
[HD2 General] jigners:
follow me

1. is the battery have enough jiuce? what HSPL you use? hope its HSPL3 2.08HSPL

2. bootloader . . . .
[HD2 General] kevinwebster83:
Thanks for your post.

Plenty of juice in the battery.

I believe it is HSPL 2.08 (well, whichever allowed me to get Android on the thing in the first place)

Bootloader what?

Kev
[HD2 General] ASCIIker:
getting into boot loader (4-color screen) is the key to the whole flash with sd card method.

keep trying. read on how to enter bootloader.

i can remember a few ways.

DEVICE IS ON

1. if phone is already on, hold down volume down (keep it pressed HARD)...don't let go of it!

2. push the little reset button under the battery cover. don't let go of the volume down button!

3. don't let go of the volume down button until the 4-color screen appears.

DEVICE IS OFF

1. remove the battery. reinsert it after a few seconds.

2. hold down volume down (keep it pressed HARD)...don't let go of it!

3. tap the end call button and don't let go of the volume down button until the 4-color screen appears.

remember, entering bootloader is the key.

EDIT: it is better to ensure you have sufficient battery. however, flashing via bootloader SKIPS the battery level checks.
[HD2 General] jigners:
in post 4 you noted you tried task 29 but was successful

you are not even familiar with bootloader, ??? makes me wonder:confused:
[HD2 General] kevinwebster83:
I'm very familiar with a bootloader, your "bootloader..." comment confused me.

Task 29 was unsuccessful. I've read in a number of posts that you can use Task 29 and start from scratch back at the original bootloader (rather than MAGLDR) but this obviously isn't the case.

Holding down the VOL-DOWN key does nothing other than get me to MAGLDR, which is what happens even if I don't hold any keys down.

I fully understand that the key is entering the bootloader, nothing seems to let me get there.

Kev
[HD2 General] jigners:
this is how i enter bootloader from magldr

remove battery

reinsert, leave device off

hold and continue to hold volume down

briefly press power/call button

now your in bootloader

this will show your hspl
[HD2 General] kevinwebster83:
Battery removed

VOL-DOWN held

Powered on

VOL-DOWN still held

MAGLDR appears

This isn't my bootloader and doesn't show HSPL
[HD2 General] jigners:
if you are now unable to enter bootloader

in this manner, there is only one thing i can think of

you got a bricked device,

you might get some help if you post your querry in the

HSPL thread, or PM cotulla and team
[HD2 General] kevinwebster83:
I'm of the same opinion; it is virtually bricked.

The stupid thing is that if I select Android Flasher from MAGLDR, I'm able to flash a different version of Android to NAND but it just won't boot.

Will try a different forum.

Thanks,

Kev
[HD2 General] jigners:
i discourage you to try another forum

if you got hold of HSPL, task 29 and other stuff here in xda

then this is the best place you can be helped

try to post in HSPL thread

or PM ClydeB1, or bepe.

if they cant help you

then i highly doubt if anyone in this world will;)
[HD2 General] kevinwebster83:
Which HSPL thread would you recommend?
[HD2 General] jigners:
the original by bepe, cotulla and DFT
[HD2 General] backlashsid:
I have the same problem...does the HD2 charge itnself in Magldr ?
[HD2 General] T-Macgnolia:
No you have to have a ROM, Android or WP7, booted up and running to charge with MAGLDR. Some will tell you that you can charge if you go to the USB Flasher option in MAGLDR, and yes it seems you may get some very small charging from this. In my opinion it is a waste of time and potentially detrimental to your battery. I did see you edit in your thread about flashing WP7 so you should be able to charge now.
[HD2 General] thehumble1:
buy an external charger on eBay for $5. Charge the battery first. You said that you have the same problem but the OP had a charged battery. Can you boot to the HSPL (multicolored) screen?

If not, I'd make sure your button still works properly. Make sure it's clicking up and down. You might even want to pull the button and try to work it manually. Make sure you are holding it down when you start the phone and keep it held down. Don't restart phone. Unplug USB, pull the battery, hold down the volume down button and then reinsert the battery and push the power button.

If you can't get to the HSPL screen, you're kind of messed up.
[HD2 General] backlashsid:
after all these efforts...i still cant make it to the bootloader !

funny how WP7 works via NAND but ANdroid doesnt...tried flashing the DFT Stock ROM and other DAF ROMS

but all of them get stuck in the android boot screen and DFT logo ! ???:(:confused::confused::confused::confused::confused::confused:
[HD2 General] mally2:
may be try this

http://xdaforums.com/showthread.php?t=893618&page=260
[HD2 General] Le Brun:
I am very curious how and if this problem has been solved as I seem to have the same problem.

The phone doesn't enter the bootloader and goes directly to magldr 1.13
[HD2 General] Destroyer90:
if you ain't flash from bootloader try to change the sd card..i got the same problem as you
[HD2 General] Le Brun:
Could you explain to me how to do that?
[Desire Q&A, Help & Troubleshooting] commando0:
i have desire rooted foryo 2.2 with unrevoked 3

i have access to system app folder using root explorer and mount as r/w.....

can i paste and remove files directly from system/app folder in phone using root explorer ....

can i delete apps like google maps (older version is there but i have installed new one )

i want to replace my stock music app with DHD music app

so simple copying pasting will work or things will get messes up