yashsingh1/xdaforums huggingface dataset:
[Legend Android Development] Spoochy:
Ok Neon... now we have learned something new today also.. :p

it was the Radio.... all working fine now after the radio update... signal is almost on top.

You can put a little "watch out msg" on your first post so you aint getting similar questions. :p

Once again... NICE SUPPORT!!! Keep it up..

br
[Legend Android Development] Neon87:
Ya sure you are right!

Thanks!
[Legend Android Development] manudas:
Hi Neon87 again!

You didn´t disabled the perflock by default in the last 0.21 rom, didn´t you?

I say that because in setcpu I cant raise any frecuency under 245 Mhz if I dont use the beta feature of perflock disabler that comes with setcpu. Using it there is no problem!

Keep doing this great work!
[Legend Android Development] Neon87:
Nope 0.21 is only sync fix.. Right now I don't think to include the kernel by default.. i want to be sure it is stable and fast first..

Yes right now you have to disable perflock with setcpu (every time you boot)..

I'm working on it..
[Legend Android Development] Neon87:
Fixed! It wasn't a freeze (I thought the same).. it was the freq table that scale to 19 mhz..

In v2 perflock is disabled by default so you can set setcpu onboot underclocking or overclocking without use perflock disable every times..

Try kernel v2 in first post and feedback please!
[Legend Android Development] Vuska:
Please let me know... how to update Radio.... :confused::confused:

if any... step by step.

Is updating Radio will losing my root ?

Thank you
[Legend Android Development] Learners Lisence:
neon, sorry to be encroaching into your territory. I was wondering since your rom is based on the rom i am presently using, can i use kernel-update-v2.zip ? And if yes what do i have to be careful about. Im also interested for underclocking to maximize battery life. I havnt found these ideas anywhere else in the legend forum so posted my queries here. Thanks.
[Legend Android Development] Neon87:
Kernel is based on HTC sources and it works on all 2.03 for sure.. I don't tried it 2. 05 but it should work well..

You have to be careful because the overclock could damage your device.. personally I don't like it and I don't use it but since a lot of people asked I try to build one..

Underclock is a good idea and you can do it easily with this kernel..

You need setCPU!

@vuska

Radio has nothing to do with root you can update it without losing it.. but be careful to upgrade it!

I'll write few words on first post asap..
[Legend Android Development] Vuska:
Bro Neon87,

I have a file called legend....radio.zip, i see a radio.img in it.

Is it safe to install it from Rom Manager ?
[Legend Android Development] Neon87:
From the thread by lyca, linked few post before, you download that file and in recovery or using Rommanager you should install it without problem.. before do that go to bootloader and check if the radio version is older and so if you have or not to install..
[Legend Android Development] manudas:
Hi Neon87. I tried your new kernel and found a possible bug. I tried with rodrigez style rom, that I think is 2.03 based. The problem is that I can´t turn on wifi now. It´s says to me: It was not possible to start the wifi function.
[Legend Android Development] Neon87:
If WiFi doesn't work is because kernels extraversions aren't equal.. you have to install also modules of neonmod kernel..
[Legend Android Development] manudas:
Ok, I´ll try with your full rom later
[Legend Android Development] manudas:
Nice!! It looks to work fine the kernel with disabled perflock, but... why did you disable the kernel to underclock to 19 mhz? It´s not a good idea to get a longer battery life when the phone is suspended...
[Legend Android Development] manudas:
Another problem:

Flashing the kernel form Android system recovery, it gives me this error:

Verifying update package...

E:Missing file:

system/lib/modules/ramzswap.ko

E:Verification failed

Installation aborted.

I had to flash form Rom manager instead
[Legend Android Development] Neon87:
I wrote in the first post that you have to install it with Rom manager.. I didn't flash it with cert.. use clockwork recovery if you can't use Rom manager..

Btw I disabled 19 mhz because it's too slow and use it is like a freze..

I made some experiment and trust me 128 mhz is pretty good..
[Legend Android Development] cbanbury:
Thanks for the new kernel! Working great fof me.

Powersave governer really seems to help battery life in standby :D
[Legend Android Development] Learners Lisence:
Thank you Neon for your advice.

I havent tried to flash your update zip yet because i got cold feet. there isnt enough written about underclocking.i followed manudas and your conv....cbanbury tried it on his desire.....

'Change the governor to "performance" (which means it will always use the highest frequency in the range), and start incrementing the max up from 528MHz,...." from zanfurs post...is it applicable for underclocking ?

i dont want to change my rom yet just for this feature.....your words are however appreciated....thanks again
[Legend Android Development] Neon87:
Underclock is easy.. overclock too but it's unsafe.. the kernel by default use the same frequency of HTC (min freq a little bit lower)..

You need only setCPU.. is extremely easy to use.. you can set what freq use and more..

Btw it's not a problem if you don't want to try it..
[Legend Android Development] cbanbury:
Ha, apparently my sig needs updating, I have a legend now. Actually had two desires this year though (don't ask lol)
[Legend Android Development] Learners Lisence:
cbanbury,im sorry, i missed some of your earlier posts.

Neon, going by the number of views in the first post the kernel idea is selling like hot cakes considering our community isnt all that big. Its a popular development. Id like to use it of course ! Thanks.
[Legend Android Development] Neon87:
Updated kernel V3:

BFS and ext4.. BFS is a new scheduler that replace that included with Linux.. You phone won't fly but i think it will be a little more reactive..

Really thanks to punk.kaos for his help!

PS

You can try all benchmark you want but performance will be the same.. Only reactivity will be a little better..
[Legend Android Development] xennr3:
hi,

I'm now at 0.2 and waiting for 0.3 for testing the new under/over-clock kernel :P Do you have some new ideas for 0.3? ^^
[Legend Android Development] stegg:
hi neon,

i installed your V3 kernel this morning and it's working... although i didn't find any change in benchmarks! :P

just one glitch: at first boot, setcpu2.02 shows 19/245 as max/min clock, and first boot is somewhat slow but I don't think it was running at 19mhz because... it booted!

then i slided the cursor to 748 mhz but setcpu showed no change; only 729 mhz works.

thus, working speeds (on my legend) are: 729, 711, 600, 480, 245 mhz.

anyway perflock is disabled, and this is good as I can set 245/128 mhz speed in screen off, thus saving a lot of battery power :D
[Legend Android Development] Neon87:
I'm working to fix it.. Anyway it should go a little bit faster thanks to bfs scheduler..

I don't know yet what I'm gonna to do with 0.3..

For sure I'll not include an overclocked kernel but the kernel with standard freq with perflock disabled so you can do easly underclocking!
[Legend Android Development] xennr3:
Okay, so 0.3 will not be released the next few days? Then i'll flash 0.21 later :)
[Legend Android Development] Neon87:
I'm working on kernel.. Install 0.21 and follow the kernel i upload in first post..

0.3 will be released but I have no idea when.. :)
[Legend Android Development] xennr3:
Already downloading 0. 21

:-)
[Legend Android Development] Learners Lisence:
Neon I think you have started a good trend at the forum by releasing kernels for clocking the cpu along with your rom with option.

I thought if i was going to take a chance why not the big one so tried the 806 kernel by dumfuq for legend. Things are pretty stable and Im also toying with overclocking the cpu. Its going to take time to figure out the best possible settings for ones own purpose. But i will be trying out your kernels too.

Thanks.
[Legend Android Development] Neon87:
I make a lot of tests with different benchmark tools and I think that graphics performance aren't better at all but if you consider setcpu test you will notice a good improvement of speed.. So benchmark aren't reliable at 100%..

Btw I think that oc on a phone remain a learning stuff and I continue to tell that it's better don't use it..

I think I'll concentrate on underclock and battery save since next version..
[Legend Android Development] santhy:
Hi! I'm new in the scene, but I'd like to say some things about this rom:

This is my first Android phone, I rooted it less than a week ago, and I have tried already some roms.

I could notice that in your ROM (with modded kernel V3) the phone starts actually at 480MHz and not at stock 600MHz. This could make booting somewhat slower.

Besides, the 'top' POSIX utility, which can be run with some Android Terminal Emulator for the phone or with ADB via USB bridge is a bit less "cute" than the one found at RodriguezStyle.

In the other one, top refreshes the screen. In this one, top creates a lot of newlines, not refreshing, and making the terminal in my mac scroll down a lot.

Another thing:

I have setCPU installed.

Let us set some settings:

Default.max = 718Mhz

Default.min = 128Mhz

ScreenOff.max = 480Mhz

ScreenOff.min = 128Mhz

On ScreenOff with custom kernel it will stay (randomly) at 718Mhz (and it should not!), and if at that moment you power on the screen, the phone will freeze and force restart itself.

Anyway, the ROM is so good, the custom kernel rocks :P
[Legend Android Development] lollazzo:
i want to try this rom,but I have a doubt : if I brick USB ,always i can repair the phone?
[Legend Android Development] yingchai:
can you re-upload the NeonMod 0.21 zip file again? the download page re-direct me to download to another file...thx
[Legend Android Development] Neon87:
I've got huge problem with internet connection.. it's 2 days I can't connect..

Please someone who as 0.21upload it somewhere..

Ps asap i'll reply to all and all pvt.. sorry..
[Legend Android Development] xennr3:
NeonMod_0.21.zip
[Legend Android Development] Neon87:
Thanks a lot!
[Legend Android Development] xennr3:
i found a bug lol

when i'm in astro and trying to put a picture as background by pushing on the file i get a "force close loop" ^^ i had to restart the phone :D
[Legend Android Development] santhy:
Another bug: incredilight (root app for using the camera LED flash as a flashlight) force close. Will never work.

Idk if it is because of the kernel, the su binary or what.

By the way, whenever Superuser tries to update the Su binary the phone restarts and it does not get updated.
[Legend Android Development] manudas:
Reporting problem:

Under settings, in personalice, scenes I get a Force Close

I searched and I didn´t find it posted. Sorry if it was reported before.
[Legend Android Development] xennr3:
i think it wasn´t mentioned before, but i can confirm this, same here.
[Motorola Droid and Milestone Q&A, Help & Troublesh] chadloel2010:
i have a motorola droid and it is rooted.i flashed a new rom and then i flashed sprecovery,i let it run its course and i disconnected the phone.when the phone turns on it starts up and then a red light comes on and my phone says please connect charger.it keeps saying android process is not responding and then the phone shuts itself off.ive tried to boot it into recovery mode and do a restore,it keeps giving me an error that says nandroid exited with status 20 and its also not reading my sd card.can somebody tell me whats happened and if it can be fixed???please and thank you:)
[Motorola Droid and Milestone Q&A, Help & Troublesh] aerdely:
Well, seems as if you need to reflash or restore because of bad flash. If you try flashing again make sure you wipe data and cache. As far as not reading sdcard I have same problem not sure why but when I'm in recovery and I choose install zip which I used clockworkmod recovery, if it fails then it reboots automatically after couple seconds not sure if this happens with sprecovery. After sdcard mount fail it shuts down and reboots so before it reboots I pull the battery and wait a minute or two before trying again. It may take me 3 to 4 times of doing this but eventually it will mount sdcard in recovery. I recommend keep trying till it allows you to apply recovery file and then flash to either clockworkmod or sprecovery which ever one you not using and then flash back to the one you want. I'd also recommend try if after all this you flash rom again and same thing happens redownload it and try again. Good luck.

Sent from Droid using, Sapphire v1.0.0/ 928Droid Black Glass 2.2 Theme/ Sholes 1.0 Ghz 7 Slot Kernel.
[Motorola Droid and Milestone Q&A, Help & Troublesh] fadimck:
Please install Advanced Task Manager and from the setting use what ever setting that might suite you.

For me i use the following setting:

Auto Kill Level --> Safe

Auto Kill Frequecny --> Every One Hour

Security Level --> Meduim

With the above setting, i didn't face any performance problem and reduced reboot frequency (General Problem in the Android).

Feel free to ask any question and I will be ready for you
[Motorola Droid and Milestone Q&A, Help & Troublesh] darukhan:
Please note, that there have been wide reports of people having issues with various task killer apps consuming excessive amounts of battery life when used on a Droid with Froyo.
[Motorola Droid and Milestone Q&A, Help & Troublesh] fadimck:
Okay, I didn't know this info as I've Milestone with stock OS 2.1
[EVO 4G Q&A, Help & Troubleshooting] xboxhacker:
I have my EVo on MetroPCS, and i have been trying to get MMS and other things working for a while.

For the most part i have had everything working 100% at one time or the other, but most things not at the same time, due to kernel and apks.

I wrote a guide to getting the MMS working, but it relies on Ava' v2RC3 ROM, witch is a port from the incredible.

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

I was messing around with a stock Fresh 3.1 ROM, i rebooted to recovery and pushed the Mms.apk from the incrediable to the /ssytem/app folder, then rebooted the phone.

I started the messaging app.... it now looked like the MMS app from the Ava_v2RC3! So i tired to send a MMS to my email address....it sent!! SO to recap, OEM EVO ROM working 100% + the Mms.apk from the incredible + Token419's metrov3 flash = working MMS!!

BUT, now here in lies the problems:

When you send a message on the OEM EVO MMS, it takes you to the thread page so you can view the conversations of that person and you.

With the MMS app from the incredible it goes to "loading"....and hangs, it does nothing...

BUT the MMS is still sent

. Now if you open the MMS app and click on a person to view their conversation thread, it says "loading"....and hangs....

SO i think we need a custom Mms.apk from the incredible for the EVO for metropcs/cricket users!!!!!

I want to know if anyone out their can modify the Mms.apk to work on the EVO.

Or point me in some direction...

It just needs to finish loading the threads...thats alll...

If you compare the Mms.apk from sprint and the Mms.apk from incredible, the sprint is bigger. I have decompiled both files, but now i have no idea what i am looking at.

Now before we get in to posts about "did you try..."

-I tried Fresh and OMJ Froyo ROMs, both had same results from above.

-I tried pushing the com.htc.recources.apk .... framework-res.apk ... Rosie.apk from the incrediable to the phone (with working MMS), rebooted, still same results from above.

-I tried building a ROM from the Fresh and OMJ ROMs, and packing the framework files into it. Still same results from above.

-Downloaded handcent form market... was NOT able to send MMS at all with handcent. so i uninstalled it, then was able to send again.
[EVO 4G Q&A, Help & Troubleshooting] token419:
i had the same results, this seems to plague not only the Evo but also the Hero Sprint stock MMS.apk's, i loaded a sprint port on my eris and had the same issue, swapped in an Mms.apk from a verizon rom and had the same results.

I too have been decompiling both Mms.apk's with the apktool and am going to run a dif later on the files to check for differences.

one thing i saw was some references to some sprint frameworks, im going to dig and ssee if i can find them as well.

A resolution seems to be simply swapping the mms.apk file, BUT i think the issue is actually in a framework file, and that swapping the mms.apk simply does not point to that framework that is not working properly on alternate carriers.

we will have to see :)
[EVO 4G Q&A, Help & Troubleshooting] xboxhacker:
@token:

But i took the com.htc.resources.apk and the framework-res.apk from the incredible, pushed them to the EVO, still with same results. Did i miss a framework file??
[EVO 4G Q&A, Help & Troubleshooting] chavonbravo:
All you need is Mms.apk from any aosp Rom. Bugless beast, or cyanogenmod for example.
[EVO 4G Q&A, Help & Troubleshooting] xboxhacker:
Tried it....did not work. I tried one from CM and one from AVa.

When you goto send a MMS, it seems to do nothing... and the send button gets grayed out.
[EVO 4G Q&A, Help & Troubleshooting] token419:
i saw somewhere about a code change that needed to be done from hero rom to port to g1, but i cant find the thread with the code change in it anymore.

but pushing the raw frameworks from another rom will surely break the rom im guessing. i would stay away from that if at all possible :) but its definately worth testing out, to find where our issue is.

unfortunately my time will be very limited for the next month or so, have quite alot of stuff to attend to.
[EVO 4G Q&A, Help & Troubleshooting] xboxhacker:
As suggested by chavonbravo, i tired the Mms.apk from the supersonic AOSP ROMs (for my EVO) With NO luck :(

So i thought, how about a Mms.apk from cyanogenmod for a Verizon phone...

It worked well, send and receive MMS, but sometimes it would fail on both.

Now the strange part, when you send a MMS with the cyanogenmod Mms.apk for the incredible, it will attach a XML file before the image. i think it was a SMIL.xml. So if you send a MMS to another mobile user, they cant see the image, because of the XML file. If you send the MMS to a email address, its ok, because you get the image and the XML, and you can open just the image.

Why is it sending the XML file too?

Now even stranger, after useing this method, i downloaded the handcent app. It also would send the XML file first. SO i then deleted the Mms.apk (adb shell rm /system/app/Mms.apk), rebooted, and the handcent STILL sent the xml......

getting closer... :)
[EVO 4G Q&A, Help & Troubleshooting] token419:
I am not an expert on the MMS protocol(s?) but i believe the XML file IS THE MMS, and the picture is the attachment from the XML if that makes sense.

I believe the XML file contains the recipient/sender/subject/text/ and what attachments there are to the message, the picture is then the attachment and called upon by the XML file.

Definitely a good find and im still working on this as well, my time is just limited but i have a few things i want to try.

one thing i noticed when i unpacked a sprint based mms.apk file was that it was calling on the specific hardware (hero) in this case, and since the app i dropped in was desirec (eris) it didnt match up, im going to go through and edit that to point to the proper frameworks to see if i can at least get it working on my phone, but that could explain why the incredible didnt work on the evo.

Im also toying with getting a AOSP or Cyanogen one together, since that would be legal to distribute i belive, even if i do find a solution, it will be instructions, as i dont want to edit/repackage/redistrubute proprietary files without consent, which i dbout we would get since we are taking their hardware/development to use on an alternate carrier.
[EVO 4G Q&A, Help & Troubleshooting] token419:
i found this:

http://www.w3.org/AudioVideo/

which points to SMIL, which is the spec for MMS messages i belive, i belive it gets put into an XML, then wrapped with SMIL, which links to all the stuff in the message.

I could be way off, but im pretty certian the XML file its sending is actually the MMS message itself.

I think our problem is still within the sprint mms.apk or an associated framework, because i think its still trying to interact with sprint's servers and not our alternate carrier.
[EVO 4G Q&A, Help & Troubleshooting] xboxhacker:
Nope...just images info.

here is a sample of the SMIL.xml file....

<smil>
<head>
<layout>
<root-layout width="320px" height="480px"/><region id="Image" left="0" top="0" width="320px" height="320px" fit="meet"/>
</layout>
</head>
<body>
<par dur="5000ms"><img src="screenshot_3.png" region="Image"/></par>
</body>
</smil>

I saw that too, when i unpacked the sprint one.
[EVO 4G Q&A, Help & Troubleshooting] xboxhacker:
Now this is funny... Incredible users putting the EVO Mms.apk on the incredible and it works fine!!!! LOLOLOL

http://xdaforums.com/showthread.php?t=754832
[EVO 4G Q&A, Help & Troubleshooting] chavonbravo:
Also, you can't put an Mms.apk from 2.2 aosp on a 2.1 rom, and vice versa. The bugless beast Mms.apk works great for the stock 2.1 rom.
[EVO 4G Q&A, Help & Troubleshooting] xboxhacker:
FYI...

Bug report:

Using the stock Mms.apk from a Incredible, you can not send a MMS with Wifi is on. It might be ROM specific, i am using Fresh 3.0.
[EVO 4G Q&A, Help & Troubleshooting] token419:
Just curious, in your APN, do you have the type set to MMS?

If so that should tell it to send MMS via your mobile network even if you are connected to wifi.
[EVO 4G Q&A, Help & Troubleshooting] xboxhacker:
Yes it is... i am using your V3.5 (also tired v3.0) Now when i used a ROM based on incredible ported to the EVO, it sent fine with your v3 and sent fine with WIFI on.
[EVO 4G Q&A, Help & Troubleshooting] token419:
im almost certain its a framework issue, and the reason the incredible mms is working is that its not calling in the framework that sprint has, its a bandaid so to say, not a resolution. Im assuming if you went through the Mms.apk from incredible and aligned all the framework calls that it may work, with wifi, but that may break the Mms again.

I just havent had the time to do a dif on the sources to compare where there are differences yet. but i think that will provide us some good information as to where the issue is.

Also im hearing reports of the paid Mms.apk not sending some pictures correctly, he can send anything that has been sent to him previously (i.e. resized properly) and also can send pics resized from his pc, so even the paid solution Mms.apk needs work. Hopefully we can nail this down and potentially even get the settings 100% for our carriers so that it will resize anything and work well :)

Alright, movie time, then bed, then work, then vacation!! Ill check back in a few weeks when im back :)
[EVO 4G Q&A, Help & Troubleshooting] xboxhacker:
Then why are the Incredible guys putting the EVO Mms.apk on the incredible and it works fine?

That would tell me that that, both Mms.apk are calling the same thing....
[EVO 4G Q&A, Help & Troubleshooting] token419:
The Mms.apk is what sets up what com.android.xxx libraries it pulls up. for example if the sprint one pulled up com.android.sprint.mms.settings.blah, and you use the verizon one that points to com.android.verizon.mms.settings.blah, then it isnt calling the broken framework to run the instruction on.

Thats just an example, not based on any findings.

Whats interesting though is that the Cyanogen and AOSP roms are failing, which as far as i know only reuse a few things from a base rom (libs and whatnot), so what im thinking is to find out a vendor tree for cyanogen and see which frameworks/libs etc that they pull from an original rom that don't get built from cyanogen sources, and that will help us narrow down what could be not working correctly.

Just a thought, ill have to experiment when i get back from vacation.

Eager to see if anything arises :)