Related
Hi Guys,
I compiled an eclair rom using the 2.9.26-eclair branch of Cyanogen kernel on github . And I ported the camera-related sources from donut branch to eclair branch. Now both 3d and camera can work on my G1. But I still canoot play mp4 on G1.
Would you please tell me how to make mp4 work on G1? I knew Kingklick had succeed to make mp4 work. Is his sources open?
Thanks.
loveheaven said:
Hi Guys,
I compiled an eclair rom using the 2.9.26-eclair branch of Cyanogen kernel on github . And I ported the camera-related sources from donut branch to eclair branch. Now both 3d and camera can work on my G1. But I still canoot play mp4 on G1.
Would you please tell me how to make mp4 work on G1? I knew Kingklick had succeed to make mp4 work. Is his sources open?
Thanks.
Click to expand...
Click to collapse
working dec libs come from the 2.1 drioderis dump which you can find in the eris dev forums.
you can also find them here
http://forum.xda-developers.com/showpost.php?p=5793964&postcount=667
Firerat said:
working dec libs come from the 2.1 drioderis dump which you can find in the eris dev forums.
you can also find them here
Click to expand...
Click to collapse
Would you please tell me which libs I should push into my 32B G1? I pushed libopencore_mp4*.so libOmxMpeg4.so from droid eris dump into my g1. But after that when I reboot my phone, my phone cannot be rebooted and stays at the first "G1 Tmobile" splash screen.
loveheaven said:
Would you please tell me which libs I should push into my 32B G1? I pushed libopencore_mp4*.so libOmxMpeg4.so from droid eris dump into my g1. But after that when I reboot my phone, my phone cannot be rebooted and stays at the first "G1 Tmobile" splash screen.
Click to expand...
Click to collapse
Code:
mkdir eris;mkdir Firerat3dvid
cd Firerat3dvid
unzip <fullpath to the update zip>
export SomeOtherDir=$PWD
cd ../eris
unzip <fullpath to dump zip>
cat > ~/bin/compmd5sum << "EOF"
#!/bin/sh
# md5sum a bunch of stuff
md5sum $1;md5sum $SomeOtherDir/$1;adb shell md5sum /$1
EOF
chmod 755 ~/bin/compmd5sum
find . |sed s/^/compmd5sum\ /|sh
now you can compare files in two dir on your linux box against the ones on your phone, tells you whats 'missing' what are the same and what are different
PS the files you need are in the zip files in the link I gave you
just thought that the above script might come in handy for someone wanting to compare files
Thank you very much!
I downloaded the CE-12-Patch_3D_vid_signed.zip you prodivded and pushed all the libraries in your zip (except the wlan.ko) into my G1. The kernel my G1 used is built from Cyanogen kernel eclair branch. After pushing the libraries, I reboot my G1.But the G1 got stucked in the first "T-mobile G1" splash screen and couldn't be reboot into the system.
Why did it happen? I should use your kernel?? The opencore library depends on the kernel?? I think the opencore is independent. Even if there is something wrong with opencore, G1 can always be reboot. Am I wrong?
Firerat said:
Code:
mkdir eris;mkdir Firerat3dvid
cd Firerat3dvid
unzip <fullpath to the update zip>
export SomeOtherDir=$PWD
cd ../eris
unzip <fullpath to dump zip>
cat > ~/bin/compmd5sum << "EOF"
#!/bin/sh
# md5sum a bunch of stuff
md5sum $1;md5sum $SomeOtherDir/$1;adb shell md5sum /$1
EOF
chmod 755 ~/bin/compmd5sum
find . |sed s/^/compmd5sum\ /|sh
now you can compare files in two dir on your linux box against the ones on your phone, tells you whats 'missing' what are the same and what are different
PS the files you need are in the zip files in the link I gave you
just thought that the above script might come in handy for someone wanting to compare files
Click to expand...
Click to collapse
loveheaven said:
Thank you very much!
I downloaded the CE-12-Patch_3D_vid_signed.zip you prodivded and pushed all the libraries in your zip (except the wlan.ko) into my G1. The kernel my G1 used is built from Cyanogen kernel eclair branch. After pushing the libraries, I reboot my G1.But the G1 got stucked in the first "T-mobile G1" splash screen and couldn't be reboot into the system.
Why did it happen? I should use your kernel?? The opencore library depends on the kernel?? I think the opencore is independent. Even if there is something wrong with opencore, G1 can always be reboot. Am I wrong?
Click to expand...
Click to collapse
your linux will be running fine, its the Android that isn't happy
the libs are not dependent on the kernel, but may be dependent on something which is already in CE
tbh I can't really help you , I have no idea what 'ROM' you are pushing these libs to.....
logcat is your friend, I have a whole bunch of them on one line
Code:
adb logcat;adb logcat;adb logcat;adb logcat;adb logcat;adb logcat;adb logcat;adb logcat;adb logcat
make sure your phone is connected the first time, and it will happily sit there when you unplug, 'waiting for device' till you plug it back in.
and in another console
adb shell busybox top
sometimes you can even shell in if you are not seeing anything on logcat
'busybox top' will give you an idea of what is running
and there is nothing stopping you from having a couple more terminals open
one with a shell for 'doing stuff' and another for pushing and pulling stuff
all while watching top and logcat
your loop is probably to do with drm, but the logcat will tell you
Firerat said:
your linux will be running fine, its the Android that isn't happy
the libs are not dependent on the kernel, but may be dependent on something which is already in CE
tbh I can't really help you , I have no idea what 'ROM' you are pushing these libs to.....
logcat is your friend, I have a whole bunch of them on one line
Code:
adb logcat;adb logcat;adb logcat;adb logcat;adb logcat;adb logcat;adb logcat;adb logcat;adb logcat
make sure your phone is connected the first time, and it will happily sit there when you unplug, 'waiting for device' till you plug it back in.
and in another console
adb shell busybox top
sometimes you can even shell in if you are not seeing anything on logcat
'busybox top' will give you an idea of what is running
and there is nothing stopping you from having a couple more terminals open
one with a shell for 'doing stuff' and another for pushing and pulling stuff
all while watching top and logcat
your loop is probably to do with drm, but the logcat will tell you
Click to expand...
Click to collapse
Thank you very much!
I used your method and found it is because my rom could not load the libwebcore.so in your zip. So I pushed my orignal libwebcore.zip back into G1, my G1 can boot now. But after that I still cannot watch Mp4 on my G1...
Would you please give me some advice? Thanks.
loveheaven said:
Thank you very much!
I used your method and found it is because my rom could not load the libwebcore.so in your zip. So I pushed my orignal libwebcore.zip back into G1, my G1 can boot now. But after that I still cannot watch Mp4 on my G1...
Would you please give me some advice? Thanks.
Click to expand...
Click to collapse
CE1.2 with my vid patch
wait for CE2
or Kings 1.8 AOSP
or
check the code in this
http://forum.xda-developers.com/showpost.php?p=5889900&postcount=4
with a bit of deduction, you could figure out what is missing/different
as I said in my last post, I can't help you as I have no idea what ROM you are trying to get mp4 to run on.........................................
Installing/Pushing CE-12-Patch_3D_Vid_signed.zip
Got a question... I recently downloaded the v4_1.zip, and was wondering if it's possible to incorporate the CE-12-Patch_3D_Vid_signed.zip in to it. I'm not new to the whole rooting thing, and have tried several variations of the Eclair and Donut roms floating around here. Unfortunately, I'm not to well versed in ADB. My main interest in pushing the above zip is to finally have an Eclair rom with working video. If anyone can help me out with this, it'd be greatly appreciated.
will4958 said:
Got a question... I recently downloaded the v4_1.zip, and was wondering if it's possible to incorporate the CE-12-Patch_3D_Vid_signed.zip in to it. I'm not new to the whole rooting thing, and have tried several variations of the Eclair and Donut roms floating around here. Unfortunately, I'm not to well versed in ADB. My main interest in pushing the above zip is to finally have an Eclair rom with working video. If anyone can help me out with this, it'd be greatly appreciated.
Click to expand...
Click to collapse
the v4 is a different beast
King's Eris has working video
King's Eris CachHacked has working video and is a lot faster
CE-12-Patch_3D_Vid_signed.zip
Thanks for the response. Actually, I was only using the v4 rom as an example. I have tried King's Eris rom, and I think I have the most recent version of it, but the last time I tried it the camcorder did it's I'm not gonna work for you thing. Is there a way to push the CE-12-Patch_3D_Vid_signed.zip to this rom instead, or did I misinterpret the description of this patch? At any rate, it is fun trying all these new and different roms. Can't wait for a fully working 2.0 pastry.
P.S: I just tried the FR-v4OL-CH-0-1_S.zip rom, and it does have video playback. Unfortunately, the camcorder is still non-funtional, of course, and data doesn't appear to be working.
will4958 said:
Thanks for the response. Actually, I was only using the v4 rom as an example. I have tried King's Eris rom, and I think I have the most recent version of it, but the last time I tried it the camcorder did it's I'm not gonna work for you thing. Is there a way to push the CE-12-Patch_3D_Vid_signed.zip to this rom instead, or did I misinterpret the description of this patch? At any rate, it is fun trying all these new and different roms. Can't wait for a fully working 2.0 pastry.
P.S: I just tried the FR-v4OL-CH-0-1_S.zip rom, and it does have video playback. Unfortunately, the camcorder is still non-funtional, of course, and data doesn't appear to be working.
Click to expand...
Click to collapse
/data not working?
if data wasn't working it wouldn't boot past the bootanimation splashscreen
if data is 'full' reboot, it will correct itself
Unfortunately, when I try to do something that requires a data connection, it suggests using wifi. During setup, I did select the first connection option, which I think was data and wifi or something like that. When I try to go into Market to sign in that way, I can't connect. Is there a step I'm missing, or has this happened to anyone else? Also, is there a way to push the CE-12-Patch_3D_Vid_signed.zip into the FR-v4OL-CH-0-1_S.zip rom, or can I just flash like a normal zip? Thanks in advance.
will4958 said:
Unfortunately, when I try to do something that requires a data connection, it suggests using wifi. During setup, I did select the first connection option, which I think was data and wifi or something like that. When I try to go into Market to sign in that way, I can't connect. Is there a step I'm missing, or has this happened to anyone else? Also, is there a way to push the CE-12-Patch_3D_Vid_signed.zip into the FR-v4OL-CH-0-1_S.zip rom, or can I just flash like a normal zip? Thanks in advance.
Click to expand...
Click to collapse
ahh, sorry I'm getting all mixed up, because everyone is stressed out over FR-a2sd using /data for something useful instead of leaving it as an empty,wasted space.
yes, data connection is not working, tbh I don't know why the Market doesn't work even if wifi is working..
The CE-12-Patch_3D_Vid_signed.zip isn't going to do anything for FR-v4OL-CH-0-1_S.zip
its just a 3D kernel , and libs I took from the eris dump which got video working.
infact , the libs are 'mostly' the same as the ones already in v4OL
( which means I'm totally not understanding why video is dark, got to be a framework thing, maybe, I don't really know, just guessing )
Flashing / pushing CE-12-Patch is just going to kill v4OL
I did CE-12-Patch a long time ago, shortly after re-visiting xda after initially rooting my g1 way back in Feb '09.. kinda wished I'd stuck around then.
anyway, CE-12-Patch WILL break v4OL, is it doesn't mount mtdblock4 in the right place.
the v4OL is beta , lots of things don't work
if you get your kicks trying to fix broken things, or making yourself understand things you don't understand ( i.e. you self teach )
then it is for you.
if you want things to work 'out of the box' ,
King's Eris mostly works
ce12 cachehack works
ce2.0 works ( with a 'lil' fixup, facebook fix is in the thread FR*S.zip coming soon.. )
OE1.3.0.1 has things working ( anyone flashed ce12-patch over oe1.3 ? )
and good ol' SuperD works very well.
personally I think your best root is the CE12 CacheHack
It's fully functional, and best of all, CE2.0 is a *no wipe* update
You can flash CE2.0 , just a couple of fixes that need to be consolidated
they are in the thread , minor fix is at post #1401 ( which I will update to a "no hassle,flash straight after CE2.0" soon )
First off, big thanks to Faux123. This is based on his repo with a few tweaks of my own. I'll be adding more as we go on. And of course, he's welcome to pull any patches he likes from my github.
Changes:
Added zram compressed swap support. I'll attach a script to turn it on and one to see what its status is. It's not like the older ramzswap that requires a special tool, everything is done through sysfs now. Very nice.
Added zcache compressed cache. This is a bigger win IMO, it compresses any compressible data in the cache. This means you can keep much more data in cache, which means you have to read it in from slow flash much less often.
Tweaked the low memory killer to take swap space into account, but only some of it.... This prevents swap thrashing while the system tries to kill processes and free up ram/swap. I also suggest using something like AutoKiller to set the levels to the best performance for your workload. We all run different apps and such, and that can affect how these things work for each user. There is no setup that is going to be perfect for 100% of users. Speaking of AutoKiller, I have found the advanced tweaks to help a fair bit as well. Don't use the memory management one, it overides your settings for things like swappyness. And the IO Scheduler doesn't do anything as we aren't using cfq. Unless you turn on cfq...
On Swap and compression:
While badly configured swap can slow things down, it's far more complex than people think. It also frees up RAM that's not being used frequently for apps that are. So your system can more efficiently use the resources it has. While compression does use some CPU time, our dual core 1Ghz+ CPUs can compress/decompress REALLY fast. Far faster than reading from the flash storage. In theory, this can affect battery life, though I haven't seen any significant issues from it.
Q: But we have 512M, that's a LOT!
A: Well, kind of... Not all of it is accessible to the kernel for running apps. 128M for the GPU, some for the cameras, wifi, etc... In the end, a little less than 400M is available. Then you have to add in system overhead from the kernel itself, Android's OS processes, etc.. That is quite limiting, IMO, so using it more efficiently is important to me.
Q: I don't like compression/swap.
A: Then don't run this kernel.
Download (OTA) v1.1: http://goo.gl/2dCK8
Scripts: http://goo.gl/M4SzG
Code:
OTA Changelog:
v1.1.1:
* Fixed Haptic Vibration
* Fixed some config settings
v1.1:
* Updates from faux123 to fix LG crap code
* Increase voltages and enable 1.5GHz
v1.0.3:
* Added low memory killer changes back in.
* Fixed Haptic Vibration
v1.0.2:
* Correct mis-applied zcache patch.
Does this kernel rebuild cache every boot like faux 1.3?
Sent from my MeGaBoT Transformer!
Haptic feedback doesn't work. Faux had the same problem in one of his earlier kernels bbut he fixed it .
Sent from my LG-P999 using XDA App
KingDavid63 said:
Does this kernel rebuild cache every boot like faux 1.3?
Sent from my MeGaBoT Transformer!
Click to expand...
Click to collapse
Yes. I've poked around, but haven't figured out why. It's certainly nothing I'm intentionally doing. I tried using the same initrd from the Weapon stock kernel, no joy. That's about the only thing the kernel should be able to change that would make a difference.
C-4Nati said:
Haptic feedback doesn't work. Faux had the same problem in one of his earlier kernels bbut he fixed it .
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
I'll test it again, but I know it was working at one point.
EDIT: Argh.. yeah, config got messed up. Compiling now.
OK. 1.1.1 is up, tested on my phone with working vibrate.
Data missing
Hey ttabbal, maybe you can help me a little bit with the issue im having with cyanogenmod based roms,
I've been trying to know a bit more bout RILs and ended up learning that it resides at the kernel. My objetive of learning about it is because no matter I do i cant have data conection on any CM7 based ROM but I DO have data on any Froyo / Gingerbread OTA rom, even tryed to change basebands, change sim card, push the apps related to the telephony from GB OTA to Cyanogen and replace Ril Libs also. Nothing had worked. And this is where you can help me a little: while using your kernel I have the exact same issue! No data whatsoever! No matter what ROM I use, in the other hand using Faux's kernel i got no issue, and bec you based yours in his work im sure you know what exactly changed between them and enlight me or make me understang what can I possibly do to fix my issue.
Thanks!
BTW I live in Guatemala CA, using a data plan from CLARO (America Movil) carrier
Look here at the Wikipedia Link to look at the baseband Im using.
albertorodast2007 said:
Hey ttabbal, maybe you can help me a little bit with the issue im having with cyanogenmod based roms,
I've been trying to know a bit more bout RILs and ended up learning that it resides at the kernel. My objetive of learning about it is because no matter I do i cant have data conection on any CM7 based ROM but I DO have data on any Froyo / Gingerbread OTA rom, even tryed to change basebands, change sim card, push the apps related to the telephony from GB OTA to Cyanogen and replace Ril Libs also. Nothing had worked. And this is where you can help me a little: while using your kernel I have the exact same issue! No data whatsoever! No matter what ROM I use, in the other hand using Faux's kernel i got no issue, and bec you based yours in his work im sure you know what exactly changed between them and enlight me or make me understang what can I possibly do to fix my issue.
Thanks!
BTW I live in Guatemala CA, using a data plan from CLARO (America Movil) carrier
Look here at the Wikipedia Link to look at the baseband Im using.
Click to expand...
Click to collapse
I'm happy to share any information I can. Your issue is interesting as I can't think of any changes that should affect the radio. Most of the radio code isn't in the kernel. It's handled by a daemon called rild. We could try reverting some patches. The first thing to try would be to test all the older versions of the kernel. I'll get links posted for you when I get to a computer. If one of those work, we can look at the differences between them to try and narrow it down.
albertorodast2007 said:
Hey ttabbal, maybe you can help me a little bit with the issue im having with cyanogenmod based roms,
I've been trying to know a bit more bout RILs and ended up learning that it resides at the kernel. My objetive of learning about it is because no matter I do i cant have data conection on any CM7 based ROM but I DO have data on any Froyo / Gingerbread OTA rom, even tryed to change basebands, change sim card, push the apps related to the telephony from GB OTA to Cyanogen and replace Ril Libs also. Nothing had worked. And this is where you can help me a little: while using your kernel I have the exact same issue! No data whatsoever! No matter what ROM I use, in the other hand using Faux's kernel i got no issue, and bec you based yours in his work im sure you know what exactly changed between them and enlight me or make me understang what can I possibly do to fix my issue.
Thanks!
BTW I live in Guatemala CA, using a data plan from CLARO (America Movil) carrier
Look here at the Wikipedia Link to look at the baseband Im using.
Click to expand...
Click to collapse
I'm not so sure the kernel is going to affect your issue much. As ttabbal said it lies in the RILD binary. CM7/Miui has known issues with no data connectivity though it seems to happen pretty random. Have you tried doing a hard reboot? (hold power + vol up approximately 10 seconds) On occasion I have the same issue with no data signal (though cell is just fine). Usually a hard reboot (or two) solves the problem though.
Whitehawkx said:
I'm not so sure the kernel is going to affect your issue much. As ttabbal said it lies in the RILD binary. CM7/Miui has known issues with no data connectivity though it seems to happen pretty random. Have you tried doing a hard reboot? (hold power + vol up approximately 10 seconds) On occasion I have the same issue with no data signal (though cell is just fine). Usually a hard reboot (or two) solves the problem though.
Click to expand...
Click to collapse
Yup, its someting else, i even managed to solve the APN dissapearing issue in other way: install market enabler, change SIM code to anything and ther revert back to defualt an it will show u again your APNs just like if you hard rebooted.
I even tried copying rild (/system/bin) from OTA GB rom to a CM7 rom and flash, and nothing, and why using your rom and faux's kernel i got data and if using ttabbal's one i have none? has to do something with the kernel! but thanks for ur posts anyways I know ur busy guys
albertorodast2007 said:
Yup, its someting else, i even managed to solve the APN dissapearing issue in other way: install market enabler, change SIM code to anything and ther revert back to defualt an it will show u again your APNs just like if you hard rebooted.
I even tried copying rild (/system/bin) from OTA GB rom to a CM7 rom and flash, and nothing, and why using your rom and faux's kernel i got data and if using ttabbal's one i have none? has to do something with the kernel! but thanks for ur posts anyways I know ur busy guys
Click to expand...
Click to collapse
Your description sounds like the known cm7 apn bug to me. Installing a kernel usually triggers the bug for me as it involves soft reboots. With dragon, do the data workarounds work? Exactly what ROM are you running?
I think im not leaving things clear, my above post was what I did to fix apn dissapearing when i flashed cm7... and even if i hard rebooted (or used the market enabler trick) and apns where restored still couldnt get data to work...
Im usign whitehawk's rom now, but if i pair it with your kernel, the issue i have is not that apn dissapear (like they did in cm7, bec of the known issue) but that I cant get data to connect.
Sent from my LG-P999 using XDA App
albertorodast2007 said:
I think im not leaving things clear, my above post was what I did to fix apn dissapearing when i flashed cm7... and even if i hard rebooted (or used the market enabler trick) and apns where restored still couldnt get data to work...
Im usign whitehawk's rom now, but if i pair it with your kernel, the issue i have is not that apn dissapear (like they did in cm7, bec of the known issue) but that I cant get data to connect.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
OK, just making sure. Here are the older versions of the kernel. Try them out and see if any resolve the data issue you are seeing.
1.1: http://goo.gl/e913p
1.0.3: http://goo.gl/7QY0a
1.0.2: http://goo.gl/O6PDb
1.0.1: http://goo.gl/OWkG8
1.0: http://goo.gl/gLeFz
I honestly don't expect them to, but if the only change is the kernel, it seems like it could be related. Could you also attach a file with logs when it's trying to connect? Perhaps also with a log when booting from Faux's kernel when it works right?
adb logcat > log.txt
adb logcat -b radio > radio.txt
I might be able to see something in there...
Just to make sure we're on the same page, by Whitehawkx's rom you mean Weapon 2.4? I just noticed your sig says 2.3... I don't see sigs when I'm on my phone, so I missed that before. Have you tried updating to 2.4? It might help... it might not...
ttabbal said:
OK, just making sure. Here are the older versions of the kernel. Try them out and see if any resolve the data issue you are seeing.
1.1: http://goo.gl/e913p
1.0.3: http://goo.gl/7QY0a
1.0.2: http://goo.gl/O6PDb
1.0.1: http://goo.gl/OWkG8
1.0: http://goo.gl/gLeFz
I honestly don't expect them to, but if the only change is the kernel, it seems like it could be related. Could you also attach a file with logs when it's trying to connect? Perhaps also with a log when booting from Faux's kernel when it works right?
adb logcat > log.txt
adb logcat -b radio > radio.txt
I might be able to see something in there...
Just to make sure we're on the same page, by Whitehawkx's rom you mean Weapon 2.4? I just noticed your sig says 2.3... I don't see sigs when I'm on my phone, so I missed that before. Have you tried updating to 2.4? It might help... it might not...
Click to expand...
Click to collapse
hahahaha noob mistake... yeah im on 2.4 just updated my sig, thanks for pointing me that, thanks man! gonna use adb to get u some usefull logcats...
BTW i've seen some interesting updates on the nightly changelog for the p999, gonna try flashing latest nightly and see if something has changed....
Logs
Ok some logs from faux's and yours latest kernels, gonna start trying previous kernels from your links, muchas gracias!
BDW: flashed nightly #124 and still no data for me, i guess its bec im using it outside the states and/or its a SIM unlocked device..
just checking ttabal... did you ever figure out the cache rebuild on every boot thing?
How to use a script?
ILUHA_89 said:
How to use a script?
Click to expand...
Click to collapse
Script Manager from Market its free, or search any other script app...
Crashes on OTA
Used for half a day and had two lock ups using GB OTA. G2X would not come out of stand by. I will retry at a later time. It was nice to be able to use annyconnect vpn.
I cannot get the zswap stats script to run properly...it says syntax error (expecting ")") or some ****...what I'm I not understanding with this
Been running the kernel for about a day, both scripts running with script manager, no freezes or issues yet. Been trying to cause problems like I've had with other kernels, and i'm not getting them.
Hi everybody!
Today I share my CM7.2 build and the device folder needed for build.
Firstly, here is the flashable zip:
http://depositfiles.com/files/3ppjnzlbd
Just put it to your SD card and flash with CWM.
What works:
- It boots.
- Theme chooser.
- Screenshot.
- Sound playing and recording.
- GPS
- Vibration (Sometimes buggy.)
What doesn't:
- Everything else. (Including for example camera, video player, wifi, bluetooth, network and mobile data, etc.)
It is going to be a very hard work to make it fully functionable. In the followings, I share my CM7.2 (and CM7. It is the same.) device folder. Here is a little readme for building. I assume the devs who are involved in the CM-development already know this (especially the first steps).
- Check out the latest CyanogenMod 7.2 sources:
repo init -u git://github.com/CyanogenMod/android.git -b gb-release-7.2
repo sync
- Put the device files into device/samsung/galaxyr
- Move cyanogen_galaxyr.mk (from the attached zip) into vendor/cyanogen/products directory.
- Open vendor/cyanogen/vendorsetup.sh and add the following line:
'add_lunch_combo cyanogen_galaxyr-eng' (Without quotes)
- Open vendor/cyanogen/AndroidProducts.mk and add the following:
'$(LOCAL_DIR)/cyanogen_galaxyr.mk' (Without quotes)
- Go to your device folder (device/samsung/galaxyr), put your phone on USB and run extract-files.sh
(It is important to run in the device folder, because it works with relative paths!)
(Your phone must have a stock or stock-based rom to copy the necessary proprietary files!)
- In your top CM source dir, execute:
'. build/envsetup.sh' (Without quotes)
- Finally:
'brunch cyanogen_galaxyr-eng' (Without quotes)
- Wait for it to finish. Flash and enjoy!
Here is the link for the GitHub repository:
https://github.com/Adam77Root/android_device_samsung_galaxyr
Some information about the files:
- The files (especially galaxyr.mk) are bloated with options and settings. I have concerns about the usefulness of some of them. We may not need them in a final/stable build.
- The kernel is the stock ZSLE6 kernel.
- gpswrapper, libaudio, libexifa, libjpega and libsensors were copied from c1-common with little modifications.
Some notices I have come across during the development:
- If we set TARGET_HAVE_TEGRA_ERRATA_657451 to true, we get a plenty of segmentation faults. On CM9, I was able to trace back the problem to this setting! CM7 (and obviously 7.2, I didn't tried) doesn't show the segfaults, probably because init and adb can't load. That's why TeamGalaxyR's rom boots to Samsung splash screen. If you try 'adb shell' on that rom, it immediately closes, because it cannot connect. After I had set this option off, I was able to build working images.
I hope other developers will start working on CM as soon as they can. It is a great project. I will also put every effort into this project, but I won't have access to my files for a week from tomorrow. However, I will stay tuned and be able to post here.
I attach two screenshots I took yesterday.
UPDATE:
Epsylon3 made some progress. The most important: Wifi is working now!!
Get it here: http://dedib.ath.cx/galaxyr/
Every modification to devices have risks. Flash this at your own risk!
Have fun and enjoy!
Thanks man (sorry i have no thanks left, i will hit later)
will try this , after i backup...
OMG OMG OMG... Now downloading. Will Flash and Revert with feedback soon... In short Reserved!!!
(⊙o⊙)Android & iOS Superuser!←_←
Ya.. Me too gonna test and feedback.... Reseved for feedback...
EDIT:
Its not working dude...
I flashed it over ZLES6 and also indian one... but it does not boot to the home screen...
And android logo comes up with black background and it just keeps on blinking...
No success on my phone
EDIT:
Sorry for wrong info.. I forgot to completewipe the device.. Its booting fine and the issues above mentioned are present.. however thanks a lot dude......
Hello Adam77Root Will you pls add some screenshot of it
Also Thanks Given
I am sad that i am off the system. Someone flash it and test it. Finally CM7.2 on r. Next would be fully working cm7 and later cm9(i hope.). Thanks given
Sent from my GT-I9103 using xda app-developers app
Thank you everybody! I added two screenshots to the first post.
in the office now,,can't donwload here due to limited downloads here..will test it at homies...:laugh::fingers-crossed::cyclops:
That's one small step for man, one giant leap for mankind. :laugh::laugh:
Adam77Root said:
Hi everybody!
Today I share my CM7.2 build and the device folder needed for build.
Firstly, here is the flashable zip:
http://depositfiles.com/files/3ppjnzlbd
Just put it to your SD card and flash with CWM.
What works:
- It boots.
- Theme chooser.
- Screenshot.
- Sound playing and recording.
- GPS
- Vibration (Sometimes buggy.)
What doesn't:
- Everything else. (Including for example camera, video player, wifi, bluetooth, network and mobile data, etc.)
It is going to be a very hard work to make it fully functionable. In the followings, I share my CM7.2 (and CM7. It is the same.) device folder. Here is a little readme for building. I assume the devs who are involved in the CM-development already know this (especially the first steps).
- Check out the latest CyanogenMod 7.2 sources:
repo init -u git://github.com/CyanogenMod/android.git -b gb-release-7.2
repo sync
- Put the device files into device/samsung/galaxyr
- Move cyanogen_galaxyr.mk (from the attached zip) into vendor/cyanogen/products directory.
- Open vendor/cyanogen/vendorsetup.sh and add the following line:
'add_lunch_combo cyanogen_galaxyr-eng' (Without quotes)
- Open vendor/cyanogen/AndroidProducts.mk and add the following:
'$(LOCAL_DIR)/cyanogen_galaxyr.mk' (Without quotes)
- Go to your device folder (device/samsung/galaxyr), put your phone on USB and run extract-files.sh
(It is important to run in the device folder, because it works with relative paths!)
(Your phone must have a stock or stock-based rom to copy the necessary proprietary files!)
- In your top CM source dir, execute:
'. build/envsetup.sh' (Without quotes)
- Finally:
'brunch cyanogen_galaxyr-eng' (Without quotes)
- Wait for it to finish. Flash and enjoy!
Here is the link for the GitHub repository:
https://github.com/Adam77Root/android_device_samsung_galaxyr
Some information about the files:
- The files (especially galaxyr.mk) are bloated with options and settings. I have concerns about the usefulness of some of them. We may not need them in a final/stable build.
- The kernel is the stock ZSLE6 kernel.
- gpswrapper, libaudio, libexifa, libjpega and libsensors were copied from c1-common with little modifications.
Some notices I have come across during the development:
- If we set TARGET_HAVE_TEGRA_ERRATA_657451 to true, we get a plenty of segmentation faults. On CM9, I was able to trace back the problem to this setting! CM7 (and obviously 7.2, I didn't tried) doesn't show the segfaults, probably because init and adb can't load. That's why TeamGalaxyR's rom boots to Samsung splash screen. If you try 'adb shell' on that rom, it immediately closes, because it cannot connect. After I had set this option off, I was able to build working images.
I hope other developers will start working on CM as soon as they can. It is a great project. I will also put every effort into this project, but I won't have access to my files for a week from tomorrow. However, I will stay tuned and be able to post here.
I attach two screenshots I took yesterday.
Every modification to devices have risks. Flash this at your own risk!
Have fun and enjoy!
Click to expand...
Click to collapse
What doesn't:
- Everything else. (Including for example camera, video player, wifi, bluetooth, network and mobile data, etc.)
if it doesn't work then what use of this rom
azhar.munshi said:
What doesn't:
- Everything else. (Including for example camera, video player, wifi, bluetooth, network and mobile data, etc.)
if it doesn't work then what use of this rom
Click to expand...
Click to collapse
The thread is tagged as [DEV]. It is not a functional rom, only a preview. Don't try it if you don't want.
Sent from my GT-I9103
azhar.munshi said:
What doesn't:
- Everything else. (Including for example camera, video player, wifi, bluetooth, network and mobile data, etc.)
if it doesn't work then what use of this rom
Click to expand...
Click to collapse
First LEARN to appreciate the work man, !!
gearbox87x said:
That's one small step for man, one giant leap for mankind. :laugh::laugh:
Click to expand...
Click to collapse
:good:
Marked as DEV man..
First show some respect. He is trying to do something that Samsung cannot do.
Encourage, but dont ever EVER discourage..
Kudos to the Dev. I will surely test it..
azhar.munshi said:
What doesn't:
- Everything else. (Including for example camera, video player, wifi, bluetooth, network and mobile data, etc.)
if it doesn't work then what use of this rom
Click to expand...
Click to collapse
You have to understand what a huge leap this is in the development of CynaogenMod for our device...
this ROM is obviously not suitable for daily use.... but this ROM gives us a ray of hope that a fully functional CynaogenMod working on our galaxy r is just round the corner.... Kudos to the developer for such an outstanding development and hope he provides a fully functioning CM 7.2 very soon
Sent from my GT-I9103 using xda app-developers app
@OP to get rid of such things better change title as PRE ALPHA or something.
I tested....
i can't wait for the Full release...!!
really appreciable Work man....!
great..
Thank you everybody! If you know somebody, who can help in development, please contact him/her. I will definitely write to Epsylon3. I'm not really familiar on the forum yet.
xlm13x said:
@OP to get rid of such things better change title as PRE ALPHA or something.
Click to expand...
Click to collapse
I append that tag.
gearbox87x said:
I tested....
i can't wait for the Full release...!!
really appreciable Work man....!
Click to expand...
Click to collapse
Thanks! Creating a full/stable release will take a lot of time.
Hey thnx for creating cm 7 for our device. but i see that u r using 2.3.7 as the android version. Cant it be ics. Plz plz try to do this i luve ics and we hv been waiting for ics from a long time.
This development has come to a stop!
But further development is taken here.
Many thanks.
Hello everyone,
I start this thread to get some more development going on for the ZTE Blade S6.
It should encouraged others to join in or describing their own rom development for this device.
To start with I will show you my first alpha build, which means that most basic function should work now, of Cyanogenmod 12.1 for the Blade S6 (P839F30). I have the AS-Version of the device so be careful, if you have a EU Blade S6 or some other similar device. But at always be careful with your device, because I'm not responsible what you do with it, make a backup with TWRP before flashing the rom.
Things I tried:
called my phone
mobile Internet
wifi shows access Points
sound
button lights
camera working
breathing notification
Not Working:
Flash don't work when taking pictures.
UMS is not working correct
Preparation:
download unofficial CM12.1 and put it on your external sd Card
make a twrp backup
factory reset your device
optional - install this mod
install CM12.1
optional - install other region kernel - AU, EU
optional - install gapps
Credits:
Whole team of CyanogenMod https://github.com/CyanogenMod/android
lonespeaker for helping getting things started
KonstaT for TWRP
repos from piccolo-dev team, at which my work is based on.
Kernel Sources my own kernel repo
Kernel Sources ZTE
Please note this is the first time I do this, I'm still learning while doing and also some things I don't know.
Download Google drive
Updated Version 16.11.2016 using data/media as internal storage
Download links for the different kernels:
EU Version
AU Version
Previous Version 20.06.2016
10.02.2016
Concerning the wifi issue you could try the wifi zip file from fortek..see https://mega.nz/#F!c9AyURra!H4Oew0HB6JmqfPpmQ4SJqA
Something new here ??
slawoko said:
Concerning the wifi issue you could try the wifi zip file from fortek..see https://mega.nz/#F!c9AyURra!H4Oew0HB6JmqfPpmQ4SJqA
Click to expand...
Click to collapse
Hey, yes this should work. I think in the official kernel source from zte the config for wifi is missing.
Maybe they have done it any other way. Will cherry pick some commits and hope wifi will be alright then.
lightwars said:
Hey, yes this should work. I think in the official kernel source from zte the config for wifi is missing.
Maybe they have done it any other way. Will cherry pick some commits and hope wifi will be alright then.
Click to expand...
Click to collapse
If the blade is the same as the SU6, copy the pronto_wlan.ko module from stock to vendor/vodafone/p839v55/proprietary/lib/modules (or whatever you've named the directory structure) and in the BoardConfig.mk in the device tree put
BOARD_HAS_QCOM_WLAN := true
BOARD_WLAN_DEVICE := qcwcn
BOARD_HOSTAPD_DRIVER := NL80211
BOARD_HOSTAPD_PRIVATE_LIB := lib_driver_cmd_qcwcn
BOARD_WPA_SUPPLICANT_DRIVER := NL80211
BOARD_WPA_SUPPLICANT_PRIVATE_LIB := lib_driver_cmd_qcwcn
WIFI_DRIVER_MODULE_PATH := "/system/lib/modules/pronto/pronto_wlan.ko"
WIFI_DRIVER_MODULE_NAME := "wlan"
WPA_SUPPLICANT_VERSION := VER_0_8_X
That worked for the SU6.
(you might need something in the device.mk file I can't remember, give me a shout if this doesn't work).
in my cyanogenmode 12.1 for zte blade worked all. release version will be the end of the month
New Version with synced cm sources uploaded, wifi should know work.
Next step to get internal sdcard function properly and Sound working is very important.
Changes could effect that EU variant could work too, but I don't own one to test it. Please be careful.
So I think the button backlights will work in next version and I trying to get the sdcard working.
Why the sound is not working properly, I don't know at this time...
Check fortek's version may be, sound works fine there
So I got a newer build working, which has working audio. What is wired that sim card isn't detected, which seems as a problem.
Internal sdcard is accessible through file manager. And unfortunately button illumination do not work, which should be okay, I had done some tests before... So another build is needed which hopefully combine all things that work.
So.. Sim Card isnt working in this build?
And does it work properly on EU / DEU (german) Version?
DStyl3 said:
So.. Sim Card isnt working in this build?
And does it work properly on EU / DEU (german) Version?
Click to expand...
Click to collapse
Apparently yes, my sim card wasn't detected. A little bit strange, cause I didn't change so much, but anyway the other build is able of it.
I must admit that I don't own a EU or DEU version of this device, only the AS version. So I couldn't test the compatibility.
We need someone to test it to know for sure...
Update: New version is uploaded with sim working and sound... I apologize, cause I changed some vendor blobs and yes also some radio related ones, that's why it stopped working.
Great progress! Now just need the camera
eremini said:
Great progress! Now just need the camera
Click to expand...
Click to collapse
Back camera is working now, though I ran out of time getting all libs for the front camera. This will be next.
And to add it the builds only uses data/media and saddly not internal storage.
Storage issue is fixable?
eremini said:
Storage issue is fixable?
Click to expand...
Click to collapse
I think it is just a matter of mounting things right and playing with the init file.zte has just made some changes to their init files which differ from aosp.
In my opinion the better way is also to get one huge partition for userdata and data.Then what it is now,with two partitions...
lightwars said:
I think it is just a matter oft mounting rings right and playing with the init file.zte has just made some changes to their init files which differ from aosp.
In my opinion the better way is also to get one huge partition for userdata and data.Then what it is now,with two partitions...
Click to expand...
Click to collapse
Yeah I think that makes more sense. BTW serveral Russian users that tested ur firmware reported very weak wifi signal, up to the point where they couldn't connect to their wifi. May be something you want to look into.
eremini said:
Yeah I think that makes more sense. BTW serveral Russian users that tested ur firmware reported very weak wifi signal, up to the point where they couldn't connect to their wifi. May be something you want to look into.
Click to expand...
Click to collapse
Thanks for your information.That is not good. I used zte's driver...
This doesn't seem to work on the AU version... goes into a boot loop. Can anyone help?
Thanks a lot.
@lightwars , it is possible that the rom work for EU version ???, and if not, can you make it compatible ??
LineageOS 13 for Life One X2 Mini
This Rom was ported from the Unofficial LineageOS 13 for the Yureka Black. First I need to give credit for all the hard work the developers put into their Rom, I only modified it to work on the Blu Life One X2 Mini.
Note: Please remember I'm doing this on my own time and using my own money to cover expenses.
What Works:
(please let me know)
Camera
Fingerprint
SIM
Data
GPS
Audio
Video Playback
Sensors
Led
Not Working Yet:
(Please let me know)
FM Radio
Bluetooth
Latest Build: https://drive.google.com/open?id=0BzMHnGbQH3bheWVUNlFDNjljcEE
Builds: https://drive.google.com/drive/folders/0BzMHnGbQH3bhRXNUWi1jaGhDR3M?usp=sharing (list view recommended)
TWRP: https://drive.google.com/file/d/0BzMHnGbQH3bhTERvcGxlSkZFa2M/view?usp=sharing
Kernel:
Gapps: http://opengapps.org
Screenshots:
Changelog
Troubleshooting
Encryption Unsuccessful Screen:
Boot into TWRP and format Data (not wipe)
reserved 4
OK--it installs correctly, but after reboot it starts optimization & then screens up with encryption unsuccessful & wants to reset phone-goes to an open script to reformat/reset in TWRP--executes it & then reboots to the same again---this repeats as long as you allow it to. I tried installing twice-- the second time I wiped the phone completely---same result.
debianmain1 said:
OK--it installs correctly, but after reboot it starts optimization & then screens up with encryption unsuccessful & wants to reset phone-goes to an open script to reformat/reset in TWRP--executes it & then reboots to the same again---this repeats as long as you allow it to. I tried installing twice-- the second time I wiped the phone completely---same result.
Click to expand...
Click to collapse
Boot into TWRP and format Data (not wipe)
srgrusso said:
Boot into TWRP and format Data (not wipe)
Click to expand...
Click to collapse
Better choice , imho, would be to unpack the boot.img and change fstab to remove "forceencript"
edit:
sorry spoke too soon.
Just looked at fstab.qcom in boot.img and it is not set to "forceencrypt"
mrmazak said:
Better choice , imho, would be to unpack the boot.img and change fstab to remove "forceencript"
Click to expand...
Click to collapse
this is the current entry:
Code:
/dev/block/bootdevice/by-name/userdata /data ext4 nosuid,nodev,noatime,noauto_da_alloc wait,formattable,check,encryptable=footer;length=-16384
If I wanted to do that what would I change it too?
Thanks
OK--everything loaded & the phone booted normally. Wi-Fi is not working (deal-breaker for me--I use cellular data as little as possible--I have Wi-Fi everywhere I normally go.) Camera works-looks normal (using Google Camera)--works normally. Bluetooth is also not working.. (notice that Bluetooth Share has stopped). Screen & touch work normally. Right now I don't have cell service (that's the reason I use Wi-Fi quite a bit--all cell service is spotty where we live) & can't check cell data. If You could get the Wi-Fi to work, I could check quite a bit more......
More about the Wi-Fi: the MAC address looks like giberish---02:00:00:00:00:00
srgrusso said:
this is the current entry:
Code:
/dev/block/bootdevice/by-name/userdata /data ext4 nosuid,nodev,noatime,noauto_da_alloc wait,formattable,check,encryptable=footer;length=-16384
If I wanted to do that what would I change it too?
Thanks
Click to expand...
Click to collapse
I added an edit to my earlier post.
The way it is looks ok.
It can be encrypted, (encryptable=footer) but not being forced to be. (forceencrypt=)
The length and location of the encryption key would be important to get right, if force is used.
debianmain1 said:
OK--everything loaded & the phone booted normally. Wi-Fi is not working (deal-breaker for me--I use cellular data as little as possible--I have Wi-Fi everywhere I normally go.) Camera works-looks normal (using Google Camera)--works normally. Bluetooth is also not working.. (notice that Bluetooth Share has stopped). Screen & touch work normally. Right now I don't have cell service (that's the reason I use Wi-Fi quite a bit--all cell service is spotty where we live) & can't check cell data. If You could get the Wi-Fi to work, I could check quite a bit more......
More about the Wi-Fi: the MAC address looks like giberish---02:00:00:00:00:00
Click to expand...
Click to collapse
if your ready to do some more testing I should be able to get wifi working.
debianmain1 said:
OK--everything loaded & the phone booted normally. Wi-Fi is not working (deal-breaker for me--I use cellular data as little as possible--I have Wi-Fi everywhere I normally go.) Camera works-looks normal (using Google Camera)--works normally. Bluetooth is also not working.. (notice that Bluetooth Share has stopped). Screen & touch work normally. Right now I don't have cell service (that's the reason I use Wi-Fi quite a bit--all cell service is spotty where we live) & can't check cell data. If You could get the Wi-Fi to work, I could check quite a bit more......
More about the Wi-Fi: the MAC address looks like giberish---02:00:00:00:00:00
Click to expand...
Click to collapse
That type of address could be sign of either a corrupted NVRAM or incorrect radio firmware.
What do you have on the about screen for "baseband version"
and also on the about device/ status / IMEI information (do not list your numbers, just wheather or not they are there)
mrmazak said:
That type of address could be sign of either a corrupted NVRAM or incorrect radio firmware.
What do you have on the about screen for "baseband version"
and also on the about device/ status / IMEI information (do not list your numbers, just wheather or not they are there)
Click to expand...
Click to collapse
The rom is missing the kernel modules from the base rom. should be an easy fix. I already been through all this porting the same rom to th X2.
I might need to edit the boot image and build a script in bin to automaticly load the modules. I don't have a mini but as far as I can tell there is not much diffference from the X2.
srgrusso said:
The rom is missing the kernel modules from the base rom. should be an easy fix. I already been through all this porting the same rom to th X2.
I might need to edit the boot image and build a script in etc to automaticly load the modules. I don't have a mini but as far as I can tell there is not much diffference from the X2.
Click to expand...
Click to collapse
Sounds good---I need the phone for tomorrow, so I'm restoring it right now---will be ready to do more testing tomorrow night. As soon as I get working Wi-Fi I can get logcat up + the normal app load I use....then I could really test it---It looks real good so far.
mrmazak said:
That type of address could be sign of either a corrupted NVRAM or incorrect radio firmware.
What do you have on the about screen for "baseband version"
and also on the about device/ status / IMEI information (do not list your numbers, just wheather or not they are there)
Click to expand...
Click to collapse
This phone's kernel uses external modules, instead of built in like most kernels, odd choice by manufacture. system/lib/modules is missing, once the modules are added, and loaded wifi should work, just fine.
vampirefo said:
This phone's kernel uses external modules, instead of built in like most kernels, odd choice by manufacture. system/lib/modules is missing, once the modules are added, and loaded wifi should work, just fine.
Click to expand...
Click to collapse
So I would guess that will close the Wi-Fi & Bluetooth issues at the same time.
debianmain1 said:
Sounds good---I need the phone for tomorrow, so I'm restoring it right now---will be ready to do more testing tomorrow night. As soon as I get working Wi-Fi I can get logcat up + the normal app load I use....then I could really test it---It looks real good so far.
Click to expand...
Click to collapse
I have a new rom uploading now. It will be waiting for you when you are ready. Since you are using the stock rom could you please post the result of "lsmod" it will help me. Also after you boot the new rom could you please put the output of "dmesg" in a text file and post me a link or else just post it in pastbin. In order to get the adb shell working you'll need to change "the usb used for" from charging to file transfer.
Thanks
srgrusso said:
I have a new rom uploading now. It will be waiting for you when you are ready. Since you are using the stock rom could you please post the result of "lsmod" it will help me. Also after you boot the new rom could you please put the output of "dmesg" in a text file and post me a link or else just post it in pastbin. In order to get the adb shell working you'll need to change "the usb used for" from charging to file transfer.
Thanks
Click to expand...
Click to collapse
No problem---I also contacted the other guy that is interested in helping---should hear from him soon. Will download the new one & be ready for tomorrow.
Here is the new build. Hopefully it fixes Wifi.
https://drive.google.com/file/d/0BzMHnGbQH3bhenZNVE5MeEttVFk/view?usp=sharing