Develop Bugs

New Clock Widget Switcher 50+ clocks and no ADB required.

Updated: Sept 8 2009 Now over 50 clocks some in 2 sizes. Have fun with the new clocks and the new Candy.
--Linuxrebel--
I'm one of those who loves Eye Candy, but hates windows. So despite some excellent work done by xidominicanoix I couldn't use the work. So with xidominicanoix's permission to use the collection I've written a shell script that can run on your SD card and installs the new clocks in quick order.
NOTE: This is for rooted phones only. I've tested it pretty heavily on my G1 but your mileage is not guaranteed. If you are not comfortable in a Linux/Unix shell you might be best off with the tool here.
I claim only that it worked on my phone, (and that it looks cool to me )
Directions for use (Copy of the directions are also in the README file):
+++++++++++++++++++++++++++++++++++++++++
This is a quick and easy way to change the clocks on your phone without the hassle of using windows adb, etc.
Unfortunately for those who aren't rooted, this will not work. Root is required to be able to use
this script and change the clock. There are lots of tutorials on how to root phones, so go forth and google to find your answers.
Usage:
+++++++++++++++++++++++++++++++++++++++++
1. Connect your phone to your main computer and copy the file clocks.tgz to your sdcard
2. Disconnect the phone, as the rest will not need your computer to complete.
3. Open a term window (I like connectbot your preference may vary)
4. su
5. cd /sdcard
6. tar -vzxf clocks.tgz (this will open the tar gzip file)
7. cd Clocks
8. sh setclock.sh backup (This will backup your existing clock)
9. sh setclock.sh [name of the clock you want to use]
You can remove the clocks.tgz file anytime you want once it is opened it's no longer used. If you run backup a second time it restores the originally backed up clock.
NOTES:
Images of the various clocks are in the the directory called Images. The Image viewer on the G1 picks them up (may need to force it to re-read) and I'd imagine that the other phones work the same, so you can see what it is you are going to get that way. The Directory name will match the name of the picture to make life better. To add a clock to this script all you need to do is make a directory under Clocks, with the AlarmClock.apk file in it, and then run the script to have it 'installed' the same as all the others.
Again thanks to xidominicanoix for gathering together permission to use all of these clocks, and giving me the idea to do it this way. (Since I couldn't use his bloody windows tools )
--Linuxrebel--
You can download the tarball at the following link:
http://www.4shared.com/file/131059734/7781f9a1/clocks.html
md5sum 7c1253ba43d6b21194b56c489b9fb7e6 clocks.tgz
Seems I forgot about the Windows side of the world. All I have at home are *nix systems (Linux, Mac and BSD), so if you are not on a *nix or Cygwin enabled system a zip file
http://www.4shared.com/file/132469430/9f73a1ba/clocks.html
md5sum f5cdb6cd3c4ad983ab30123b1acce3f7 clocks.zip

good work man ... now Mac and Linux users can all enjoy

xidominicanoix said:
good work man ... now Mac and Linux users can all enjoy
Click to expand...
Click to collapse
And noobs who can't get it work like me
Thank you both for your hard work on this.

Adam17 said:
And noobs who can't get it work like me
Thank you both for your hard work on this.
Click to expand...
Click to collapse
Are you having hard time with xidominicanoix's version or mine? If mine let me know what the problem is. If xidominicanoix's I'm going to be as in the dark as anyone could be.

Yeah I am having problems with his, just can't seem to get it working for me.
Edit: So we have to go back into term everytime we want to change it? Or am I missing the easier way to do it?

Adam17 said:
Yeah I am having problems with his, just can't seem to get it working for me.
Edit: So we have to go back into term everytime we want to change it? Or am I missing the easier way to do it?
Click to expand...
Click to collapse
Good bad or ugly, yes you do need to go back to term. UNLESS a miracle happens and I instantly figure out how to to Android style programming I'm an admin not a programmer.

Np, I can deal with term a helluva a lot easier than I can with adb.

works great..takes a few seconds after initial set up to bang into terminal the commands to change the clock. I have had issues with ADB where I seem to lose adb connection for unknown reasons and phone doesnt connect so this method for me is alot easier.
thanks!

works great .. .thanks ... it shows up on my home screen but does not show up in my open home home screen :/ is there a way I could make it work in open home?

wow so easy and straight from the phone
thanks for this!!

hello .... it's not working for me..
when i get to step:
8. sh setclock.sh backup (This will backup your existing clock)
my g1 says cp: cannot stat '//system/app/AlarmClock.apk': No such file or directory
hmmmmmmmmmmm
what to do
i HAve Cm 4.0.2
and the oreo red n blk theme

bboy_201 said:
hello .... it's not working for me..
when i get to step:
8. sh setclock.sh backup (This will backup your existing clock)
my g1 says cp: cannot stat '//system/app/AlarmClock.apk': No such file or directory
hmmmmmmmmmmm
what to do
i HAve Cm 4.0.2
and the oreo red n blk theme
Click to expand...
Click to collapse
Looking into it.
EDIT: I did the only thing I can imagine is that a theme you are using has moved the AlarmClock.apk package and I've no idea where.

I'm stumped
linuxrebel said:
Looking into it.
Click to expand...
Click to collapse
The normal location of the clock is /system/app (or //system/app, same place extra /)
Is it perhaps possible that the theme you are using moves the AlarmClock.apk? If you can give me a link to the theme (I'm more than a little tired at the moment and having really lousy luck with search.) I'll see if I can figure out what the author of that did, or if it is even the problem.

Worked perfect I love it thank you very much!

i iused the other verion of doing this from the link provided in the top of the 1st post......
http://forum.xda-developers.com/showthread.php?t=538189&page=12
that worked for me!!!!!!!!!!!!

edit:
found it out myself

And what about even more easiest switching. Try this one http://www.mediafire.com/?whgtmmt5uui. Unpack copy folder to sd card then run just once clock_install.sh via GScript Lite app. For switch clock open terminal and write clock.

I'm running on CM 4.0.4 and when I input the setclock.sh clock name it works and everything works perfect except that I never can get the clock widget its always the same watch as before any help?

AndroidFiend said:
I'm running on CM 4.0.4 and when I input the setclock.sh clock name it works and everything works perfect except that I never can get the clock widget its always the same watch as before any help?
Click to expand...
Click to collapse
I am running CM 4.04 too on my MT3G and everything works. I now have TedLight clock on my phone. The only problem I have is that I wanted Clock5, but my keyboard or emulator refuse to use digits. What am I doing wrong? Is there a way to type digits or it is just my phone is not cooperating?
Thanks.

Would anybody mind posting some highlights?

*OUTDATED* ROM porting for kaiser/vogue [Linux] NOOB friendly!

THIS IS NOW OUTDATED!!
It uses the old sqsh method WITH a rootfs. So if you're using the NoMoRootfs method, this won't work. Please use the already complete builds in the Kaiser/Vogue threads as they are working the best at this moment.
DISCLAIMER:
I take no responsibility for anything that may happen to your phone/computer. Use at your own risk.
PURPOSE:
This is for informational/testing purposes. And for people to stop asking, "can somebody port X rom!!! PLZ!!!"
PREFACE:
I made this as a quick tool to port ROMs from the Dream/Sapphire forums to work with our phones. It's a very quick and dirty script I threw together using bash, so there's probably some problems with it. This tool is simply designed to make a copy of the Dream/Sapphire ROM. Once you get the setup, it's really easy and you'll be porting like crazy.
I did this all on Ubuntu 9.10 so things might not work properly if you're using another distro.
THANKS:
All credit goes to the people that made this possible, in no particular order...
dzo, vilord, mssmison, zen, enatefox, pmos, jamezelle, craig0r, cyanogen, and so many more. If I forgot you, I'm sorry, but you know if you helped in some way.
THE SETUP:
1) Download this file
2) Extract the folder to your desktop. Then copy and paste the following code into the terminal:
Code:
sudo mv -f $HOME/Desktop/Android/genext2fs /bin/genext2fs; sudo chmod 755 /bin/genext2fs; sudo dpkg -P squashfs-tools; sudo dpkg -i $HOME/Desktop/Android/squashfs-tools_3.3-7_i386.deb; sudo rm -r $HOME/Desktop/Android/squashfs-tools_3.3-7_i386.deb; sudo chmod 777 $HOME/Desktop/Android/*.build.script
3) Now go into synaptic package manager, search for squashfs-tools, select it and under Package, check Lock Version so that way it won't try to update.
4) Now cruise over to the Dream android development forum or the Sapphire android development forum and download the ROM you would like to port. Place the zip file in the Android folder. (no need to rename)
5) Place any .apk's you would like built into the system in the Apps folder.
ADVANCED SETUP:
If you would like to tweak the system before building, open the script in a text editor and you'll find a line to uncomment that will halt the script until you are ready.
HOW TO RUN:
Either run the script from a terminal
Code:
./$HOME/Desktop/Android/HERO.build.script
or
./$HOME/Desktop/Android/Donut.Build.script
Or double click and Run in Terminal
You will get a prompt for your password to use the sudo command. THIS IS NOT SAVED ANYWHERE OR MAGICALLY SENT TO ME. It is just to get the system.sqsh setup for you to use.
You will now see a Donut/Hero folder inside the Android folder. Inside that will be a nice little system.sqsh with the date ready to boot!
*Rename to system.sqsh when you put on your SD card*
Grab the latest basefiles from vogue-android and you're good to go.
~~~~~~ To get an output of what's happening run in a terminal as described above but add " > build.txt" and you'll see a txt file in the Android folder. ~~~~~~~
CHANGING SYSTEMS:
If you want to port a new rom, replace the .zip.
UPDATES:
1) Download the updates from HERE
2) Extract to the Android folder overwriting if necessary.
3) Copy and paste the following code into a terminal:
Code:
sudo chmod 777 $HOME/Desktop/Android/*.script
CLEANUP:
If you follow the advanced setup and/or accidentally closed the terminal before the build finishes, run the cleanup script. This will unmount everything that might be mounted and delete all folders that are made during the process.
DOWNLOADS:
If you're too lazy or just want a quick link:
Main "Android porting" folder
Updates

Input, testers, bugs, and tweaks to the scripts are appreciated!
FAQ:
Why does my system.sqsh not work?
Most likely cause is that you're not using the correct version of squashfs-tools. You'll have to find version 3.X for the distro you're using. Version 4.X will NOT work!!!
When I try to boot a system.sqsh I just made I keep getting something about android power wake locks. WTF?
You're probably trying to port an eclair or cyan ROM. These don't work at the current state. Hopefully soon I'll get these working.
Will update more when they arise.
CHANGELOG:
11-27-09:
-Created a cleanup script in case the terminal is closed during the build process.
-Bug fixes in Donut and Hero scripts
11-24-09:
-Added an Apps folder for apk's you want built into the system.
-Bug fixes in scripts
11-22-09:
-Combined everything needed into a zip file
-WAY easier to setup
11-20-09:
-Added feedback to make more user friendly
-Append time to system.sqsh

loserskater said:
Input, testers, bugs, and tweaks to the scripts are appreciated!
Click to expand...
Click to collapse
Will try today... Downloading
Tried and working. Had to change the script for it work with ubuntu version that i use. Thanks this is really great

garynsa said:
Will try today... Downloading
Tried and working. Had to change the script for it work with ubuntu version that i use. Thanks this is really great
Click to expand...
Click to collapse
What did you change?
Glad to see it's working.

loserskater said:
What did you change?
Glad to see it's working.
Click to expand...
Click to collapse
hI
For some reason I cannot use -a in the genext2fs command. Had to remove that..
One of the Donut is working. Couldnt get the Cyanogen build working . Struggling with hero build also.
Will try again in the next couple of days and post results.
Thanks

garynsa said:
hI
For some reason I cannot use -a in the genext2fs command. Had to remove that..
One of the Donut is working. Couldnt get the Cyanogen build working . Struggling with hero build also.
Will try again in the next couple of days and post results.
Thanks
Click to expand...
Click to collapse
Make sure you use the genext2fs that I referenced.
That one works with -a and might take care of some issues. try that and see if it works.

Updated script to now move system to a Hero or Donut folder.
Working on the cyanogen build now...
EDIT: Here's a cyanogen script that gets it to boot, but sits at a black screen. I haven't had much time to test it so it might boot further than that if you leave it. If somebody wants to test this out or tweak it in some way go for it.
It uses the donut.sqsh in the Android folder so you shouldn't have to do anything with it except make it executable.
EDIT 2: Still working on cyan builds... that script didn't work.

great job i like to see stuff like this to motivate people!!! also note this will work with any donut or hero build from the sapphire forum

jamezelle said:
great job i like to see stuff like this to motivate people!!! also note this will work with any donut or hero build from the sapphire forum
Click to expand...
Click to collapse
Good point, forgot to mention that. Updated first post.
I'm hoping it will help people start to learn to tweak system's. But I have a slight feeling wer're going to start seeing a lot of "MLIGN/DWANG/etc's Android Rom" threads from random people.

Hi
Was able to port the DWANGs build using your script. Thanks a lot for making life this simple. Howev3er, hero build is still not working. Tried your genesxt2fs. Is it possible to get the links to correct base hero version to use? I tried magic and normal version. It keeps giving me black screen and doesnt completely boot. I think the base hero version is not the right one i am using
Thanks

OK, I think I figured out the problem. The apps folders weren't copying over from the data folder to the system folder correctly. Testing now, and will update first post with new scripts.
EDIT: Finally got the Hero builds working correctly. You should still be able to use any hero.sqsh.

loserskater said:
OK, I think I figured out the problem. The apps folders weren't copying over from the data folder to the system folder correctly. Testing now, and will update first post with new scripts.
EDIT: Finally got the Hero builds working correctly. You should still be able to use any hero.sqsh.
Click to expand...
Click to collapse
Hi
The new script is great.. I was able to get the hero to boot I still have 2 check a few thing willl post later in the night with more
Thanks a lot

garynsa said:
Hi
The new script is great.. I was able to get the hero to boot I still have 2 check a few thing willl post later in the night with more
Thanks a lot
Click to expand...
Click to collapse
Glad to see its working. Thanks for the feedback!

Most things working
Hi
was able to get the hero ported and a few things worked
1. Calls
2. SMS
3. Wifi (getting ips)
4. Working with partition rootfs (speed quite great with this)
Not working
1. Camera
2. GPS
I am using he ION build to build the hero roms (based on the inputs of Zen). May be I need to use another hero rom for the camera to work? I recommend that the links to the recommended build to be used as template (donut, hero...) be updated on the first thread to make it easy for others to have a single starting platform

garynsa said:
Hi
was able to get the hero ported and a few things worked
1. Calls
2. SMS
3. Wifi (getting ips)
4. Working with partition rootfs (speed quite great with this)
using u
Not working
1. Camera
2. GPS
I am using he ION build to build the hero roms (based on the inputs of Zen). May be I need to use another hero rom for the camera to work? I recommend that the links to the recommended build to be used as template (donut, hero...) be updated on the first thread to make it easy for others to have a single starting platform
Click to expand...
Click to collapse
If using a hero.sqsh doesnt fix the problem it sounds like it might be the rootfs (probably not copying over correctly). Ill take a look at it when I get home and update the first post with hero/donut.sqsh's.
Im also thinking about combing the 2 into just one script and youll be able to just type which build you want when you run it. What do you think? Or is the 2 seperate scripts more convenient?

loserskater said:
If using a hero.sqsh doesnt fix the problem it sounds like it might be the rootfs (probably not copying over correctly). Ill take a look at it when I get home and update the first post with hero/donut.sqsh's.
Im also thinking about combing the 2 into just one script and youll be able to just type which build you want when you run it. What do you think? Or is the 2 seperate scripts more convenient?
Click to expand...
Click to collapse
Personally i prefer the separate scripts mainly because each requires a different base templates. However if you prefer to combine them may be have sub-folders within the main so that the work happen for each port within the sub-folder.
Few suggestions if you like (please ignore if not correct.. being a non-programmer of linux I can be a bit off )
1. Let the folder names be requested at start and use them
2. If possible to put in a log of the run to check if there were issue or not (because i use double-click to run the script sometimes there is a problem that i face if i dont watch the window. for now i have put some waits to check the errors. Had this issue while testing to port one)
If I can help (except on coding as I dont know it.. generally change the script just enough to work... )
Queries/questions
1. Is there a way to test the build on the comp itslef rather than to keep booting on the phone (takes a lot of time and the phone is not usable all that time...)
Thanks for all the work

garynsa said:
Personally i prefer the separate scripts mainly because each requires a different base templates. However if you prefer to combine them may be have sub-folders within the main so that the work happen for each port within the sub-folder.
Few suggestions if you like (please ignore if not correct.. being a non-programmer of linux I can be a bit off )
1. Let the folder names be requested at start and use them
2. If possible to put in a log of the run to check if there were issue or not (because i use double-click to run the script sometimes there is a problem that i face if i dont watch the window. for now i have put some waits to check the errors. Had this issue while testing to port one)
If I can help (except on coding as I dont know it.. generally change the script just enough to work... )
Queries/questions
1. Is there a way to test the build on the comp itslef rather than to keep booting on the phone (takes a lot of time and the phone is not usable all that time...)
Thanks for all the work
Click to expand...
Click to collapse
I'll try to make the script more user friendly with prompts if something doesn't happen correctly. And also work on naming folders.
But first I want to figure out the camera/gps issues...
There isn't a way to boot it on the comp that I know of. I'll upload blank data.img's for each build so that they'll boot faster but other than that I think moving to SD Card and booting is the only way. But once all these bugs get sorted out, you won't have to do it as often!
EDIT: Which folders would you like to name? Just where the system.sqsh gets stored?

loserskater said:
I'll try to make the script more user friendly with prompts if something doesn't happen correctly. And also work on naming folders.
But first I want to figure out the camera/gps issues...
There isn't a way to boot it on the comp that I know of. I'll upload blank data.img's for each build so that they'll boot faster but other than that I think moving to SD Card and booting is the only way. But once all these bugs get sorted out, you won't have to do it as often!
EDIT: Which folders would you like to name? Just where the system.sqsh gets stored?
Click to expand...
Click to collapse
Hi
Thanks for the answers. For me it should be both (but the starting folder is main. Other can be a sub-folder like u have now to be renamed as choice)

garynsa said:
Hi
Thanks for the answers. For me it should be both (but the starting folder is main. Other can be a sub-folder like u have now to be renamed as choice)
Click to expand...
Click to collapse
Are you referring to the Android folder? Or just a folder where everything is kept when it runs?

loserskater said:
Are you referring to the Android folder? Or just a folder where everything is kept when it runs?
Click to expand...
Click to collapse
Android folder... but its not a big deal as one can easily change it while startign the script

Howto make a permanent change to $PATH?

Is there a way to make a permanent change to the $PATH variable to place /system/xbin ahead of /system/bin? I found /init.rc when the phone is booted, but obviously I can't make changes to that yet. When booted into recovery, I can't find the same file to edit it. The /init.rc file is specific to the recovery image at that point.
Basically, I have busybox installed in /system/xbin and want it to override the /system/bin apps. I do not want to install busybox in /system/bin.
Any help would be appreciated. Thanks!

are you trying to export a path? if so it would go something like
export PATH=$PATH /system/bin
or you can
PATH=$PATH /system/bin
export PATH

B-dub25 said:
are you trying to export a path? if so it would go something like
export PATH=$PATH /system/bin
or you can
PATH=$PATH /system/bin
export PATH
Click to expand...
Click to collapse
He's trying to make it so he doesn't have to reset the $PATH variable every time. I'm assuming you are currently just using something like.
export PATH=/system/xbin:/sbin:/system/sbin:/system/bin
every time you enter shell. The way I would do it is by editing the init.rc as you stated, however it doesn't stick on the incredible, also as you stated.
The only thing I can recommend is making it a shorter PATH to type. You could just enter
export PATH=/system/xbin:$PATH
for example, and that would accomplish the same thing with less typing.
The only other way that I know of would be to make a start-up script, not sure how to accomplish this outside of init.rc however. In linux I would add it to the bash_profile or something similar. Not sure how to do it in android...

Not only for shell, but I'd like to be able to do it for installed apps as well, such as OpenVPN. Ah well, just have to wait for full root unlock.

This is done in the ramdisk. You can actually do this yourself. You need to extract the boot image, break it apart into the ramdisk and kernel, alter the init.rc file, package it back up and then flash it back to your phone in recovery.
Even if we get the nand unlocked, you will still need to do this since the init.rc recreates itself from the ramdisk during each boot.
If you are using a custom ROM, just request the dev to do this.

ihtfp69 said:
This is done in the ramdisk. You can actually do this yourself. You need to extract the boot image, break it apart into the ramdisk and kernel, alter the init.rc file, package it back up and then flash it back to your phone in recovery.
Even if we get the nand unlocked, you will still need to do this since the init.rc recreates itself from the ramdisk during each boot.
If you are using a custom ROM, just request the dev to do this.
Click to expand...
Click to collapse
Thank you kindly, didn't know where those files were kept. Interesting how that works, so basically the phone works like a hardware chip, where the main parts of the OS recreate themselves from ROM, similar to firmware... I like it... prevents corruption I suppose.
Out of curiosity (I've never made a ROM, and therefor never packaged the boot image), is it packaged as a tarball? Or do you require ADB to extract? If you don't want to answer, I can probably track it down somewhere.

It's a bit more complicated than that. Take a look at this link. I'm sure there are other ways, but I would recommend only doing this in some flavor of Linux like Ubuntu.
HOWTO: Unpack, Edit, and Re-Pack Boot Images

ihtfp69 said:
It's a bit more complicated than that. Take a look at this link. I'm sure there are other ways, but I would recommend only doing this in some flavor of Linux like Ubuntu.
HOWTO: Unpack, Edit, and Re-Pack Boot Images
Click to expand...
Click to collapse
Cool link. Thanks.
But yea, pretty much seems to be that simple, Just a gzip (zip) and tarball (cpio). The only thing I wasn't expecting was stripping out the 2k header with a hex editor, but I think I'll try using the scripts found through that link to do that, not that I couldn't do it by hand... but I'm lazy...
Thanks again.

[Q] SU not working

I am just about to release my new barebones build with a lot of new features but one thing is killing me. I cannot get superuser to work anymore with the latest build and the latest kernel. Rogue tools won't overclock without SU working and that just totall kills the speed of my build =(. The build is based off scoot's release 5 and I am using the latest kernel with and without the module update SU is unaffected. Everything else works though.

What have you changed from the build i sent you that might effect it? Does it work for you with the original build? Things to check are the sysinit.rc, make sure it calls userinit.sh on startup, and also check your userinit.sh in the /bin directory and make sure the su fix is still present in the file Otherwise, try opening the super user app and downloading the latest su binary file, if it fails to install then you most likely have partition permission issues.

I did edit userinit to enable the odex script. I am gonna check that now.

Ok I am pretty sure that was it. how do I add this line to userinit to have it be proper then? /system/bin/odex.sh

aceoyame said:
Ok I am pretty sure that was it. how do I add this line to userinit to have it be proper then? /system/bin/odex.sh
Click to expand...
Click to collapse
You'd need to put it in sysinit.rc like this :
service odex /system/bin/odex.sh

So put that line right at the end then? Or is there a special format it has to go in. Sorry, I have just never had to edit this particular file before lol.

aceoyame said:
So put that line right at the end then? Or is there a special format it has to go in. Sorry, I have just never had to edit this particular file before lol.
Click to expand...
Click to collapse
At the end is fine, you will see some similar lines in there, you may want to add some options such as :
console
user root
oneshot
I don't know what the structure of the odex script is so i don't know which options you will need to get it to run properly but these are the most likely, just experiment and see

I've always put it at the end, after the su fix just as "/system/bin/odex.sh" and nothing else. What does service do? will it run it continuously or just with different permissions?
I would say its more likely that something's gone wrong while you edited userinit.sh, and now it can't be executed.
did you edit it in windows? you may have /n/r line endings now instead of /n
if you did it in linux it may be a permissions problem

fixed! I used the userinit from my old barebones. Something changed in the update. The two looked totally different.

[Q] EL26 modem not as fast as EG30 modem

I recently updated to a complete EL26 system with matching ROM kernel and modem...I've noticed when I run speedtest to test my WIFI speed my results are consistantly low getting on average .76 Mbps down where as my EG30 setup got consistantly 15Mbps down...as fast as my comupter...
I was wondering if anybody knew what factors contributed to this descrepency and if anybody had any suggestions on how to fix this problem.
thanks in advance
please keep in mind this is for WIFI ONLY

Just go back to EG30 then. There is no "fix". Certain modems are good in certain areas. Have you tried EL13?

yes i tried EL13 and EK02...at first with EK02 it was as fast as EG30...but soon slowed to .76Mbps

Then stick with EG30 or investigate whether there are conditions other than the modem that might be causing the speed change. Is there intermittent interference from neighbors?

I have noticed that undervolting too much will impact data speed on my device. Just something to look into.

no just two other laptops on this connection...when i run a speedtest on my computer and speedtest on my phone... like one right after the other i get 15 on my comp and less than 1 on my phone...if i go back to EG30...which AIO do i use...can i still use Roms based on EL26...and will i b ok with rogues desperado kernel?

Drumrocker said:
I have noticed that undervolting too much will impact data speed on my device. Just something to look into.
Click to expand...
Click to collapse
thanks...but i havent gotten in to undervolting yet...that was going to b my next venture...actually something i planned on getting into today...so i will keep ur advice in mind...any other advice for undervolting is welcomed

lunchboxVA said:
if i go back to EG30...which AIO do i use...can i still use Roms based on EL26...and will i b ok with rogues desperado kernel?
Click to expand...
Click to collapse
You said EL26 modem is worse than EG30 modem, so that assumes you tested them in isolation, but the statment you made above makes it seem like you are not clear on the differences between Modem, Kernel, and ROM.
To go back to EG30 modem, just use CWM and flash the EG30 modem only with your existing setup (kernel/ROM/AIO/etc). You can find the EG30 modem in my signature. Make sure your CWM is packed with EK02/newer-based kernel.

o no sorry for the confusion i know the difference between the three...i was asking because i have read that wen u have all three matching u get the best results...i do get confused when a rom says its based on for instance el26...i would assume that it means its packaged with the el26 modem...i just dont know what based on means...
and i asked about which aio do i use because when i was on the eko2 setup i flashed aio for eg30 and my phone would get past the bootscreen the screen went black and i had to reflash eko2 and then wen i flashed the matching aio it went through fine
samething with el26...i had an el26 setup and flashed an aio for el13...and it caused the same black screen issue which was only resolved after i installed matching aio

ROM could either refer to the entire Modem/Kernel/ROM set or just the ROM portion, depending on context.
Usually EL26-based ROM is only referring to the ROM portion. It may or may not come bundled with a Kernel and normally isn't bundled with a Modem.
You can tell which modem/baseband you are running by going to menu->settings->about phone->baseband and seeing what it says
AIO is implemented in the ROM portion. It usually is not a good idea to mix/match ROM components.
In theory it is best to have Modem/Kernel/ROM versions to match as that is what was tested together, but in reality people have found you can mix/match the 3 components w/o issues.

sfhub said:
ROM could either refer to the entire Modem/Kernel/ROM set or just the ROM portion, depending on context.
Usually EL26-based ROM is only referring to the ROM portion. It may or may not come bundled with a Kernel and normally isn't bundled with a Modem.
You can tell which modem/baseband you are running by going to menu->settings->about phone->baseband and seeing what it says
AIO is implemented in the ROM portion. It usually is not a good idea to mix/match ROM components.
In theory it is best to have Modem/Kernel/ROM versions to match as that is what was tested together, but in reality people have found you can mix/match the 3 components w/o issues.
Click to expand...
Click to collapse
do you know anything about modifying the sys directory or adding folders to it...im trying to get the enable touchscreen 1 script to work...but it cannot modify the sys directory so it errors out

lunchboxVA said:
do you know anything about modifying the sys directory or adding folders to it...im trying to get the enable touchscreen 1 script to work...but it cannot modify the sys directory so it errors out
Click to expand...
Click to collapse
Not familiar with that script, but /system is mounted read-only, so you need to use your root privileges to remount /system to be read/write
I mean this with all the best intentions, but it sounds like you probably should do some more reading before making too many changes in /system

thanks...all i do is read...but as i said i gave it all the permissions and i did run in root explorer with root access...the folders i create dont stick...and then when i try to use the root explorer included with rom toolbox..it says it cannot create the file even tho it has root access

You've verified you still have root? How did you verify?

sfhub said:
You've verified you still have root? How did you verify?
Click to expand...
Click to collapse
in root explorer in the top is says ro or rw plus there super user is installed...and in system tools which i also have i am required to tick the su box

What happens when you type "su" in adb shell?
The reason I'm asking is you are describing actions that should be working if you have root, but saying they aren't working.
Superuser showing up in the app drawer doesn't actually mean you still have root. It is a database of who gets root permissions. The actual command that gives you root is /system/bin/su or /system/xbin/su

i was doing some readying and it seems like modifying sys folder is more complicated than any other folder including the system folder...but i will try what you just recommended to ensure i have root

so i was messing with adb on the computer I wanted to see what happened if i tried to pull the sys directory to alter it...i made sure i had root access and remounted the system...when i typed in adb pull /sys it caused my cmd to freak out it started scrolling through a million files...i assume it was going through all the files in the directory but each line said special file when it finally stopped it rebooted my phone and kicked me out

lunchboxVA said:
so i was messing with adb on the computer I wanted to see what happened if i tried to pull the sys directory to alter it...i made sure i had root access and remounted the system...when i typed in adb pull /sys it caused my cmd to freak out it started scrolling through a million files...i assume it was going through all the files in the directory but each line said special file when it finally stopped it rebooted my phone and kicked me out
Click to expand...
Click to collapse
So you really wanted to edit /sys rather than /system. I actually thought you were substituting /sys for /system.
/sys aren't real "files". They are mappings to kernel internals that are represented as files. Normal file "operations" may not have the same meaning as you are used to.

Ran Speedtest from about 30 ft away from my router the other night on both my netbook and my phone.. Netbook got somewhere around 12 Mbps and EL26 got around 6.5 Mbps. When you take other factors into account (size of WIFI antenna in a laptop/netbook vs a phone) it isn't that big of a difference.