yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] Paulynator:
Hangs at Android logo

I had just finished flashing LeanDroid when I noticed your (what I like to call) "LeanDroid on Steroids" (on Steroids due to being overclocked). I had been thinking if I were to right a ROM, this would be it...so...I was jazzed. I spent all day trying things over and over and can't get it installed. It just hangs at the "Android" screen. I had to install something so went back to regular LeanDroid and installed it again with no problems. I did everything you suggested including the wipe and the new CWM to no avail. Did anybody else get it installed?
[Android Software/Hacking General [Developers Only]] PaulMilbank:
Oh, ok... interesting. will have to do a wipe and flash and see what is going on at some stage. Have been developing it as I go on my phone, so possibly it works as I have been flashing kernels and such over existing builds.

Has anyone else had this problem?

Does CWM give any errors with installing?

Im guessing you are reasonable experienced with flashing, but how long did you leave it for on the android screen?

is this the android animation screen or the boot splash?

Does the MD5 hash match?

Thanks for helping test this, hopefully can get some more info and testing done to work out what is going on here.
[Android Software/Hacking General [Developers Only]] PaulMilbank:
heh, just flashed it from fresh and no dice, boot loop. trying to suss it now.

Going to upload a more basic build which is just leandroid+ kernel. Just tested on fresh install and it boots fine. Link will be updated in the first post.

Paul
[Android Software/Hacking General [Developers Only]] PaulMilbank:
Ok, take 2... try the new mod which is in the original post. It is straight LEANdroid+fusion kernel.
[Android Software/Hacking General [Developers Only]] Paulynator:
CWM gives no errors. Not heavy enough to know the meaning of "MD5 hash match" but also not fresh out of the box; I gave it at least 5 minutes on the "Android" screen (don't know if that's called the animation or boot splash); regular LeanDroid takes almost exactly 2 minutes so I thought 5 should be long enough. Will try the new one now. If doesn't work it will take me a little while to get back to you about it because I'll have to reinstall a working ROM so I can connect and reply. Here goes.

PS: I'm not doing this for fun; I just wanted a fast & lean ROM because I found myself demanding a lot of my little IDEOS and she was getting intolerably slow...am I'm really exhausted from trying to come up to speed on all this over the last few weeks...so...I want to be finished with this now...so...when you do any future updates (in gratitude for my help :) ) if it's even possible, could you please make sure it catches this LEANdroidMOD_2 so I don't have to do anything else to have your final version? I'd really appreciate it. Here goes. I'll let you know what happens.
[Android Software/Hacking General [Developers Only]] Paulynator:
OK. It loaded. Took 2 minutes just like plain LeanDroid. I went straight to the app drawer to play with NoFrills but it's not there. I realize you probably "lightened" this one as a troubleshooting tool to get her working. I just installed NoFrills and it does offer the 691MHz of the custom kernel. Sorry for asking you to educate me but:

1. Is it very advantageous to have NoFrills (or any desired apps) built in to the ROM instead of installed separately and if so, why?

2. Should I go 691, 122, ondemand, & deadline or what?

3. Should wait before I start heavily customizing my homescreens with postits, etc. because this prelim version won't be updated?

4. Is there a way to update to a more final version without losing my homepage customizations?

Thanks for the (I say best) ROM and any educating you give.
[Android Software/Hacking General [Developers Only]] PaulMilbank:
Hey Paulynator, thanks for your patience. Leandroidmod_2 was a very quick build to get things moving as I had to build something to get my phone working after the first rom didn't boot in testing! Will upload another build with busybox by default and a couple of small mods today. Problem came from data/app, so ditched that and put apps into /system/app.

Questions:

1)Not really, I just like it, others may prefer setcpu or something else instead.

2)You go with what you feel happy and doesnt crash your phone, try 652 and 60 first, then go higher and lower if it is working fine. Just leave apply on boot unchecked in nofrills until everything is working fine. Ondemand and deadline will be fine.

3)Updates should be able to be installed without a wipe.

4)Just install zip in CWM over your install, sorry, I cant promise anything though.

Thanks

Paul
[Android Software/Hacking General [Developers Only]] PaulMilbank:
Ok, take 3. everything from 2+busybox and some custom bits. Tested on my phone and it boots fine with a total wipe. Hopefully wont need to do a total wipe, but have not tested flashing over an existing install.
[Android Software/Hacking General [Developers Only]] Paulynator:
For question #1, I didn't mean NoFrills as opposed to SetCPU or something else; I'm asking if it's very advantageous to have desired apps built in to the ROM instead of installed separately and if so, why?
[Android Software/Hacking General [Developers Only]] Paulynator:
Paul,

Report on LEANdroidMOD_3 (a.k.a. LeanDroidOnSteroids, c'mon, it rhymes!) (or even "cleaner": SteroidLeanDroid. If I say so myself, awesome title for an awesome ROM...to me.)

Installed over version #2 w/o wipe seems to be ok...to the extent that I started the process of recluttering (restoring) my Ideos as though "she's a keeper", i.e. no more wiping; the records stay intact from now on.

Paul

---------- Post added at 05:55 PM ---------- Previous post was at 05:47 PM ----------

Sorry to hit you with 3 since your last but since we have a "hard"/permanent Home button right below the screen, is the redundant one at the bottom of the app drawer removable from a menu or would I have to mod the rom to remove it?
[Android Software/Hacking General [Developers Only]] PaulMilbank:
Doesnt matter one way or the other, I just liked it built in. Only possible advantage is that some apps in /system/app wont use space in /data/app, but this is lost the moment you update them as updates seem to install into /data/app. So my Leandroid with nofrills in /system/app still gives 164mb free space in data partition until things get updated.
[Android Software/Hacking General [Developers Only]] PaulMilbank:
Good work, thanks for the update that it can be installed over a previous install.

Home button is part of launcher pro. on the home screen, hit menu>preferences>appearance settings>uncheck home button on app drawer.
[Android Software/Hacking General [Developers Only]] Paulynator:
Just found a possible glitch. Don't know if it's the ROM so tried the obvious things to no avail. The camera app (any camera app; I tested the problem by downloading and trying others) won't access the gallery. In the stock app, the little preview window (that tapping opens the picture in the main window) won't open the picture. It gives an error message saying "app initialize failed. please download the app from the market". The app isn't in the market so I d/l'd 2 other camera apps and they both did the same. Using Root Explorer to try to open a picture also wouldn't work. Could you please try to access the gallery on a phone you've installed your ROM on and let me know if it works? I'd appreciate it. Thanks.
[Android Software/Hacking General [Developers Only]] PaulMilbank:
Works fine on mine. Try go to the market and update Quickpic. It does not like being in /system/app so if you update it, it should work. It was one of the reasons I tried to put it in a data/app from the start, but that caused bigger problems like the rom not booting.

I could also put the stock gallery back in alongside quickpic if needed but it does not have multitouch.
[Android Software/Hacking General [Developers Only]] Paulynator:
Cam fixed, thanks. Suggestion re:partitioning?

Yeah, I must've somehow broke the original gallery. Already had Quickpic and it gave the same msg. So, as you suggested, I updated Quickpic and it and it worked! The camera gallery now uses Quickpic (I don't see a way to even access the camera's gallery function anymore) but that's o.k. (I think) because Qp does everything the camera's gallery did, right? For me, no need to put the stock gallery back in alongside quickpic because I was one of the "lucky" ones to get a unit with the Melfas screen/no multitouch, unfortunately. Thanks for that and belated thanks for the app drawer home button info in LauncherPro; I obviously haven't played with it much. BTW, I had forgotten to do the site thanks function for you so I caught up just now.

On an unrelated subject, if you wouldn't mind giving me some guidance on this:

I'm using app2sd/move2sd and I was using it w/o making an additional partition but everything i've read says I have to make a partition. Weird.

Link2sd seems to say with it you can even move widgets and they'll still work.

What's your take? Am I imagining Move2SD enabled me to move much more, maybe even all apps (albeit breaking some)

Do I have the 2 apps capabilities assessed correctly?

What do you use?

Thanks for your help/suggestions.
[Android Software/Hacking General [Developers Only]] PaulMilbank:
Yep, Quickpic= better original gallery. I will try include the default gallery in future so people have a choice and can delete one or the other if needed. One will definitely work.

WRT the app2sd/move2sd stuff, Froyo has a built in way to move some files to the sd card. The downside to this is that some files such as widgets cant be moved and also dev's have to enable this functionality in their apps. This may be what you are using atm. App2sd shows what apps can be moved easily and moves them using the froyo move function. This is ok and wont break anything.

I understand their is a way some people have used which forces all the apps on the phone to the sd card by forcing data/app to be located on the sd card in a second partition. I have never used this, but would not recommend it, sd card is generally slow and it may break things with no way to fix them.

This is why I use Link2sd. Link2sd still uses a second partition, but it allows you to choose what you link and how. For example, I tried to move the updated market and it broke, with forcing everything to the sd card, I would be SOL, but with link2sd, I simply unlinked it and it worked again. It allows you to choose what goes where and allows more apps to be moved to the sd card than the default froyo way. I generally link everything except the library files and I don't link widgets.

Sorry for the long explanation.

Paul
[Android Software/Hacking General [Developers Only]] Paulynator:
I appreciate the thorough explanation. This whole thing of me flashing a new ROM began because I too broke the Market app. (I don't know what library files are.) With App2SD enhanced by Move2sdEnabler, I'm "hoarding" 15 apps (of 144 something reported) that "they" will move but that I've decided not to move (like widgets or others some of which I want to make sure stay running in the background and others I'm afraid to break because they might be too integrated with the O/S like the Market was) and only 4 that they say they won't move.

1. I know you said Link2SD "allows more apps to be moved to the sd card than the default froyo way" but will it allow significantly more than App2SD WITH Move2sdEnabler?

2. And with it would more be able to stay connected/keep running?

3. When you said "App2sd shows what apps can be moved easily and moves them using the froyo move function. This is ok and wont break anything" I may be a little braver trying to see if some of those 15 will move w/o breaking my OS like the Market move did if you mean even the App2SD/Move2sdEnabler combination won't break anything. Is A2SD still safe when empowered by M2sdEnabler?

4. It sounds like using Link2SD might be at least a little more complicated to use in that you might move part of the app but not the app's library files. I might want to avoid the add'l complexity if I now have room for my stuff (with the partition) and the speed is decent (with the freed ram and NoFrills). Would you say it would be a good compromise since I have App2SD/Move2SD in place and can avoid learning how to use Link2SD?

I'll stop hammering you with newby questions soon but since you're my personal guru...

I just repartitioned my 2GB card using Minitool:

1.46GB FAT primary

400 MB ext2 primary, I named sd-ext (some ref's said to use FAT32 if got mount error. I didn't)

Then I copied an exact copy of what I used to have on my sd back to the big partition. Then I used App2SD/Move2sdEnabler and moved a bunch of apps to SD. (Did they go to the right partition? Not a clue.) Then I used Minitool again to look at the sd (while still in the phone but mounted to pc) and it says I've used about 12MB of the 400MB.

5. Does that sound like it's utilizing the new little partition right or did I mess up copying everything back to the big partition? and if I didn't do it right, what do I do?

6. Minitool said that Windows won't see the add'l partition and it's true; Explorer doesn't show it...so...is there a way to see what is being put in the new partition?

Thanks again very much for your expert guidance and patience!
[Android Software/Hacking General [Developers Only]] PaulMilbank:
Sorry, have not used Move2sdenabler, so not sure what it is or does. Sounds like it moves everything to the sd card if you set it up right going by the little blurb on the market. But here goes!

1) Link2sd allows everything to be moved to the sd card, but you have a choice what you move. So possibly it will allow you to move the same or less than Move2sdenabler.

2) not sure, but if they stop, just move them back.

3) Not sure how Move2sdenabler works, so cant say for sure.

4) There is quite a bit of free space with leandroid, so using built in move and app2sd or move2sd, you should be fine, but feel free to experiment with moving more if you want to. Link2sd does take a little bit of figuring out, but I think it works well when it is set up right.

5) No, it sounds like it is just a formatted partition unless your apps were tiny.

6) Ubuntu linux or any linux will mount and read both partitions. Windows only reads the first partition I think, but try http://www.fs-driver.org/ and see if it can pick it up. I have only used fs-driver before and it worked to mount a linux disc on my hard drive dual boot.

Paul
[Android Software/Hacking General [Developers Only]] followthewhiterabbit:
Great

Hey man really great job. Running the latest version of the mod, OC'd to 691mhz. Running very smoothly, stock keyboard is a tad slow but I think that's across the board in all mods. Having a slight issue with my wifi, could just be my phone but its not locating the signal or dropping it when it is pouged in to my work PC. Also running Zeam launcher, and I still think it's faster and more reliable than L.Pro. All up, super solid Rom
[Android Software/Hacking General [Developers Only]] proprg8:
Hello Mr. Milbank,

My compliments on your work here. I just tried out your MOD_3 and I have to say it is lean and snappy. Had a little hitch with the quickpic app which was fixed by reinstalling it but otherwise everything seems to be working so far. Good job :-)
[Android Software/Hacking General [Developers Only]] PaulMilbank:
Hey everyone, thanks for installing this, helping test it and all the feedback. Have just updated this to LEANdroidMOD 5 with a custom tweaked kernel based on aorth's NOMA kernel source. Update if you want to, should still flash over the top of any previous install. This build is about testing a custom tuned smartass governer to see if battery life and responsiveness can be improved.

I had a similar wifi issue and it seems to have gone away after I went into recovery and wiped cache and dalvic cache then rebooted. May have just been something still cache'd and causing problems. Does not delete apps, just takes time first boot to rebuild cache's.

Quickpic is a known issue and it fixes itself after reinstalling, I think I will include default gallery in future builds.

If you are wondering about ldm 4, dont ask, lets just call it an internal testing build and leave it in the trash where it belongs! Unfortunately, I still have not found a way to theme this rom with framework and wifi in /cust.

Paul
[Android Software/Hacking General [Developers Only]] followthewhiterabbit:
LEANdroidMOD 5 is great, really REALLY sappy in Launcher Pro and other apps like Opera mini. Also I take back all I said about Zeam Launcher, LP is the way to go for this Rom.

Cleared my battery stats in ClockworkMod and let it run dry on LEANdroidMOD 5, got around 1 day 14 hours - not sure exactly how long it was, I took screenshots but they didn't work. This is with what I would call everyday use, including light browsing, a few calls and a lot of text and also and wifi on for most of the time (85%).

My only complaint is that when I get a call with a custom rungtone running, the screen takes a while to turn on so I can accept take the call (about 2-3 sec).

But otherwise, a VAST improvement from stock and also Leandroid, which I have enjoyed using so much these past few months.

Chur :)
[Android Software/Hacking General [Developers Only]] proprg8:
I agree! I like what you've done with this ROM. it has a good degree of snappiness, and since it's froyo based, everything works! I think I'm going to stick with this one as my daily driver when I'm not experimenting with GB/ICS ROM'S. I noticed you've done something with memory management, it always seems to have plenty of free memory and it runs great wthout any OC, so battery life is good as well :-)
[Android Software/Hacking General [Developers Only]] PaulMilbank:
Yeah, the memory tweaks really get this phone smooth, cpu profiles help a bit too. after playing around with them a lot, settings are basically stock but empty app memory and content providers are killed at 8960 bytes instead of 8136 bytes or whatever default was. They are not providing anything to user experience so it doesn't matter if they are killed earlier. Seems to work well.
[Android Software/Hacking General [Developers Only]] Tabatj:
Sorry for my english (google translated:))

I tried to install the ROM Lendroid v.5 (also starting from the original Vodafone ROM, and doing all wipes) but but when I try to turn the wifi gives me error ..

How can I fix this?

Thanks in advance.

Tabat
[Android Software/Hacking General [Developers Only]] PaulMilbank:
Hi Tabat, im sorry, Im not sure. I just wiped cache and dalvic cache and it worked fine. What ROM were you using before? Does it work with other Roms?
[Android Software/Hacking General [Developers Only]] Tabatj:
Before I was put on this ROM Dronix 0.54 Fast. I installed over your ROM by wipe all without success. Then I tried to put the original ROM of Vodafone stock by then wipe all this time without success ... I also tried to do to wipe recovery / Dalvin-cache / cache after installing the ROM, but without success this time too ...
[Android Software/Hacking General [Developers Only]] Paulynator:
LeanDroid_mod3 still fine but can't create shtcuts; LauncherPro's doing?

Wanted to report still happy with LeanDroid_Mod3 but have lost one function I really liked. I used to used eFile and Xshortcut to create shortcuts to folders/files and quick links to certain settings. Now, when I try to create them, everything looks like the creation process worked (no error messages) but the shortcuts never appear on the desktop. Is that something that LauncherPro could be causing?...or do you have any other suggestions to get them back working. Thanks for your help and the good ROM.
[Android Software/Hacking General [Developers Only]] PaulMilbank:
Tabat, if I understand right, your wifi is not working with any rom? I would find the stock vodafone rom and follow Veers guide here: http://xdaforums.com/showthread.php?t=1011527 to put the phone back to stock. If it still not working with the stock rom, then you need to get it fixed by vodafone.
[Android Software/Hacking General [Developers Only]] PaulMilbank:
Not sure sorry, did they work on leandroid? You could try an alternative launcher such as zeam or adw and see if they come up. Other than that, I'm not sure what to suggest.
[Android Software/Hacking General [Developers Only]] Tabatj:
Thanks for the reply. :)

Pretty much the wifi with other functions while the ROM install your ROM returns an "error" and does not work. With other ROM (Dronix, Fusion, LeanDroid, Vodafone stock, etc. etc.) has always worked ...
[Android Software/Hacking General [Developers Only]] Paulynator:
Testing shortcut creation in LEANdroidMOD

Not sure that the launcher is causing it; just a guess. Didn't try to create a create a shortcut during the couple of hours I was using plain LeanDroid...before I flashed LEANdroidMOD.

I'm receptive to any ideas to get shortcuts working again.

1. Regarding switching launchers, presumably to test a different launcher I'd remove LauncherPro but isn't it integrated into the ROM...so unremovable? Or could I remove it using Titanium or App2sd/Move2sd and do it without breaking my OS?

2. On a device of your where you're running LEANdroidMOD, could you please install eFile (free) and try creating a shortcut with it. You just pick a file or folder, single tab to select, then under File menu select shortcut and it should put it on your desktop. Thanks for your help doing this test.
[Android Software/Hacking General [Developers Only]] PaulMilbank:
Tabat: Sorry mate, I cant help. All you can try is to redownload the rom to make sure it was not corrupted in some way. I only have my phone to test on and it works perfectly on my phone. I would just suggest picking another rom that works.

Pauly: You just download a launcher alongside your current one. When you press the home key, it should give you the option to select the other launcher with a checkbox to say if it should be the default one, dont select default yet. If it doesn't work, uninstall the new launcher and it will go back to launcherpro, or go to manage apps and find the new launcher, there will be an option to clear defaults, hen you press home you will be able to choose launcher again. Will try and test tomorrow if I have time.

Paul
[Android Software/Hacking General [Developers Only]] Tabatj:
Thanks man:)

I'll try to do as you said and re-download the ROM. Is a pity that I was not able to run your ROM, I find it quite interesting and fluid. Anyway thanks for your support and your work.

Tabat
[Android Software/Hacking General [Developers Only]] PaulMilbank:
Thanks for the support Tabat, wish I knew more to be able to get it running on your phone.
[Android Software/Hacking General [Developers Only]] PaulMilbank:
Hey Tabat

Could you try LDM 6, it is based on an updated rom and possibly the wireless drivers may support your phone. I cant promise anything though.

Paul
[Android Software/Hacking General [Developers Only]] Tabatj:
Hello boss :)

I will try your new ROM Leandroimod v.6 and then check on the operation of wifi

Thank you for your work and passion you put into the project:)

Tabat
[Android Software/Hacking General [Developers Only]] Paulynator:
Paul,

I tried 2 other launchers and still couldn't create shortcuts. Did you get a chance to try it? I also tried a new thing, the symbolic link creation in Root Explorer. It didn't work either but at least it gave a (long) error message:

Link Failure

The link operation failed with the following message:

"link failed Operation not permitted"

This may be because the target file system does not support symbolic links.

Most SD cards do NOT support links.

I don't know if this operation is the same as creating shortcuts to folders but I thought it might be a clue...and also it gave me the idea that besides changing rom's, I also partitioned my SD card to use with App2SD/Move2SD and that might be preventing shortcut creation somehow...especially if I didn't do it quite right...like wrong FAT type or something...but seems to be working fine otherwise. Any ideas? Thanks for your help.