I spent the last two months analyzing and studying kernel sources, driver sources, openFIMG sources... But i can't get how Samsung FIMG and openFIMG works! I want to get Samsung FIMG on the latest Alpha9 (possibly MTD) because IMHO openFIMG are still not good for daily usage, and lot of textures won't show up. At first i tried to compile the whole CM7 removing libsgl and adding samsung proprietary files instead, FAIL, then when i checked out the G3MOD initramfs and i discovered that i needed some module to make the whole thing work i converted my phone back to BML, flashed G3MOD 2.4.1 and then copied samsung proprietary files to /system/lib/egl , gralloc.apollo, copybit.apollo etc... to /system/lib/hw and libChunkAlloc.so to /system/lib, the phone booted but nothing (not even the bootanimation) showed up on the screen. So i checked out the marcellusbe's MTD kernel initramfs and i saw that it had no modules, so after looking the thread i realized that modules in MTD version were in the /system partition, so i checked the system partition and i saw that there was no 3D module!
If someone can point me to the right direction i would be really glad, because i'm really confused right now
And sorry for bad english.
You desperately need @marcellusbe and @hillbeast to help you.
Sent from my DEATH NOTE with Shinigami by my side!
superfrancy97 said:
I spent the last two months analyzing and studying kernel sources, driver sources, openFIMG sources... But i can't get how Samsung FIMG and openFIMG works! I want to get Samsung FIMG on the latest Alpha9 (possibly MTD) because IMHO openFIMG are still not good for daily usage, and lot of textures won't show up. At first i tried to compile the whole CM7 removing libsgl and adding samsung proprietary files instead, FAIL, then when i checked out the G3MOD initramfs and i discovered that i needed some module to make the whole thing work i converted my phone back to BML, flashed G3MOD 2.4.1 and then copied samsung proprietary files to /system/lib/egl , gralloc.apollo, copybit.apollo etc... to /system/lib/hw and libChunkAlloc.so to /system/lib, the phone booted but nothing (not even the bootanimation) showed up on the screen. So i checked out the marcellusbe's MTD kernel initramfs and i saw that it had no modules, so after looking the thread i realized that modules in MTD version were in the /system partition, so i checked the system partition and i saw that there was no 3D module!
If someone can point me to the right direction i would be really glad, because i'm really confused right now
And sorry for bad english.
Click to expand...
Click to collapse
Oh dear. There's a lot wrong with what you're trying to do so let me try and explain it as best I can:
Android libraries are not like Windows where you can mix and match drivers to different versions. Every time Google makes a new version of Android, they change how they want to do the graphics drivers. It's really annoying that they do this, but they aren't trying to make a desktop OS, they are making an embedded OS that the phone manufacturer then modifies to get it going on their hardware. This means that drivers for Eclair don't work on Froyo, and drivers for Froyo don't work on Gingerbread, and drivers for GB don't work on ICS. There are hacks and ugly mods you can do to make them kind of work, but basically it doesn't work. If you can get the drivers to work, it's so broken and laggy that you don't want it to be working.
Samsungs FIMG drivers are made for Eclair and Froyo, and that's only because those were the two firmwares Samsung made for the Apollo. Gingerbread did a lot of changes to the graphics subsystem and this basically breaks all compatibility with Froyo drivers
Replacing the OpenFIMG libraries with the Samsung FIMG libraries won't work because the Android frameworks in CM7 were compiled around OpenFIMG. When marcell had it working on Samsung FIMG drivers, he had to modify the interfaces for the graphics libraries that communicates between the Android framework and the hardware specific libaries (OpenFIMG/Samsung FIMG) to make it talk to it the way the Samsung FIMG libraries worked. When he moved to OpenFIMG he would have reverted it back to how Google would want it because OpenFIMG is made for GB/ICS+ and doesn't need this compatibility wrapper.
G3MOD works differently to the CM7 kernel. G3MOD needed to support many different firmwares and many different graphics modes. This means that to make it work on other firmwares, we had to modularise components of it so certain kernel functions were used on certain firmwares. This is why there are modules for G3MOD to work with OpenFIMG and not on other kernels.
Kernel modules are kernel specific. They only work with the kernel they were compiled for. You can't use a G3MOD module on Fugumod and vice versa.
hillbeast said:
Oh dear. There's a lot wrong with what you're trying to do so let me try and explain it as best I can:
Android libraries are not like Windows where you can mix and match drivers to different versions. Every time Google makes a new version of Android, they change how they want to do the graphics drivers. It's really annoying that they do this, but they aren't trying to make a desktop OS, they are making an embedded OS that the phone manufacturer then modifies to get it going on their hardware. This means that drivers for Eclair don't work on Froyo, and drivers for Froyo don't work on Gingerbread, and drivers for GB don't work on ICS. There are hacks and ugly mods you can do to make them kind of work, but basically it doesn't work. If you can get the drivers to work, it's so broken and laggy that you don't want it to be working.
Samsungs FIMG drivers are made for Eclair and Froyo, and that's only because those were the two firmwares Samsung made for the Apollo. Gingerbread did a lot of changes to the graphics subsystem and this basically breaks all compatibility with Froyo drivers
Replacing the OpenFIMG libraries with the Samsung FIMG libraries won't work because the Android frameworks in CM7 were compiled around OpenFIMG. When marcell had it working on Samsung FIMG drivers, he had to modify the interfaces for the graphics libraries that communicates between the Android framework and the hardware specific libaries (OpenFIMG/Samsung FIMG) to make it talk to it the way the Samsung FIMG libraries worked. When he moved to OpenFIMG he would have reverted it back to how Google would want it because OpenFIMG is made for GB/ICS+ and doesn't need this compatibility wrapper.
G3MOD works differently to the CM7 kernel. G3MOD needed to support many different firmwares and many different graphics modes. This means that to make it work on other firmwares, we had to modularise components of it so certain kernel functions were used on certain firmwares. This is why there are modules for G3MOD to work with OpenFIMG and not on other kernels.
Kernel modules are kernel specific. They only work with the kernel they were compiled for. You can't use a G3MOD module on Fugumod and vice versa.
Click to expand...
Click to collapse
Thank you for your answer :laugh: now i eventually understood how graphics driver works. So basically the only way to get proprietary fimg on alpha9 is getting alpha7 sources and apply all the alpha9 patches manually except the ones of openFIMG or i'm still thinking in the wrong way?
superfrancy97 said:
Thank you for your answer :laugh: now i eventually understood how graphics driver works. So basically the only way to get proprietary fimg on alpha9 is getting alpha7 sources and apply all the alpha9 patches manually except the ones of openFIMG or i'm still thinking in the wrong way?
Click to expand...
Click to collapse
If it compiles, it could... unfortunately, I lost alpha7 sources and I can't spend (a lot of time) to done it again ...
The other way is to get surfaceflinger, libui (and probably others) libs sources from froyo .. You will have errors when compiling (because of the CRT animations, screenshot implementations in GB) but it's possible to fix the errors.
It works. I currently have cm7 mtd with samsung's fimg libs but now camera need to be fixed, re-implement screenshot and CRT anim and some color problem when rendering pictures.
You asked kernelmtd sources. I will upload them to github today.
edit : sources uploaded here -> https://github.com/sdadier/gb_kernel_2.6.32.9-mtd
marcellusbe said:
If it compiles, it could... unfortunately, I lost alpha7 sources and I can't spend (a lot of time) to done it again ...
The other way is to get surfaceflinger, libui (and probably others) libs sources from froyo .. You will have errors when compiling (because of the CRT animations, screenshot implementations in GB) but it's possible to fix the errors.
It works. I currently have cm7 mtd with samsung's fimg libs but now camera need to be fixed, re-implement screenshot and CRT anim and some color problem when rendering pictures.
You asked kernelmtd sources. I will upload them to github today.
edit : sources uploaded here -> https://github.com/sdadier/gb_kernel_2.6.32.9-mtd
Click to expand...
Click to collapse
R u still working on g3?
Sent from my DEATH NOTE with Shinigami by my side!
Arjav23 said:
R u still working on g3?
Sent from my DEATH NOTE with Shinigami by my side!
Click to expand...
Click to collapse
Not seriously ... only when I have nothing better to do
marcellusbe said:
Not seriously ... only when I have nothing better to do
Click to expand...
Click to collapse
It would be great sir if you could spend a little of your valuable time in giving a try of whether kitkat could be ported to g3
Or
Help us to get a 3.4.x kernel!
Sent from my DEATH NOTE with Shinigami by my side!
Arjav23 said:
It would be great sir if you could spend a little of your valuable time in giving a try of whether kitkat could be ported to g3
Or
Help us to get a 3.4.x kernel!
Sent from my DEATH NOTE with Shinigami by my side!
Click to expand...
Click to collapse
Wow ... it's about 2 years of work for me !
I can't dedicate much time for g3.
marcellusbe said:
If it compiles, it could... unfortunately, I lost alpha7 sources and I can't spend (a lot of time) to done it again ...
The other way is to get surfaceflinger, libui (and probably others) libs sources from froyo .. You will have errors when compiling (because of the CRT animations, screenshot implementations in GB) but it's possible to fix the errors.
It works. I currently have cm7 mtd with samsung's fimg libs but now camera need to be fixed, re-implement screenshot and CRT anim and some color problem when rendering pictures.
You asked kernelmtd sources. I will upload them to github today.
edit : sources uploaded here -> https://github.com/sdadier/gb_kernel_2.6.32.9-mtd
Click to expand...
Click to collapse
Uhm, i have lot of free time so i will give it a try, who knows, maybe i'm going to learn something useful :laugh:! I found alpha7 device folder in venkat kamesh's github account could that be useful?
marcellusbe said:
Wow ... it's about 2 years of work for me !
I can't dedicate much time for g3.
Click to expand...
Click to collapse
But @hillbeast got a start already.
Won't that help?
Sent from my DEATH NOTE with Shinigami by my side!
marcellusbe said:
Not seriously ... only when I have nothing better to do
Click to expand...
Click to collapse
do you have the cm9 sources? becuase i couldnt fin them and wanted to fix the superuser problem
marcellusbe said:
If it compiles, it could... unfortunately, I lost alpha7 sources and I can't spend (a lot of time) to done it again ...
The other way is to get surfaceflinger, libui (and probably others) libs sources from froyo .. You will have errors when compiling (because of the CRT animations, screenshot implementations in GB) but it's possible to fix the errors.
It works. I currently have cm7 mtd with samsung's fimg libs but now camera need to be fixed, re-implement screenshot and CRT anim and some color problem when rendering pictures.
You asked kernelmtd sources. I will upload them to github today.
edit : sources uploaded here -> https://github.com/sdadier/gb_kernel_2.6.32.9-mtd
Click to expand...
Click to collapse
I should take the " surfaceflinger, libui (and probably others) libs sources" from froyo or AOSP?
Related
This is a development thread. If you want a conversation thread, please open one in the general forum!
I've released the source a little early of completion, so I can get others on teamacid to help out. So until we get on the android-samsung-2.6.35-gingerbread branch and changes added, tested, pushed, and tested by a more general audience, I would NOT SUGGEST FLASHING THIS. Don't expect any wiz-bang features added or anything like that. This is a port. After the port is done, we can do all sorts of stuff.
Milestones to complete:
Scrub existing code that does not relate to Galaxy S 4G (SGH-T959V/VibrantPlus) from arch/arm/...
Move architecture specific code to mach-herring.c (as it should be) and make the changes diff cleanly with the aosp samsung android-samsung-2.6.35-gingerbread branch
Scrub and import needed drivers to new android-samsung-2.6.35-galaxys4g branch with herring conversion stuff imported.
Try to get rid of dvfs stuff and move to stock cpufreq (for easier future porting to Linus's mainline, which is the goal of this kernel, amongst other modifications that will open up...)
Get all components working (wifi/bt/gps/etc. It may not be possible to use bml/fsr/rfs/ext4, because of the symbol table changing, but lets try to see if we can get it working before making the kernel compatible with cm/aosp)
investigate BML<->MTD rom conversion kernel
I have currently completed Milestone 1. I am currently running stability tests with unnamed rc2. The binary should be the same as the minimal changes to stock source to make it boot and work with a standard bml rom, but without the other board code for dempsy, kepler, vibrant, vibrantplustelus, flemming, aries ntt, and others. All code is cleaned up and specific for VibrantPlus/SGH-T959V.
I've put together a new initramfs/recovery based on v5.0.2.8 to work on BML. This does not contain the voodoo lagfix support.
You WILL have to use an updater-script that forces conversion to ext4.
GitHub:
Kernel - https://github.com/bhundven/android_kernel_samsung_galaxys4g
Initramfs - https://github.com/bhundven/android_initramfs_samsung_galaxys4g
Stay tuned... I will update with progress.
post for uploads
OP updated. Using new initramfs (gingerbread branch), some kernel and build.sh fixes.
Just a note, I've made a little progress on m2.
Looking at possibly having something releasable here in the next week or two.
I've been out of work now since may 1st and its been hard to motivate myself on anything phone related.
Much thanks to the members of teamacid and teamkickass for keeping this stuff going!
Sent from my SAMSUNG-SGH-I717 using xda premium
So these are BML kernels converted to MTD?
Sent from my SGH-T959V using XDA
smontero said:
So these are BML kernels converted to MTD?
Sent from my SGH-T959V using XDA
Click to expand...
Click to collapse
You missed the point entirely.
EDIT
Look under "Milestones to complete"
I see but I don't completely understand. I just found out the difference between BML and MTD but I was asking cause I'm using the miui MTD and i wanted to know if these kernels would work
Sent from my SGH-T959V using XDA
He hasn't posted download links to them yet.
FBis251 said:
He hasn't posted download links to them yet.
Click to expand...
Click to collapse
Right. If you know how to compile the kernel, you could. If you did, you would currently have a BML kernel. (note there is also no mtd support in the current initramfs either)
I'm not sure if Milestone 2 will be able to support RFS. I may pull in the FSR code from supercurio's repository so that we can still have BML+ext4, but that code was for a froyo kernel.
If I can't get that to work, then this kernel will be MTD only. I'm still having some problems where my current Milestone2 changes (not checked in) is not booting correctly.
As I said, I'll have an update soon.
Let's try get cm10 too boot atleast im downloading the sources i read a few guides every omap4 device except the lg optimus 3d is either running cm9 or cm10 im gonna try to get it to atleast boot even if nothing else work right well something todo till lg decides to do the upgrade. by the way in the GB Sources for the lg p940 in the kernel sources it contains stuff to do with our phone driver wise i think the only thing that differs is camera + ram.
anybody tried it before?
I'm thinking of trying it, please link the guides you've found!
Sent from my LG-P920 using xda app-developers app
Good luck guys we are all "rooting" (hahah get it, get it ) for you guys , defcomg are you going to try and port the prada ics first and then cm10, or directly ??
If you're hell bent on trying, I would suggest porting a mixture of the Prada ICS and CM10: Prada ICS for most of the drivers and code to make things work and CM10 for the base. This is because you have the CM10 source so it's easy to modify what doesn't work, since the Prada ICS kernel probably won't work out of the box anyway. You could port Prada ICS wholesale but I suspect more things won't work that way given CyanogenMod often has open source blobs for most of the drivers and for whatever chips that are different from the Prada phone whose drivers you need.
defcomg said:
anybody tried it before?
Click to expand...
Click to collapse
yes, but i got an non booting ramdisk + a zipp without media, fonts, vendor and apps.
but it could also be that i have failed, today i will tray it again so let's hope somebody will make it
FPtje said:
I'm thinking of trying it, please link the guides you've found!
Sent from my LG-P920 using xda app-developers app
Click to expand...
Click to collapse
http://www.kernel-xp.net/index.php/en/guide/25-android/32-compilare-cm10
http://wiki.cyanogenmod.com/wiki/Building_from_source
http://forum.xda-developers.com/showthread.php?t=1668483&highlight=build+cm9+source
http://forum.xda-developers.com/showthread.php?t=1668396
http://forum.xda-developers.com/showthread.php?t=1807505&highlight=build+cm10
rezzsha said:
Good luck guys we are all "rooting" (hahah get it, get it ) for you guys , defcomg are you going to try and port the prada ics first and then cm10, or directly ??
Click to expand...
Click to collapse
Was gonna port it directly i was gonna run a comparison on winhex to see how the kernels differ
pandaball said:
If you're hell bent on trying, I would suggest porting a mixture of the Prada ICS and CM10: Prada ICS for most of the drivers and code to make things work and CM10 for the base. This is because you have the CM10 source so it's easy to modify what doesn't work, since the Prada ICS kernel probably won't work out of the box anyway. You could port Prada ICS wholesale but I suspect more things won't work that way given CyanogenMod often has open source blobs for most of the drivers and for whatever chips that are different from the Prada phone whose drivers you need.
Click to expand...
Click to collapse
Repo failed have to start over damn i think i have identified a few chips. if there was a way to get the kernel what drivers are loaded
Well that's new. Did you do repo init, repo sync and also installing all the dev tools as recommended here (http://source.android.com/source/initializing.html)? To extract the drivers, you'll have to decompile the Prada ICS kernel, extract the drivers, find a CM10 supported device with similar hardware, replace drivers for the different hardware, do a bit of coding to set up a new CM branch on your com and set up brunch/lunch and vendorsetup/makefile and fill it up with the files mentioned above and see if you can compile it.
http://processors.wiki.ti.com/index.php/TI-Android-ICS-PortingGuide
Hope this helps! Good luck!
Sent from my phone.
good luck and hope you manage this would be amazing. A big thank you just for your effort
I just started a new cm9 build with prada ics kernel but with my lame pc it will take some time.
pandaball said:
Well that's new. Did you do repo init, repo sync and also installing all the dev tools as recommended here (http://source.android.com/source/initializing.html)? To extract the drivers, you'll have to decompile the Prada ICS kernel, extract the drivers, find a CM10 supported device with similar hardware, replace drivers for the different hardware, do a bit of coding to set up a new CM branch on your com and set up brunch/lunch and vendorsetup/makefile and fill it up with the files mentioned above and see if you can compile it.
Click to expand...
Click to collapse
Closest Device Running CM10 Same SOC
[JB]Samsung I9100G - https://github.com/CyanogenMod/android_device_samsung_i9100g/tree/jellybean
[ICS]LGE P940 - https://github.com/milaq/android_device_lge_p940
Would This Work Replace the LIBS and Configs in devices/samsung/i9100g with the ones from Prada Compile then in the OUT Folder replace WIFI MOdule wpa_sup the issue here is the kernel i can modify the ICS Kernel of the Prada to Match that of the p920 most things are the same its only a few files that change when kernel is compiled should i just place it on the root of the device folder?
I din't know if that stuff that I think make sense but wouldn't it be better if we try to make at first
a working cm9 zip, and after that try to port cm10? It's because there are already some tutorials of how
to "converting" ics into jellybean.
I also started again building a cm9 build, this time with ics prada kernel source and
the command
Code:
make otapackage
instead of brunch p920.
But it will take some time to compile that because my PC isn't the best (single core 2.8 ghz Intel celeron with 2gb RAM)
This looks way too difficult for me. While I might be able to build Android, I'll have no clue on how to debug or fix issues.
berni987654321 said:
I din't know if that stuff that I think make sense but wouldn't it be better if we try to make at first
a working cm9 zip, and after that try to port cm10? It's because there are already some tutorials of how
to "converting" ics into jellybean.
I also started again building a cm9 build, this time with ics prada kernel source and
the command
Code:
make otapackage
instead of brunch p920.
But it will take some time to compile that because my PC isn't the best (single core 2.8 ghz Intel celeron with 2gb RAM)
Click to expand...
Click to collapse
Well Im Runnning UBUNTU on VMware left it compiling a test build i have two Sources JB/CM @ Android/system ICS/ASOP @ Working_Directory. i just thought it would be much easier to just complile cm10 instead of cm9 then cm10 let me know how your build goes. The Prada Kernel is it modded for P920 or is it stock.
Most tutorials to Compile from Source are not good maybe we could ask codeworx for help he got JB Running on the i9100g
The Needs to be a Convert CM7 to CM9 to CM10 Guide.
FPtje said:
This looks way too difficult for me. While I might be able to build Android, I'll have no clue on how to debug or fix issues.
Click to expand...
Click to collapse
i know what you mean before attempting this i had not even used linux but guides and tuts can only get you so far when Ricardo had a working cm9 all that was whacked was the dsp this was before the lg prada it now has ics wonder why he did not get required dsp drivers and modules from prada ics source it would be cool if he released CM9 at whatever state its in im sure we would manage to get it fully functional
defcomg said:
i know what you mean before attempting this i had not even used linux but guides and tuts can only get you so far when Ricardo had a working cm9 all that was whacked was the dsp this was before the lg prada it now has ics wonder why he did not get required dsp drivers and modules from prada ics source it would be cool if he released CM9 at whatever state its in im sure we would manage to get it fully functional
Click to expand...
Click to collapse
Well I dont thinks so that's gonna happend, I just asked him that on G+ and he said "No".
this time i managed to get apps but who finds the fail?
berni987654321 said:
this time i managed to get apps but who finds the fail?
Click to expand...
Click to collapse
Fail? is it the apps only are the other folder libs etc bin also compiled?
My build was taking to long so i stopped it will attempt again in the weekend this Source Compilation is way hectic
I meant that there's a nfc.apk in the app folder xD . My computer is now working since 9 hours.
app, etc, framework, fonts should be ready but there are some libs missing and I don't know about
the other folders so let's hope that I'm getting this atleast to the cm9 bootanimation.
---------- Post added at 10:15 PM ---------- Previous post was at 10:08 PM ----------
my terminal is completly full just with compiling libwebcore -_-'
I originally released this rom on 2fastforums.com (http://2fastroms.com/showthread.php?5435-WIP-18-Dec-2012-CM7-Kernel-CM-msm7x30) and now feel it is ready for release on XDA. (Site is currently down for unknown reasons)
CM7 for HTC Merge/Lexikon
Click to expand...
Click to collapse
Code:
Features:
-100% stock CM7 from source
What works:
Almost everything
Click to expand...
Click to collapse
What doesn't work:
MMS on USC?
Jittery Compass
Click to expand...
Click to collapse
Instructions
1) Flash recovery through bootloader or fastboot
2) Boot into recovery and factory reset, also go into mounts and format system
3) Flash Rom
4) Flash GApps
Click to expand...
Click to collapse
Downloads
Recovery: http://d-h.st/users/e334/?fld_id=6766 (Either one will work, I personally prefer v5.0.2.8 Capacitive Touch)
ROM: http://d-h.st/users/e334/?fld_id=6727
GApps: https://www.box.com/s/79bpq0ywdxcf4093t926 (thanks liamf1!)
Click to expand...
Click to collapse
Source
Kernel: https://github.com/jianC/htc-kernel-msm7x30
Lexikon Device Tree: https://github.com/jianC/android_device_htc_lexikon
Lexikon Proprietary Vendor Tree: https://github.com/jianC/android_vendor_htc
Click to expand...
Click to collapse
All my changes are documented on github.
Credits: Cyberblade (CDMA fix), liamf1 (beta tester/helpful feedback) 2fast4u88, Cyanogenmod & Team, Kali-, Neopeek & Team, UnitedDev & Team, and everyone else who contributed.
Please leave any feedback about bugs/problems/glitches/etc and I will try to fix them.
Thank you ;D
Sent from my HTC Merge using Tapatalk 2
faille13 said:
Thank you ;D
Sent from my HTC Merge using Tapatalk 2
Click to expand...
Click to collapse
Nice to see you on here too
Lol yeah, I'm everywhere.
Sent from my HTC Merge using Tapatalk 2
---------- Post added at 01:34 PM ---------- Previous post was at 01:12 PM ----------
I don't get around here too often. I haven't seen a dedicated forum for my merge yet.
Sent from my HTC Merge using Tapatalk 2
GPS problem
How to fix the GPS ?
It won't turn on , I mean GPS icon is not shown in the notifications bar and it searches for the satellites forever .
I use 20130121 version of this mod and gsm mode .
Gytixas said:
How to fix the GPS ?
It won't turn on , I mean GPS icon is not shown in the notifications bar and it searches for the satellites forever .
I use 20130121 version of this mod and gsm mode .
Click to expand...
Click to collapse
Hmm.. i'll look into it.
I am so happy that new version established but i GSM doesn't work. Please fix the bug
Thanks
Mistake
sorry sorry, GSM works perfect, Just needed to reboot. Thanks a lot. but Bluetooth and GPS doesn't work either. Plz fix these bugs ! Thanks
nikoloz995 said:
I am so happy that new version established but i GSM doesn't work. Please fix the bug
Thanks
Click to expand...
Click to collapse
+1
development of the firmware is?
Thank you so much, this is the best rom for this phone (the only working cyanogen). I am happy to report that after a few weeks use it has across the board improved my phones responsiveness, battery life, and usability. However... I have one problem. I live in Alaska and have GCI as a carrier... when I alter my cdma apn info, everything works up to the point I want to change my MCC and MNC... it's defaulting to 310 and 012 respectively. When I leave those values alone it saves the apn... when I alter them, the apn entry disappears! How can I fix this? I I need it to be 311 and 370 but can't get it to save my apn.
If this never works, I don't care, I wil continue using this rom without mobile internet or mms downloads... it's just that good.
lexikonlover said:
Thank you so much, this is the best rom for this phone (the only working cyanogen). I am happy to report that after a few weeks use it has across the board improved my phones responsiveness, battery life, and usability. However... I have one problem. I live in Alaska and have GCI as a carrier... when I alter my cdma apn info, everything works up to the point I want to change my MCC and MNC... it's defaulting to 310 and 012 respectively. When I leave those values alone it saves the apn... when I alter them, the apn entry disappears! How can I fix this? I I need it to be 311 and 370 but can't get it to save my apn.
If this never works, I don't care, I wil continue using this rom without mobile internet or mms downloads... it's just that good.
Click to expand...
Click to collapse
APN backup and restore app worked for me on US Cellular (backup apn from stock install, then restore to CM7), though I had to switch to GoSMS as a messaging app for MMS to send properly (stock app would receive but not send MMS - SMS worked normally in both). I had no success manually entering the apn info - didn't seem to have any effect when I tried.
@JianC
I found an issue with the 20130121 version from Jan 21 you posted on 2fastroms: If the phone is left on the charger it will charge all the way up, then discharge all the way back to zero while still plugged in. It still displays that it is at 100%, but then abruptly drops to whatever the actual charge level is after a few minutes of use. I've tried wiping battery stats to no effect and it works properly in stock rom. This is the only bug I can't seem to work around... Any fix or suggestions for things to try would be most appreciated! Thanks again for your work on this ROM!
Fixed GPS (and other issues), please see OP!
EDIT: I'll look into the apns issue... I don't use my Merge on CDMA so it's a stab in the dark.
The final version of CM7 has been uploaded (charging bug *should* be fixed).. I will not be supporting CM7 anymore but will be working on Evervolv/CM10.1.
Thanks for your feedback and support!
jianC said:
The final version of CM7 has been uploaded (charging bug *should* be fixed).. I will not be supporting CM7 anymore but will be working on Evervolv/CM10.1.
Thanks for your feedback and support!
Click to expand...
Click to collapse
CM10.1 availible to test?
DJ_MiX said:
CM10.1 availible to test?
Click to expand...
Click to collapse
Nope, he working on kernel .
http://review.evervolv.com
Sent from my HTC Merge using xda premium
If any help with the kernel is needed I will try my best to free up some time and pitch in some help. I have made several kernels for several other devices and the most popular being for the Acer Iconia tablets here on XDA see my signature. Great to see a CM rom for the merge on here though!! GB works fine for me, not that much cool factor from cm 10 or cm 10.1 as I have compiled quiet a few nightlies for the A100.. Other than the Project Butter and the overall UI I could care less about JB/ICS.
linuxsociety said:
If any help with the kernel is needed I will try my best to free up some time and pitch in some help. I have made several kernels for several other devices and the most popular being for the Acer Iconia tablets here on XDA see my signature. Great to see a CM rom for the merge on here though!! GB works fine for me, not that much cool factor from cm 10 or cm 10.1 as I have compiled quiet a few nightlies for the A100.. Other than the Project Butter and the overall UI I could care less about JB/ICS.
Click to expand...
Click to collapse
@linuxsociety That would be awesome if you could. Elginsk8r and I have already ported the board files but I can't figure out what's keeping it from booting..
@ everyone: CM9 for the htc merge is here!: http://forum.xda-developers.com/showthread.php?p=44487058#post44487058
jianC said:
@linuxsociety That would be awesome if you could. Elginsk8r and I have already ported the board files but I can't figure out what's keeping it from booting..
Click to expand...
Click to collapse
Does it just boot loop or does it go black? does the CM logo appear? Guess there is no logcat output via adb either or you'd probably have nailed it by now. Maybe we will have to get jtag debugging output so we can see exactly what is causing the kernel panic and work from there.
I have just now had time to get on xda and check up on the new status. I will try to clone the git repository and check the kernel .config for the cm10 build. Just a thought but on most devices that have a working kernel with cm9 the exact same kernel + modules work fine with CM10. Have you all tried the kernel from CM9 that was just recently posted on any CM10 builds for the device? Not much has changed between ICS and JB that are dependent on in kernel features or that require bleeding edge mainline kernel and/or proprietary kernel patches. However there is a good possibility that the issue is more to do with the bootloader that is required to chainload the android OS for JB causing CM10 not to boot properly. So updating the bootloader may be necessary for JB/CM10 to boot properly. Nevertheless we need some debugging output in order to pinpoint what exactly is the problem going on. I am going to flash cm9 to my merge now and see how everything goes. I may experiment with the cm9 kernel and a cm10 build if I can find one for the merge. My hardware I have right now would take quiet some time to build JB as I haven't even used this old c2d laptop to build any android roms yet lol. Sorry for such a long posting but hopefully it is of some help in finding the resolution to the problems we have.
Thanks guys!
linuxsociety said:
Does it just boot loop or does it go black? does the CM logo appear? Guess there is no logcat output via adb either or you'd probably have nailed it by now. Maybe we will have to get jtag debugging output so we can see exactly what is causing the kernel panic and work from there.
I have just now had time to get on xda and check up on the new status. I will try to clone the git repository and check the kernel .config for the cm10 build. Just a thought but on most devices that have a working kernel with cm9 the exact same kernel + modules work fine with CM10. Have you all tried the kernel from CM9 that was just recently posted on any CM10 builds for the device? Not much has changed between ICS and JB that are dependent on in kernel features or that require bleeding edge mainline kernel and/or proprietary kernel patches. However there is a good possibility that the issue is more to do with the bootloader that is required to chainload the android OS for JB causing CM10 not to boot properly. So updating the bootloader may be necessary for JB/CM10 to boot properly. Nevertheless we need some debugging output in order to pinpoint what exactly is the problem going on. I am going to flash cm9 to my merge now and see how everything goes. I may experiment with the cm9 kernel and a cm10 build if I can find one for the merge. My hardware I have right now would take quiet some time to build JB as I haven't even used this old c2d laptop to build any android roms yet lol. Sorry for such a long posting but hopefully it is of some help in finding the resolution to the problems we have.
Thanks guys!
Click to expand...
Click to collapse
The .35 kernel works fine for CM10.0 but I'm having some issues booting cm10.1 with the .35 kernel because of some graphics memory allocation issues. The main issue is that there are a few issues that can't be fully fixed without the 3.0 kernel such as the camera/camcorder, ION support, etc (which is WIP here: http://review.evervolv.com/#/c/6609/ ). I have already tried probing for the UART TX/RX pins on the lexikon motherboard with a bus pirate but I have not found anything to date. I ordered a micro usb breakout board yesterday for USB UART debugging and am going to pick up some resistors from radioshack so we can hopefully get some progress on the 3.0 kernel because it won't boot far enough to adb or dmesg for our purposes. The problem isn't CM10 right now, but the kernel, which would require jtag or uart debugging, as you have mentioned. I hope that we can get the 3.0 kernel booting soon so we can have cm9/10 fully working.
jianC said:
The .35 kernel works fine for CM10.0 but I'm having some issues booting cm10.1 with the .35 kernel because of some graphics memory allocation issues. The main issue is that there are a few issues that can't be fully fixed without the 3.0 kernel such as the camera/camcorder, ION support, etc (which is WIP here: http://review.evervolv.com/#/c/6609/ ). I have already tried probing for the UART TX/RX pins on the lexikon motherboard with a bus pirate but I have not found anything to date. I ordered a micro usb breakout board yesterday for USB UART debugging and am going to pick up some resistors from radioshack so we can hopefully get some progress on the 3.0 kernel because it won't boot far enough to adb or dmesg for our purposes. The problem isn't CM10 right now, but the kernel, which would require jtag or uart debugging, as you have mentioned. I hope that we can get the 3.0 kernel booting soon so we can have cm9/10 fully working.
Click to expand...
Click to collapse
This sounds about like the exact same issues that was experienced when I was helping hashcode work on the original kindle fire device and getting it to work with ICS. I 'think' with the HTC it shouldn't be near as hard to resolve the issue to get full hw acceleration, memory mappings camera/gps and all the extra bells and whistles if we make an attempt at backporting the necessary support into the .35 kernel instead of trying to upgrade * to 3.x which will be adding to the work and break more things than it fixes. Since HTC apparently isn't going to be releasing any updates for the device it looks like it is going to be left all up to us to make one of two decisions:
1) backporting kernel - only the few things remaining needed for our current working GB kernel to have full support for ICS/JB roms
OR
2) updating to 3.x.x and merging HTC fixes and 3rd party patches -through several mainline kernel patches and keeping the proprietary htc addins compatible.
My opinion/suggestion:
I'd think of the two options that backporting would be the most logical answer to the equation since we are only missing support for few things and you already have everything working except the camera, ION, BINDER(?), and other >=3.0.0 android patches. Plus the device is pretty well coming to a good place to say cease development work and either enjoy the device or upgrade to something newer. So if we could get JB support or even just ICS working fully I think 99.99% of all owners/users would be more than 99.99% happy!! I know I would be very happy myself!
this is just a demo of a kernel based on quarx 3.0.8 kernel sources,maybe later i'll try to merge several fixes or something but till then lets say i've reached a small milestone like finishing to compile this kernel,booting it up,take some screenshots from it.
known bugs,just like initial quarxs or blenchose commits.
Warning:flash at your own responsability,works only with cm 10.1 under boot options by ticking 2ndboot and ticking adb disable
link to kernel:http://www.mediafire.com/?vdjoj438tlvz2lw
NOTE:kernel sources are based on quarx repo on github:https://github.com/Quarx2k/jordan-kernel
What's this? A fix for CM10.1 23/01?
I think it's a 3.0 kernel... so not a fix.
i think , quarx2k also made many changes with his CM 10.1-3.0 branch which corresponds to the 3.0 kernel ..( eg - hwcomposer sources)
so it will be better if u can compile and upload both ROM + KERNEL package in order to have maximum working efficiency
Shubhamqweasd said:
i think , quarx2k also made many changes with his CM 10.1-3.0 branch which corresponds to the 3.0 kernel ..( eg - hwcomposer sources)
so it will be better if u can compile and upload both ROM + KERNEL package in order to have maximum working efficiency
Click to expand...
Click to collapse
you're right,because i could not boot this kernel on 4.1.2 so tried with 4.2.1 without adb manual boot,the difference is that i added forced module unloading and allow old eabi binaries to run with this kernel trying to get some backwards compatibility thus my conclusion is that either this kernel needs scratch bins in the os for propper functioning
rodrigoswz said:
What's this? A fix for CM10.1 23/01?
Click to expand...
Click to collapse
nope,my bad to mention that is an kernel build on quarx repo
You know opening a new thread was unnecessary as we already have a 3.0 kernel thread and CM10.1 also.... BTW the kernel and CM10.1 are both easily compiled if you know what you're doing
Let's Go ^_^
Kayant said:
You know opening a new thread was unnecessary as we already have a 3.0 kernel thread and CM10.1 also.... BTW the kernel and CM10.1 are both easily compiled if you know what you're doing
Let's Go ^_^
Click to expand...
Click to collapse
The thread is already reported
Sent from my MB526 using xda premium
nogoodusername said:
The thread is already reported
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
thank you for your support nogood username,that helps alot and to what i can do for this comunity,for example my own kernel sources for linux kernel 3.7.5,as of this post was just an test to see if it works and 3.7.5 yup it likes the cpcap drivers and firmware,just some gpu issues to display under menuconfig
drunk_ryder24 said:
thank you for your support nogood username,that helps alot and to what i can do for this comunity,for example my own kernel sources for linux kernel 3.7.5,as of this post was just an test to see if it works and 3.7.5 yup it likes the cpcap drivers and firmware,just some gpu issues to display under menuconfig
Click to expand...
Click to collapse
I appreciate your work, and I'm not the one that reported (as far as I remember)
Sent from my MB526 using xda premium
nogoodusername said:
I appreciate your work, and I'm not the one that reported (as far as I remember)
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
maybe i started wrong but my intention was to give some help for the comunity,as for my attempt on kernel 3.7.5:bump cant port sgx drivers,got cpcap to show up in menuconfig even mapphone but its like impossible to show up,tried a workaround with similar devices to get the gpu drivers but no chance
drunk_ryder24 said:
maybe i started wrong but my intention was to give some help for the comunity,as for my attempt on kernel 3.7.5:bump cant port sgx drivers,got cpcap to show up in menuconfig even mapphone but its like impossible to show up,tried a workaround with similar devices to get the gpu drivers but no chance
Click to expand...
Click to collapse
Thanks for your efforts I think I was the one that reported it can't remember now ..... The reason I did it was because like you said you're trying to port 3.7.5 which we already have thread for where you cab discuss about porting 3.0.0 kernels
Some advice and questions......
I was wondering why are you trying to port 3.7.5 which is not even on any other android device yet??
IMO I think a higher version of the 3.0 base kernel is not needed as am sure most of the new things in it would not benefit us as we probably couldn't use it anyway since we have old drivers, old cpu/gpu etc.....
Getting it to show up in defconfig is not the hard part you can activate anything you want from there they are just the configuring files the hard part is configuring the activated drivers for the defy which requires dev work and debugging just look Quark's commits
I think what we have is fine and I don't think anything much higher would be any benefit for us also we have older drivers and the things we need for 4.2 to work properly are in 3.0.8 like the new wifi drivers maybe Quarx will update it to a higher minor version later like he did with 2.6.32.9 to 2.6.32.60......
Don't worry yourself to much there are many other things you can do to help us in the defy community. This is not worth your time trust me from experience :cyclops:
Btw the menuconfig iust activates the stuff you want for your device and mapphone_defconfig is where all the options you picked from menuconfig is stored. Each defconfig is different as they are specify to one device.
Kayant said:
Thanks for your efforts I think I was the one that reported it can't remember now ..... The reason I did it was because like you said you're trying to port 3.7.5 which we already have thread for where you cab discuss about porting 3.0.0 kernels
Some advice and questions......
I was wondering why are you trying to port 3.7.5 which is not even on any other android device yet??
IMO I think a higher version of the 3.0 base kernel is not needed as am sure most of the new things in it would not benefit us as we probably couldn't use it anyway since we have old drivers, old cpu/gpu etc.....
Getting it to show up in defconfig is not the hard part you can activate anything you want from there they are just the configuring files the hard part is configuring the activated drivers for the defy which requires dev work and debugging just look Quark's commits
I think what we have is fine and I don't think anything much higher would be any benefit for us also we have older drivers and the things we need for 4.2 to work properly are in 3.0.8 like the new wifi drivers maybe Quarx will update it to a higher minor version later like he did with 2.6.32.9 to 2.6.32.60......
Don't worry yourself to much there are many other things you can do to help us in the defy community. This is not worth your time trust me from experience :cyclops:
Btw the menuconfig iust activates the stuff you want for your device and mapphone_defconfig is where all the options you picked from menuconfig is stored. Each defconfig is different as they are specify to one device.
Click to expand...
Click to collapse
thats the whole point,everithing gets trouc the cross compiler even battery and every hw aspect for defy,but cant seem to get sgx drivers on it it boots but only backlight flickers,also the importance of this is that one day we might bump in a problem like this(maybe future android versions will use kernel 3.7.5 as default)and my opinion is that we should have some widen experience about it in any way possible
Kayant said:
Thanks for your efforts I think I was the one that reported it can't remember now ..... The reason I did it was because like you said you're trying to port 3.7.5 which we already have thread for where you cab discuss about porting 3.0.0 kernels
Some advice and questions......
I was wondering why are you trying to port 3.7.5 which is not even on any other android device yet??
IMO I think a higher version of the 3.0 base kernel is not needed as am sure most of the new things in it would not benefit us as we probably couldn't use it anyway since we have old drivers, old cpu/gpu etc.....
Getting it to show up in defconfig is not the hard part you can activate anything you want from there they are just the configuring files the hard part is configuring the activated drivers for the defy which requires dev work and debugging just look Quark's commits
I think what we have is fine and I don't think anything much higher would be any benefit for us also we have older drivers and the things we need for 4.2 to work properly are in 3.0.8 like the new wifi drivers maybe Quarx will update it to a higher minor version later like he did with 2.6.32.9 to 2.6.32.60......
Don't worry yourself to much there are many other things you can do to help us in the defy community. This is not worth your time trust me from experience :cyclops:
Btw the menuconfig iust activates the stuff you want for your device and mapphone_defconfig is where all the options you picked from menuconfig is stored. Each defconfig is different as they are specify to one device.
Click to expand...
Click to collapse
and how is that a problem if someone wants to attempt a higher version kernel?
if there is no benefit then there is no loss either
I understand your point and even I know nothing is impossible.
BUT, there has to be a logic in things that you are doing, isn't it? Believe me, Nobody is discouraging him. Anyways, its a matter of understanding and not a debate.
FYI and to my knowledge, very few devices like xperia T/V has kernel 3.4
abhifx said:
and how is that a problem if someone wants to attempt a higher version kernel?
if there is no benefit then there is no loss either
Click to expand...
Click to collapse
Like brajesh.sharma87 said am not trying to discourage him anything am just giving him some advice. This is mainly just my opinion based on experiences I had trying to port the newer wifi drivers from 3.0 base to our 2.6 kernel..... he doesn't have to listen to what am saying.
Like brajesh.sharma87 said it's matter of knowledge because the Linux kernel changes so much between versions and the work Quarx has done on the 3.0.8 base may become outdated and needs to be changed to get it to work for the new base.
Am just trying to put things into prospective as I think it's not worth his time and effort trying to port a higher version kernel without good knowledge and experience on kernel porting. Again that's for him to decide.
Drunk_ryder24 if you still want to try here are is something you can do that may help -
If you haven't already tried this but try cherry-picking Quarx's commits from the p-android-omap3-3.0 branch since the code is related to the defy but keep in mind not all of Quarx's work may work on the new base.
Kayant said:
Like brajesh.sharma87 said am not trying to discourage him anything am just giving him some advice. This is mainly just my opinion based on experiences I had trying to port the newer wifi drivers from 3.0 base to our 2.6 kernel..... he doesn't have to listen to what am saying.
Like brajesh.sharma87 said it's matter of knowledge because the Linux kernel changes so much between versions and the work Quarx has done on the 3.0.8 base may become outdated and needs to be changed to get it to work for the new base.
Am just trying to put things into prospective as I think it's not worth his time and effort trying to port a higher version kernel without good knowledge and experience on kernel porting. Again that's for him to decide.
Drunk_ryder24 if you still want to try here are is something you can do that may help -
If you haven't already tried this but try cherry-picking Quarx's commits from the p-android-omap3-3.0 branch since the code is related to the defy but keep in mind not all of Quarx's work may work on the new base.
Click to expand...
Click to collapse
well ive done cherry picking from quarx repo and i must say that quarx done an excelent job compiling the modules since they are recognized and compiled by the toolchain with no major errors,just a few ignorable errors,boy quarx must have nerves of steel to bare so much time in developing from scratch,oh btw i will post this as a reply in 4.1.2 tread,ive mixed kernel zimage and ramdisk of quarx 2.6.32.60 after applying sevenrock's kernel 2.6.32.9-the whole point is that it might have been something changed in either ril or wifi module cause 2.6.32.60 seems just a little laggy but no ringtone bug or reboots by this method
drunk_ryder24 said:
well ive done cherry picking from quarx repo and i must say that quarx done an excelent job compiling the modules since they are recognized and compiled by the toolchain with no major errors,just a few ignorable errors,boy quarx must have nerves of steel to bare so much time in developing from scratch,oh btw i will post this as a reply in 4.1.2 tread,ive mixed kernel zimage and ramdisk of quarx 2.6.32.60 after applying sevenrock's kernel 2.6.32.9-the whole point is that it might have been something changed in either ril or wifi module cause 2.6.32.60 seems just a little laggy but no ringtone bug or reboots by this method
Click to expand...
Click to collapse
That sounds good am I bit surprised it worked so well with not that much errors but thats's good Yh I know Quarx is unstoppable and good luck with the project ..... If you need any more advice or help just shoot me up with a pm and I will see what I can do
kayant said:
that sounds good am i bit surprised it worked so well with not that much errors but thats's good yh i know quarx is unstoppable and good luck with the project :d..... If you need any more advice or help just shoot me up with a pm and i will see what i can do
Click to expand...
Click to collapse
thanks for your support,its wellcomed
Hi guys
I'm really into Android 4.3.
I'm running CM10.2 (thanks Duy) and loving it.
So I want to make it work with GPS, to be able to make it a daily driver.
SGS i9000 is also working on CM10.2 with aries kernel and GPS is working there.
So I want to compare GPS threads of our and their kernel.
I understand I have to launch a Linux machine (I installed CygWin on my Win8 but couldn't find any proper documentation on what to do with it).
Please explain or direct me to how to extract our boot.img kernel so I will be able to make this comparison and maybe get it started.
Thanks.
Would love to help you, but sadly I don't know how. BUT, I will applaud your initiative. Go, go, go!!!!
Bump
sent from me
@Itzik: tbh I don't have faith for GPS on this phone lol (as for vibrant, GPS works sometimes but lame as hell afaik). Anw, for ur question , I think u should look at the source code tho, compare the two aries upstream at Cyanogen git and our phone aries kernel githubs. Then if u don't know where to start, try reviewing the commits for GPS of upstream aries for vibrant or so. But mayb it's not kernel bug tho, mayb it is device tree bug or vendor as well.
There is no way u can extract a Galaxy S (amd variants) boot.img coz of the kernel header as I read somewhere bout it.
Sent from my SGH-T959V using Tapatalk 2