Related
Please read this entire post!
<<<This is a link to the... FAQ Click it!!>>>
I have created a complete bundle of GingerBread with the newest kernel from GIT (Feb 28 / 1276), and the newest rootfs from GIT (Feb 24).
Please, feel free to DONATE to the XDAndroid project!
Every little bit helps!
Directions:
1. Download the full bundle (zip). (Updated Mar. 11 2011)
If instead you just want the system.ext2 (zip) file (updated Mar. 25 2011) by itself... Don't download this unless you know you want to update!!
2. Extract it. You’ll see a folder, GBX0A, copy its contents to the root (base) of your SD card. If you want to run Android from a folder instead of all the files on the root of the card, follow the steps below.
3. Go into the STARTUPS folder. Grab the appropriate startup.txt for your device (if you don't know what device you have, you should read the FAQ), and move it to the root of the card (or where you run haret.exe from. If you want to change the location of the build, put a rel_path= statement in the cmdline section of the startup.txt. Mine is located two folders deep on the SD, so my rel_path=Androids/TP2Ref)
4. Download the ts-calibration file from this post (should work for RHOD/TOPA) and extract the .zip to where you run haret.exe from - typically the root or 'base' folder of the SD card. Not within any folders, unless you run haret.exe from a folder!
**If you have issues with the above file, you must calibrate manually. To start manual calibration, just delete any ts-calibration files and boot. Sometimes this doesn't work, and you have to use an older kernel from GIT (I found 1225 works well) and generate the ts-calibration file by booting and pressing the 5 zones. Once you have a good calibration file hold on to it (make 15 copies if it's a really good one ), reboot & go back to the newest kernel from the autobuild service! Thanks**
6. Run haret.exe... Profit!
Let it settle out on the first boot. Many have reported they had to reboot basically because it was so slow - if you let it sit for about 10 mins or so the media scanner can go thru everything, etc. If you want adb in and watch the processes via top, you'll see why the phone seems so slow - there's lots of background processes cranking because this is the first boot .
Troubleshooting:
Please read the... FAQ
If you have any issues with the kernel, feel free to change it:
There are some devices that are having issues with the newest kernels. Please see the kernel autobuild service to get newer or archived kernels. Once you download a replacement kernel, go to where you run haret.exe from - remove your old zImage/modules-xxxxx.tar.gz. Take the new zImage/modules-xxxxx.tar.gz and replace the old ones, same folder - where you run haret.exe from. Make sure the ‘zImage’ is named just that. Do not rename the modules file, do not extract it - should be in .tar.gz format.
In addition, I am using the newest rootfs from GIT - Feb. 10. There are other rootfs options, see F22’s thread if you want to use more keys or move around the home button. Of course, there's always the roofs autobuild service if you want "stock" rootfs images - F22 builds his off of these and modifies them .
See Incremental Updates for more information on this topic of updating!!
Random issues can often be solved by forcing the system to create a new data.img. If you're worried about losing data, Titanium Backup works quite well. If you wish, you can rename the data.img to something else, and let the system create a new one - just to see if it resolves your problem.
Similarly, if you wish try formatting your SD card - I prefer to use the HP Tool - do a full format, FAT32.
Obviously this build is Alpha, and there are going to be problems. The next post will address issues particular to this build - PLEASE READ THESE before asking questions! Feel free to post questions in this thread, I will do my best to address them. Big thanks to stinebd for releasing the system image, and of course the other developers for their hard work on making these kernels available.
stinebd's original post HERE
Mar. 11 2011 Changelog
Things broken in this build:
libgps - explains itself, no GPS and probably no netloc (cell-tower based location). I think this also breaks the stock browser, I recommend using Dolphin Mini!
HW3D is either not working, or just not preset - I ran neocore and let's just say a lot of textures are missing. Got a ridiculous score, but again - no textures, not much to render haha.
Data - very flaky - CDMA users have data break for them after every phone call, and GSM users seem to have better luck but it's not flawless. Even seen reports of wifi having issues with data not going out to the WAN. There is a bug filed on this issue.
Anything that's broken in Froyo, is probably broken in this build. Although what is interesting, I noticed that in this build I don't have the landscape-on-boot issue that I get with Froyo...
Changelog March 25, 2011
Further tuned keyboard sizing to be useful on VGA (also made the key labels bigger)
World-phone settings support (very important for future RIL enhancements especially on CDMA)
Enabled HSPA icon (someone on GSM please let me know if it actually works)
Works good so far
Been using this for about 3 hours so far. Here's a little review. Upgraded through Stinebd's link in the XDAndroid thread (same as this I guess, but the arggggh's complete package includes all files needed). I deleted the data.img and replaced my system2 file. The first boot set itself up and then rebooted to winmo. The second boot worked. I was able to download Titanium backup from the market and restore my apps that I was using in Froyo. Overall it was working well. The default keyboard is tiny on my screen. My data connection is a little finicky as it was working when I restored my apps, but I could not connect after a while (same thing happened in my Froyo build periodically). As far as speed is good and bad, sometimes it's quick, other times it's quite slow. Overall, it's pretty good considering it was just released to us. Looking forward to future builds.
Edit: I reused my calibration file from Froyo. No issues
Rhod400, 2/10 Zimage and Rootfs from GIT
mmm, I may be blind but I can't see any download link! I'd like to test it and let you know!
anyway I already want to thank you for the hard work!
The system file was posted by stinebd in this thread:
http://forum.xda-developers.com/showthread.php?t=627997&page=1226
Thanks, I've included the original link to stinebd's post in my first post.
Still working out kinks, and stine will probably want me to host it on files.xdandroid.com - sorry for the delay... It will be here soon .
so this is the neopeek build only in an image?
husam666 said:
so this is the neopeek build only in an image?
Click to expand...
Click to collapse
This has nothing to do whatsoever with neopeek. This is AOSP code, modified to work on our phones. The system image work is done entirely by stinebd, and I have made a bundle - Link up!
arrrghhh any idea what the kernel incompatibility comes from? Thats strange...
edit- nvm I reread it a 5th time and understood heh
randomblame said:
arrrghhh any idea what the kernel incompatibility comes from? Thats strange...
Click to expand...
Click to collapse
You mean the calibration issue? Some commit broke it, not sure which one. There's rumors that we can read it from the spl, then we won't need a kernel-based calibration - we'll be able to do it in userland, which is really what we want especially going forward to NAND.
Gonna try this release this weekend
rhod100 does have the same panel problems as on a FRX04 release a guess?
JBS2 said:
Gonna try this release this weekend
rhod100 does have the same panel problems as on a FRX04 release a guess?
Click to expand...
Click to collapse
Panel problems are kernel related, not system image related.
What kernel do you run FRX04 on...? Thanks.
arrrghhh said:
Panel problems are kernel related, not system image related.
What kernel do you run FRX04 on...? Thanks.
Click to expand...
Click to collapse
Most recent from your testing topic.
Panel wakes up very slow normally or after touching the screen or power button multiple times.
JBS2 said:
Most recent from your testing topic.
Panel wakes up very slow normally or after touching the screen or power button multiple times.
Click to expand...
Click to collapse
Ah. Again, that's a testing kernel. Let's keep testing kernel discussion in that thread and build talk about this build in this thread... Thanks...
arrrghhh said:
Ah. Again, that's a testing kernel. Let's keep testing kernel discussion in that thread and build talk about this build in this thread... Thanks...
Click to expand...
Click to collapse
I know, you asked which kernel I was using
Just wondering if these release has something to do with the panel issues but I realize this is a kernel related problem.
Keep up the goog work, I'll keep testing the testing kernels to see if the known problem could be fixed
Okay, here's my 2cents:
BTW, i use rhod100.
Hardware3d doesn't work because the line is missing from the startup (as far as i am concerned, maybe you removed it on purpose).
steyn_e said:
Okay, here's my 2cents:
BTW, i use rhod100.
Hardware3d doesn't work because the line is missing from the startup (as far as i am concerned, maybe you removed it on purpose).
Click to expand...
Click to collapse
That entry is no longer required. Put it in and see... Thanks!
this is such an exciting build. It runs really fast. keep up the good work guys. Btw, to get a bigger gingerbread keyboard, search for "gingerbread Keyboard" in the market. its a larger sized version of the one that comes with the rom.
kdub94 said:
this is such an exciting build. It runs really fast. keep up the good work guys. Btw, to get a bigger gingerbread keyboard, search for "gingerbread Keyboard" in the market. its a larger sized version of the one that comes with the rom.
Click to expand...
Click to collapse
I've already included a fix in the second post, thanks!
Warning: Use this fix at your own risk. Please do not pm me for support on this. I'm just sharing a fix I found already in place and used in another rom.
Credit: 100% credit goes to iamgpc http://www.mobile01.com/topicdetail.php?f=224&t=1957441&m=f&r=3&p=1 http://forum.xda-developers.com/showthread.php?t=909096 .
Problem:
- Outgoing (dialing out) volume defaults to the maximum. The work around is to either hit the volume + or - or turn the speaker phone on and off quickly during a outgoing to force the device to pick up the preset volume
- Depending on the preset volume, incoming calls could be quiet and outgoing calls can be extremely loud depending on the htcleo.acdb file
- I had this issue on almost every rom I used
Solution - libaudio.so
- During my testing of "gpc_hd2_gingerbread_v19b" rom, I noticed this issue did not exist on this particular rom.
- Traced this back to libaudio.so after comparing various libs under /system
- Pushed libaudio.so from the gpc rom to /system/lib/ using tyween's "Typhoon" rom and noticed the max outgoing call volume issue was not longer present
Fix
- Highly recommend doing a nandroid back-up prior to applying fixes. If fix does not work and cause boot loops, you will have to restore /system .
- Extract and push the lib files from the attached zip file to /system/lib/.
or
- Try flashing the zip using CWM. I quickly slapped it together so not sure if it is working correctly
Tested to work on following rom's:
libaudio-fix-CM-Typhoon.zip for the following builds:
- tyween's "Typhoon CM7 2.4.5" rom no longer needed. Incorporated in V2.5+
- Mdeejay 2.6 CM7 build - Based on user feedback
- Pongster's HyperDroidGBX v7 - Based on user feedback
libaudio-fix-NexusHD2-Ginger-tytung.zip for the following builds:
- Tytung's "NexusHD2 Gingergread 2.3" rom
- rafpigna's RAFDROID HD 3.2.2 - SD build only
- Untested on other builds
Change log:
- Mar 02, 2011 - Added separate zip file (libaudio-fix-NexusHD2-Ginger-tytung.zip) for Tytung's ginger bread
Nice man!
Edit: Just tried on a Desire build doesn't boot for me
after installing in rafdroid 3.1 it stucks in the first screen.....
Doesn't work on NexusHD2-Gingerbread
At startup:
E/AndroidRuntime( 94): java.lang.UnsatisfiedLinkError: Cannot load library: link_image[1962]:
66 could not load needed library 'libsystem_server.so' for 'libandroid_servers.so' (link_image[1962]:
66 could not load needed library 'libaudioflinger.so' for 'libsystem_server.so' (link_image[1962]:
66 could not load needed library 'libaudio.so' for 'libaudioflinger.so'
(reloc_library[1311]: 66 cannot locate '_ZN7android14AudioParameter7keyFmOnE'...
Click to expand...
Click to collapse
Maybe it worked only on CM7 builds
Works very good for me.
MDJ cyanogenmod 7 v. 2.6
It doesn't work with 2.2.1
Thanks for the hard work. Tested working perfect on Typhoon 2.4.5..
stanleywoon said:
Thanks for the hard work. Tested working perfect on Typhoon 2.4.5..
Click to expand...
Click to collapse
I am not sure I feel this really makes a difference.
All my calls starts with the other party saying:
"wow, it's very loud on your side."
or
"you are talking too loud"
I thought this fix would have solved the problem.
Any suggestions ?
Zagzag read again the first post its not fixing you "problem"
DimICE said:
Doesn't work on NexusHD2-Gingerbread
At startup:
Maybe it worked only on CM7 builds
Click to expand...
Click to collapse
Thanks for the logcat. Updated to work on Tytung's NexusHD2 gingerbread build. Use zip libaudio-fix-NexusHD2-Ginger-tytung.zip.
zagzag99 said:
I am not sure I feel this really makes a difference.
All my calls starts with the other party saying:
"wow, it's very loud on your side."
or
"you are talking too loud"
I thought this fix would have solved the problem.
Any suggestions ?
Click to expand...
Click to collapse
The high mic gain is a separate issue. There is a fix by using a different htcleo.acdb file. Try searching for the fix. I don't have the link at the moment.
pecora said:
Works very good for me.
MDJ cyanogenmod 7 v. 2.6
Click to expand...
Click to collapse
Yes. Ive got a same detection. Great work .......... Thanx
Tested working on RAFDROID Desire HD 3.2.2 - SD build. This should also work on Rafdroid Desire HD 3.2 nand build.
You think it will also work on Desire based build? (not HD)
DFT
will this work on the DFT version of MDJ CM7 2.6? If so how can I apply it?
Working with HyperDroidGBX v7! Thanks! libaudio-fix-CM-Typhoon.zip
But it feels like volume is loud at first, but than quickly became normal..is it ok?
The Phone Volumen works fine now,but the Media Volumn become too low?
Anyone have the same Problem?
PS: Typhoon_CM7_2.4.5
EDIT: The ideal solution for this problem is to fix the source code. Unfortunately, I don't have the time and proper tools to decompile the lib file libaudio.so. Any Dev's want to give this a try? I'm not sure if this lib is based on the passion(Nexus one).
ITAYSHARONI said:
You think it will also work on Desire based build? (not HD)
Click to expand...
Click to collapse
Which Desire build are you using? I'm not certain if these fixes will work on the Desire build you are using. Unfortunately the libs are not consistent between builds and contain different modifications. When changing anything in /system, there is always the risk of having to restore.
If you are comfortable with basic ADB commands, you could copy the original libs as backup and push them back using ADB if you get a bootloop. But be warned, you may have to reflash causing data loss if you use a DFT based flash(no clockwork mod recovery). I should note I've intentionally caused the bootloop on various builds just to identify the libs that are different between builds and have always been able to recovery from boot loop pushing the original files back.
lowrider262 said:
will this work on the DFT version of MDJ CM7 2.6? If so how can I apply it?
Click to expand...
Click to collapse
You could try using either adb or root explorer to manually push the file. Make sure you back up the original lib file. I would strongly recommend you try Typhoon CM7 rom. It is much more up to date in comparison to Mdeejay's rom.
Kefir.net said:
Working with HyperDroidGBX v7! Thanks! libaudio-fix-CM-Typhoon.zip
But it feels like volume is loud at first, but than quickly became normal..is it ok?
Click to expand...
Click to collapse
This appears normal. The volume is at max for half a second and corrects to the pre-set value.
freemanxp said:
The Phone Volumen works fine now,but the Media Volumn become too low?
Anyone have the same Problem?
PS: Typhoon_CM7_2.4.5
Click to expand...
Click to collapse
I'm running the same rom and don't notice any difference in media volume.
2000impreza said:
Tested working on RAFDROID Desire HD 3.2.2 - SD build. This should also work on Rafdroid Desire HD 3.2 nand build.
Click to expand...
Click to collapse
Which CWM-Zip file did you use , becouse i want to try it on my rafdaroid 3.2 NAND
Im using Bauner-LEO-V4_20.02.11_cwm Build
When i tried the first file it didn't eve got to a bootloop, it got stuck on htc logo
zaidsa3sa3 said:
Which CWM-Zip file did you use , becouse i want to try it on my rafdaroid 3.2 NAND
Click to expand...
Click to collapse
I would highly suggest doing a nandroid backup before flashing. As indicated on the first post, try zip file: libaudio-fix-NexusHD2-Ginger-tytung.zip for Raftdroid rom.
ITAYSHARONI said:
Im using Bauner-LEO-V4_20.02.11_cwm Build
When i tried the first file it didn't eve got to a bootloop, it got stuck on htc logo
Click to expand...
Click to collapse
Unfortuneately I don't have the time to look at the libs for this rom to figure what will/won't work. Since it uses CWM to flash the rom, you could do a nandroid backup followed by flashing zip file: libaudio-fix-NexusHD2-Ginger-tytung.zip to see if it works. Worse case, restore /system from the nandroid backup if it doesn't work.
The best solution is to rebuild libaudio.so from source to correct the issue. Unfortuneately I don't have the expertise nor time to do this. Any dev's willing to look at this?
[updated 20150104]
version v2.2
migration to twrp2.8.3.0
quickfix for lzma initrd roms
fix baseband not recognized on some tw roms
added f2fs feature to multiboot kernel for future versions..
moved qemu tools to sdcard to free space
[updated 20150101]
version v2.13
lollipop support
Hi all,
This dev thread is to continue the multiboot thread that I starded few months ago in general section.
To read history of the project you can take a look here http://forum.xda-developers.com/showthread.php?t=2577211
With Multiboot, you can launch any ROM from your internal card or your external sdcard. It is a TWRP recovery ROM modified to add this feature.
This feature is possible thank's to kexec-hardboot method created by mkasic (http://forum.xda-developers.com/showthread.php?t=1266827).
I adapted this method to be able to apply it quite easily on any android device.
This method includes few pieces of software ( sources will be published) :
kexec-hardboot : kernel patch from mkasic
hardboot-reserve : new kernel patch
kload-hardboot : new userspace program
Next part of the method is an on the fly modification of initrd ramdisk before injecting new kernel/initrd. Early versions of multiboot (before v1.2) were simply modify [on fs] section of init.rc to replace original block devices ( mmcblk0p14, mmcblk0p15 etc ) by loop devices pointing to img files.
Since Multiboot v1.2, a new method is used to replace original filesystems : a script replace original init binary, his goal is to prepare all the filesytems before launching original init.
All this method is done by shell scripts that you can check in /sbin and /multiboot directories when booted into recovery.
Creating img files (raw) is very efficient on internal sdcard as this card is formatted ext4 and img files can be thin provisiionnig ( sparse files ).
Unfortunaltely, external sdcard are offently fat32 or exfat formated. Those filesystems do not support thin provisionning ( note also that multiboot supprot only vfat for the moment ).
Creating img files on vfat filesystems is very long process and consume lot of space.
Version Multiboot V2.1 add support for ubuntu touch 14.04 support ( only img files )
Version .Multiboot V20 introduced a new feature : qcow2 support for external sdcard.
With qcow2 image files, we can create small images which grows only when needed.
You can check some video demonstrating features of multiboot on youtube channel : http://www.youtube.com/channel/UCefO8F4YX6qMQsqpBHTqTqQ
Main advantages of using qcow2 :
thin provisionning
snapshots
compression
liveboot ( livefull if small rom, "livedvd-like" if bigger roms )
Some problem (and solutions) of qcow2 :
need target kernel with nbd support - nbd is very easy to activate when compiling kernels but not already activated on kernels. Decimalman kernels already are compiled with it. http://forum.xda-developers.com/showthread.php?t=2226889
Slow speed on standard : speed on qcow2 especially when first installation is not good. To reduce this, livesnap booting mode gives very good speed.
suspend/resume : on tw43 kernels, deepsleep can hang the system. To correct it, their are 2 methods : adding a wakelock or apply a small patch to nbd.c sources.
Some details about qcow2 booting mode :
- standard : qcow2 images are acceded read/write directly on sdcard ( not recommended especially in firsts boot )
- livesnap : qcow2 images are acceded read, writes are done in zram snapshots. commit are done at reboot time : this is the recommended mod. If you install apps, you'd better to reboot first to commit qcow2. Note that if modifications are big, reboot can be long ( few minutes ), be patient. Note also that in this mode, I added a wakelock to fix suspend/reboot of tw roms.
- liveboot : same that livesnap but without commit - Same than a LiveCD in linux world. reboot speed is regular
- fulllive : only for small roms ( say ~500M ). All qcow2 are copied to zram at boot and mounted from memory. No internal/external card needed. very good speed.
- livesnap2 : same than livesnap but without wakelock. Best for speed and battery. Working except tw43. Download my modified dkp kernel to use this option on tw43 roms.
Important recommendations :
- when choosing qcow2, always choose the right nbd kernel as the last zip to install ( and don't reboot after Aroma installer )
take dkp kernels for tw43 and kk4.4.2 : http://forum.xda-developers.com/showthread.php?t=2226889
or kernels I compiled
- please follow videos on youtube
Here are last video I did to demonstrate qcow2 features. Some parts of video are boring ( during compression or commit ) but I wanted to let it go live to give an idea of processing times.
Downloads : http://www.androidfilehost.com/?w=files&flid=12801
References / Credits :
mkasic : kexec-hardboot creator - http://forum.xda-developers.com/showthread.php?t=1266827
Tassadar : MultiROM creator - best project - http://forum.xda-developers.com/showthread.php?t=2011403 - bbootimg used
TWRP Team : http://www.teamw.in/project/twrp2
reserved
First
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Love your work Philippe. This has been amazing to use for testing out multiple roms and still maintaining my daily driver. I'm a crack flasher so its nice having the options to constantly change.
Sent from my SCH-I535 using Tapatalk
Totally forgot about this, I'll have NBD included in my next kernel so this can work
this is awesome ! i been looking for muilt-boot since i got an S3 !
it's working great!
Awesome!
Now does it matter what bootloader you're on for this?
i want to try this... but the bandwidth Nazi's at work wont let me download and watch YouTube videos. would the main ROM need to be on the internal memory? or would it matter? just wondering.
Do these videos have audio? kinda hard to follow... or it just my laptop?
Restore
Hello,
Since I install the V2.0 I can't restore my new backup. I can restore the backup make before V2.0 installation but the one made with V2.0 multiboot.
Restore Failed
I try with different TWRP 2.6.3.1 and 2.7.0
Do you have and idea how to fix that.
Thanks
PwnCakes193 said:
Totally forgot about this, I'll have NBD included in my next kernel so this can work
Click to expand...
Click to collapse
I will add a link to your kernel in first message when it becomes compatible with qcow2 support.
vbetts said:
Now does it matter what bootloader you're on for this?
Click to expand...
Click to collapse
There is no prerequisite about bootloaders versions. Just be sure that your bootloader is unlocked ( I mean that you can install custom recovery images - for example, verizon 4.3 ota update locked the bootloader )
stanguay said:
Hello,
Since I install the V2.0 I can't restore my new backup. I can restore the backup make before V2.0 installation but the one made with V2.0 multiboot.
Restore Failed
I try with different TWRP 2.6.3.1 and 2.7.0
Do you have and idea how to fix that.
Thanks
Click to expand...
Click to collapse
As multiboot feature does not have relation with this part of twrp, not sure if it is linked with multiboot.
Do you have same behavour with original twr2.7.0 ?
Philippe,
ubuntu touch trusty in progress
Hi all,
Just to give a small news.
I started try to port latest ubuntu touch release (trusty) and to integrate it to multiboot.
Now, at least, I can boot on it, get the GUI, touchscreen, wifi, rotation, battery level and on/off button working.
( everything else not working : no sound, no phone, no gps etc... )
But at least, it is "usable" to play with it... Also, I integrated it to multiboot.
Don't know if you want to try that at this stage ( not sure than I can go further and get other things to work....)
Just tell me, I will package this week-end a multiboot v2.01 and ubuntu_touch_trusty_d2att.zip.
Here is a small video : http://youtu.be/y1G9hZI3deg
Philippe,
Philippe,
Phil_Suz said:
Hi all,
Just to give a small news.
I started try to port latest ubuntu touch release (trusty) and to integrate it to multiboot.
Now, at least, I can boot on it, get the GUI, touchscreen, wifi, rotation, battery level and on/off button working.
( everything else not working : no sound, no phone, no gps etc... )
But at least, it is "usable" to play with it... Also, I integrated it to multiboot.
Don't know if you want to try that at this stage ( not sure than I can go further and get other things to work....)
Just tell me, I will package this week-end a multiboot v2.01 and ubuntu_touch_trusty_d2att.zip.
Here is a small video : http://youtu.be/y1G9hZI3deg
Philippe,
Philippe,
Click to expand...
Click to collapse
I remember the last time someone built Ubuntu Touch to the d2att S3, but we ran into the same issues as you previously mentioned. Will there ever be a way to get the data to work?
codemonkey98 said:
Will there ever be a way to get the data to work?
Click to expand...
Click to collapse
Hi codemonkey98, the answer is possibly yes.
In fact, I succeeded to make cellular data work under my ubuntu touch port ( Bell carrier) .
Just have to confirm this first experimental results - I can surf internet with cell data ( without wifi ).
However, phone line is still not working.
[edit] Also sent and received SMS, so this is working also.
Philippe,
Phil_Suz said:
Hi codemonkey98, the answer is possibly yes.
In fact, I succeeded to make cellular data work under my ubuntu touch port ( Bell carrier) .
Just have to confirm this first experimental results - I can surf internet with cell data ( without wifi ).
However, phone line is still not working.
[edit] Also sent and received SMS, so this is working also.
Philippe,
Click to expand...
Click to collapse
I'd be very interested in testing the very alpha versions of this, as long as they're d2att or d2lte. best of luck man, i'm looking out for great stuff from you.
https://www.youtube.com/watch?v=j6GdvUfNppE In this video I see that you booted in the ROM w/o flashing gapps along w/ flashing the ROM ... is that necessary for this to work?
If you need a tester for anything, I'm always available.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
shekinahsmoke said:
https://www.youtube.com/watch?v=j6GdvUfNppE In this video I see that you booted in the ROM w/o flashing gapps along w/ flashing the ROM ... is that necessary for this to work?
Click to expand...
Click to collapse
Hi shekinahsmoke, no it is not necessary at all. It's better to install all zip in one shot, but I did this demo to show that you can come back to multiboot, select an already created rom and apply another zip ( gapps in this example ) even after first installation.
codemonkey98 said:
I'd be very interested in testing the very alpha versions of this, as long as they're d2att or d2lte. best of luck man, i'm looking out for great stuff from you.
Click to expand...
Click to collapse
rani9990 said:
If you need a tester for anything, I'm always available.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Hi codemonkey98 and rani9990, thank's for your future help on testing. I am now able to call and be called . I fixed partially audio too. Calling ring and microphone during call are now ok, only incoming audio is problematic ( because exit from speaker and not earphone ).
Fall-back temporarly solution is to plug headset, in this case everything is fine during phone calls.
Now, I will start to prepare version 2.1 of multiboot to support this ubuntu touch and I will probalby open a dev thread dedicated to this ubuntu touch 14.04 when I finish first package ( this we or start of next week ).
Philippe,
Phil_Suz said:
Hi codemonkey98 and rani9990, thank's for your future help on testing. I am now able to call and be called . I fixed partially audio too. Calling ring and microphone during call are now ok, only incoming audio is problematic ( because exit from speaker and not earphone ).
Fall-back temporarly solution is to plug headset, in this case everything is fine during phone calls.
Now, I will start to prepare version 2.1 of multiboot to support this ubuntu touch and I will probalby open a dev thread dedicated to this ubuntu touch 14.04 when I finish first package ( this we or start of next week ).
Philippe,
Click to expand...
Click to collapse
I'm glad to hear. I appreciate you shedding some light towards us with Ubuntu Touch and your support for multiboot. :good:
Hi All,
Multiboot v2.1 is now ready on same download link ( http://www.androidfilehost.com/?w=files&flid=12801 )
This version add support for unbutu touch 14.04.
Philippe,
Phil_Suz said:
Hi all,
Just to give a small news.
I started try to port latest ubuntu touch release (trusty) and to integrate it to multiboot.
Now, at least, I can boot on it, get the GUI, touchscreen, wifi, rotation, battery level and on/off button working.
( everything else not working : no sound, no phone, no gps etc... )
But at least, it is "usable" to play with it... Also, I integrated it to multiboot.
Don't know if you want to try that at this stage ( not sure than I can go further and get other things to work....)
Just tell me, I will package this week-end a multiboot v2.01 and ubuntu_touch_trusty_d2att.zip.
Here is a small video : http://youtu.be/y1G9hZI3deg
Philippe,
Philippe,
Click to expand...
Click to collapse
I would love to try your touch port I have been using your recoveries for a few weeks now and just flash the touch wip Rom that is on the site but to have a simi-working port to play with would be awesome.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
CyanogenMod 11 with crDroid additions for Xiaomi MiPad
!! IMPORTANT !!
xep.8800.org will be temporarely down from 29.03.15 for couple of weeks so it would be great if somebody do mirror of latest buld and post link here. Thx!
About:
Source built CM except proprietary blobs and binary kernel from stock MIUI rom.
This is not a port from another binary rom.
Click to expand...
Click to collapse
What's working:
It seems everything working for now..
Click to expand...
Click to collapse
Not working/Bugs:
"Wi-Fi region code" setting is broken. Do not touch it or it will break your wi-fi.
you tell me.. testing in progess..
Click to expand...
Click to collapse
Instructions:
1. Install CWM Recovery
2. Do Full Wipe If coming from another ROM
3. Flash ROM
4. Flash Google Apps (my recommendation is to install minipal gapps due to /system partition size limits)
5. Reboot
Click to expand...
Click to collapse
Multirom Instructions:
1. Install TWRP Multirom Recovery
2. Reboot into TWRP and install multirom-20150205-v30-UNOFFICIAL-mocha.zip
3. Click "Advanced->Multirom" and flash your desired second rom.
4. Return to the installed roms listing, click fresh installed rom and click "Remove boot.img" (Due to closed kernel sources kexec-hardboot is not implemented so we need to remove boot.img)
5. Reboot. Select your desired rom from multirom menu
Click to expand...
Click to collapse
Downloads:
cm-11-20150327-UNOFFICIAL-mocha.zip
CWM
Multirom:
TWRP_multirom-v2.8.4-mocha.zip
multirom-20150205-v30-UNOFFICIAL-mocha.zip
I don't know if it is actually compiled with TEGRA optimizations but have created CWM flashable zip with stock bionic libraries. You can flash it on top of CM installation:
tegra_bionic.zip
Changelog:
15.02.15
* apply qcom bionic optimization
* build.prop dalvik etc tweaks
02.02.15
* Reboot to recovery fixed
* Recents view proportion fixed
26.01.15
* Synced with CM repo
* have enabled Display mirroring (miracast) though it does not work with my EZ dongle, sound is ok but screen is black. May be it'll work with another dongles...
21.01.15
* Update to the latest kernel from stock MIUI
20.01.15
* Sleep issue fixed
* Adopt nvcplsvc for CM & implement Performance Profile selection
18.01.15
* Synced up with CM repo.
* Added USB Mass Storage mode for external sd. Though it does not work along with ADB Debug enabled, need to be switched off when using UMS mode.
17.01.15
* Switch to CM's audio_effects and make Dirac plugin work. Equalizer crash fixed.
Click to expand...
Click to collapse
Links:
http://github.com/cyanogenmod
http://github.com/cristianomatos
https://github.com/faust93
Click to expand...
Click to collapse
I take no responsibility for what this may or may not do to your device.
Do not forget to click Donate button! It makes me work harder!
Thanks Pumbaster for your work!
My device doesn't seem to go to sleep...
WakeLockDetector shows Android System --> ConnectivityService as the main issue. BetterBatteryStats shows the same...
I tried turning location services off, froze Mobile Data and Mobile Network Configuration in Titanium Backup but that doesn't help. No checking if the same wakelock appears with wifi off...
Anyone with any clue? Or the same problem?
Will check the ROM and tell you dagrim.
But first thing first, I have to install it. And I have 2 questions, to avoid screwing things.
- Does it works with TWRP instead of CWM?
- Is there a reason to have a June version of minimal gapps where a version of December exist?
Thanks to everyone in the process (romers, informers, helpers)
Krystanos said:
Will check the ROM and tell you dagrim.
But first thing first, I have to install it. And I have 2 questions, to avoid screwing things.
- Does it works with TWRP instead of CWM?
- Is there a reason to have a June version of minimal gapps where a version of December exist?
Thanks to everyone in the process (romers, informers, helpers)
Click to expand...
Click to collapse
I used pico gapps myself and the june version is way smaller then the december version, then again I actually did try the december version as well and it seemed to work fine. So not sure, apart from the size...
About TWRP vs CWM, not sure. Guess it also should work with TWRP but haven't tried... CWM is needed for True Dual Boot, but that seems bugged anyway.
By me too. Battery drain is to much, device don't go to sleep...
zolikaDB said:
By me too. Battery drain is to much, device don't go to sleep...
Click to expand...
Click to collapse
Yeah, seems to be a common issue.
My device only goes to sleep when wifi is turned completely off. When I have it set to turn off when display is off I still get the wakelocks. I also have set the scanning for open wifi to off, location services turned off, etc.
For now I flashed back to the 0114 version as that one is working fine here...
If I can share some logs or anything, I'd be more then happy to!
@dagrim1: I hope, Pumbaster make new, fixed build
I Encounter Graphical Glitches with 3rd Party Browsers (Opera and UC Browser)
Chrome works fine so far. Also heavy Battery drain an 17/1
@faust93: what is with battery drain?
Did a very dirty try or replacing frameworks.jar but that didn't work...
Saw some wifiStateTracker errors and that and ConnectivityService seemed to be part of the framework, that's why I gave it a shot. 0118 still has the deespleep/wakelock issue btw...
I don't really care about dual boot. MIUI has so much limits. Once I go to CM, I don't think I'll be able to come back to MIUI...
But I'll stick to CWM, just in case...
I just tried the wpa_supplicant.bin file posted by pumbaster on 4pda and it seems to solve the deepsleep issues!
Post 351 of the custom mipad 4.4.4. rom thread there...
http://xep.8800.org/mipad/wpa_supplicant.bin
Place in system/bin and set permissions to rwxr-xr-x
@faust93: I hope you don't mind me posting this here but I saw you posted links to the same location in the topic start, if so my apologies and I will remove it asap (but I am going to sleep now, so won't be up until next morning...)
Also had some iussues with stuttering video playback, but setting 'disable hardware overlay' in developer settings fixed that for now...
Thanks for the awesome work!
dagrim1 said:
I just tried the wpa_supplicant.bin file posted by pumbaster on 4pda and it seems to solve the deepsleep issues!
Post 351 of the custom mipad 4.4.4. rom thread there...
http://xep.8800.org/mipad/wpa_supplicant.bin
Place in system/bin and set permissions to rwxr-xr-x
@faust93: I hope you don't mind me posting this here but I saw you posted links to the same location in the topic start, if so my apologies and I will remove it asap (but I am going to sleep now, so won't be up until next morning...)
Also had some iussues with stuttering video playback, but setting 'disable hardware overlay' in developer settings fixed that for now...
Thanks for the awesome work!
Click to expand...
Click to collapse
Is this bin file integrated in 2015.01.18 build? What do you know about this ROM? Did you test it?
zolikaDB said:
Is this bin file integrated in 2015.01.18 build? What do you know about this ROM? Did you test it?
Click to expand...
Click to collapse
I don't believe it's integrated in 0118, think that fixes some sd stuff...
I am currently running the 0118 build (with the wpa_supplicant.bin file replaced manually) and seems to be working pretty fine. Had some video issues with a certain app (video jumping a bit, stuttering) but think I fixed that with 'disable hardware overlay' in developer options.
Without the replaced .bin I also had a problem with turning off and on wifi. It would work when booting, but if I turned it off I couldn't turn it on again... The replaced .bin also fixes that. Now checking if antutu finishes it's run...
@dagrim1: hope, Pumbaster fix this problem!
Just another small question: full wipe will delete the /data partition too right ? So the ROM zip file will be deleted too ? Or am I missing something ?
Thanks.
I tried to install with TWRP and when I reboot, I get to MIUI v6 so I guess it rebooted in the wrong system.
jastonas said:
I tried to install with TWRP and when I reboot, I get to MIUI v6 so I guess it rebooted in the wrong system.
Click to expand...
Click to collapse
Unfortunately I tried to install CWM with fastboot and it failed to install... No specific error message.
I have seen a port of TWRP for MiPad. Have you tried this one, or the standard one?
How I wish I could just flash CM on my MiPad...
Rom updated on May 19. This is LP 5.1 release 2. Latest Google/CM/Resurrection sources + all hardened features. Plus cleaned IP addresses (got rid of Google, Level 3 communication, AT&T, Orange, Department of Defense and other shady ips). Also enabled is Volte (enhanced LTE), which is Voice over LTE. This depends on the service provided by your carrier. In the States, for example, T-Mobile provides such services, which include high definition voice. Usually, you need special update done by the manufacturer in conjunction with your carrier. This rom does not need that. Your Z1 is already provisioned for Volte. You will see in Mobile Settings another entry: Enhanced 4g LTE Mode. ALso, in test menu/phone (*#*#4636#*#*), you will see a Volte Provisioned Flag. So, as soon as your carrier starts Volte, you are all set.
Sources are the same...
Download Link: http://forum.xda-developers.com/devdb/project/dl/?id=12531
_____________________________________________________________________________________
Rom updated to latest sources on May 4. In addition to regular hardened features, more than 40 instances of Google IP, Level 3 Communication and Department of Defense IPs removed from sources both for IPV4 and IPV6. The same is replaced with Opendns IP. Keep in mind that those ips go not only in configuration files, but libs also and the latter cannot be decompiled and fixed...
Download link: http://forum.xda-developers.com/devdb/project/dl/?id=12289
______________________________________________________________________________________
Rom Updated to LP 5.1.1. All hardened/security features implemented. Kernel used from Slimroms 5.1.
TWRP 2.8.6 is integrated in kernel.
Obviously, this is an alpha version...
Download Link: http://forum.xda-developers.com/devdb/project/dl/?id=12110
Kernel Source: https://github.com/AOSP-Argon/kernel_sony_msm8974/tree/lp5.1
___________________________________________________________________________________________________
Rom updated to 5.1: all hardened features enabled.
Download link: http://forum.xda-developers.com/devdb/project/dl/?id=11901
___________________________________________________________________________________________________
March 31: kernel updated to include screen color calibration:
See Download link: http://forum.xda-developers.com/showpost.php?p=59801528&postcount=94
_________________________________________________________________________________________________
March 27: New build is up, latest CM and Resurect changes; kernel includes voltage table, syncookie and TWRP.
Download Link: http://d-h.st/lw2s
Mirror Link: http://forum.xda-developers.com/devdb/project/dl/?id=11744
_________________________________________________________________________________
March 15: New build is up including latest sources, TWRP integrated in kernel, led lights fixed
DOWNLOAD LINK: http://d-h.st/UO7W
_______________________________________________________________________________________________
Marchh 7: Rom Updated to the latest version + plus all security enhancements. Sources for security changes are the same as posted
See Download section for update
Here is Resurection Remixed Lollipop hardened and secure. Built from sources on February 24.
Changes:
First of all, as many know, encryption on lollipop slows down the device to almost unusable. I was able to resolve that. The culprit was Qualcom crypto module and drivers that collide with graphics. In this rom, when you encrypt your device, there is no noticeable slow down at all. Your master encryption key is no longer stored in crypto module (which rumor has it is backdoored anyway), but rather hashed and salted on the drive itself.
1. Modified kernel to disable creepy SElinux and enable Tomoyo security. Now you can safely use Xposed framework and some modules such as Xprivacy, Appsettings and ShowDialpad, as well as many others
2. Modified kernel to disable qualcom module and drivers
3. Disabled creepy qualcom random number generation and enabled all other methods
4. Enabled 256 bit AES drive encryption as opposed to Google's default 128 bit
5. Enabled all ciphers and hashes available in kernel and disabled by default (thanks Sony and Google)
6. Latest CM changes
7. Omniswitch (to be flashed separately after flashing the rom)
Maybe more
INSTALL:
1. Be on Kitkat, rooted with CWM or TWRP
2. Enter Recovery, wipe System, Data, Cache
3. Flash the rom
4. Flash Omniswitch
5. Reboot and enjoy
If you want to encrypt your device, you need to do 2 additional steps before or after encryption. Go to Developer Options and enable "Force GPU rendering" and "Disable HW overlays. Yes, you have to enable (not disable) "Disable HW overlays" option. The latter won't stick after reboot. So, manually transfer the attached init.d script to /system/etc/init.d and set permissions to at least 744. This way the option will be set at boot and you won't have any noticeable slowdown. In fact, I don't see any difference in speed between encrypted and non encrypted device.
CREDIT: Resurection-Remix Team, Cyanogenmod, AOSP and Omniroms
WARNING:
I am not responsible if your device explodes and kills everyone around. You are doing it on your own. Russians, who are definitely coming, won't help you either :laugh:
Download links
Rom: http://d-h.st/l1rB For Update see Download Section
Omniswitch: http://d-h.st/AbGH
Init.d script (in case you want to encrypt your data): http://d-h.st/QIiE
Sources: https://github.com/ResurrectionRemix
https://github.com/HonamiZ1/android_system_vold
https://github.com/HonamiZ1/kernel_sony_msm8974
XDA:DevDB Information
Resurection-Remixed Lollipop 5.1.1 Hardened, ROM for the Sony Xperia Z1
Contributors
optimumpro
ROM OS Version: Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP, Cyanogenmod
Version Information
Status: Testing
Created 2015-02-25
Last Updated 2015-05-19
screenshots
Screenshots added
Kernel updated with CPU voltage table
Kernel updated to allow under/over volting. See attachment.
Instructions:
1. Unzip the file
2. Flash in fastboot: fastboot flash boot boot.img and fastboot reboot
Enjoy
Thanks for this ROM, are there any known bugs?
wis3m0nkey said:
Thanks for this ROM, are there any known bugs?
Click to expand...
Click to collapse
All CM bugs as of February 24. You can go on their site and see the list of changes...
optimumpro said:
All CM bugs as of February 24. You can go on their site and see the list of changes...
Click to expand...
Click to collapse
So just need to look at http://forum.xda-developers.com/xperia-z1/general/rom-official-cyanogenmod-12-nightlies-t3007118 is that right?
Sorry I have to confirm, there are multiple threads (Official/Development) for CM12.
This ROM will maintain root and recovery, right?
I'll flash and let you know if I find any other issues.
Tried it. Works great. Some strange problem with mms though. Could not load them even though data works perfectly. Battery life looks great. Didn't try calling so i can't say anything about the mic.
Kyrius said:
Tried it. Works great. Some strange problem with mms though. Could not load them even though data works perfectly. Battery life looks great. Didn't try calling so i can't say anything about the mic.
Click to expand...
Click to collapse
I use Textsecure as sms replacement. Microphone works great...
Very buggy
you should definately fix this rom as i cannot start camera it fc. it restart itseft
NOT STABLE
darkdevu said:
you should definately fix this rom as i cannot start camera it fc. it restart itseft
NOT STABLE
Click to expand...
Click to collapse
1. Learn the rule about not posting bug reports without logcat
2. Camera works fine: verified
3. Always wipe System/Data/Cache before flashing
4. Are you sure you have Xperia Z1?
Cheers
his profile says Z3. lol
Any further reports on this ROM? Interesting to know how it performs and about stability
Deleted
wis3m0nkey said:
Thanks for this ROM, are there any known bugs?
Click to expand...
Click to collapse
Rom Updated to the latest version. See Download section in the OP.
and where is the link to the update?
shikimafia said:
and where is the link to the update?
Click to expand...
Click to collapse
It is in Download section:
http://forum.xda-developers.com/devdb/project/?id=8412#downloads
Screenshots added in post #2. Note that only this rom and SlimLP work with the latest Xpivacy module. Tried on Crdroid and others and there is bootloop as soon as you enable Xprivacy.
Has no one tried this rom as not reports or posts
tried flashing update from scratch and get play services fc on every gapps i used............i am guessing i may have to flash initial release and dirty flash this over it? excuse me if i may have got it wrong
shingers5 said:
Has no one tried this rom as not reports or posts
Click to expand...
Click to collapse
Well. The first version had 69 downloads. The latest one had 20. Other than the bogus claim about camera foreclosing (by someone who has Xperia Z3) there were no reports of problems. I have been using this rom for about 10 days without any problems...
optimumpro said:
Well. The first version had 69 downloads. The latest one had 20. Other than the bogus claim about camera foreclosing (by someone who has Xperia Z3) there were no reports of problems. I have been using this rom for about 10 days without any problems...
Click to expand...
Click to collapse
I'm having issues flashing the new version as getting play services errors.... Was gonna try dirty flash over previous versions