Database Develop

[PRJ] Linux and Android for CDMA Diamond (DIAM500)

Android 2.0 (Eclair) for CDMA Diamond (DIAM500)
Instructions
Put the files from my zip file (zImage, modules, startup.txt) in the root of your Internal Storage
From this xda post, download the latest XDANDROID build.
From the XDANDROID 7z file, extract system.sqsh, haret.exe, initrd.gz, calibration, conf/, media/, and (optionally) AndroidApps/ into the root of your Internal Storage
From stinebd's rootfs autobuild site, download the latest rootfs, rename it to rootfs.img, and put it in the root of your Internal Storage.
If you are updating from an earlier version of Android or just want to clear your settings, you can delete data.img from the root of Internal Storage.
Run haret.exe and boot
Notes
Touchscreen calibration values are stored in the ts-calibration file in the root of Internal Storage. To re-calibrate, delete the file and restart.
The "end call" button takes the phone in and out of sleep.
Android's "Menu" button is mapped to the top-left/Home button. The 5-way pad and the scroll ring both work.
Android's "Home" button is mapped to the power button on top of the phone.
Wi-Fi is working, although Linux sometimes crashes when WiFi is turned off.
If you want to try Android 1.6: From this Android build, extract haret.exe, initrd.gz, system.sqsh, calibration, calibration_diamond, and the AndroidApps/, conf/ and media/ directories into the root of your Internal Storage.
ChangeLog
3-23-2010:
Touchscreen double-tap issue should be gone, big thanks to eval- and especially bzo
HTC wired headset and 3.5mm headphones both work
3-8-2010:
Hardware 3D is re-enabled (accidentally disabled it)
3-6-2010 Update:
Bluetooth now works, big thanks to bzo
Touchscreen should be improved
Power-off now resets the phone instead of crashing
2-25-2010 Update:
When WiFi is turned off the phone shouldn't crash
2-19-2010 Update:
Power collapse now works, so power consumption should be much lower when the screen is turned off.
WiFi should work, as long as you use a new rootfs from stinebd's autobuild site. If you tried to use WiFi in the last ~2 weeks and it failed, WiFi still may not work with this new rootfs and kernel. See this post for solutions.
2-17-2010 Update:
Microphone works without having to make a call in WinMo
WiFi still isn't working, but I'll post a patched rootfs soon to fix it
2-10-2010 Update:
Hardware 3D acceleration is working under Eclair
Brought in makkonen's fixes for battery status--they're rough, but better than being stuck at 5% all the time
WiFi is not working at the moment, but I'll lean on the XDANDROID guys to get my fix in.
2-3-2010 Update:
Linux is now using much more of the phone's memory: 180MB vs. 103MB, thanks to some patches from the Hero and Droid Eris kernel source.
Touchscreen calibration is now supported with the Feb. 2 XDANDROID build, thanks to makkonen and phh.
1-27-2010 Update:
Stability should be much improved
A new touchscreen driver is included that is a big improvement over the old one, thanks to makkonen and phh. A calibration utility is coming soon. Until then, calibration is stored at the bottom of conf/eclair.user.conf, and you can put your WinMo calibration in there with this guide.
The USB product ID has been changed in the hope that ADB will work on Windows. Try it out and post back if it works.
1-22-2010 Update:
The power button (on top of the phone) is now mapped to Home, and holding it down will show apps running in the background
Sound, data, and WiFi should all be working
1-11-2010 Update:
Tested and working with Eclair
Deep sleep should be working better (use less power)
12-26-2009 Update:
Kernel improvements:
The speaker and earpiece now work (but not the microphone)
Screen backlight control works
Rootfs improvements:
Thanks to makkonen's RIL fix, cell data works in Android without having to end the connection in WinMo first
I made a change to /init that might help mjb94, hackman238 and others that have partitioned internal storage. If you were getting a "cannot mount" error on boot, let me know if this fixes it.
12-16-2009 Post
We do have a Google wave for Android--right now it's a cross between a wiki-status-report and chat room. I'm not sure how to give a link to a wave, but it's open to everyone and called "Android on HTC Windows Mobile Phones (Diamond, Raphael, Blackstone, Rhodium, Topaz)". If anyone wants a wave invite, PM me and I have a few to give out.
Enjoy Android, and if you need help or have questions, PM me or post here
Donations are greatly appreciated , or help finding an engineering job in San Diego!

thanks mr. pippy for all your work. my wife is happy that once the microphone works i wont want to buy a new phone!

wow
you are definately making progress on the diamonds android

Is there any chance of the mic working anytime soon? I know this isn't an fast paced process but I'm just so sick of wm.

Can someone invite me to Google Wave please?
my gmail account is mike.cgy

bdusmc said:
Can someone invite me to Google Wave please?
my gmail account is mike.cgy
Click to expand...
Click to collapse
I just sent you one.

Awesome - I got it... Thanks a lot!

Wow, you're getting a lot done in a short period of time, Thanks!
Will donate as soon as I can!

the boot stops on
"handhover: boot [htc_fb-1] -> real [ttyo]"

For the latest version, it will boot for me, but as soon as I have a 3g connection it seems to reboot any time I touch anything.

Boots up fine
Latest build boots up and seems to run fine for several hours but after playing with it, it seems to get more and more unstable. I went 10 hours with it plugged in sleeping and then unplugged it and used it moderately for about 3 hours before it crashed. Now it's crashed 3 times within minutes of each other. Good stuff though, can't wait until it's stable enough to use full time. Diamond has plenty of nuts to run it pretty good. Sure would be nice to have a dual boot phone. No reason to upgrade and get the best of both worlds...

giovesoft said:
the boot stops on
"handhover: boot [htc_fb-1] -> real [ttyo]"
Click to expand...
Click to collapse
I get the same error on my Raph500. I tried from the micro SD card and from the root of the fs.

giovesoft said:
the boot stops on
"handhover: boot [htc_fb-1] -> real [ttyo]"
Click to expand...
Click to collapse
rothgar said:
I get the same error on my Raph500. I tried from the micro SD card and from the root of the fs.
Click to expand...
Click to collapse
Sorry, my kernels are only tested on DIAM500. The RAPH500 mtype (set in startup.txt) is 2182, you should have better luck with that. Also, this thread is for RAPH800 but there may be some RAPH500 people there.

mr pippy i still get the same error as in your other post with the failed to mount sd and the 2 partions, i tried reformatting

mjb94 said:
mr pippy i still get the same error as in your other post with the failed to mount sd and the 2 partions, i tried reformatting
Click to expand...
Click to collapse
Did you reformat or repartition? Would you happen to be one of those people who has a partitioned card? Basically, I think the layout of your MC can have as many partitions as you want on it as long as mmcblkp1 (the first partition) is a fat32 partition with the needed files on it. There's also a little info on this problem on the wiki, lavender.t posted a solution that works 100% of the time if you're able to enter keystrokes.

Willis111 said:
Did you reformat or repartition? Would you happen to be one of those people who has a partitioned card? Basically, I think the layout of your MC can have as many partitions as you want on it as long as mmcblkp1 (the first partition) is a fat32 partition with the needed files on it. There's also a little info on this problem on the wiki, lavender.t posted a solution that works 100% of the time if you're able to enter keystrokes.
Click to expand...
Click to collapse
I simply in disk utility clicked on restore and erased the disk restoring with ms-dos fat
is there another way to do this. i have access to linux and osx not windows
it only shows i have one partition so idk!
no dice. heres what i have done
ok i restore the disk in to ms-dos fat
no dice
i repartiton with a scheme of one partition
no dice
i change the partiton table no dice
i tried lavaders thing but i couldn't get the keyboard to come up

there is a new android version called eclair 2.0 here http://forum.xda-developers.com/showthread.php?t=601751 .

i also formatted from the phone

Possible fix for microphone
I haven't tested this yet, but blast3r in irc tested a workaround for the microphone this morning and said it worked:
In WinMo, start a voice call and leave it connected while you open HaRET and boot into Linux. In Android, the microphone should now work for voice calls.

MrPippy said:
I haven't tested this yet, but blast3r in irc tested a workaround for the microphone this morning and said it worked:
In WinMo, start a voice call and leave it connected while you open HaRET and boot into Linux. In Android, the microphone should now work for voice calls.
Click to expand...
Click to collapse
Yep, confirmed for me. Made a phone call with android and could talk just fine. Probably can just call voice mail with win mobile and launch HaRET. Trying that right now.

[ROM][HC][3.2.1] Ideapad K1 Rooted + CWM (14_14_120109 build)

Greetings,
This is a rooted Rom for the Lenovo Ideapad K1. It also includes CWM version 5.5.0.4.
Original Thread at Rootz
-Already rooted with the latest version of Superuser.apk
-Google Apps
-build.prop changes to spoof Motorola Xoom (Was missing many apps from the market before, i.e. GTA III)
-Lenovo Market Removed
-Based off the 14_14_120109 US update
-Android Terminal Emulator
-OI File Manager
-Reboot to Recovery Widget/App
-init.d support
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Flash at your own risk. I am in no way responsible for any damage done to your device. This will wipe your entire device except the EXTERNAL sdcard.
If you are using Windows make sure you have installed the APX drivers before continuing.
Nvflash Windows Drivers
md5sum: 9aa3a4814ca63366329d85a22ed01f64
To boot into APX mode
1. Power off
2. Hold down the Vol - and the Vol +
3. While holding the Volume keys down, Power on
4. The display should go black, and both LED's on either side of the home button should light up. This is APX mode. If using Windows make sure the drivers are installed
Instructions
Windows
1. Extract the K1_Stock_120109_nvflash_R2.zip contents to a directory
2. Double click the "flash-windows.bat" file
Linux
1. Extract the K1_Stock_120109_nvflash_R2.zip contents to a directory
2. Open a terminal and cd into the extracted directory
3. Copy and paste the following command
Code:
chmod a+x ./flash-linux.sh && chmod a+x ./files/nvflash
4. Run either
Code:
sudo ./flash-linux.sh
or from a root prompt
Code:
./flash-linux.sh
CWM Controls
Power = Back (Any submenu), Toggle Display (Main Menu),
Vol+ = Highlight Up
Vol- = Highlight Down
Home = Select
To boot into recovery
You can now use the built in app or widget to reboot to recovery
**Superuser may crash during the first couple of reboots to recovery. Dont worry
Or run 'k1recovery' from the terminal or adb
Notes
If you try to flash any of the OTA update.zip's, it will probably work, but you will be shut out of CWM and will not be able to get back in unless you reflash everything via nvflash
Downloads
K1_CWM_120109_Rooted_nvflash_R2.zip
md5: dc5264c761e96f9fb9f240924cf60217
K1_CWM_120109_M_GE_Rooted.zip
md5: 280e18ecf837bf030f0a0fe83ec3e824
updater_120109_R2.zip
md5: 48cb5fefac3dcfcb89cddde501ac3e27
updater_120109_M_GE_R2.zip
md5: ef45437e57d257e54054cf9b70a0fcd8
Honeycomb_statusbar_120109.zip - Idea by Shaztech
md5: df290cfd0125f1dde2255a8518cd493f
Restores the default Honeycomb Status Bar, with the favorites button hidden.
To Install:
1. Put the Honeycomb_statusbar_120109.zip on the external sd card storage (Internal will not work)
2. Boot into recovery (via Widget or App)
3. Go to install .zip from sdcard
4. Choose Honeycomb_statusbar_120109.zip and flash.
ThirdPartyAppsRestore.zip - People report loosing market apps after using this. Removing link until I have time to test
md5: dd3ed7584c4c4813277ec96f55e4023a
Restores all the third party apps that came with the stock Rom.
To install:
1. Put the ThirdPartyAppsRestore.zip on the external sd card storage (Internal will not work)
2. Boot into recovery (via Widget or App)
3. Go to install .zip from sdcard
4. Choose ThirdPartyAppsRestore.zip and flash.
If you want to remove any of the third party apps you can remove the apk from /data/app/temp
The device tree used to port CWM is posted in my github.
http://github.com/khanning
I will be in Freenode IRC room #ideapad-k1 if anyone wants to discuss development and to answer any questions.

Flashing this ROM. Finally taking a plunge to root the device - can't wait!
So far, the process has been simple and sweet - hope the entire flashing and post flashing process experience is sweet too!!
Thanks Khanning for such a quick turn-around to my request
---------- Post added at 02:59 AM ---------- Previous post was at 02:45 AM ----------
Ok, it really was extremely simple. I'm rooted with a 14_14 and EXTREMELY happy! This opens multiple doors for me with this device now. Thanks again Khanning - you'r the man!!

Thanks for the heads up, will try this out on mine, it has been quite limiting so far....
Any idea on how to change the country? Am in the UK so rather connect to the UK market etc.... Thanks

Hi, I got a European IdeaPad with integrated HSDPA and after flashing your rom, it doesn't show the 3g connectivity anymore, what can I do?
Please help!
Edit:
I also can't restore the original OTA .zip download from Lenovo because thet ablet isn't recognized as a K1 anymore! :'(

twe69 said:
Thanks for the heads up, will try this out on mine, it has been quite limiting so far....
Any idea on how to change the country? Am in the UK so rather connect to the UK market etc.... Thanks
Click to expand...
Click to collapse
Try Market Enabler, that might help with the market region, although not sure since that probably uses gsm values to trick the market..
Sent from my HTC Vision

Adrixan said:
Hi, I got a European IdeaPad with integrated HSDPA and after flashing your rom, it doesn't show the 3g connectivity anymore, what can I do?
Please help!
Edit:
I also can't restore the original OTA .zip download from Lenovo because thet ablet isn't recognized as a K1 anymore! :'(
Click to expand...
Click to collapse
That's because on this ROM, the tablet is cloaked to work as a Xoom tablet for full app compatibility on the market. If you can change that on the build.prop (I think that's where it is) manually, it should accept it.
Although like I was told the OTA aren't full version of the ROMS, you might want to find and use the full version? Just a thought - more experienced users can give better suggestions.
Sent from my HTC Vision

rezapatel said:
Try Market Enabler, that might help with the market region, although not sure since that probably uses gsm values to trick the market..
Sent from my HTC Vision
Click to expand...
Click to collapse
Will try that as is, since it currently thinks I am in America etc....
This includes google maps.... It will start off in USA then jump to the UK.....
Some websites seem to go to .com instead of sticking to co.uk......
Summer time started at the weekend here but the tablet did not change the time.....
Any idea what I can do for those problems? Thanks.....

twe69 said:
Will try that as is, since it currently thinks I am in America etc....
This includes google maps.... It will start off in USA then jump to the UK.....
Some websites seem to go to .com instead of sticking to co.uk......
Summer time started at the weekend here but the tablet did not change the time.....
Any idea what I can do for those problems? Thanks.....
Click to expand...
Click to collapse
Try disabling the Geolocation option, you should find that under -
Settings -> Location and Security -> "Use location for Google Search" and "Use GPS Satellites" (try disabling these option).

Super easy to flash and runs great and the status bar rocks.. that original was horrid
Sent from my Xoom using xda premium

Awesome
This was the easiest install I think I have came across for an android rooting method. Runs so much smoother now. does the status bar write over and remove the lenovo bar? Any issues, thinking I am going to run this. Has anyone ran any performance tweaks, V6supercharge etc. Any benefit? Running much better now.
I did notice all my google apps updated to Play versions but the market still has not changed to the google play icon or version. Do i need to do a wipe cache etc?

dc52317 said:
This was the easiest install I think I have came across for an android rooting method. Runs so much smoother now. does the status bar write over and remove the lenovo bar? Any issues, thinking I am going to run this. Has anyone ran any performance tweaks, V6supercharge etc. Any benefit? Running much better now.
I did notice all my google apps updated to Play versions but the market still has not changed to the google play icon or version. Do i need to do a wipe cache etc?
Click to expand...
Click to collapse
Am running autokiller memory optimizer and it definitely made the device faster. Also the free memory has been behaving nicely.
I flashed the stock staus bar too, ii have felt, this made the device faster too. The lenovo bar was pretty slow and would hang pretty frequently.
I have also change the home launcher to Go launcher ex, feels better and more standard as I have this on other devices too. Love the inbuilt task manager on go launcher.
I yet have to try out V6, would love to see the results. Although as earlier suggested by Khanning, delete the /data/firstboot folder prior to trying else the device won't be able to rebuild your Dalvik cache. I wouldn't try it without making a backup using CWM, incase it messes up and you need to revert.
Let me know the results if you try out V6.
Cheers
Sent from my HTC Vision

I will probably start with some of the tweaks you mentioned before I attempt any v6 type adjustments. Have you or anyone tried ROM toolbox for adjusting memory, build prop, etc. I have used this on my Droid INcredible, and works great but there is a good amount of information on the settings people have been using on phones. Thanks for the information.
rezapatel said:
Am running autokiller memory optimizer and it definitely made the device faster. Also the free memory has been behaving nicely.
I flashed the stock staus bar too, ii have felt, this made the device faster too. The lenovo bar was pretty slow and would hang pretty frequently.
I have also change the home launcher to Go launcher ex, feels better and more standard as I have this on other devices too. Love the inbuilt task manager on go launcher.
I yet have to try out V6, would love to see the results. Although as earlier suggested by Khanning, delete the /data/firstboot folder prior to trying else the device won't be able to rebuild your Dalvik cache. I wouldn't try it without making a backup using CWM, incase it messes up and you need to revert.
Let me know the results if you try out V6.
Cheers
Sent from my HTC Vision
Click to expand...
Click to collapse

dc52317 said:
I will probably start with some of the tweaks you mentioned before I attempt any v6 type adjustments. Have you or anyone tried ROM toolbox for adjusting memory, build prop, etc. I have used this on my Droid INcredible, and works great but there is a good amount of information on the settings people have been using on phones. Thanks for the information.
Click to expand...
Click to collapse
Haven't used rom toolbox to make any custom adjustments to the build.prop, but technically if it makes changes to the build.prop file, its pretty much the same risk of a bootloop as trying out v6. Just that it can be controlled by inducing one tweak / value at a time. You can also take a backup of the files and push the originals using adb.
I really wouldn't all that effort unless I find lots of free time soon
But pls do share your experience, most specifically modifying the build.prop and deleting the dalvik cache (and having it rebuild on startup). If this works, I will plunge in and try out other stuff.
P.S. I am now using RAM Manager Pro and feel, this has made the device much snappier. Experiencing the same snappiness on my HTC Vision too. So far, I feel its performing much better than v6 or akmo.
Sent from my HTC Vision

Installed the rom and its nice and snappy....
Can someone give a break down to wipe the dalvik cache please?
Got the can't install app from market problem to and I guess that is the way to fix it, to delete it?
Thanks.

ANY idea why I can't boot recovery to sdcard? Just dcim, android, and data folders

no usb connection to xp
I loaded rom and Honeycomb status bar fix. The speed and root is nice. But i just noticed I can not get a usb connection to be recognized by my windows machine, so I can copy over backup'd files.
Anybody know what needs to be done to restore USB connection? Is it because the device is no longer K1 and is now Xoom that it wont work wth lenovo usb drivers?
Please help. Thanx.

Is there a chance for a Version based on
K1_A301_12_12_120109_M_GE
for the UMTS/3G+wifi model?
Thanks.

Twist79 said:
Is there a chance for a Version based on
K1_A301_12_12_120109_M_GE
for the UMTS/3G+wifi model?
Thanks.
Click to expand...
Click to collapse
Yup yup
Can someone with the M_GE edition hop into freenode irc #ideapad-k1 with me to test it. If you don't have an irc client you can just go to http://webchat.freenode.net/?channels=ideapad-k1
[Edit]
Updated the first post with a link to K1_CWM_120109_M_GE_Rooted.zip for my mobile friends in Austria
thanks to isime13 for testing

Thanks I will try it ASAP. And this comes from Austria and not Germany.

Feedback for the DE Version.
look like rooted on the first look.
Superuser app installs fine.
BUT: Apps don't get super user rights. superuser cant update itself and busybox pro complains it cant install because it does not get superuser rights.
So on the second look...no it does not work right.

[Q]Is there a possibility to install rom on sd

Welcome. Already he was just asking about the same with the addition of some suggestions.The init.d directory has the opportunity to start up the concrete near the beginning of a comment, start the machine.One could initiate concrete partitions on the SD card to have played a role partition "mtd" for example / system / data / cachefrom what I noticed the kernel to jb has otherwise changed little these partitions (size).I do not know exactly how it looks with them, but if one could perform 2 partitions by mtd / system (small to perform the basic start-up and later redirects to / systemsd and the rest used as a framework or a particle cache?)
examples of partition
mtd / system (start-up)
mtd / ram (unless you know)
mmc / fat32
mmc / systemsd (the rest of the system)
mmc / data
mmc / .......
and so onthat was a minimum of 4 block
for it is our memory that was on the phone at the same time much bigger and faster (unless there think) than a swap sdanother thing that applications were loaded into the framework so that if they were around 500 + mb ram for the system to switch on only long landing and later had to speed up.I came up with this idea a bit strange when I have made applications to change fat32, after connecting the USB cable.for me my memory card is slightly odd partitions of personal reasons
Class10+ 32gb
fat32 / sdcard 26gb block1
ext4 / 4gb sd-ext Block2
swap ... 2gb block3
fat32 / sdcard2 2gb block4
sorry to my poor english. I hope you understand my gibberish (a lot of words I could not remember so I used google translator)

-AsA- said:
Welcome. Already he was just asking about the same with the addition of some suggestions.The init.d directory has the opportunity to start up the concrete near the beginning of a comment, start the machine.One could initiate concrete partitions on the SD card to have played a role partition "mtd" for example / system / data / cachefrom what I noticed the kernel to jb has otherwise changed little these partitions (size).I do not know exactly how it looks with them, but if one could perform 2 partitions by mtd / system (small to perform the basic start-up and later redirects to / systemsd and the rest used as a framework or a particle cache?)
examples of partition
mtd / system (start-up)
mtd / ram (unless you know)
mmc / fat32
mmc / systemsd (the rest of the system)
mmc / data
mmc / .......
and so onthat was a minimum of 4 block
for it is our memory that was on the phone at the same time much bigger and faster (unless there think) than a swap sdanother thing that applications were loaded into the framework so that if they were around 500 + mb ram for the system to switch on only long landing and later had to speed up.I came up with this idea a bit strange when I have made applications to change fat32, after connecting the USB cable.for me my memory card is slightly odd partitions of personal reasons
Class10+ 32gb
fat32 / sdcard 26gb block1
ext4 / 4gb sd-ext Block2
swap ... 2gb block3
fat32 / sdcard2 2gb block4
sorry to my poor english. I hope you understand my gibberish (a lot of words I could not remember so I used google translator)
Click to expand...
Click to collapse
I didn't get you.
But it is possible to install rom on sdcard with High read/write speed.(class 6 or higher)
all U need is a dual-boot recovery
(I don't know that u must have a Rom installed in internal memory or not(
Sent From My "ULTIMATE ROM- gb - WP8 edition" via Tapatalk

yes, but not on my mind
dual-boot umount dir and make new to port img file. mtd block is not changed
my idea if edit mtd block
Memory phone
mtdblock0 /system size 206 mb
mtdblock1 /cache size 50 mb
mtdblock3 /data size 211mb
mayby mtdblock2 is block ram1, ram2 ..... size ~200mb
all ~667mb
my idea is
mtdblock0 /system (basic start-up i don't know mayby 20mb-67mb)
and mtdblock1 is block ram 600mb
of sd card make block to /system /data etc
this is my idea but I do not know if possible

@-AsA-
Hi. I am working on a dual-boot project. I sent you an invite to our group. It would be awesome if we could work together. I have a test kernel ready, if you want to test. It's still a WIP. Everything modified is mentioned there. Please take a look. Thank you.
Looking forward to working with you.
sgt. meow

sgt. meow said:
@-AsA-
Hi. I am working on a dual-boot project. I sent you an invite to our group. It would be awesome if we could work together. I have a test kernel ready, if you want to test. It's still a WIP. Everything modified is mentioned there. Please take a look. Thank you.
Looking forward to working with you.
sgt. meow
Click to expand...
Click to collapse
im helping you on dboot project

The bootloader won't boot directly from the sdcard.
Nevertheless, you can definitely have ROM images in the sdcard and use those while booting android (basically you only have to update init.rc for that).
Check 'multiboot' in my signature for more details.

nobodyAtall said:
The bootloader won't boot directly from the sdcard.
Nevertheless, you can definitely have ROM images in the sdcard and use those while booting android (basically you only have to update init.rc for that).
Check 'multiboot' in my signature for more details.
Click to expand...
Click to collapse
Can we edit bootloader?
Sent from my XPERIA X8 using xda premium

fotak-x said:
Can we edit bootloader?
Sent from my XPERIA X8 using xda premium
Click to expand...
Click to collapse
First make it unlockable for newer devices
Then edit
sent from my W8 using client-server technology

fotak-x said:
Can we edit bootloader?
Sent from my XPERIA X8 using xda premium
Click to expand...
Click to collapse
S1loader is not open source to work with. You could hex-edit it if you had some easy way to flash it and recover from the countless hard bricks the bootloader development process has. Unfortunately this is doable via jtag only. My knowledge is limitted on that area.
Sent from my Galaxy Nexus using xda app-developers app

As for the bootloader, what could be the first real-time editor hex can perform a large change in the machine switched on.
When it comes to dual boot I can help not only the development of a test.
slightly going back bootloader to my x8 from the beginning she had unlocked (date of manufacture 10W40 surprisingly). I had not unlocked. To change the kernel or other heavy operations.Never failed to I managed to brick trying to do specifically
not worried about the phone I'm always ready to purchase a new...

The idea of a modified bootloader is nice, but it have two problem.
1. Modify the bootloader to add capability to boot directly from sdcard is basically useless because this is possible with a simple script in a modified ramdisk. Check the post from nAa, or search the thread about nBoot from feherneoh. This is easy and not need to do dangerous things.
2. The modification of the bootloader is near impossible because:
- the working of S1Boot is not documented
- this is a non-standard raw binary, hard to disassembly/decompile
- if someone can disassembly it correctly, need VERY HIGH skills in native arm assembly programming
- need special hardwares to revive the dead phone after all failed modifications (special cables, setool, etc...)
Don't forget: we had to wait more than a year to get unlocked bootloader (and this modification only skip the security verification), and this is working only with devices what older than 1-1,5 years.
I think if someone have these prerequisites, better if he/she working on valuable things instead of boot from sdcard (add fastboot support to bootloader, etc...)

I was thinking of making nBoot work with JB (it didn't). If that fails we will come up with a new method.
It's almost impossible for us to re-write the bootloader.
It would be super cool if someone added fastboot support to our bootloaders.

nobodyAtall said:
The bootloader won't boot directly from the sdcard.
Click to expand...
Click to collapse
maybe not in our device but its not impossible
http://forum.xda-developers.com/showthread.php?t=2061437

stamatis said:
maybe not in our device but its not impossible
http://forum.xda-developers.com/showthread.php?t=2061437
Click to expand...
Click to collapse
Obviously I was talking about these devices not some Samsung one...
@sgt. meow fastboot support is not something that can be added to an existing bootloader. The bootloader itself has to support this protocol. Hence the only solution would be to switch to another bootloader which would have to be ported from scratch for these devices.
The job would require a tremendous amount of effort since not even miniloader works for them!

Can we use dd to write an entire directory to a .img file? I'm thinking of something.
@nAa
I know. I was just unaware that bootloaders could be ported for our device (even if it meant no sleep for 6 months for the brave dev).

sgt. meow said:
Can we use dd to write an entire directory to a .img file? I'm thinking of something.
@nAa
I know. I was just unaware that bootloaders could be ported for our device (even if it meant no sleep for 6 months for the brave dev).
Click to expand...
Click to collapse
Mtd devices are not block devices. What are you trying to achieve?
Sent from my Galaxy Nexus using xda app-developers app

I was thinking of using feherneoh's nBoot, but in a different way. My idea was to somehow write the current ROM's /system to system.img on sdcard and the same thing with data and cache. Then install another ROM that uses the same kernel (JellySony for example). Then if XXX is present in /sdcard, it would mount system.img as /system (and the same with data and cache), thus enabling dual-boot. In a kinda stupid way.

sgt. meow said:
I was thinking of using feherneoh's nBoot, but in a different way. My idea was to somehow write the current ROM's /system to system.img on sdcard and the same thing with data and cache. Then install another ROM that uses the same kernel (JellySony for example). Then if XXX is present in /sdcard, it would mount system.img as /system (and the same with data and cache), thus enabling dual-boot. In a kinda stupid way.
Click to expand...
Click to collapse
This is how my multiboot mod worked actually - except from the fact that back in those days we couldn't flash custom kernels and the whole job was done via the chroot/hw_config.sh hack.
The bummer is you can't switch kernels so multiboot between say gb and jb is not possible.

nobodyAtall said:
S1loader is not open source to work with. You could hex-edit it if you had some easy way to flash it and recover from the countless hard bricks the bootloader development process has. Unfortunately this is doable via jtag only. My knowledge is limitted on that area.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
...where can i find s1loader in phone? can i pull it out?just curious.....

fotak-x said:
...where can i find s1loader in phone? can i pull it out?just curious.....
Click to expand...
Click to collapse
There are two options:
- Export all the partitions (I think the file is nand_partitions.c) from kernel. The mtdump/dd it.
- Use the mtdmapper module that is in the unlocking bootloader tool to get all the partitions to map and then dump it.
Both ways basically do the same thing and they both have a pretty BIG chance of getting your device hard bricked (even when you are in read-only mode).

Open Source CM10.1 for Dell Streak 7 continuation, and some helpful setup info.

Okay if you do some work to make your Dell Streak 7 work right with the AOKP 4.2.2 here.
Everything you needed is linked in this post to get you up and running with 4.2.2.
Now for the stuff you need to do to make your 7 run big apps like this Rich! Free Casino Slots okay.
First once you have setup you install of 4.2.2 goto system settings. from there goto Developer options.
Once there goto Force GPU rendering and check that.
Now go get Memory Manager from the play store.
Now once you have that running set it's presets to Aggressive.
Once that is done check the Apply at boot.
Now head over to get Trickster MOD Kernel Settings from the store.
Now that you have that start it up and goto General tab.
In there set the I/O Control Scheduler to noop.
Then goto in the same tab, CPU Governor Control and set the Governor to smartassV2.
Now you can try playing around with overclocking the CPU, but I have found most of the 7's don't like anything over 1 GHz top end due to voltages.
But try at your own rick.
Anyway once you have those set then click the first app setting in the upper right and of the app.
Once in there set all of the On Boot setting to on i.e. check them all.
Now you can play with the delays but I have found if they are set to 0 it works better, don't ask why.
Now that we are done with that app the next app to get is Zram Settings Free.
Now once you have that installed.
open it up and check all the check marks you can. DON'T REBOOT THE SYSTEM YET.
Now close that out.
Now get Root Browser.
The reason for this app over others is because this one when it opens and edits files or makes new files or folders will make them so that Android will like them.
Because the next part is only for the brave of hart and mind. LOL
Okay open up Root Browser and get it setup.
Next head to /etc/sysctl.conf file. Open it up and add this to the last of the file.
vm.swappiness = 90
Click to expand...
Click to collapse
or what ever you like from 1 - 100. I set it to 90 so that my system will load most big apps. With out to much lag.
Now that is done and the file saved.
here come the real fun part.
Next head over to Terminal and open it up.
Now in here we put.
su
mount -o rw,remount /dev/block/platform/sdhici-tegra.3/by-name/APP /system
TARG=/system/.swapfile
dd if=/dev/zero of=$TARG bs=$((1024*1024)) count=400
Click to expand...
Click to collapse
The count=400 part is the size of the swap file we are setting up in the /system folder. So if you want something bigger then that put it in as a MB at the count part.
mkswap $TARG
chmod 600 $TARG
Click to expand...
Click to collapse
The last part sets the new swap file to root only keeps it from being deleted.
swapon $TARG
free -m
Click to expand...
Click to collapse
The last two things do this.
1: it tells Android to use the new file as swap.
2: should show you a 400MB size swap file being used.
Now to get this all to restore it's self after a reboot we are going to need to do a bit more, but it's fast should be the end of this.
Okay before we try a reboot head back over to the Play Store one more time and get yourself.
Script Manager - SManager
Now once you get this app setup we are going to make a .sh file.
A .sh file is a shell script file for *inux based systems. Yes that's OS X no matter what apple wants you to think other wise.
Okay to make this file open SManager
Then hit the menu key, then tap new script.
Name it what ever you would like. I called mine swap.sh
Next use the TB editor.
It should have this in the window to start with if not put it in.
#!/system/bin/sh
Click to expand...
Click to collapse
Now the next part to make this all work right.
TARG2=/system/.swapfile
mount -o rw,remount /dev/block/platform/sdhci-tegra.3/APP /system
swapon $TARG2
Click to expand...
Click to collapse
Now once that is saved in your internal SDCard then tap it and then tap the root icon and the boot icon.
Now when you reset the tab it can take up to 2 minutes to fully load out but now swap will be running and the tab will be fast and big apps like games and Netflix should load and work. Now I have only tested this on game like Hit It Rich or Fast 6. I have yet to try it with Netflix so don't blame me if it still don't work.

Can you show your swap output, I cannot remember if I even enabled that option in the kernel.

giveen said:
Can you show your swap output, I cannot remember if I even enabled that option in the kernel.
Click to expand...
Click to collapse
Here is the Terminal output as you asked. As you can see it's working with a swap file.
I have been unable to get it to work with a swap portion be it on the main internal SD Card or on an Ext SD Card.
I'm thinking that it may have something to do with the way Dell did there mounting system, but I have never really been a kernel guy.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is reading from ZRam Setting app.
And here is some more info for you to look at.
Now I only put the file in the system folder because when it was on the SD Cards it would do things to the system that was not good.
That and I kept losing data on the cards.
So I put the swap file in system folder and the script I put in /data/scripts/. The scripts folder I made.
That way when I did my Nandroid backups I would always have the file and scripts.
Any help you could give me to get my script to run at boot with indit.d would be great as I know android don't really have cron in any working form.

michaelcrossland said:
Here is the Terminal output as you asked. As you can see it's working with a swap file.
I have been unable to get it to work with a swap portion be it on the main internal SD Card or on an Ext SD Card.
I'm thinking that it may have something to do with the way Dell did there mounting system, but I have never really been a kernel guy.
View attachment 2901112
Here is reading from ZRam Setting app.
View attachment 2901113
View attachment 2901114
And here is some more info for you to look at.
View attachment 2901115
View attachment 2901116
View attachment 2901117
Now I only put the file in the system folder because when it was on the SD Cards it would do things to the system that was not good.
That and I kept losing data on the cards.
So I put the swap file in system folder and the script I put in /data/scripts/. The scripts folder I made.
That way when I did my Nandroid backups I would always have the file and scripts.
Any help you could give me to get my script to run at boot with indit.d would be great as I know android don't really have cron in any working form.
Click to expand...
Click to collapse
Tutorial [Guide] [Dec.15] How to Tweak and Mod Android Using Init.d Scripts
and, in the jb defconfig,
CONFIG_SWAP=y

Thanks for that link. But it don't help with showing how to make the script do anything that would need SU rights to do.
My script need to be ran as root. But thanks for the info.
And as far as your 2nd part. That's great for that info but what *.conf file does that setting need to be put into?
Sent from my Streak 7 using XDA Premium HD app

michaelcrossland said:
Thanks for that link. But it don't help with showing how to make the script do anything that would need SU rights to do.
My script need to be ran as root. But thanks for the info.
And as far as your 2nd part. That's great for that info but what *.conf file does that setting need to be put into?
Sent from my Streak 7 using XDA Premium HD app
Click to expand...
Click to collapse
I though all init.d scripts ran as root. Why not try it and see?
the second part, is from giveen's github kernel source, and unless the one built into your ROM uses another defconfig, you do have swap enabled.
in terminal, as su, zcat /proc/config.gz > /sdcard/config.txt
then you can look for SWAP in the text file and see what it's currently set to. You can't change whether swap is enabled or not without rebuilding the kernel.

This is after attempting to flash the test kernel.

ElfinJNoty said:
This is after attempting to flash the test kernel.
Click to expand...
Click to collapse
My kernel already has it on, no need to flash any other kernel
https://github.com/giveen/kernel_dell_streak7/blob/cm10.1/arch/arm/configs/streak7_jb_defconfig

giveen said:
My kernel already has it on, no need to flash any other kernel
https://github.com/giveen/kernel_dell_streak7/blob/cm10.1/arch/arm/configs/streak7_jb_defconfig
Click to expand...
Click to collapse
Has what on?
As far as I know, with @bigsupersquid helping, the kernel is missing some things
Like proper modules for logging
If swap is on already, that's good to know...
bigsupersquid was trying to help me make a new kernel, blindly. But could never compile it correctly to be a flashable zip or fastboot the IMG.
@giveen, think we tried to reach out to you via pm

giveen said:
My kernel already has it on, no need to flash any other kernel
https://github.com/giveen/kernel_dell_streak7/blob/cm10.1/arch/arm/configs/streak7_jb_defconfig
Click to expand...
Click to collapse
ElfinJNoty said:
Has what on?
As far as I know, with @bigsupersquid helping, the kernel is missing some things
Like proper modules for logging
If swap is on already, that's good to know...
bigsupersquid was trying to help me make a new kernel, blindly. But could never compile it correctly to be a flashable zip or fastboot the IMG.
@giveen, think we tried to reach out to you via pm
Click to expand...
Click to collapse
I built from that repo with that defconfig.
Not surprising that's what's in the ROM already.
Just couldn't recombine the boot.img in a way that the streak would accept.

You need more than the kernel to build a boot.img that the DS7 will take.
Steps:
1. Download CM10 (or CM10.1 or CM10.2)
2. Download the device tree AND the kernel tree from github
3. Place device tree in source/device/dell/streak7
4. Place kernel in source/kernel/dell/streak7
5. Run "make boot"
6. Fix any compile issues that come up
.....
10. Profit.

giveen said:
You need more than the kernel to build a boot.img that the DS7 will take.
Steps:
1. Download CM10 (or CM10.1 or CM10.2)
2. Download the device tree AND the kernel tree from github
3. Place device tree in source/device/dell/streak7
4. Place kernel in source/kernel/dell/streak7
5. Run "make boot"
6. Fix any compile issues that come up
.....
10. Profit.
Click to expand...
Click to collapse
I was trying instead to split and recombine the cm10.2 boot.img.
Got a readable ramdisk out of it, but when recombined with the new kernel with abootimg (or perl tools, or mkbootimg) I ended up sending off unbootable images. They stuck at the logo I believe.
I don't have a cm10 tree... just cm11. running out of hard drive space, too. But I appreciate the specific info on how to fix the problem. Thanks.

bigsupersquid said:
I was trying instead to split and recombine the cm10.2 boot.img.
Got a readable ramdisk out of it, but when recombined with the new kernel with abootimg (or perl tools, or mkbootimg) I ended up sending off unbootable images. They stuck at the logo I believe.
I don't have a cm10 tree... just cm11. running out of hard drive space, too. But I appreciate the specific info on how to fix the problem. Thanks.
Click to expand...
Click to collapse
I just put my streak on the charger.... Just in case

bigsupersquid said:
I was trying instead to split and recombine the cm10.2 boot.img.
Got a readable ramdisk out of it, but when recombined with the new kernel with abootimg (or perl tools, or mkbootimg) I ended up sending off unbootable images. They stuck at the logo I believe.
I don't have a cm10 tree... just cm11. running out of hard drive space, too. But I appreciate the specific info on how to fix the problem. Thanks.
Click to expand...
Click to collapse
CM11 is a whole 'nother animal, as CM changed a lot of things with the bootup files and how the disks are partitioned/mounted.

DJ Steve and I have an updated kernel for the cm10.1(really an aokp 10.1) ROM by Giveen that is optimized and increases available memory by about 70mb. Amazing how much improvement off of more available ram. Continuing to test and implement changes and add in features. Also working to convert for bootable lollipop ROM.... Stay tuned:
http://forum.xda-developers.com/showthread.php?t=3330564

I think its awesome that you guys are progressing so quickly! Picking up the torch and finishing the race!

[PORT] Ubuntu Touch for LG L90 Dual

Update 30 October 2016: I'm sorry for very long delay. Being a university student make my free time lower considerably. Anyway, new device tarball is released in stable and rc-proposed channel. This version mostly contains minor fixes, but more importantly, this includes fixes for some famous vulnerability, including the Quadrooter and dirty CoW vulnerabilities. Go to "System Settings" to get your update, or follow instructions below if you haven't update your phone since 9 January 2016.
I still ship experimental fixes in rc-proposed that may freeze your phone when the screen is off. If this matters to you, you may consider using stable channel for now, but that has pretty bad power consumption (but that still means about one day of light usage). Also, there is known bug about mobile network not usable on some network that affects all channels.
Oh, and for those stay on absolute bleeding edge on devel-proposed channel, I currently don't have enough time to test that. So, no release to devel-proposed just yet. Sorry!
Disclaimer
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
By the way, this disclaimer is actually copied from somewhere else just to protect me from being in the court, and I won't actually laugh at you if your device bricks. If your device really bricks, I will help you as much as possible.
Introduction
This is a port of Ubuntu touch to LG L90 Dual and all L90 models. (See below for tested devices.) Basic functionalities work, but there're still some rough edges all around. It's stable enough to use daily, and I personally use it on my phone every day. If you're tired of Android, you may want to give Ubuntu touch a try.
Tested device
This doesn't mean other devices aren't supported. If your device is labeled as "L90" (or can run Cyanogenmod for LG L90), you can give this a try.
LG L90 Dual (D410) (My device )
LG L90 D405n (single card) (Thanks, keturidu!)
LG Optimus L90 D415 (T-Mobile variant) (Thanks, JamesB3)
Click to expand...
Click to collapse
What's working/not working
Note that this is tested using rc-proposed channel.
Screen: Works
Touch: Works
Audio: Works
Screen rotation: Works
Vibration: Works
Camera: Stil picture works for both camera. But video recording doesn't work for the front camera.
Mobile Phone: Works for both SIM, but please see "Bugs and workarounds" below for info about 3G slot and data connection.
Wifi: Works
Video playback: Works
GPS: Works.*
Bluetooth: Works, but on/off doesn't.
*Do note that Wi-Fi-assisted location isn't available as it's licensed for the official devices only.
Click to expand...
Click to collapse
Screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Information about device tarball and channel selection (obsolete)
Now, you don't have to worry about correct device tarball anymore. You just type in correct channels in the command, and the flashing software will get the correct files for you. You can find out more about Ubuntu touch channels at https://developer.ubuntu.com/en/start/ubuntu-for-devices/image-channels/. If you're in doubt, I recommend you to use stable channel.
Click to expand...
Click to collapse
How to install/upgrade
Installing for the first time (updated):
The easiest way to install it is using ubuntu-device-flash. All of your personal data will be deleted. Make sure you backup everything important before install.
You have to root your device and unlock device's bootloader. This forum has a good tutorial on that.
For rooting, I recommend http://forum.xda-developers.com/lg-l90/general/guide-root-l90-varients-updates-t2928364. If that doesn't work, try http://forum.xda-developers.com/showthread.php?t=2732311. This guide is guaranteed to work.
For unlocking bootloader, I recommend http://forum.xda-developers.com/lg-l90/general/guide-guide-to-unlocking-bootloader-l90-t2852917
Also, you'll need an Ubuntu (virtual) machine.
If your device has been running Lolipop, you may have to flash Kitkat-based bootstack for your device (http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632). Make sure you know exact phone model (Dxxx__).
Follow the instruction for preparing your desktop in this link.
Select channel (see information about selection above). Don't download device tarball. The flashing software will get it for you.
Enable ADB for your device. I won't teach you here, but, again, this forum has a good tutorial about that.
Plug your device into your computer. Then, put the device in fastboot mode by running the following command:
Code:
adb shell su -c 'dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/boot bs=16 count=1'
adb reboot
The first command will wipe the first 16 bytes of the boot partition. So, when the device reboot, it'll boot into fastboot mode as the boot partition is broken. Don't worry, it'll be flashed by Ubuntu Touch anyway.
When the device is in fastboot mode, run the following command:
Code:
sudo ubuntu-device-flash --server http://system-image.ubports.com/ touch --channel ubuntu-touch/{selected channel} --device w7 --bootstrap --wipe
There maybe some trouble flashing recovery. If that happen, re-plug the USB chord and try again. You'll see a lot of text and then purple recovery screen. At this point, the computer will push the files into your device. Don't unplug your USB chord until the device reboot again with big Ubuntu logo spinning. Wait until the device reboot into Ubuntu Touch, and, viola, Ubuntu Touch is installed!
Upgrading your device or switch channel (updated):
If you've updated your device with new instruction at least once (since 9 January 2016) and just want to update the device tarball, just go to "System settings" on your device to get your update. But if you've never updated with the new instruction, read on.
Enable developer mode on the device by going to System Settings > About this phone > Developer mode. If you don't have a passcode for your device, set it now by pressing Lock security. Then, enable developer mode by pressing at the check.
Plug your device into the computer, unlock your device (this is important) and run:
Code:
ubuntu-device-flash --server http://system-image.ubports.com/ touch --channel ubports-touch/15.04/stable
Don't unplug your USB chord until the device reboot again with big Ubuntu logo spinning.
Flash different (Android-based) recovery:
Ubuntu recovery can't be used to flash Android-recovery-format ZIP file. If you want to go back to Android using backed up file or ZIP file, you'll need custom Android-based recoveries, such as TWRP or CWM. You'll need raw disk image (IMG file) for this. Run the following command in terminal:
Code:
adb reboot recovery
# wait for recovery to appear
adb push {recovery image name}.img /cache
adb shell dd if=/cache/{recovery image name}.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
adb reboot recovery
Click to expand...
Click to collapse
Download & Source code
You don't need to download device tarball manually anymore as flashing software will deals that for you. But if you want, you can download device-specific tarball using --download-only flag with ubuntu-device-flash. Be warned that you can't flash that image directly because updater in recovery image won't trust the signature.
Customization on the Android side can be found in the local manifest in this Github repository:
https://github.com/peat-psuwit/ubuntu-phone_manifest_w7
All kind of pull request is welcome on all of my repository.
Most customization on Ubuntu side can be found at
https://launchpad.net/~peat-new/+archive/ubuntu/lg-d410-custom/+packages
For those interested, this is programs that make phone call on this device works: https://github.com/peat-psuwit/pulseaudio-droid-card-parameters-setter
Click to expand...
Click to collapse
Legal notice
This distribution of software contains software from Android Open Source Project and CyanogenMod Project. It's under Apache license. Additionally, this distribution also contains software that is normally distributed with Android system, being under various licenses. The detail of license of those files is at /system/etc/NOTICE.html.gz after the system is installed.
This distribution of software contains part of PulseAudio. (Particularly, the modified version of droid module.) It's licensed under GPL version 2 or any later version of GPL. (it's actually distributed under LGPL 2.1+, but it's used with GPL-only libraries, making the effective license GPL. Please look at /usr/share/doc/pulseaudio-module-droid/copyright for detail). Get the patch at https://github.com/peat-psuwit/pulseaudio-droid-card-parameters-setter
This distribution of software contains timekeep, a small utility to keep track of time & date. This is Copyright (c) 2015, Sony Mobile Communications Inc, and licensed under 3-clauses BSD license. The full license can be seen at https://github.com/peat-psuwit/timekeep/blob/master/license.txt
Old legal notice:
This distribution of software contains modified version of oFono, Open Source Telephony. It's licensed under GPL version 2. You may have your source-code at https://launchpad.net/~peat-new/+archive/ubuntu/lg-d410-custom/+packages
This distribution of software contains part of GStreamer, open source multimedia framework. (Particularly, the modified version of androidmedia plugin.) It's licensed under LGPL version 2 or any later version of LGPL. You may have your source-code at https://launchpad.net/~peat-new/+archive/ubuntu/lg-d410-custom/+packages
Click to expand...
Click to collapse
Changelogs
Latest update: 30 October 2016
Fix problem where pressing buttons below the screen in certain way will cause screen not to go sleep.
Fix Quadrooter, dirty CoW, and other vulnerabilities.
Change some aspect of build system.
Make system use our GPS configuration instead of system's default.
Older update
16 June 2016
Fix thumbnail generation for some video resolution.
Revert NetworkManager workaround added in the last release as NM 1.2 is now in both rc-proposed and stable channel.
Change method to wait for Bluetooth config at startup.
Change grid unit size to 13px.
(rc-proposed only) Run init.zetaw.post-boot.sh when the phone finished booting. This'll make battery consumption a lot lower but will cause the phone to lock up sometimes. That's why I release this fix to rc-proposed channel only. If you can't bare with something like this, switch to stable channel.
28 April 2016
Add a workaround for NetworkManager, to fix Wi-Fi connectivity after mobile data is disconnected. The actual fix is preparing to land in rc-proposed soon, but until then, let's use this workaround.
8 April 2016
Update Pulseaudio-module-droid to incorporate audio recording fix.
4 April 2016 (rc-proposed only update)
Update Pulseaudio-module-droid
Update configuration to run ADB in secure mode.
Update recovery image.
11 March 2016
Fix race condition in Bluetooth initialization code.
Update recovery image
4 March 2016
Enable Bluetooth in kernel and android parts.
Update recovery image
6 February 2016
Update pulseaudio-module-droid distributed in device tarball.
9 January 2016
Enforce GPG verification for UBPorts system-image server.
Reduce possibility to reboot at startup due to Wi-Fi subsystem.
3 January 2016
Fixes in kernel and framework for camera due to changes in Ubuntu side.
Make Wi-Fi (pseudo-)on/off works. This fix Wi-Fi not work at startup.
Change the way to distribute Pulseaudio module.
Fix for touchscreen not working in new revision of Ubuntu.
20 November 2015
Split device tarball into 2 versions.
Disable some service in Android container that crashes all the time.
26 August 2015
Working video recording.
4 July 2015:
Include timekeep, a small utility to keep track of time & date.
Remove oFono and gstreamer1.0-plugins-bad, as patches are accepted upstream.
8 Jun 2015
Working GPS.
Update oFono.
1 Jun 2015
Working mobile phone for both SIM slots.
Update gstreamer1.0-hybris, oFono and droid module of PulseAudio, for supporting new Ubuntu version (wily).
6 May 2015
Finally working video playback. Although this is not so good as I cannot make hardware rendering works yet.
Include a modified version of gstreamer1.0-hybris package.
Update oFono and droid module of PulseAudio.
17 April 2015
Update Pulseaudio.
7 April 2015
Fix Wi-Fi
Temporary disable ubuntu-location-service. As GPS doesn't work yet, leaving that enable will make battery drain fast as it'll always try to load GPS library.
4 April 2015
Fix mobile phone in the hackery way.
17 March 2015:
Partially fix camera. It can take a still picture, but cannot record video.
Fix the problem about GPG signature properly. The hack is no longer needed.
Click to expand...
Click to collapse
Bugs and workarounds
Note that this list is based on rc-proposed channel and stable-based device tarball.
At boot, the device may freezes and restarts itself. This is due to the Wi-Fi system and I'm investigating this issue. This is due to fatal subsystem failure in the kernel. I've reduced possibility for Wi-FI subsystem (this is the most common failure), but this may still happen but at the lower rate.
If Wi-Fi list doesn't update during the day, turn Wi-Fi off and on.
Turning Wi-Fi on and off currently doesn't work. (Note that while you can turn Wi-Fi on-off in system settings, the Wi-Fi chip will be not turned off.)
If you're using rc-proposed channel, you may experience lockup when you're trying to wake the phone up from sleep. Currently, there's no fix yet, but if you can't live with it, use stable channel instead.
If you're using some mobile provider, your phone will not be able to detect SIM card. The fix is being developed. (If you're curious, it's about comunication between RILD and oFono and how your SIM card is programed.)
Fixed or disappeared problem:
Camera will stop working after you bring camera app from suspended state. Workaround: bring app back to suspend state and bring back again. This can be done by swiping from left edge. This seems not be the case now.
Sometime, the device may seems freeze because an app is crash. This seems to be the problem in graphic subsystem. The system may becomes responsive again after seconds, but if it takes too long, just restart the phone. This seems not be the case now.
Sometime (at boot or sometime after), Wi-Fi stops working. This can be noticed by having Wi-Fi network list not updated. Fixed by pseudo-on/off fix.
Second One or both SIM slots may stop working at some boot. Simple rebooting should fix it. You may have to reboot multiple times. Seems to be disappear.
3G slot selection doesn't work when there's only 1 SIM card. Workaround: use another SIM slot. (Fix released)
Data connection will work with only 1 of the slots (the one you most recently used before flashing Ubuntu touch. Don't worry, if you can't remember you van try them both). Workaround: put the SIM card with a data plan in another SIM slot. If you happened to have only 1 SIM and the slot that data works is different from the slot with 3G capability, I recommend you to temporary borrow another SIM card from your friend so that you can change 3G slot. change 2G slot in system settings. Fix accepted and released.
Click to expand...
Click to collapse
Credits goes to
Quarx2k for the initial Cyanogenmod port.
Cyanogenmod for many components I used to simplify my build.
Every contributor of LG L90's device tree on Cyanogenmod.
Ubuntu for the porting guide.
awe, ogra, abeato, rsavelti, popey, anpok, and much more people on irc.freenode.net #ubuntu-touch
Sony for timekeep.
mariogrips for UBPorts.
Click to expand...
Click to collapse

Im not testing yet as you dont have phone call working.. But when you do i'm going to take a peek..
Enviado do meu LG-D405n através de Tapatalk

I will try it when I have the time. I have been waiting to try Ubuntu Touch
Question: Does this method of install wipe custom recovery?

ardentis said:
Question: Does this method of install wipe custom recovery?
Click to expand...
Click to collapse
This method will install Ubuntu's recovery before using that recovery to install Ubuntu Touch. So, yes, your custom recovery will be wiped.

I would love to test this out on my D415. Once you get mobile phone and wifi(because t-mobile's mobile data sucks here. I only get 2G xD ), Once those two things get solved i'll be happy to test. Also I think if you moved this thread over to the android development section you'll get more interest shown. I know Ubuntu isn't android but it's still technically development.

JamesB3 said:
I would love to test this out on my D415. Once you get mobile phone and wifi(because t-mobile's mobile data sucks here. I only get 2G xD ), Once those two things get solved i'll be happy to test. Also I think if you moved this thread over to the android development section you'll get more interest shown. I know Ubuntu isn't android but it's still technically development.
Click to expand...
Click to collapse
I'm working on mobile phone now and I promise that Wi-Fi will be the next. Anyway, I cannot guarantee that it'll work on your phone, because I have only LG L90 Dual (D410). It may boot or it may not. I have no clue at all.
BTW, I don't know how to move the thread. Please tell me how.

peat_psuwit said:
I'm working on mobile phone now and I promise that Wi-Fi will be the next. Anyway, I cannot guarantee that it'll work on your phone, because I have only LG L90 Dual (D410). It may boot or it may not. I have no clue at all.
BTW, I don't know how to move the thread. Please tell me how.
Click to expand...
Click to collapse
That's great! I understand I just want to ask if I will have any way to get my device back to android if it doesn't boot?
And you could probably PM the moderators of the forum and get them to move it.

I'm a fan of ubuntu. Never heard much of the mobile version though. How much app is available on this platform or are Android apps also compartible?

ichiato said:
I'm a fan of ubuntu. Never heard much of the mobile version though. How much app is available on this platform or are Android apps also compartible?
Click to expand...
Click to collapse
There are a little over a thousand apps right now and its just an upcoming platform so it doesnt have good support yet. Android apps are not compatible and will not be officially compatible though someone will eventually change that.

ardentis said:
There are a little over a thousand apps right now and its just an upcoming platform so it doesnt have good support yet. Android apps are not compatible and will not be officially compatible though someone will eventually change that.
Click to expand...
Click to collapse
Thanks. Is there any way I can browse through the list of apps and see? I also read somewhere that the apps for desktop version are compatible with that of the mobile version. How through is this?

ichiato said:
Thanks. Is there any way I can browse through the list of apps and see? I also read somewhere that the apps for desktop version are compatible with that of the mobile version. How through is this?
Click to expand...
Click to collapse
https://uappexplorer.com/ is an unofficial app store. I know nothing about compatibility other than what Canonical has said. I have no experience using Touch. It would be awesome if Touch could be flashed by zip because I dont feel like f-ing up my only phone..

Has anyone tested this rom yet? I am curious how well it performs and of any bugs. I want to install it but I dont want to screw anything up

Is there anyway to recover from this if it doesnt work? Or anyway to go back to android?
Is the developer still working on the project at all?

JamesB3 said:
Is there anyway to recover from this if it doesnt work? Or anyway to go back to android?
Click to expand...
Click to collapse
You can take a backup with CWM/TWRP before install. If the rom doesn't work, you can boot into recovery, flash CWM/TWRP back, and restore your android.
If in doubt, you can always install stock rom via KDZ file. Search this device's forum for instruction.
JamesB3 said:
Is the developer still working on the project at all?
Click to expand...
Click to collapse
I'm still working on it if the time permit. The latest update have working Wi-Fi now. Please, don't ask the question like this again, because porting an operating system is not an easy task.

peat_psuwit said:
You can take a backup with CWM/TWRP before install. If the rom doesn't work, you can boot into recovery, flash CWM/TWRP back, and restore your android.
If in doubt, you can always install stock rom via KDZ file. Search this device's forum for instruction.
I'm still working on it if the time permit. The latest update have working Wi-Fi now. Please, don't ask the question like this again, because porting an operating system is not an easy task.
Click to expand...
Click to collapse
Oh ok thats cool. I'll test on D415 when i have time.
I know. I apologize.

peat_psuwit said:
You can take a backup with CWM/TWRP before install. If the rom doesn't work, you can boot into recovery, flash CWM/TWRP back, and restore your android.
If in doubt, you can always install stock rom via KDZ file. Search this device's forum for instruction.
I'm still working on it if the time permit. The latest update have working Wi-Fi now. Please, don't ask the question like this again, because porting an operating system is not an easy task.
Click to expand...
Click to collapse
Do i use Ubuntu's terminal to install?

Instructions for installing Ubuntu can be found here: https://developer.ubuntu.com/en/start/ubuntu-for-devices/installing-ubuntu-for-devices/.
Instructions for reverting back to android can be found here: https://developer.ubuntu.com/en/start/ubuntu-for-devices/reinstalling-android/.
I don't know if the installation instructions will vary at all since we have our own image instead of pulling from their repository....but I imagine it would be similar.
Hope that helps!

JamesB3 said:
Do i use Ubuntu's terminal to install?
Click to expand...
Click to collapse
Yes, you'll use terminal in Ubuntu to type those command. I'm not sure if ubuntu-device-flash is available on another Linux distro.
BellaMay95 said:
Instructions for installing Ubuntu can be found here: https://developer.ubuntu.com/en/start/ubuntu-for-devices/installing-ubuntu-for-devices/.
Instructions for reverting back to android can be found here: https://developer.ubuntu.com/en/start/ubuntu-for-devices/reinstalling-android/.
Click to expand...
Click to collapse
Most of installing instruction will apply here, just don't forget to specify device as generic and provide our device tarball. The parts that doesn't apply is about unlocking bootloader, because we actually can't do it that way. Instead, use instruction in this device's forum.
The reverting instructions can't be used here, as LG doesn't ship our device's ROM in that format. Instead, search this device's forum for instruction.

I tried to install but after install recovery it says that i´ve no space on the device

afpereira said:
I tried to install but after install recovery it says that i´ve no space on the device
Click to expand...
Click to collapse
I guess you probably need to check free space on your computer. The phone probably have enough space to install this.
But if it still doesn't work, please copy full message printed on the terminal. The error should say if it happen on the phone or on the computer.