Develop Bugs

[ROM-DEV] Ubuntu Touch port for Desire Z [WIP][Sources Alpha1&ROM Alpha3 ONLINE]

{
"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"
}
DEVELOPERS ONLY
These builds are very unstable and should not be used on a daily base. It's pretty much just a preview of a preview. Use these builds at your own risk!
Ubuntu Touch is not ready for daily usage yet and these builds lack a lot of functionality usually available in Ubuntu Touch - you have been warned!
I will publish new builds when new features are done! Please do not aks for ETAs as this is very new stuff to work on, for me.
Code:
#include
/*
* 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.
*/
This is very early port of Ubuntu Touch for the HTC Desire Z.
This is a developer preview! Do not expect it to have every bell and whistle functional.
Have fun!
Video​Thanks to HTCDreamOn
No more needed!!!
Pre-requirements:
ADB commands
Some knowleges with ADB commands
To start Ubuntu Touch (until I fix it!)​
Plug your device to your computer,
In a prompt, type :
For Linux users :
Code:
adb kill-server
sudo adb start-server
Code:
adb root
adb shell
ubuntu_chroot shell
ubuntu-touch-session
Usb can't be unplugged ATM or Ubuntu Touch will be down!!!
Flinny and Andromadus for the work on cm10.1
HTCDreamOn for the kernel
gh1234 for his great help
w-flo (ubuntu mailling liste) for his sources and great help
Some people on freenode live chat
MonkeySnot for banners
Ubuntu
Google

Remember Ubuntu is already in pre-alpha build....
Alpha 3
Speed improvements
+ others minor fix
Alpha 2
Fixed autoboot
Fixed wifi
SMS
Phone call
Sound
Alpha 1
Initial release.
How to Build :​
Follow https://github.com/utopykzebulon/android/blob/master/README.md
Initialize your repo with git://github.com/utopykzebulon/android.git
Add the ubuntu/hybris (lphablet-extras/libhybris) and ubuntu/platform-api (lplatform-api) parts.
Run brunch cm_vision-eng
Hboot need to be updated :
Desire Z :
Boot your device into Bootloader/Fastboot
fastboot devices //Verify that the device is detected
fastboot erase cache //Not sure if this is completely necessary, but the guide I followed included it as a step
fastboot oem rebootRUU //Boot into RUU, which lets you flash HBOOT, radio, etc.
Download DesireZ_Hboot.zip
fastboot flash zip DesireZ_Hboot.zip //Flash the new Hboot 0.85.00015
fastboot reboot-bootloader //Bootloader will write "***locked***", you can unlock it with htcdev.com
TMobile G2 :
I'll need testers, please PM me! thx
***/!\*** All the files must be on the root of your sdcard
Alpha 3
1. Flash updated Hboot
2. cm-10.1-20130725-UNOFFICIAL-vision.zip
3. vision-saucy-preinstalled-phablet-armhf.zip
4. You'll need also "ubuntu-touch-saucy-armhf.tar.gz" you can found it in saucy-preinstalled-phablet-armhf.zip from ubuntu cdimage. extract the .tar.gz
push all the 3 files to the root of your sdcard, install 1. then 2.
Alpha 2
1. cm-10.1-20130705-UNOFFICIAL-vision.zip
2. vision-saucy-preinstalled-phablet-armhf.zip
3. You'll need also "ubuntu-touch-saucy-armhf.tar.gz" you can found it in saucy-preinstalled-phablet-armhf.zip from ubuntu cdimage. extract the .tar.gz
push all the 3 files to the root of your sdcard, install 1. then 2.
Alpha 1
Make a full Wipe,
Copy Ubuntu_Touch-vision.zip to Sdcard root,
Copy install_ubuntu-rootfs_from_sdcard.zip to Sdcard root,
Copy ubuntu-touch-session.zip to Sdcard root,
Copy ubuntu-rootfs.tar.gz to Sdcard root,
Install Ubuntu_Touch-vision.zip,
Install install_ubuntu-rootfs_from_sdcard.zip (this'll take a while.),
Install ubuntu-touch-session.zip,
Reboot, type adb commands and enjoy.

Thanks to gh1234 to give me the way!
Some of old device haven't enough space in /DATA tou install ubuntu-rootfs so we we'll install it from sdcard!
First of all extract "ubuntu-touch-***-armhf.tar.gz" from your "***-preinstalled-phablet-armhf.zip" rename it as "ubuntu-rootfs.tar.gz"
Delete "ubuntu-touch-***-armhf.tar.gz" in your zip file
Patch these both files :ubuntu_deploy.sh and updater-script.
Copy "ubuntu-rootfs.tar.gz" and your patched "***-preinstalled-phablet-armhf.zip" into the root of your sdcard.
Files have to be like this. :
ubuntu_deploy.sh
Code:
#!/sbin/sh
android_boot=/system/boot
ubuntu=/data/ubuntu
ubuntu_boot=$ubuntu/boot
ubuntu_bak=/data/ubuntu_bak
phablet_home=$ubuntu/home/phablet
phablet_home_bak=$ubuntu_bak/home
timezone=$ubuntu/etc/timezone
timezone_bak=$ubuntu_bak/timezone
ofono=$ubuntu/var/lib/ofono
ofono_bak=$ubuntu_bak/ofono
network_settings=$ubuntu/etc/NetworkManager/system-connections
network_settings_bak=$ubuntu_bak/nm_connections
tmp_extract=/data/ubuntu_tmp_extract
backup() {
mkdir -p $ubuntu_bak
if [ -d $2 ]; then
echo "Removing previous backout of $1"
rm -rf $2
fi
if [ -d $1 ]; then
echo "Backing up $1 to $2"
mv $1 $2
fi
}
restore() {
if [ -d $2 ]; then
echo "Restoring $1 from $2"
rm -rf $1
mv $2 $1
fi
}
copy_android_ramdisk() {
if [ -f $android_boot/android-ramdisk.img ]; then
cp -f $android_boot/android-ramdisk.img $ubuntu_boot
fi
}
deploy_ubuntu() {
echo "Deploying Ubuntu"
if [ -d $tmp_extract ]; then
rm -rf $tmp_extract
fi
mkdir -p $tmp_extract
tar --numeric-owner -xzf /sdcard/ubuntu-rootfs.tar.gz -C $tmp_extract
if [ -d $ubuntu ]; then
rm -rf $ubuntu
fi
mv $tmp_extract $ubuntu
}
backup $phablet_home $phablet_home_bak
backup $network_settings $network_settings_bak
backup $ofono $ofono_bak
backup $timezone $timezone_bak
deploy_ubuntu
copy_android_ramdisk
restore $phablet_home $phablet_home_bak
restore $network_settings $network_settings_bak
restore $ofono $ofono_bak
restore $timezone $timezone_bak
Updater-script
Code:
ui_print("");
ui_print("Welcome to the Ubuntu RootFS Sdcard Installer by Utopykzebulon");
ui_print("");
show_progress(1.000000, 60);
ui_print("Mounting system, userdata and Sdcard partitions...");
run_program("/sbin/mount","/system");
run_program("/sbin/mount","/data");
run_program("/sbin/mount","/sdcard");
set_progress(0.100000);
ui_print("Checking Files...");
package_extract_file("ubuntu_deploy.sh", "/tmp/ubuntu_deploy.sh");
set_perm(0, 0, 0777, "/tmp/ubuntu_deploy.sh");
set_progress(0.300000);
ui_print("Deploying Ubuntu Touch from Sdcard...");
run_program("/tmp/ubuntu_deploy.sh");
set_progress(0.800000);
unmount("/data");
unmount("/system");
run_program("/sbin/sync");
set_progress(1.000000);
Or you can download mine from here.

Srlsy dude? Don't post anything, when you're not 100% sure that you have links working, info all over post about rom, and needed stuff. I don't want to mock or offend You, but these are the rules of forum. There was similiar situation few weeks ago.
BTW. Keep working on it.
Sent from my HTC Vision using xda app-developers app

Xardejn said:
Srlsy dude? Don't post anything, when you're not 100% sure that you have links working, info all over post about rom, and needed stuff. I don't want to mock or offend You, but these are the rules of forum. There was similiar situation few weeks ago.
BTW. Keep working on it.
Sent from my HTC Vision using xda app-developers app
Click to expand...
Click to collapse
Man, have a look on it

it's Great ! if the touch and sim card no problem , worth to try it.
utopykzebulon said:
Man, have a look on it
Click to expand...
Click to collapse
THX for DZ the ubuntu touch.

I'm working on screen and WiFi... Screen is better now
Sent from my HTC One using xda app-developers app

good，if you uploaded links， i will be download and to try.
utopykzebulon said:
I'm working on screen and WiFi... Screen is better now View attachment 2023035
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
expect your links！

Wow, cant wait.

When we will see it ?
Sent from my HTC Desire Z using xda app-developers app

Nice job!
Hey, man, just wanted to say it's a great thing you're doing, I'll be following the thread closely! :good:

greed2 said:
When we will see it ?
Sent from my HTC Desire Z using xda app-developers app
Click to expand...
Click to collapse
I'm uploading an Alpha build...

All files are now uploaded...

Only glanced at this in the app, will need to see in browser, but this is all custom build, not flashable zip?
Sent from my HTC Vision using xda app-developers app

Hope ubuntu touch is less ram hungry than android
Good job!! :good:

RE: [ROM-DEV] Ubuntu Touch port for Desire Z [WIP][ONLINE]
@utopykzebulon Finally got the chance to test this now anything specific you want tested/logged/recorded ?
*EDIT*: Woo this is AWESOME thanks so much for this can't wait to see your progress. I've made a quick video about 3 and a half minutes long, but no logs or anything sorry, don't know if they'd've been of any help though, I didn't bother trying wifi etc. as you already seem to know of all the problems. But by god this thing is smooth, I expected serious lag but it seems great to use :good:

HTCDreamOn said:
@utopykzebulon Finally got the chance to test this now anything specific you want tested/logged/recorded ?
*EDIT*: Woo this is AWESOME thanks so much for this can't wait to see your progress. I've made a quick video about 3 and a half minutes long, but no logs or anything sorry, don't know if they'd've been of any help though, I didn't bother trying wifi etc. as you already seem to know of all the problems. But by god this thing is smooth, I expected serious lag but it seems great to use :good:
Click to expand...
Click to collapse
Normally audio, WiFi and auto start are easy to fix... Next build I hope but if you want to try to fix some things I'll be happy cause I don't have a lot of time... Send me the link of your video please I'll push it in the 1st post...

utopykzebulon said:
Normally audio, WiFi and auto start are easy to fix... Next build I hope but if you want to try to fix some things I'll be happy cause I don't have a lot of time... Send me the link of your video please I'll push it in the 1st post...
Click to expand...
Click to collapse
Nobody can tell us to buy a new phone. (if I were rich I would have 3 Desire Zs) Ubuntu touch on DesireZ, WTF?? So nice bro! Keep it up the good work :good:

Can't wait for the sources!
I just flashed and tried your build - it's working pretty nicely! Obviously drivers etc. are the next thing.
I can't wait for you to get the sources uploaded so we can have a poke about!

mrvelvet said:
I just flashed and tried your build - it's working pretty nicely! Obviously drivers etc. are the next thing.
I can't wait for you to get the sources uploaded so we can have a poke about!
Click to expand...
Click to collapse
I'll upload them tonight if I got the time...
Sent from my HTC One using xda app-developers app

[Scripts]i9505 Boot.img Creator (deployable over all kernel sources)

GT-i9505 Boot.img Creator​
Info
I made this little package that includes an automated shell script to build a boot.img file for the desired rom type, ramdisks of TouchWiz, CM 10.1, AOSP 4.2.2 Google Edition and AOSP 4.3 Google Edition are included. Next to that I made a flash script to flash the created boot.img directly on your device. Of course there is also an possibility to push the modules as well and wipe the dalvik-cache.
Its a simple deployment package, you just copy it over your kernel source and use it. (kernel compiling needs to be done by you, its only for distributing the boot.img)
Noob Proof Script
Only use on i9505 or i9505G, do not use on i9500
Screenshots:
{
"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"
}
Beginners reference:
(or download in full hd)
Instructions for developers
Code:
cd to parent directory of kernel source
git clone https://github.com/broodplank/i9505_bootimg_creator
cp -Rf i9505_bootimg_creator/* kernel-source/
cd kernel-source
./build_bootimg && ./flash_bootimg
Download
Download v1.0 or clone it!

Stop making so awesome things
Good work mate

nolinuxnoparty said:
Stop making so awesome things
Good work mate
Click to expand...
Click to collapse
haha no way, i'm just getting started

Very good work broodplank thx...

I'll report this thread.
Just because it's too awesome haha :good:
Thanks for this Will try that out

m3dd0g said:
Very good work broodplank thx...
Click to expand...
Click to collapse
Thanks, and you're welcome
.c0dy said:
I'll report this thread.
Just because it's too awesome haha :good:
Thanks for this Will try that out
Click to expand...
Click to collapse
Hehe nice ^^. probably not portal material but still thanks for the report :good:
Let me know how it works if you tested it

broodplank1337 said:
Thanks, and you're welcome
Hehe nice ^^. probably not portal material but still thanks for the report :good:
Let me know how it works if you tested it
Click to expand...
Click to collapse
Sorry to "spam" your threads ^^
After successfully compiling the kernel with some changes (just for testing ) i wanted to create the boot.img.
So i used your script:
The following error occurs:
Copying zImage and modules
Packing ramdisk
./build_bootimg: line 50: ../mkbootfs: cannot execute binary file
Packing boot.img
./build_bootimg: line 52: ../mkbootimg: cannot execute binary file
Cleaning left overs
Moving boot.img to build/output/boot.img
mv: cannot stat ‘boot.img’: No such file or directory
Click to expand...
Click to collapse

.c0dy said:
Sorry to "spam" your threads ^^
After successfully compiling the kernel with some changes (just for testing ) i wanted to create the boot.img.
So i used your script:
The following error occurs:
Click to expand...
Click to collapse
Ah ok thnx. As soon as im home ill take a look at it. Seems the binary file is missing somehow

broodplank1337 said:
Ah ok thnx. As soon as im home ill take a look at it. Seems the binary file is missing somehow
Click to expand...
Click to collapse
I've found the problem.
Or better said - a solution.
I took mkbootfs and mkbootimg from ktoonse.
After that you have to edit the script as the following:
echo "Packing ramdisk"
../mkbootfs ./boot.img-ramdisk-tw | gzip > ramdisk.gz
echo "Packing boot.img"
../mkbootimg --kernel zImage --ramdisk ramdisk.gz --cmdline "console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3" -o boot.img --base "0x80200000" --ramdiskaddr "0x82200000"
Click to expand...
Click to collapse
to this:
echo "Packing ramdisk"
../mkbootfs ./boot.img-ramdisk-tw | gzip > ramdisk.gz
echo "Packing boot.img"
../mkbootimg --kernel zImage --ramdisk ramdisk.gz --cmdline "console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3" -o boot.img --base "0x80200000" --ramdisk_offset "0x82200000"
Click to expand...
Click to collapse
In short:
Replace mkbootfs and mkbootimg from ktoonse and
change --ramdiskaddr to --ramdisk_offset
EDIT: Can't i commit that on your repo that you can accept it? Or isnt that possible on git?
EDIT 2: That should do the trick https://github.com/c0dycode/i9505_bootimg_creator/commit/6ec6558ed359608fbeb6905ecbc6f5134ccb1fa8

.c0dy said:
I've found the problem.
Or better said - a solution.
I took mkbootfs and mkbootimg from ktoonse.
After that you have to edit the script as the following:
to this:
In short:
Replace mkbootfs and mkbootimg from ktoonse and
change --ramdiskaddr to --ramdisk_offset
EDIT: Can't i commit that on your repo that you can accept it? Or isnt that possible on git?
EDIT 2: That should do the trick https://github.com/c0dycode/i9505_bootimg_creator/commit/6ec6558ed359608fbeb6905ecbc6f5134ccb1fa8
Click to expand...
Click to collapse
Thanks a lot ill merge your changes
edit: done, merged

Hi @broodplank1337 any chance the boot image creator can be updated for 5.01 lollipop? It may help solve an issue several people have had due to flashing CM then reverting back to stock. It seems our cypress keyboards have been updated to 0x1a but Lollipop will only work with FW of 0x12, this info can be checked on your samsung phone with the dialer and typing *#2663#, anyway the only way we can fix this is in the bootcode and certain changes must be made to get the FW softkeys bin back to 0x12.

Match found !!!
Same request here.

[Q&A] [MOD][2013-08-10][V3.03]TURBO BOOST - Triple Swap Space in Cache, Data, System

[Q&A] [MOD][2013-08-10][V3.03]TURBO BOOST - Triple Swap Space in Cache, Data, System
Q&A for [MOD][2013-08-10][V3.03]TURBO BOOST - Triple Swap Space in Cache, Data, System ...
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [MOD][2013-08-10][V3.03]TURBO BOOST - Triple Swap Space in Cache, Data, System .... If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Turbo Boost compitability
I am sorry but i couldn't locate my device in the thred, can i use this with samsung gt s6312 with mammoth kernel v.5 ?
not sure if it has swap support, v2 had , but it was awfully laggy after a while

Sucore said:
I am sorry but i couldn't locate my device in the thred, can i use this with samsung gt s6312 with mammoth kernel v.5 ?
not sure if it has swap support, v2 had , but it was awfully laggy after a while
Click to expand...
Click to collapse
go to the turbo boost thread and see if your device is supported

rzr86 said:
go to the turbo boost thread and see if your device is supported
Click to expand...
Click to collapse
Well i did that and i could not locate my device in there, samsung has a huge variaty and i suppose that maybe gt s6312 is supported but is not mentioned.
Also i tried to reply there but since i have less than 10 posts it redirected me here.
I will search a kernel with swap support for my device and i will test it my self then.
Other question : do i have to backup before?
What is the worst that can happen?
Thank you for your time
Sent from my GT-S6312 using XDA Free mobile app

Tried it with stock 4.3 and Fancy Kernel r56 in a Galaxy Nexus, maguro. Tried with different versions of BusyBox but when I put the command "free -m" in the Terminal Emulator it always says "0 0 0" in the swap voice. So I gave up.

Sucore said:
Well i did that and i could not locate my device in there, samsung has a huge variaty and i suppose that maybe gt s6312 is supported but is not mentioned.
Also i tried to reply there but since i have less than 10 posts it redirected me here.
I will search a kernel with swap support for my device and i will test it my self then.
Other question : do i have to backup before?
What is the worst that can happen?
Thank you for your time
Sent from my GT-S6312 using XDA Free mobile app
Click to expand...
Click to collapse
if your device is not supported somewhere in the turbo boost thread shows how to put the scripts manually AFAIK
also there is a section on how to support your device
you have to pm the devs
but i don't think you will get any answer anymore
AlogarF said:
Tried it with stock 4.3 and Fancy Kernel r56. Tried with different versions of BusyBox but when I put the command "free -m" in the Terminal Emulator it always says "0 0 0" in the swap voice. So I gave up.
Click to expand...
Click to collapse
maybe init.d folder doesn't execute the scripts properly
did you used init.d universal from play store?

rzr86 said:
maybe init.d folder doesn't execute the scripts properly
did you used init.d universal from play store?
Click to expand...
Click to collapse
OK, I did this, now the swap is active, but I don't know how it would work properly. According to the Terminal Emulator the "used" swap was to 4, I tried to open a lot of apps and it went on 7, then 8, then 12. It grows every time I start to open apps to test the multitasking. Now it's 20, is it normal? I thought it would have opened more apps together, but I can't see differences. I chose 150 MB in cache partition.

Does it work with HTC evo 4g?? I got a slimrom 4.2.2

hugobossSM said:
Does it work with HTC evo 4g?? I got a slimrom 4.2.2
Click to expand...
Click to collapse
go to the turbo boost thread and see if your device is supported

Information needed !!!!!!!!!
If this mod creates swap partition on internal storage
isn't there a chance to brick the device ?
Also can i know the reading and writing speeds of redmi 1s
and the speeds at which this mod reads and write

Will this work with miui V5 for htc one v?

Amish. said:
Will this work with miui V5 for htc one v?
Click to expand...
Click to collapse
first check if your device is supported from turbo boost thread
then your kernel must support swap

rzr86 said:
first check if your device is supported from turbo boost thread
then your kernel must support swap
Click to expand...
Click to collapse
Its there in supported devices..how to check whether it will work with my kernel..my kernel is 3.0.16-Charm-CM10..will it work? this one is roms stock kernel.

Amish. said:
Its there in supported devices..how to check whether it will work with my kernel..my kernel is 3.0.16-Charm-CM10..will it work? this one is roms stock kernel.
Click to expand...
Click to collapse
flash the mod
then check from terminal with free -m and cat /proc/swaps
also check in your inetrnal memory if the rom has init.d support
go to system->etc-.init.d

rzr86 said:
flash the mod
then check from terminal with free -m and cat /proc/swaps
also check in your inetrnal memory if the rom has init.d support
go to system->etc-.init.d
Click to expand...
Click to collapse
it does have init.d but after flashing i feel no difference should i change the kernel? will that help?

Amish. said:
it does have init.d but after flashing i feel no difference should i change the kernel? will that help?
Click to expand...
Click to collapse
did you check it from terminal?
also ask in the kernel thread if it supports swap

Test results after installation:
Code:
[email protected]:/ $ su
[email protected]:/ # cat /proc/swaps
tmp-mksh: cat: /proc/swaps: No such file or directory
1|[email protected]:/ # su
[email protected]:/ # free -m
total used free shared buffers
Mem: 1835 1641 194 0 47
-/+ buffers: 1593 241
Swap: 0 0 0
[email protected]:/ #

auastyle said:
Test results after installation:
Code:
[email protected]:/ $ su
[email protected]:/ # cat /proc/swaps
tmp-mksh: cat: /proc/swaps: No such file or directory
1|[email protected]:/ # su
[email protected]:/ # free -m
total used free shared buffers
Mem: 1835 1641 194 0 47
-/+ buffers: 1593 241
Swap: 0 0 0
[email protected]:/ #
Click to expand...
Click to collapse
you have no swap
check if your kernel supports swap
if it supports then install init.d universal from play store
https://play.google.com/store/apps/details?id=com.androguide.universal.init.d&hl=el

rzr86 said:
you have no swap
check if your kernel supports swap
if it supports then install init.d universal from play store
https://play.google.com/store/apps/details?id=com.androguide.universal.init.d&hl=el
Click to expand...
Click to collapse
This is the universal init.d result
{
"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"
}

auastyle said:
This is the universal init.d result
Click to expand...
Click to collapse
reboot the device and check again from terminal

[ROM][5.1.1][OFFICIAL] CyanogenMod 12.1 for S3 Neo[LEGACY]

[ROM][5.1.1][OFFICIAL] CyanogenMod 12.1 for S3 Neo[LEGACY]
{
"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"
}
NOTE: PLEASE ALSO READ ALL OF THE FAQ IN THE SECOND POST. IT COVERS MANY OF THE COMMON PROBLEMS AND QUESTIONS!
CyanogenMod 12.1 is a free, community built, aftermarket firmware distribution of Android 5.1.x (Lolipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* 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.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
The source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Changelog:
https://www.cmxlog.com/12.1/s3ve3g/
Requirements:
Custom recovery (either TWRP or CyanogenMod)
Soon other things will be added
Known Bugs/Issues: (fixed nightly date)
NFC
If camera not working flash this: LINK
Offline charging(02.09.2016)
(Please don't ask ETA for any bug fixes)
Bug reports for this ROM should be officially submitted via CyanogenMod's Jira bug tracking sytstem. Please fully read the FAQ entry on bugs and bug submission before submitting any tickets.
FAQ, other information:
Soon
Download:
https://download.cyanogenmod.org/?device=s3ve3g
Note to users: I'm not responsible if you brick your phone. See the disclaimer above.
Note to admins/moderators: I'm not a developer / contributor of CyanogenMod and not associated with Cyanogen, Inc. in any way. If this thread is inappropriate, please move/delete it.
Thanks to These People:
Zola
@rox
Abhisek Devkota
Samsung Devs
CyanogenMod Devs
XDA:DevDB Information
Cyanogenmod12.1, ROM for the Samsung Galaxy S3 Neo
Contributors
n1kolaa, Zola III
Source Code: https://github.com/CyanogenMod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Version Information
Status: No Longer Updated
Stable Release Date: 2016-08-22
Beta Release Date: 2015-10-19
Created 2015-09-23
Last Updated 2018-05-14

How to report problem with new kerel or rom?
tonyp said:
We're on a development site - at least in theory.
To help out development without actually having some knowledge it's really important to know how and when to get logs.
Lately more and more people in this section do grab appropriate logs, which is a good thing and has already helped in fixing a bunch of bugs.
To stop (especially new) people from constantly asking how to get logcats I decided to hand out a quick reference on how to grab logs efficiently via adb / terminal / app.
There is an app which can export apps (see the end of this post), but you should learn how to get logs via adb anyways, as a dmesg is often crucial in case of debugging bsods.
I won't post instructions in how to get adb working - you can use Google or take this CM wiki entry as a starting point.
The three most important log types are:
logcat: the logoutput of the Android system
radio logcat: the log outpur ot your System / BB / RIL communication
kernel log (kmsg / dmesg): the kernel messages
Additionally there's the last_kmsg which is a dump of the kernel log until the last shutdown.
Normal Logcat:
Code:
adb logcat -v time -d > logcat.log
Radio Logcat:
Code:
adb logcat -b radio -v time -d > logcat_radio.log
Note: Cyanogenmod (based) ROMs require the following setting to export kernel logs via adb:
Settings - Developer Options - Root access - choose: "Apps and ADB"
Kernel Log:
Code:
adb shell su -c dmesg > dmesg.log
Last_kmsg:
Code:
adb shell su -c "cat /proc/last_kmsg" > last_kmsg.log
For getting the logs via the Terminal Emulator app the commands differ a little:
Get logs via Terminal Emulator:
Normal Logcat:
Code:
logcat -v time -d > /sdcard/logcat.log
Radio Logcat:
Code:
logcat -b radio -v time -d > /sdcard/logcat_radio.log
Kernel Log:
Code:
su -c dmesg > /sdcard/dmesg.log
Last_kmsg:
Code:
su -c "cat /proc/last_kmsg" > /sdcard/last_kmsg.log
Notes:
-v time will include timestamps in the logcats
-d will export the complete log.
If you want to save a continuous log you can remove the -d parameter - then you need to cancel the logging process via CTRL+C.
To export a continuous kernel log use adb shell su -c "cat /proc/kmsg" > dmesg.log (and cancel it via CTRL+C again).
Exporting logs with an app:
I used to recommend Lumberjack for grabbing logs, but it doesn't work with Jellybean properly anymore and fails to export the dmesg.
I googled for a while and found a great (and fully open sourced) alternative to export logs: SysLog
With this great app there are no more excuses - at least open the app, export all 4 log types and attach the zip file from /sdcard/SysLog to your bug report.
Before anyone asks (duh!), Kernel log = dmesg, Last kernel log= last_kmsg, main log = logcat, modem log = radio log.
Lumberjack still is great to have a look at logs on the phone, but for exporting you probably should use SysLog as it does it quickly and reliable
SysLog (source):
​
Click to expand...
Click to collapse
#o#
tonyp said:
When to post which kind of logs:
If you got any kind of ROM problems - especially problems with Apps like force closes, attach a logcat.
If there are problems while calling or with your signal attach a radio logcat to the normal logcat.
In kernel threads or on issues which might be kernel related (from A as auto brightness to Z as ZRAM) you need a kernel log
If you had a sudden reboot attach a last_kmsg, then we can check if it's been kernel related
As our phone has always been on the edge of bsod's and freezes, some special notes about them as well:
If you had a bsod and/or freeze a logcat dmesg after rebooting is useless, as it doesn't show anything from before the reboot
There are two things you can do:
While the phone's screen is black connect the cable to your computer and check if the device is accessable via adb (check e.g. with "adb devices").
If it is export the dmesg like explained above. If not go on to step 2:
Note that two of the bsod problems of the ICS/CM kernel have been fixed by pengus by the logs I managed to get while the phone has been in a bsod - which means this is crucial!
Pull the battery and insert it again as quickly as possible. Why? The phone does hold a so called last_kmsg in RAM.
It's non-permanent memory, which means it doesn't survive a loss of power - sometimes we're in luck by a quick pull though.
If we're not in luck the file will be empty or contain scrambled characters.
Last but not least some general remarks:
If you don't provide useful logs we can not help you in 95% of the cases in case we can't reproduce it.
Buf even if we could reproduce it - let's assume one of YOUR apps is force closing. Why should we install the app to reproduce the problem and get the logs ourselves.
YOU want help, so YOU should provide the log.
Every real dev with some coding knowledge will need logs to fix the bugs.
This site is called xda-developers - which means that the initial intention of this forum is the actual development itself - and not "making your phone cool".
The least you can (and must) do is to provide useful help with a clear problem description and attached logs when you run into some issues
Click to expand...
Click to collapse

Donations for s3 dual sim
Use "Send payment" option on paypal
@Ahmad Tawfik: 1,62 USD; 1,18 USD
@S3-Neo 5 USD
@naik2902 6.00 USD
@aelfinn 5.51 USD
@St.Ungulant 5.49 USD
Ulrich 10.99 USD!
@Droidaner 13.49 US
I need about 50 euros for used dual sim phone

FAQ POST
Q: When you will realse CM13.0?
A: DON'T ASK FOR ETA(ETA = Estimated Time of Arrival)

Reserved #2

Is offline charge working with this kernel?
Edit:
sorry but I did not read the 1st post

Everything is fine
Installed and booted without issue. Kernel seems to be changed. :good: :highfive:

Is that working on Resurection Remix 5.5.6 ?

Removed

Ahmad Tawfik said:
Offline charge isn't working for me
Click to expand...
Click to collapse
Read OP...
" ##Bugs:##
no bugs so far(offline charging like cm12.1) "
Btw thanks n1kolaa!

Zokhii said:
Read OP...
" ##Bugs:##
no bugs so far(offline charging like cm12.1) "
Btw thanks n1kolaa!
Click to expand...
Click to collapse
I hope you like it
Np It will be assome to rate it 5 starts and make review.

ahmo67 said:
Is that working on Resurection Remix 5.5.6 ?
Click to expand...
Click to collapse
if its based on cm12.1 it shoud.
Take a backup if you not shure.

Mediafire folder is empty for me

jad88 said:
Mediafire folder is empty for me
Click to expand...
Click to collapse
https://www.mediafire.com/folder/3c3y68hehuv9t/n1kernel

MediaFire links not working...

n1kolaa said:
https://www.mediafire.com/folder/3c3y68hehuv9t/n1kernel
Click to expand...
Click to collapse
It's the same... Maybe it's my browser

Is this kernel base on Rox kernel?
And can you add this future for color calibration --> http://forum.xda-developers.com/android/software-hacking/dev-kcal-advanced-color-control-t3032080
We need this futures.
---------- Post added at 01:48 PM ---------- Previous post was at 01:34 PM ----------
jad88 said:
It's the same... Maybe it's my browser
Click to expand...
Click to collapse
Download one buy one !

Sectorian said:
Is this kernel base on Rox kernel?
And can you add this future for color calibration --> http://forum.xda-developers.com/android/software-hacking/dev-kcal-advanced-color-control-t3032080
We need this futures.
---------- Post added at 01:48 PM ---------- Previous post was at 01:34 PM ----------
Download one buy one !
Click to expand...
Click to collapse
I wont add it. Its based on Rox kernel

I had to login to my mediafire account. It works on latest RR. (Flashed with flashify)

Sorry, one question. If i flash your kernel, did i lose my data?

[WIP] Stock Kernel Compiled From Source

Hello Everyone,
I recently bought this device G7 play with on-going offer with MetroPCS. Since last one week, I've been getting my hands dirty on successfully building and booting the kernel from the source code provided by moto here https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-PPYS29.105-134-7
I would like to share with you all my progress currently.
Working:
Boots
Touch works
Not Working:
Camera
Baseband (radio)
A lot more
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"
}
I will update my progress here and release it once I manage get around few major issues and also I'm working on building TWRP for our device from source.

Sorry for my ignorance, but what does this mean for the g7 play development?, Thnx

Hello, is this 32bit or 64bit?

brickhayabusa said:
Sorry for my ignorance, but what does this mean for the g7 play development?, Thnx
Click to expand...
Click to collapse
I will try to build a functional TWRP, custom kernel and maybe even a ROM.
Electimon said:
Hello, is this 32bit or 64bit?
Click to expand...
Click to collapse
It is a 64 bit build

kD said:
I will try to build a functional TWRP, custom kernel and maybe even a ROM.
It is a 64 bit build
Click to expand...
Click to collapse
Do you have telegram?

@kD
You might be able to get LTE working by reflashing the modem and wiping modemst1 & 2. Your kernel might actually get around the security problems we have with installing twrp on stock as well. I'd love to do some testing with it. If you feel like dropping me a link, please send me a pm.

Spaceminer said:
@kD
You might be able to get LTE working by reflashing the modem and wiping modemst1 & 2. Your kernel might actually get around the security problems we have with installing twrp on stock as well. I'd love to do some testing with it. If you feel like dropping me a link, please send me a pm.
Click to expand...
Click to collapse
Sent a PM to you.

Thanks for your work!!!
A custom kernel for this device will be amazing! Go on!!

Using this kernel im going to build halium-boot eta s0n

This is amazing!! Please continue, you are a hope for us and share your progress with us

nothing new?

@kD
I don't know if you saw this but one of the devs from Motorola finally updated the build process. You'd have to adapt some minor things like folder names, and the -j number but it should work. I can't believe how stupidly complicated building the kernel modules are. No body would remember this line for line, and they waited like a year to tell us this crap.
https://github.com/MotorolaMobilityLLC/readme/blob/master/MMI-PPYS29.105-134-7.txt

Spaceminer said:
@kD
I don't know if you saw this but one of the devs from Motorola finally updated the build process. You'd have to adapt some minor things like folder names, and the -j number but it should work. I can't believe how stupidly complicated building the kernel modules are. No body would remember this line for line, and they waited like a year to tell us this crap.
https://github.com/MotorolaMobilityLLC/readme/blob/master/MMI-PPYS29.105-134-7.txt
Click to expand...
Click to collapse
Seems like great news! When we can get a 64 bit OS running ill make a zip to convert from this 64 bit rom to 64 bit halium 9!

Hey man! Good work! Any news in your 64bit kernel?

@kD
How do you get past this part compiling the kernel?
Code:
( perl -le 'print \"# This file was automatically generated from:\n#\t\" . join(\"\n#\t\", @ARGV) . \"\n\" ~/android/kernel/msm-4.9/arch/arm/configs/msm8953-perf_defconfig ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953_32.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-sdm632-channel.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953_32.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-sdm632-channel.config && cat ~/android/kernel/msm-4.9/arch/arm/configs/msm8953-perf_defconfig ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953_32.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-sdm632-channel.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953_32.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-sdm632-channel.config ) > ~/android/out/target/product/generic/obj/kernel/msm-4.9/mapphone_defconfig || ( rm -f ~/android/out/target/product/generic/obj/kernel/msm-4.9/mapphone_defconfig && false )
It originally gave me an error because of an extra ' symbol in there. Upon removing it, the command goes through, but... It drops me into some kind of "perl shell" that I can't get out of to enter the next commands. I almost have a script ready to auto build our kernel, but that perl command is holding up progress.

Spaceminer said:
@kD
How do you get past this part compiling the kernel?
Code:
( perl -le 'print \"# This file was automatically generated from:\n#\t\" . join(\"\n#\t\", [user=2467029]@argv[/user]) . \"\n\" ~/android/kernel/msm-4.9/arch/arm/configs/msm8953-perf_defconfig ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953_32.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-sdm632-channel.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953_32.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-sdm632-channel.config && cat ~/android/kernel/msm-4.9/arch/arm/configs/msm8953-perf_defconfig ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953_32.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-sdm632-channel.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953_32.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-sdm632-channel.config ) > ~/android/out/target/product/generic/obj/kernel/msm-4.9/mapphone_defconfig || ( rm -f ~/android/out/target/product/generic/obj/kernel/msm-4.9/mapphone_defconfig && false )
It originally gave me an error because of an extra ' symbol in there. Upon removing it, the command goes through, but... It drops me into some kind of "perl shell" that I can't get out of to enter the next commands. I almost have a script ready to auto build our kernel, but that perl command is holding up progress.
Click to expand...
Click to collapse
Hi @Spaceminer.
I'm a new XDA Developers Community member. English is not a my first language. I'm a Software Engineer in my country and I'm 23 years old.
Even so, I'm going to try to support you with anything. I don't know a lot of Android, I've done some Android applications and I know a very little about root, recovery and custom kernels.
I don't know perl, but I've seen that you have forgotten to write ' at the end of this part:
join("\n#\t", @argv) . "\n"
PD: I'm from Mexico. Greetings.

ErikAlvarez00 said:
Hi @Spaceminer.
I'm a new XDA Developers Community member. English is not a my first language. I'm a Software Engineer in my country and I'm 23 years old.
Even so, I'm going to try to support you with anything. I don't know a lot of Android, I've done some Android applications and I know a very little about root, recovery and custom kernels.
I don't know perl, but I've seen that you have forgotten to write ' at the end of this part:
join("\n#\t", @argv) . "\n"
PD: I'm from Mexico. Greetings.
Click to expand...
Click to collapse
That explains the problem. I removed one of those, because it caused an error, but it really needed to be moved to the end... Thank you so much!

What's wrong with this command?
I need help with the syntax on this. There's an error somewhere and I can't find it, so I can't finish building a 64bit kernel. I've tried moving the ' symbol to a few places and nothing works. I'm very lost on this part.
Code:
( perl -le 'print \"# This file was automatically generated from:\n#\t\" . join(\"\n#\t\", [user=2467029]@argv[/user]) . \"\n\"' kernel/msm-4.9/arch/arm/configs/msm8953-perf_defconfig kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953.config kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953.config kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953_32.config kernel/msm-4.9/arch/arm/configs/ext_config/debug-sdm632-channel.config kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953_32.config kernel/msm-4.9/arch/arm/configs/ext_config/moto-sdm632-channel.config && cat kernel/msm-4.9/arch/arm/configs/msm8953-perf_defconfig kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953.config kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953.config kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953_32.config kernel/msm-4.9/arch/arm/configs/ext_config/debug-sdm632-channel.config kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953_32.config kernel/msm-4.9/arch/arm/configs/ext_config/moto-sdm632-channel.config ) > $kernel_out_dir/mapphone_defconfig || ( rm -f $kernel_out_dir/mapphone_defconfig && false )
Edit: I think that I found the solution. It should actually be this according to build instructions for other Motorola devices.
/bin/bash -c "( perl -le 'print "# This file was automatically generated from:\n#\t" . join("\n#\t", @argv) . "\n"'