Related
I found this patchd version of google chrome over on the arc forum, it does install and sign me in but doesn't display web pages for me, the non patched version from the market will not run at all for me and i know is due to no hardware acceleration yet on ics builds for defy, but maybe a dev here can work with this version, maybe not but thought I'd post anyway,
I did not patch this and do not know who did but here is the post i got it from http://forum.xda-developers.com/showthread.php?p=22910621 ,
Download here
http://www.mediafire.com/?4df8r5djnahde60
Sent from my MB525 using xda premium
We'd still need HWA, wich we can't implement on gingerbread so all you can do is wait for CM9 to have it
CM7 + CM9 double boot
HWA will soon be implemented in Defy/Defy+ CM9 ...
lutch83 said:
HWA will soon be implemented in Defy/Defy+ CM9 ...
Click to expand...
Click to collapse
Where from you know that? Is it certain information or you just assuming?
Could someone competent introduce me to the HWA problem on AOSP ICS? Is there a need for new drivers for each GPU model or CM team is prepairing universal solution for this? I'm not very into Android architecture, maybe someone who is can answer?
adiq_ambro said:
Where from you know that? Is it certain information or you just assuming?
Could someone competent introduce me to the HWA problem on AOSP ICS? Is there a need for new drivers for each GPU model or CM team is prepairing universal solution for this? I'm not very into Android architecture, maybe someone who is can answer?
Click to expand...
Click to collapse
Eppy and quarx are working on hardware acceleration for CM9 at the moment. They have got HDA working partially (3D accel.) But 2D acceleration is not yet working. And it's 2D acceleration that is needed in order for chrome to work.
It may be a driver matter, i don't know, but i'd make an intelligent guess on it
CM7 + CM9 double boot
helllo xda, many of you might have heard that I AM building CM10 from source and I have heard the we need the (kernel,gpu.....) drivers,
now broadcom released them and this is good.
my question is : how to use them ? pls help me
Many of u have heard?
Phone Slow? go ------>HERE<------
_____________________________________
"All my life I had one dream to achieve many many goals"
As I said earlier,
Building from source is better than porting.
But... if you're building from source , you'll be stuck having the same bugs as CM9 by whitexp has.
Sources which broadcom released (actually patch files, not actual source) are mostly meant for CM7. That's why whitexp couldn't proceed with CM9. It you see the madteam forum, and check whitexp's comment on asking proper release of sources , you'll get to know what I'm trying to say.
Also,
I did say earlier that whitexp made CM10 via sources and had end up getting the same bugs as CM9. Try fixing CM9 , if possible
tingtingin said:
Many of u have heard?
Phone Slow? go ------>HERE<------
_____________________________________
"All my life I had one dream to achieve many many goals"
Click to expand...
Click to collapse
Yes I have made a thread for that
Sent from my GT-S5360 using xda premium
Gamer R said:
As I said earlier,
Building from source is better than porting.
But... if you're building from source , you'll be stuck having the same bugs as CM9 by whitexp has.
Sources which broadcom released (actually patch files, not actual source) are mostly meant for CM7. That's why whitexp couldn't proceed with CM9. It you see the madteam forum, and check whitexp's comment on asking proper release of sources , you'll get to know what I'm trying to say.
Also,
I did say earlier that whitexp made CM10 via sources and had end up getting the same bugs as CM9. Try fixing CM9 , if possible
Click to expand...
Click to collapse
They cant work for cm10
Sent from my GT-S5360 using xda premium
mohamedrashad said:
They cant work for cm10
Sent from my GT-S5360 using xda premium
Click to expand...
Click to collapse
Maybe, maybe not. Patched blobs Broadcom made available for CM7 could be linked to specific version of libraries in CM7 that could have changed in CM9 or CM10, the only way to know is trying to build CM10 using this blobs, they must be placed somewhere under vendor/samsung/totoro/propietary/lib
You better read the whole Getting Started section here first, then the thread from Whitexp about building CM7 and adapt it for CM10.
It will be useful if you had previous experience building succesfully the Linux kernel for any architecture or something like Linux From Scratch, a good understanding of how a Linux system works is critical to be able to set up the environment and do a succesful build.
Be prepared to spend a lot of time reading, hunting and fixing missing dependencies! Good luck.
celisdelafuente said:
Maybe, maybe not. Patched blobs Broadcom made available for CM7 could be linked to specific version of libraries in CM7 that could have changed in CM9 or CM10, the only way to know is trying to build CM10 using this blobs, they must be placed somewhere under vendor/samsung/totoro/propietary/lib
You better read the whole Getting Started section here first, then the thread from Whitexp about building CM7 and adapt it for CM10.
It will be useful if you had previous experience building succesfully the Linux kernel for any architecture or something like Linux From Scratch, a good understanding of how a Linux system works is critical to be able to set up the environment and do a succesful build.
Be prepared to spend a lot of time reading, hunting and fixing missing dependencies! Good luck.
Click to expand...
Click to collapse
thanks
This thread is for developers to discuss bringup for the 3.4 jb kernel on various devices in the Nitro HD "iproj" family. These include P930, SU640, VS920, and LU6200.
Downloaded the su640 jb sources and compiled for ijb_skt. Tried to boot on my "gimpy" p930. No boot.
Enabled console framebuffer and snapped a pic just before reboot. It's complaining about fatal regulator error (msm_rpm_err_fatal). Anyone else get this far and/or see anything similar?
If anyone wants to use a console framebuffer, here's how:
1. Enable CONFIG_FRAMEBUFFER_CONSOLE and CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY.
2. Modify console_setup() in kernel/printk.c. Delete the function body and replace it with just "return 1".
Be prepared with a camera to snap an image of the screen before it reboots.
tdmcode said:
Downloaded the su640 jb sources and compiled for ijb_skt. Tried to boot on my "gimpy" p930. No boot.
Enabled console framebuffer and snapped a pic just before reboot. It's complaining about fatal regulator error (msm_rpm_err_fatal). Anyone else get this far and/or see anything similar?
If anyone wants to use a console framebuffer, here's how:
1. Enable CONFIG_FRAMEBUFFER_CONSOLE and CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY.
2. Modify console_setup() in kernel/printk.c. Delete the function body and replace it with just "return 1".
Be prepared with a camera to snap an image of the screen before it reboots.
Click to expand...
Click to collapse
Working on bringing this up for the vs920 as that's the only one I've got.
So far I've copied the ijb_skt bits over to ijb_vzw and used a bit of grep/sed magic to replace the skt bits to vzw in the files, and add ||'s for ijb_vzw wherever ijb_skt was a condition. I'm getting successful builds But they won't boot (yet). I'll keep you updated. I'll be pushing to here as I make any changes/progress.
Got past the RPM error with a hack.
In arch/arm/mach-msm/clock.c @ clock_late_init(), remove the list_for_each_entry_safe block.
Obviously, this is just a hack. We need to figure out what's causing the issue.
Next up is the display. The kgsl driver in this kernel does not match the kgsl libs in CM10. I'm going to download the 4.1 flashable rom from this forum and see if I can update the drivers to match.
I think kgsl is happy now. Next up is the msm video driver.
tdmcode said:
I think kgsl is happy now. Next up is the msm video driver.
Click to expand...
Click to collapse
Man, You're a machine... Here I'm still trying to get something that'll boot past the LG logo lol
Got boot animation and home screen. Then it reboots after a minute or so. The shell in adb gets really laggy right before reboot. Likely causes are a kernel hardware driver failing somewhere or a massive memory leak.
I see touch events logged but by the time the home screen shows I think it's too far gone to act on them. Same with hard buttons and capacitive buttons.
Oh .. by the way I'm using CM10 not CM10.1. It matches better since it's a 4.1 kernel.
Gotta stop for the day. Here's what I've got so far...
http://androidrepo.net/roms/quattrimus/iproj/iproj-3.4-checkpoint1.diff
tdmcode said:
Oh .. by the way I'm using CM10 not CM10.1. It matches better since it's a 4.1 kernel.
Gotta stop for the day. Here's what I've got so far...
http://androidrepo.net/roms/quattrimus/iproj/iproj-3.4-checkpoint1.diff
Click to expand...
Click to collapse
Nevermind. I thought the link I just posted was for someone working on another 3.4 kernel... it wasnt.
*Edit*
I'm obviously doing something horribly wrong by trying to borrow/reuse the ijb_skt files, because I can't get a kernel that even tries to boot (gets off the first LG logo)... and don't really have the know-how to reconstruct the files.
Didn't get a chance to work on this today I was busy on another project. But I'll be back on it Monday for sure.
@Yoinx: you are going to have a harder time with the vs920 because the hardware is different and it won't boot the su640 kernel.
I do not know the approach of developing cm10 kernel from stock kernel.
According to miroslav_mm,
http://forum.xda-developers.com/showpost.php?p=42075037&postcount=40
I tried using stock 3.4 zImage + cm10 ramdisk + required libs. It boots with blackscreen
lyfkevin said:
I do not know the approach of developing cm10 kernel from stock kernel.
According to miroslav_mm,
http://forum.xda-developers.com/showpost.php?p=42075037&postcount=40
I tried using stock 3.4 zImage + cm10 ramdisk + required libs. It boots with blackscreen
Click to expand...
Click to collapse
You need to change the kgsl and msm video code to match cm10. See my patch.
tdmcode said:
You need to change the kgsl and msm video code to match cm10. See my patch.
Click to expand...
Click to collapse
The boot.img provided by @navik
Same approach, i.e. stock zImage + cm10 ramdisk
I can boot into home screen with my su640 now.
Signal, wifi work.
but laggy, blinking screen(check hw overlay setting in option can fix), no sound, no bootanimation (black screen)
----------------------------------------------------
edit:
Merged your patch
able to see boot animation
Sent from my LG-LU6200 using xda premium
LU6200 jb source is released
https://wws.lg.com/global/support/opensource/opensourceList?types=ALL&search=lu6200
lyfkevin said:
I do not know the approach of developing cm10 kernel from stock kernel.
According to miroslav_mm,
http://forum.xda-developers.com/showpost.php?p=42075037&postcount=40
I tried using stock 3.4 zImage + cm10 ramdisk + required libs. It boots with blackscreen
Click to expand...
Click to collapse
I finished my new build CM10, on 3.4 kernel, with new JB camera libs, and other new properitary stuff. Dont have any problem with 3.4 kernel on CM10 (4.1.2), I didnt patch any KGSL driver, sources from my Github working, it dont have last updates but it working. I cant upload new ROM for test now, I dont have internet at home, when I fix my provider I will upload it.
lyfkevin which display libs did you use? Did you complete build CM10 with new kernel and headers?
Take this variant:
1.) display libs: copybit.msm8660.so, gralloc.msm8660.so, hwcomposer.msm8660.so, libgenlock.so, libhwcexternal.so, libhwcservice.so, libmemalloc.so, libqdutils.so, libtilerenderer.so, and libqdMetaData.so take from official STOCK 4.1 + take Adreno libs with MetaData support from my last CM10 or from STOCK 4.1 (older version) = its working on CM10
miroslav_mm said:
I finished my new build CM10, on 3.4 kernel, with new JB camera libs, and other new properitary stuff. Dont have any problem with 3.4 kernel on CM10 (4.1.2), I didnt patch any KGSL driver, sources from my Github working, it dont have last updates but it working. I cant upload new ROM for test now, I dont have internet at home, when I fix my provider I will upload it.
lyfkevin which display libs did you use? Did you complete build CM10 with new kernel and headers?
Take this variant:
1.) display libs: copybit.msm8660.so, gralloc.msm8660.so, hwcomposer.msm8660.so, libgenlock.so, libhwcexternal.so, libhwcservice.so, libmemalloc.so, libqdutils.so, libtilerenderer.so, and libqdMetaData.so take from official STOCK 4.1 + take Adreno libs with MetaData support from my last CM10 or from STOCK 4.1 (older version) = its working on CM10
Click to expand...
Click to collapse
is your 3.4 kernel compatible with your previous cm10 builds? a lot less MBs, easier to upload.
tdmcode said:
This thread is for developers to discuss bringup for the 3.4 jb kernel on various devices in the Nitro HD "iproj" family. These include P930, SU640, VS920, and LU6200.
Click to expand...
Click to collapse
Exece me,I want to build aosp of su640 based on LG offical open sourse. I have try serverl times,but end with failure.
Should you give me some advices or guide? Thanks for your reply!
navik said:
Exece me,I want to build aosp of su640 based on LG offical open sourse. I have try serverl times,but end with failure.
Should you give me some advices or guide? Thanks for your reply!
Click to expand...
Click to collapse
You cannot do this. There are many changes to files which are not gpl .
It takes a lot of work to make an aosp ROM. You need most of the cm hardware changes and various other changes through the system. I have done it for 4.1 with only one bug: the front camera does not work. I have not tried with 4.2 yet.
tdmcode said:
You cannot do this. There are many changes to files which are not gpl .
It takes a lot of work to make an aosp ROM. You need most of the cm hardware changes and various other changes through the system. I have done it for 4.1 with only one bug: the front camera does not work. I have not tried with 4.2 yet.
Click to expand...
Click to collapse
Thanks，but I want to build aosp based on LG open sourse instead of porting.
Do you have read the guide of LG offical open sourse？It say we can build stockrom based on LG official open sourse and Google android open sourse，we just need to copy LG open sourse into android open sourse. then breakfast and lunch.but I fail，I think I didn't pick up the guide of LG open sourse 。Do you have some good advices？Thanks again！
Sent from my LG-SU640 using xda premium
Well, here we go...
This is not the way I wanted to post this thread, but fate was stronger than me
Guys, I spent last several months working on a stable Sense 4.1 base for our HD2. I succeeded in a lot of things. I got BT working. I got mic working in applications. I got this damn thing running smoother than my wife's Galaxy S3 (I'm not kidding)...
So, yesterday my HD2 died on me. For the second time. I can't afford to fix it anymore, I don't have neither time nor money for that. Mainly time... So, unfortunately, I have to stop the development right here.
Someone, please take it from here. It would be a real pity for me if this ROM died together with my HD2.
Guys, as you can see further in this thread, someone donated a fully working HD2 to me. Just like that. For free.
If you ask me, this is an act of an incredible generousity.
Thanks a million, Legion.X. I'm still to find a way to thank you.
Let the development continue!
Introducing Common Sense 4.1
link to ver. 0.2:
http://www.mediafire.com/download/75m6jwtcq28gg8u/CommonSense41_next.zip
please test and comment.
previous versions:
ver 0.1: https://mega.co.nz/#!WhpRzJQa!DOdybh...6N52mPTfNkXk1k
what works:
* full Sense 4.1. almost everything works. daily driver.
* silky smooth, as good as native. flies at 20-30FPS with live wallpaper, probably around 60FPS with still wallpaper
* fast and snappy.
* sound recording works. voice input works. BT works.
* full 3D Rosie
* live wallpapers, Sense lockscreens etc.
* EXT2 over YAFFS loop (works automatically out of the box)
* should be snappier than ver. 0.1
known problems:
* it does reboot randomly from time to time. I'm looking for ways to solve these... looks like we'll end up recompiling libs from source.
ANYONE WHO HAS EXPERIENCE AND/OR WORKING ENVIRONMENT TO RECOMPILE FILES FROM SOURCE, PLEASE PM ME. My goal is to take gralloc sources from CM9 and adapt them for sense. but I don't have linux and don't have the toolchain set up. I'd appreciate any help with this.
* probably won't work in full NAND on TMOUS. anyone who wishes to participate, please try to install on TMOUS without sd-ext and report what you get. logcats are most welcome!
* WiFi router doesn't work. Custom routers from Play Store should work.
* Video shooting works at 15FPS. Don't know if that can be fixed... for me 15FPS is fine anyway
next steps:
* hopefully fix some of the crashes
* fix terrible lags during initial configuration and in the setup wizard
* improve Rosie (I know how to make it even smoother )
* try crossbreeder
* install XPosed framework
* please suggest more things to improve!
installation:
* BACKUP!!!
* IMPORTANT: you need CWM 3.0.0.6.. Other recoveries may or may not work. voronkov_pavel reports that CWM touch recovery beta 8 does not work with this ROM.
* REMEMBER: for Data On Ext, keep your system partition small! philliped364 reports that 55MB works just fine
* install Common Sense from recovery
* reboot. the first boot will take a while (although it's waaaay faster than in other ROMs thanks to odexing). should boot in 2-3 minutes. if it doesn't boot within 10 minutes, please report
* wait for the lockscreen to appear. DON'T PULL THE RING YET!
* make some coffee. let your HD2 settle down for at least half an hour
* pull the ring to unlock. if the setup wizard does not appear immediately, don't touch the device for another half an hour. if the device reboots by itself, please report.
* complete the setup wizard. it will lag. please be patient. DON'T SIGN IN TO YOUR GOOGLE ACCOUNT YET! finish the wizard and let Sense load.
* wait for two minutes and reboot
* let it settle down for another half an hour. it will optimize the databases during that phase. don't try to work with the device. it will lag terribly.
* unlock, go to Settings -> developer's settings, scroll down, disable "force GPU rendering"
* reboot
* your device should be fully functional now. now go to Settings -> accounts and sign it to your google account, email and whatever you like
big thanks to Legion.X (for sending me his HD2 for free), philliped346 (for his immense help and making my ROM nativeSD), saurabhrendale (for his incredible animations), Mr Evil (for letting me kang sound files from his EvoHD2 ROM), ckpv5 (for letting me kang Sense files from his MyOneDx ROM), dorimanx (for his kernel), RobbieP, ya5, aazzam16661, Daekin and many, many others for helping me out.
Some technical details about the ROM:
Config: Data on Ext, DB on NAND, looped over EXT2.
System: mostly taken from other Sense 4.1 devices, proprietary files taken from several half-working Sense 4.x ROMs flying around here. Sound system taken from EvoHD2 ROM (yeah, CM9). Credits to Mr Evil for these files.
Kernel: Dorimanx 7.2 HWA (credits to Dori please)
Framework: stock Desire X ROM as a base, heavily modified to work with CM9 sound system, heavily optimized for smoothness.
Sense: mostly myONEdx RC4.0 FX+ ROM. Rosie modified by me. Some files taken from stock Desire X ROM.
A word about kanging:
my goal is to create a stable Sense 4.1 base for HD2. feel free to kang anything you find here. just please PLEASE give proper credits. don't forget the guys who gave me some of the files: Mr Evil (creator of the EvoHD2 ROM) and ckpv5 (creator of the MyOneDx ROM)
NOTE for DEVs:
I was stunned to discover that DISABLING HW acceleration makes scrolling silky-smooth in 99% of the applications. Exceptions are: Rosie, Browser and... uh... that's it, I think. So, I REVERSED the way framework enables HW acceleration. Here's how: if the application doesn't request HW acceleration, it doesn't get it by default. If it requests it (HWAcceleration=true in the manifest), it DOESN'T get it either. If hwAcceleration=false in manifest, it DOES get it. This way, I only had to modify Rosie and the Browser and set hwAcceleration=false for them to actually GET the acceleration. The other apps just denied the acceleration natively. Please be aware of this change
Enjoy.
Report bugs.
May the Force be with you
thelonewolf_pav said:
Well, here we go...
This is not the way I wanted to post this thread, but fate was stronger than me
Guys, I spent last several months working on a stable Sense 4.1 base for our HD2. I succeeded in a lot of things. I got BT working. I got mic working in applications. I got this damn thing running smoother than my wife's Galaxy S3 (I'm not kidding)...
So, yesterday my HD2 died on me. For the second time. I can't afford to fix it anymore, I don't have neither time nor money for that. Mainly time... So, unfortunately, I have to stop the development right here.
Someone, please take it from here. It would be a real pity for me if this ROM died together with my HD2.
Here's the link. Enjoy.
http://d-h.st/7MZ
Disclaimer:
Frankly, I don't even know if it boots the way it is now. I was in the middle of something when this happened. Most probably, it will just work though.
Technical details:
Config: Data on Ext, DB on NAND, looped over EXT2. Yeah, it's returded fast.
System: mostly taken from other Sense 4.1 devices, proprietary files taken from several half-working Sense 4.x ROMs flying around here. Sound system taken from EvoHD2 ROM (yeah, CM9). Credits to Mr Evil for these files.
Kernel: Dorimanx 7.2 HWA (credits to Dori please)
Framework: stock Desire X ROM as a base, heavily modified to work with CM9 sound system, heavily optimized for smoothness.
NOTE for DEVs:
I was stunned to discover that DISABLING HW acceleration makes scrolling silky-smooth in 99% of the applications. Exceptions are: Rosie, Browser and... uh... that's it, I think. So, I REVERSED the way framework enables HW acceleration. Here's how: if the application doesn't request HW acceleration, it doesn't get it by default. If it requests it (HWAcceleration=true in the manifest), it DOESN'T get it either. If hwAcceleration=false in manifest, it DOES get it. This way, I only had to modify Rosie and the Browser and set hwAcceleration=false for them to actually GET the acceleration. The other apps just denied the acceleration natively. Please be aware of this change
Sense: stock Desire X ROM. I've got permission to use MyOne ROM (see Desire X forum), it has full 3D effects enabled and runs smooth as silk on HD2 (it's pretty damn smooth even with live wallpapers!)
What should work:
Everything. I know that WiFi router doesn't work, but that's it, more or less. Video shooting works at 15FPS. Sound recording works. Voice input works. BT works.
Known problems:
It does crash from time to time. Needs more work on system files. I was planning to recompile gralloc from CM9 to use it here, but didn't have the privilege to finish that.
For EXT2 loop to work, one needs to add creation of an empty data.img file in /Data/Data folder. Make it as big as possible. Format it for Ext2. The rest will be done by init.rc
............. Well, that's it. I'll be watching this thread. Don't ask me to develop anything though, I can't do anything without a working HD2. Sorry guys and good luck to anyone who will take it from here.
Bye
Click to expand...
Click to collapse
I will continue your hard work with Daekin
I've been working on Desire X Sense 4.1 port so, this will fix BT for us(build prop)
Thanks
Cant Install
Hello,i tried installing this rom but i couldnt..i get E:error in sdcard/commonsense41..zip(status6) any ideas?
blackphoenix50 said:
Hello,i tried installing this rom but i couldnt..i get E:error in sdcard/commonsense41..zip(status6) any ideas?
Click to expand...
Click to collapse
I cannot check for an obvious reason, but my gut feeling tells me that you downloaded a corrupted file. Try to open it with winzip. if it opens, extract the files and pack them back.
or just download again....
thelonewolf_pav said:
I cannot check for an obvious reason, but my gut feeling tells me that you downloaded a corrupted file. Try to open it with winzip. if it opens, extract the files and pack them back.
or just download again....
Click to expand...
Click to collapse
I did all these but still cant install.....tried also with twrp it gave me an error about updater binary...i searched at google and i think that the problem is the updater-script file...could someone plz check it cz i dont have the knowledge for that....
thelonewolf_pav said:
Well, here we go...
This is not the way I wanted to post this thread, but fate was stronger than me
Guys, I spent last several months working on a stable Sense 4.1 base for our HD2. I succeeded in a lot of things. I got BT working. I got mic working in applications. I got this damn thing running smoother than my wife's Galaxy S3 (I'm not kidding)...
So, yesterday my HD2 died on me. For the second time. I can't afford to fix it anymore, I don't have neither time nor money for that. Mainly time... So, unfortunately, I have to stop the development right here.
Someone, please take it from here. It would be a real pity for me if this ROM died together with my HD2.
Here's the link. Enjoy.
http://d-h.st/7MZ
Disclaimer:
Frankly, I don't even know if it boots the way it is now. I was in the middle of something when this happened. Most probably, it will just work though.
Technical details:
Config: Data on Ext, DB on NAND, looped over EXT2. Yeah, it's returded fast.
System: mostly taken from other Sense 4.1 devices, proprietary files taken from several half-working Sense 4.x ROMs flying around here. Sound system taken from EvoHD2 ROM (yeah, CM9). Credits to Mr Evil for these files.
Kernel: Dorimanx 7.2 HWA (credits to Dori please)
Framework: stock Desire X ROM as a base, heavily modified to work with CM9 sound system, heavily optimized for smoothness.
NOTE for DEVs:
I was stunned to discover that DISABLING HW acceleration makes scrolling silky-smooth in 99% of the applications. Exceptions are: Rosie, Browser and... uh... that's it, I think. So, I REVERSED the way framework enables HW acceleration. Here's how: if the application doesn't request HW acceleration, it doesn't get it by default. If it requests it (HWAcceleration=true in the manifest), it DOESN'T get it either. If hwAcceleration=false in manifest, it DOES get it. This way, I only had to modify Rosie and the Browser and set hwAcceleration=false for them to actually GET the acceleration. The other apps just denied the acceleration natively. Please be aware of this change
Sense: stock Desire X ROM. I've got permission to use MyOne ROM (see Desire X forum), it has full 3D effects enabled and runs smooth as silk on HD2 (it's pretty damn smooth even with live wallpapers!)
What should work:
Everything. I know that WiFi router doesn't work, but that's it, more or less. Video shooting works at 15FPS. Sound recording works. Voice input works. BT works.
Known problems:
It does crash from time to time. Needs more work on system files. I was planning to recompile gralloc from CM9 to use it here, but didn't have the privilege to finish that.
For EXT2 loop to work, one needs to add creation of an empty data.img file in /Data/Data folder. Make it as big as possible. Format it for Ext2. The rest will be done by init.rc
............. Well, that's it. I'll be watching this thread. Don't ask me to develop anything though, I can't do anything without a working HD2. Sorry guys and good luck to anyone who will take it from here.
Bye
Click to expand...
Click to collapse
wow, nice job!
blackphoenix50 said:
I did all these but still cant install.....tried also with twrp it gave me an error about updater binary...i searched at google and i think that the problem is the updater-script file...could someone plz check it cz i dont have the knowledge for that....
Click to expand...
Click to collapse
There are a few double brackets in there. Mike_1996 noticed a few in this thread http://forum.xda-developers.com/showthread.php?t=2694879 thanks Mike. I spotted a couple more.
https://dl.dropboxusercontent.com/u/24033707/updater-script
Not tried this yet but looking forward to it, sad news about phone though, thanks.
updater-script modified http://www.mediafire.com/download/q8wt2wlh8aaokf8/updater-script.zip
modified with notepad++
now boot fine but take a long time !
i have installed with 5/40/5 partition clk 1.5 and ext4 2100 mb.
wifi don't work for me
bluetooth also
and comcorder
http://www.mediafire.com/download/zu1sz8u4qz7vwdr/commonsense4.1.zip
an image !
philipped346 said:
updater-script modified http://www.mediafire.com/download/q8wt2wlh8aaokf8/updater-script.zip
modified with notepad++
now boot fine but take a long time !
i have installed with 5/40/5 partition clk 1.5 and ext4 2100 mb.
wifi don't work for me
bluetooth also
and comcorder
http://www.mediafire.com/download/zu1sz8u4qz7vwdr/commonsense4.1.zip
Click to expand...
Click to collapse
does the recent apps appear when you long press the home button?cz i think its an essential feature...
I would just remove menu button and assign that to recent apps. that is the modern way. (not Samsung dinosasur way )
For system crash could be kernel fault... I remember when I tested dorimanx kernel each release was never really 100% stable independently from clock frequencies.
II test this rom of dungphp with tytung kernel (thank to all) and this is the same with sense 4.1 .
wifi/3g , camera , bluetooth , sound work .
camcorder don't work and google play work with uptades but can't instal news applications.(fixed instal apk
)
it's a very smooth rom and if someone can fix this problems .
View attachment 2656090
View attachment 2656091
this the link of one s ics2ville:removed
I have installed system on nand with dataonext (initrd intégrated) 5/370/5 :silly:
I have updated Google play in new installation and now it's OK.
new link http://www.mediafire.com/download/c8ds4r7g7qd7n5e/one_s_ics.zip
zenida said:
For system crash could be kernel fault... I remember when I tested dorimanx kernel each release was never really 100% stable independently from clock frequencies.
Click to expand...
Click to collapse
Dorimanx's kernel haven't given me one single problem with this ROM.
I used it as my daily driver until my HD2 died...
zenida said:
I have installed system on nand with dataonext (initrd intégrated) 5/370/5 :silly:
I have updated Google play in new installation and now it's OK.
new link http://www.mediafire.com/download/c8ds4r7g7qd7n5e/one_s_ics.zip
Click to expand...
Click to collapse
if you're using my ROM (I couldn't figure this out from your post), and use my initrd, then you have to make your system partition as SMALL as possible. Most of system files are relocated to EXT4.
For camcorder to work, copy it from any CM9 ROM.
Sense camcorder tries to record at 30FPS, which doesn't work with this version of stagefright. CM9 camcorder records at 15FPS and works flawlessly
thelonewolf_pav said:
if you're using my ROM (I couldn't figure this out from your post), and use my initrd, then you have to make your system partition as SMALL as possible. Most of system files are relocated to EXT4.
For camcorder to work, copy it from any CM9 ROM.
Sense camcorder tries to record at 30FPS, which doesn't work with this version of stagefright. CM9 camcorder records at 15FPS and works flawlessly
Click to expand...
Click to collapse
your rom is very smooth but i can't have wifi/3g working , it's a problem
philipped346 said:
your rom is very smooth but i can't have wifi/3g working , it's a problem
Click to expand...
Click to collapse
this is really strange. I had wifi and 3g working without any problems. I use both of them daily...
are you using magldr or clk?
what's your system size?
did you look at the logcat?
I use clk 1.5 and système size 5/40/5 .
Sent from my Nexus 5 using XDA Premium 4 mobile app
philipped346 said:
I use clk 1.5 and système size 5/40/5 .
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
interesting.
can you use ADB? if yes, try to:
cd /data
chmod -R 777 data
chmod -R 777 system
let me know if that changes anything
I test tomorow now i watch football .
Sent from my Nexus 5 using XDA Premium 4 mobile app
.
.
.
sediROM - or why I created a new ROM based on the good old ("ancient") ICS
.
.
.
Long story short. The following list are my requirements to a custom ROM:
I need my phone everyday so I need to resist that it is working everyday (means rock stable).
I do NOT need the latest available Android version.
I WANT to have the other components (like Kernel etc) up to date.
I REALLY REALLY need headset profiles for my bluetooth devices (Jabra, Nokia and Plantronics)
I need root access, of course.
I want to get the best battery life possible.
GB is too old for me.
Stock ROM is "too stock" for me.
I have tried all available captivate ROMs starting from ICS over Jelly Bean to KitKat.
Android < v4.x are too old for my requirements. Several features missing and well it even LOOKS old..
Android >= v4.1 are working well with the Glide but there is 1 main killer function which is completely broken since Android 4.1: Bluetooth Headset Profiles
(The Bluetooth stack was completely re-developed in 4.1)
The version which is the best compromise of beeing fresh enough - but working like a charm is Android v4.0.4 (ICS)
The problem is.. there is no ICS based ROM out there which completely fullfill ALL my requirements.
So I thought it is time for me to create my own daily-use feature-complete and rock stable ROM for the Samsung Captivate Glide / SGH - I927..
IMO the best working and best battery saving ROM for the Glide is PACMAN ROM (used pac_i927-milestone.1.RC1.4.zip)!
The problem: the earliest version of it is based on Android 4.1 which is a No-Go for me because of Bluetooth HSP.
--> I recommend the mentioned version of PACman as your daily driver if you do NOT need BT HSP. I had it running several weeks without any problems but really great battery saving.
.. well that said I couldn't fork PACman ..
So I've downgraded to all available ICS based ROM again (which was VERY painful because of broken links to the apps because of different mount point names etc).
I have tried those all again (IcePOP, Cranium, Stock, DMans ICS, etc.) but no was "as good as" LiteROM (IMHO) - which I used several weeks before.
.. so +1 for forking LiteROM ...
The problem with LiteROM is that there are still issues and no further development is done on it.
Some of the major LiteROM issues for me (those are also the reasons why I first tried newer Android versions):
It looses the paired devices after a reboot ! (but that sounded to me like it can be fixed somehow)
The lags/waits when pressing the power button to switch the display on
Battery life is not the best
not the latest Kernel
many little things in the installer like it re-installs everything when only switching to another modem etc.
Nevertheless LiteROM is still the best base I can get (because it fits to my requirements best and is rock stable) and therefore I started in May 2014 the build of sediROM which is a fork of LiteROM v0.9.
UPDATE:
sediROM is officially available and have tons of fixes and enhancements inside. Check it out in the DEV thread:
--> http://forum.xda-developers.com/showthread.php?t=2789727
Best regards
xdajog :victory:
what kernel do you use? Stock or litekernel?
Replacing kernel is very easy.
No documentation for BT sound, I dont think anybody would fix it. I've tried to find dev to find alsa HAL ( that is for voip sound fix), and no luck, while fixing alsa much more easier then fix BT sound.
Somebody tried to port cm10, it has many issue, you can find that topic in dev forum.
The idea for sediROM is to have a very well tested setup of default settings (like which kernel, etc.) but the free choice to modify it later whenever you like it.
bubor said:
what kernel do you use? Stock or litekernel?
Click to expand...
Click to collapse
Well not 1 only ... there are 4 available atm (and more when I find them and find them good enough...) (while using LiteKernel v1.2.2 as default atm - but you have the free choice)
Stock Kernel
LiteKernel v4.0 OverClocked and without UnderVoltage
LiteKernel v1.2.2 GPU not OverClocked and with UnderVoltage
LiteKernel v1.2.2 GPU OverClocked and with UnderVoltage
I tried with the ardatdat 4.x Kernels,too but without success.
Replacing kernel is very easy.
Click to expand...
Click to collapse
Well yes and nowhere such comfortable as in sediROM You can choose one of the above within the aroma installer. The same for several Modems which coming with LiteROM already (nice for testing around).
No documentation for BT sound, I dont think anybody would fix it. I've tried to find dev to find alsa HAL ( that is for voip sound fix), and no luck, while fixing alsa much more easier then fix BT sound.
Somebody tried to port cm10, it has many issue, you can find that topic in dev forum.
Click to expand...
Click to collapse
BT sound? Do you have any issues here? For me BT sound itself is working great (using it daily in my car)?! But you talked about voip - is your problem skype related?
Regards
xdajog
xdajog said:
The idea for sediROM is to have a very well tested setup of default settings (like which kernel, etc.) but the free choice to modify it later whenever you like it.
Well not 1 only ... there are 4 available atm (and more when I find them and find them good enough...) (while using LiteKernel v1.2.2 as default atm - but you have the free choice)
Stock Kernel
LiteKernel v4.0 OverClocked and without UnderVoltage
LiteKernel v1.2.2 GPU not OverClocked and with UnderVoltage
LiteKernel v1.2.2 GPU OverClocked and with UnderVoltage
I tried with the ardatdat 4.x Kernels,too but without success.
Well yes and nowhere such comfortable as in sediROM You can choose one of the above within the aroma installer. The same for several Modems which coming with LiteROM already (nice for testing around).
BT sound? Do you have any issues here? For me BT sound itself is working great (using it daily in my car)?! But you talked about voip - is your problem skype related?
Regards
xdajog
Click to expand...
Click to collapse
would you point to sediROM? I couldnt find anything with google.
I dont know what is litekernel v4, I tought the last one was 2.x or less.
Litkernel has many power save improve, but it has many bugs too,
You have said already headset doesnt work, or does it work? I'm confused.
bubor said:
would you point to sediROM? I couldnt find anything with google.
Click to expand...
Click to collapse
It will be available soon - The first barrier was the post restriction which is ok now And now I need to find a place for uploading the 430 MB and then I will post it in the dev area..
I dont know what is litekernel v4, I tought the last one was 2.x or less.
Litkernel has many power save improve, but it has many bugs too,
Click to expand...
Click to collapse
--> http://goo.im/devs/thegreatergood/LiteKernel/ICS
You have said already headset doesnt work, or does it work? I'm confused.
Click to expand...
Click to collapse
Oh no I said Bluetooth is generally working fine in Android v4.0 and therefore in sediROM / LiteROM but not in other ROMs which are based on Android 4.1 or higher
--> The only thing which are not perfect in v4.0 (or especially in LiteROM) is that Bluetooth Pairing are lost after rebooting.
--> ... and that is fixed in sediROM
Smashing! :laugh: I have been roaming around for something like this! Bloody awesome! Let me know when you have the download link ready! I will be glad to test it, and if it is stable as stock ICS I will definitely keep it as my DD! Thanks in advance for this! If you say it is indeed a fork for LiteROM with no bugs it will be the s#$)!!! And of course a keeper. Same as you, I´ve tried almost every ROM available for our cappy, but never totally satisfied with none. :fingers-crossed: Hoping this ROM is what I have been looking for. What exactly did you fix, aside from the pairing issues? Any luck with the automatic toggles, Force close issues, deep sleep power button.... :fingers-crossed::fingers-crossed::fingers-crossed:
Man gimme more details! Freakin excited here :silly: jue jue jue jue
lasuazo said:
Smashing! :laugh: I have been roaming around for something like this! Bloody awesome! Let me know when you have the download link ready! I will be glad to test it, and if it is stable as stock ICS I will definitely keep it as my DD! Thanks in advance for this! If you say it is indeed a fork for LiteROM with no bugs it will be the s#$)!!! And of course a keeper. Same as you, I´ve tried almost every ROM available for our cappy, but never totally satisfied with none. :fingers-crossed: Hoping this ROM is what I have been looking for. What exactly did you fix, aside from the pairing issues? Any luck with the automatic toggles, Force close issues, deep sleep power button.... :fingers-crossed::fingers-crossed::fingers-crossed:
Man gimme more details! Freakin excited here :silly: jue jue jue jue
Click to expand...
Click to collapse
whooa keep calm my friend
as said I try to solve all the problems I saw in my case and that's what I fixed. If that fixes all yours.. - I don't know
The thing which sounds interesting to me is that you talk about automatic toggles and force closes.
I never seen automatic toggles and force closes but it may be because I use another Kernel. Well we will see when you have tried it .
I cannot promise it is bug free (in this early state of this ROM there is at least 1 known bug - to be honest) but I may can help to fix things..
Rest and details coming soon... :angel:
I'd definitely be interested in testing your ROM. Your idea is more or less what I wanted for my i927. Hope to be able to try it soon.
xdajog quick question mate, which Kernel have you been using so far? Stock Kernel, Litekernel (version)?
I remember lite kernel causes battery drain in ics
Sent from my SGH-I927 using XDA Premium 4 mobile app
Androide3 said:
I remember lite kernel causes battery drain in ics
Sent from my SGH-I927 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Exactly, that is why I would like to know which kernel would be recommended Never tried liteRoM with stock kernel
Will be fun to test out. I mostly stick to CM11 but I like to try out others often.
lasuazo said:
xdajog quick question mate, which Kernel have you been using so far? Stock Kernel, Litekernel (version)?
Click to expand...
Click to collapse
Androide3 said:
I remember lite kernel causes battery drain in ics
Click to expand...
Click to collapse
Well that point is not totally fixed yet. I'm currently using Litekernel 1.2.2 in the not-overclocked version but also played around with the others - even Stock of course. That said I cannot say that I've found a perfect kernel (grakernel may the one but it is for JB and higher only ) and still testing others.
So the short answer is that there are not such differences between them when it comes to battery drain (see my post in the dev because that's one of the open points yet)
... and only to ensure that we have all the same understanding: sediROM is my experiment to go to / to get / to become the perfect stable but actual ROM for the Glide. It is "on it's way" you now
For becoming that I need feedback of course and I believe there will be many things I may not seen/use like you do so don't expect something "perfect"
xdajog said:
It will be available soon - The first barrier was the post restriction which is ok now And now I need to find a place for uploading the 430 MB and then I will post it in the dev area..
--> http://goo.im/devs/thegreatergood/LiteKernel/ICS
Click to expand...
Click to collapse
You are really miss the point.
4.0 means android version not kernel version.
The litekernel package includes a boot image, that boot.img include kernel,ramdisk.
Ramdisk is the root on your android. Litekernel has some ramdisk modification too ( https://github.com/thegreatergood/LiteKernel---Glide/tree/master/Build4.2/ramdisk/sbin/ext https://github.com/thegreatergood/L...ster/Build4.2/ramdisk/sbin/LiteKernel_Manager )
Grakernel should work with any rom, it doesnt change ramdisk, just replace kernel and install modules to /system/lib/modules. I think modules in you rom is in /lib/modules on ramdisk, so you need to change my install script to modify ramdisk.
bubor said:
4.0 means android version not kernel version.
Click to expand...
Click to collapse
oh I'm quite new in that and a little disappointed now :crying: Well kernel v1.x is not for Android 1.x so .. in a perfect world the version naming would be everytime the same.. so everyone would know what it means... So I it may be the same as one of the 1.x LiteKernels available.
Grakernel should work with any rom, it doesnt change ramdisk, just replace kernel and install modules to /system/lib/modules. I think modules in you rom is in /lib/modules on ramdisk, so you need to change my install script to modify ramdisk.
Click to expand...
Click to collapse
Hm so you say replacing the kernel, adding the modules and it should work?
I've tried that already but without success (booting but display keeps black with some green pixels ..)
As I can see in your link the Litekernel mods are note relevant for functioning or am I wrong? They seem to do some power saving stuff nothing else?
xdajog said:
oh I'm quite new in that and a little disappointed now :crying: Well kernel v1.x is not for Android 1.x so .. in a perfect world the version naming would be everytime the same.. so everyone would know what it means... So I it may be the same as one of the 1.x LiteKernels available.
Hm so you say replacing the kernel, adding the modules and it should work?
I've tried that already but without success (booting but display keeps black with some green pixels ..)
As I can see in your link the Litekernel mods are note relevant for functioning or am I wrong? They seem to do some power saving stuff nothing else?
Click to expand...
Click to collapse
Litekernel has 2 version string, one from the build version and one from android version. Litekernel has some power save codes, it cases that deep sleep issue IMHO.
Did you download kernel from i9103 forum or mine from http://dualhoki.vim.hu/bubor/dev/grakernel/ ? Sound like you have i9103 version.
bubor said:
Did you download kernel from i9103 forum or mine from http://dualhoki.vim.hu/bubor/dev/grakernel/ ? Sound like you have i9103 version.
Click to expand...
Click to collapse
it was yours (1.4.3) - but I will re-test it again to be sure..
I want to give a try
i am very very very interrested in your ROM!
The BT-Headset function is very important for me, because for my car hifi handsfree bluetooth mode.
Battery Life
Since we are on the topic of battery life... does KitKat have the best battery life, or should I be using something else?