Well this thread basically contains all beta builds of ROM ports which everyone maybe working on for everyone to basically test and give feedback on before they become official releases i'll be holding the first post for all my ports
hopefully all the other porters take the first few posts and reserve em for their test builds
firstly i found a 2.1 ROM from cdma forums which is known as RegaWMOD
i got fond of the features so i thought i'll make a quick port of it
i have no clue if its running at all since i havent flashed it myself
hoping one of the flash junkies could test it n see if its working
RegaWMOD 2.1update-1 ROM
flash only if ur willing to test and give me feedback on it!
the second ROM i made was the TeamHeroc build of cm7 which very similair to decked up for life but untested.....it is AOSP GB as decked........i havent applied Gapps package so plz REMEMBER TO FLASH GAPPS WHEN TRYING THIS ROM!
Link to TeamHEROC 22OCT
TeamHeroC build
DietGB from the Sapphire forums
GB aosp ROM same as decked and Teamheroc but only ported from the sapphire forums....its a test build again n no gapps included jus remember to install gapps after installing the ROm
Diet GB!---DONT FLASH I HAVENT FINISHED THIS YET MADE A FEW MISTAKES IN THIS BUILD!
AOSPC MOD based on the aospCMOD from the cdma
forumsLink to original thread!
This is by far the lightest gingerbread rom i came across so far,ROM size is 45.1MB which is like WTF!!!
anyway it is by far one of most stable ports so far n i compare it to decked wit respect to speed and stability......
u will find it is based on gingerbread 2.3.4 sources and very smooth as a daily....
Link to download
as always i look forward to feedback!
based on your feedback i'm hoping to pursue a future in these ROMs and get em to more stable states!
PLZ REMEMBER THESE ARE FOR TESTING ONLY AND NOT OFFICIAL RELEASES!
downloading, trying the RegaWMOD 2.1update-1 ROM
Did you do anything special to make the TeamHeroC port working? I compiled it from source but I can't seem to get it booting.
From logcat:
Code:
I/Netd ( 558): Netd 1.0 starting
E/Netd ( 558): Unable to start DnsProxyListener (No such file or directory)
E/SocketListener( 558): Obtaining file descriptor socket 'dnsproxyd' failed: No such file or directory
E/NetdConnector( 128): Communications error
E/NetdConnector( 128): java.io.IOException: No such file or directory
E/NetdConnector( 128): at android.net.LocalSocketImpl.connectLocal(Native Method)
E/NetdConnector( 128): at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:238)
E/NetdConnector( 128): at android.net.LocalSocket.connect(LocalSocket.java:98)
E/NetdConnector( 128): at com.android.server.NativeDaemonConnector.listenToSocket(NativeDaemonConnector.java:99)
E/NetdConnector( 128): at com.android.server.NativeDaemonConnector.run(NativeDaemonConnector.java:83)
E/NetdConnector( 128): at java.lang.Thread.run(Thread.java:1019)
E/NetdConnector( 128): Error in NativeDaemonConnector
E/NetdConnector( 128): java.io.IOException: No such file or directory
E/NetdConnector( 128): at android.net.LocalSocketImpl.connectLocal(Native Method)
E/NetdConnector( 128): at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:238)
E/NetdConnector( 128): at android.net.LocalSocket.connect(LocalSocket.java:98)
E/NetdConnector( 128): at com.android.server.NativeDaemonConnector.listenToSocket(NativeDaemonConnector.java:99)
E/NetdConnector( 128): at com.android.server.NativeDaemonConnector.run(NativeDaemonConnector.java:83)
E/NetdConnector( 128): at java.lang.Thread.run(Thread.java:1019)
Maybe the latest sources are broken...
Will try your port!
Did you do anything special to make the TeamHeroC port working? I compiled it from source but I can't seem to get it booting.
From logcat:
I/Netd ( 558): Netd 1.0 starting
E/Netd ( 558): Unable to start DnsProxyListener (No such file or directory)
E/SocketListener( 558): Obtaining file descriptor socket 'dnsproxyd' failed: No such file or directory
E/NetdConnector( 128): Communications error
E/NetdConnector( 128): java.io.IOException: No such file or directory
E/NetdConnector( 128): at android.net.LocalSocketImpl.connectLocal(Native Method)
E/NetdConnector( 128): at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:238)
E/NetdConnector( 128): at android.net.LocalSocket.connect(LocalSocket.java:98)
E/NetdConnector( 128): at com.android.server.NativeDaemonConnector.listenToSocket(NativeDaemonConnector.java:99)
E/NetdConnector( 128): at com.android.server.NativeDaemonConnector.run(NativeDaemonConnector.java:83)
E/NetdConnector( 128): at java.lang.Thread.run(Thread.java:1019)
E/NetdConnector( 128): Error in NativeDaemonConnector
E/NetdConnector( 128): java.io.IOException: No such file or directory
E/NetdConnector( 128): at android.net.LocalSocketImpl.connectLocal(Native Method)
E/NetdConnector( 128): at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:238)
E/NetdConnector( 128): at android.net.LocalSocket.connect(LocalSocket.java:98)
E/NetdConnector( 128): at com.android.server.NativeDaemonConnector.listenToSocket(NativeDaemonConnector.java:99)
E/NetdConnector( 128): at com.android.server.NativeDaemonConnector.run(NativeDaemonConnector.java:83)
E/NetdConnector( 128): at java.lang.Thread.run(Thread.java:1019)
Maybe the latest sources are broken...
Will try your port!
Click to expand...
Click to collapse
Lol no sources aren't broken its a cdma Rom remember? U jus have to change the netd file in system/bin wit one of our Roms,n remember all radio related files have to b changed
Sent from my HTC Hero using xda premium
bharat_goku said:
Lol no sources aren't broken its a cdma Rom remember? U jus have to change the netd file in system/bin wit one of our Roms,n remember all radio related files have to b changed
Sent from my HTC Hero using xda premium
Click to expand...
Click to collapse
Ahh, something must be wrong in my vendor tree that makes it compile all those binaries for CDMA...
Testing RegaWMOD 2.1update-1 ROM
After installing RegaWMOD 2.1update-1 ROM and I'm really surprised.
I've tried for about 3 hours without any FC
almost everything works.
Camera: ok
Video: ok
Zoom in camera and video: ok
WIFI: ok
GPS: ok
USB network sharing: ok
WIFI Tether: ok
Led Notifications: ok
Language:Only English
Little bugs
APN: was empty .. but it works after inserting it manually...
I've only been able to authenticate on facebook after updating it with the version of the market
This is the result of Antutu-Benchmark
RAM: 68
CUP integer: 151
Float-point CPU: 13
2D Graphics: 301
3D Graphics: 316
Database IO: 45
Total Score: 1067
CPU Frequency 518
jkballero said:
After installing RegaWMOD 2.1update-1 ROM and I'm really surprised.
I've tried for about 3 hours without any FC
almost everything works.
Camera: ok
Video: ok
Zoom in camera and video: ok
WIFI: ok
GPS: ok
USB network sharing: ok
WIFI Tether: ok
Led Notifications: ok
Language:Only English
Little bugs
APN: was empty .. but it works after inserting it manually...
I've only been able to authenticate on facebook after updating it with the version of the market
This is the result of Antutu-Benchmark
RAM: 68
CUP integer: 151
Float-point CPU: 13
2D Graphics: 301
3D Graphics: 316
Database IO: 45
Total Score: 1067
CPU Frequency 518
Click to expand...
Click to collapse
Hmm I guess they r pretty minor bugs any more reviews on this build?
Sent from my Hero using xda premium
Installed RegawMod rom.
At first it was pretty slow and laggy. I kept getting a FC stating OMADM was not working..... seems to have stopped after setting up.Seems to speed up a bit after 20 mins use. I have also clocked from the 518 up to my usual 652 and it made a big difference.
Wifi works, Camcorder and camera work. Market is old but works. No problems installing anything. Felt very much like my original stock 2.1..... I didnt keep that for long.
I would suggest Rose v* feels faster and definitely looks a lot better.
Just installed Endomondo which has been an issue recently for me. No problem from the market and it quickly got a good GPS lock.
I cant really comment on tethering as I dont ever use it.
USB links to my Win7 laptop quickly. Actually... all feels pretty quick now..... but for me no where near quick enough to warrant a return from a well polished GB rom.
---------- Post added at 11:17 PM ---------- Previous post was at 11:16 PM ----------
OK. Installed TeamHeroC build using the 20110613 gapps
All feels very familiar as I use Decked Up For Life as my daily rom.
Installed with no issues, personalised ok, No problems at all with apps.
CPU runs from the box at 576 so I set to 652 as usual. Benefits from Fly13 kernel so Smartass V2 is my option.
Market is old version from this gapps but found and installed apps quickly.
Wifi set up quickly, GPS got an instant fix with endomondo app.
USB links to my Win7 laptop quickly.
All in all.... this feels the same as all the decked roms.
Not quite as fast perhaps but I'm comparing it to my daily use which is tweaked a lot.
Good rom
Well I am gonna check out this RegaqMOD one. And see what I can do with it
---------- Post added at 01:03 AM ---------- Previous post was at 12:33 AM ----------
Ok well I ofc changed the package and removed all the Sprint stuff that well is useless for me. and I am booting it now.
Changes I made so far
-FlyKernel 13 in it as default
-Superuser 3.0.5 (or 6 XD )
-Other boot animation (Not really a Geregirl
-Some small build.prob edits
-Added Maps. The latest. From the heroine topic. Wonder how that one works.
-Added very few ringtones
-New market and removed marketupdater.
That was about it, I did not even remove social crap. And I even hate that.
And I am suprised it is booting. The way I did it was well messy XD
Ok ended in bootloop XD
Now on Try 2
---------- Post added at 01:24 AM ---------- Previous post was at 01:03 AM ----------
Ok it is booted. Gonna continue on it tomorow.
Booted. the theme looks weird. it has 1.5 android aspects and some other espresso parts, Don't know if I really like that but then agian I can easely install the normal theme from the reg topic but I will see what I will do with this tomorow. No FC's and stuff so far. its faster then Kimera. And well its nice XD
Lirasina said:
Well I am gonna check out this RegaqMOD one. And see what I can do with it
---------- Post added at 01:03 AM ---------- Previous post was at 12:33 AM ----------
Ok well I ofc changed the package and removed all the Sprint stuff that well is useless for me. and I am booting it now.
Changes I made so far
-FlyKernel 13 in it as default
-Superuser 3.0.5 (or 6 XD )
-Other boot animation (Not really a Geregirl
-Some small build.prob edits
-Added Maps. The latest. From the heroine topic. Wonder how that one works.
-Added very few ringtones
-New market and removed marketupdater.
That was about it, I did not even remove social crap. And I even hate that.
And I am suprised it is booting. The way I did it was well messy XD
Ok ended in bootloop XD
Now on Try 2
---------- Post added at 01:24 AM ---------- Previous post was at 01:03 AM ----------
Ok it is booted. Gonna continue on it tomorow.
Booted. the theme looks weird. it has 1.5 android aspects and some other espresso parts, Don't know if I really like that but then agian I can easely install the normal theme from the reg topic but I will see what I will do with this tomorow. No FC's and stuff so far. its faster then Kimera. And well its nice XD
Click to expand...
Click to collapse
Faster than kimera? xD
Sent from my Hero using xda premium
bharat_goku said:
Faster than kimera? xD
Sent from my Hero using xda premium
Click to expand...
Click to collapse
Yes.
But one problem XD When I want to dial a number it smashes a 1 in front of it... And me no like that.. XD
Check call settings n disable home dialing ,should do the trick,how's ur rom running otherwise???any chance of a release?
Sent from my Hero using xda premium
bharat_goku said:
Check call settings n disable home dialing ,should do the trick,how's ur rom running otherwise???any chance of a release?
Sent from my Hero using xda premium
Click to expand...
Click to collapse
Well I could release it. But then again. It is almost like all the other sense roms. And Heroine beats it head on. So if you like a fast 2.1 rom. Go for that one XD I could release a basic theme for it. so it looks a little like this one. Not that it will look 100% the same cuss that one is Odexed.
But yea I can release one. If people like that XD
Just asked I won't use it though
M happy wit my decked build or rose fr sense
I just thought this is a complete 2.1package n ppl might like it,ur choice anyhow
Sent from my Hero using xda premium
bharat_goku said:
Just asked I won't use it though
M happy wit my decked build or rose fr sense
I just thought this is a complete 2.1package n ppl might like it,ur choice anyhow
Sent from my Hero using xda premium
Click to expand...
Click to collapse
The reason why it is so fast. cuss lots of HTC stuff aint in it. So that is a minus. It was a nice test but for my taste it is not worth it to post it up I am on Heroine now and I am happy with it for now. Need a working phone for the next couple of days
@Bharat_Goku, just a suggestion. Maybe it wouldn't be bad if you tried to port some froyo edition from CDMA forum. I mean, if GB is lot faster than current ports from GSM forum then froyo could be blazingly fast . Of course if you got time
Cheers
I have been looking at the difference from CDMA roms and GSM. And well I think 99% is placebo effect why people think it is faster. If someone says. its faster :O well yea noo XD I ran a GB CM7 nightly and well it ran at the same speed as Decked. and well SFM rans a little faster then Rose. mostly cuss Rose has more crap in it (no pun intended). Speedmachine is the fastest Froyo rom we got for the Hero and faster then that is like not possible in my eyes.
Lirasina said:
I have been looking at the difference from CDMA roms and GSM. And well I think 99% is placebo effect why people think it is faster. If someone says. its faster :O well yea noo XD I ran a GB CM7 nightly and well it ran at the same speed as Decked. and well SFM rans a little faster then Rose. mostly cuss Rose has more crap in it (no pun intended). Speedmachine is the fastest Froyo rom we got for the Hero and faster then that is like not possible in my eyes.
Click to expand...
Click to collapse
different opinions from different people I guess. from my personal experience on my phone with my style of usage:
- floyo 1.2 is fastest froyo rom, speedmachine isn't all THAT fast but is a very nice rom all the same.
- cm7 is noticeably slower than decked gb, for example. I tried ele's "custom" gb rom last week - it wasn't any where as quick and responsive as decked, in fact SFM is faster than it when running launcher pro with the same config in each rom (yes sfm is sense but I run LP on it and it's super fast).
but besides that I definitely do agree in placebo effect - it's happened to us all at times. it's human nature. but for some reason cdma roms have long since solved the cm slowdowns in froyo and gb and the gb responsiveness issues that otherwise plagued the gsm developed roms.
Keep in mind it isn't really cdma developed roms that are faster than gsm.
It's roms that were developed by super experienced developers or teams and released for several different models of phones. For example, sfm is super fast and it was developed by a really experienced guy who devs for several platforms (or at least for his own platform and then ports it to several other platforms and tries to support them), not just the hero. so it's no surprise that it's such a solid rom. and most other gb sense roms use some of SFM's code apparently.
Same with roms like decked... I don't believe decked is based on an original cdma hero rom. I think it's based upon a gb aosp-style rom (with a few cm pieces included) that was made for several phones. So again, with a team like that behind the rom there's no surprise that they can get further than we can here with single solitary yet very hard working and clever people like erasmux, elelinux, jieehd, Riemer, etc and of course our Lira.
I dont buy fully into the placebo effect.
There is a definite difference from one rom to another. Switching between rom backups to run them for a while only re-afirms to me that each rom has its characteristics, good and bad.
On top of that, each one of us will use different apps for clocks, I use a lot of widgets over 7 screens, live weather, emails, etc etc and and A.N Other will only have 3 home screens with a few shortcuts and an analogue clock.
Other sociable people will have friendstraem running all day with Twatter n all the other kak..... Then there's gamers (who have no friends)
I setup every rom the same.... (sense roms differently obviously) so I can see them operate on a level playing field.
What I'm saying I suppose is that in answer to peoples asking "Is Rom X faster than Rom Y............ How does this compare to that.....?".... Install it..... set it up and YOU tell US if its faster for you.
Related
This thread is primarily for ROM developers. So please chime in only if you have something development oriented to add. I suspect many of us are looking to port the new Sensation Sense 3.0 leak over to the DZ/G2. So I figured it would make sense to start a thread to discuss what our findings and collaborate on getting a port working.
I just started looking at the leak myself but have a few initial thoughts. This is obviously Gingerbread and the only real GB sense kernel comes from the 2.30 leak. I suspect that's the kernel we're going to want to use. Next, the system image is almost ~500MB and is already deodexed. We're going to need to slim it down by ~120MB or so to fit on the G2 partition (which is smaller than the DZ).
If you're a developer and want a fast mirror of the leak, PM me.
somehow i overlooked this partition size, anyways iv slimed it down to 238mb compressed. will see how it goes.
trying to port qHD sense ui to wvga? good luck with that..
shenshang said:
trying to port qHD sense ui to wvga? good luck with that..
Click to expand...
Click to collapse
Seriously?...
shenshang said:
trying to port qHD sense ui to wvga? good luck with that..
Click to expand...
Click to collapse
As long as HTC didn't hard code anything in the frameworks, you should be able to decompile the framework files, resize the HDPI files to the correct size for G2/Glacier/Ace screen size and repack them back into the framework... Lots of work but not impossible...
What's hard are the kernel and libraries.... At least G2, you guys have a true GB (2.6.35 kernel) to start with, then you need to somehow find libs that would play nicely with 3.0 Sense Framework... This is might be much harder than just the graphics. From what was presented, HTC has modified/rewrote quite a bit of framework for 3.0.... So finding libraries (even from Sense 2.1 ROMs) to work with 3.0 will be a major challenge....
i see no indication that this rom is only for qhd phones, checking the htc frameworks i saw hdpi folder, so that mean this rom must support res of 800x480
for some reason i cant get logcat working.
siulmagic said:
for some reason i cant get logcat working.
Click to expand...
Click to collapse
That's a function of kernel/ramdisk. Which of those are you using?
rmk40 said:
That's a function of kernel/ramdisk. Which of those are you using?
Click to expand...
Click to collapse
i tried the kernel from the official leak, and a cm7 one witch i changed the bootclasspath.
Well, here's where I'm at now. After pushing the entire Sensation ROM to system, I've replaced the following libs with those from the GB leak:
libandroid_runtime.so
libaudio.so
libaudioalsa.so
libaudioeffect_jni.so
libaudioflinger.so
libaudiopolicy.so
libhtc_acoustic.so
libhtc_ril.so
libreference-ril.so
libril.so
libsurfaceflinger.so
libsurfaceflinger_client.so
Replaced bins:
app_process
bluetoothd
rild
rmt_storage
sound7x30
surfaceflinger
Entire /system/etc/firmware directory replaced with GB leak.
All /system/etc/*.csv replaced with GB leak.
And here are the errors I'm seeing on startup: http://pastebin.com/YR5UVNbB.
E/JNIHelp ( 2854): RegisterNatives failed for 'android/server/BluetoothService'
E/AndroidRuntime( 2854): Unable to register all android natives
E/HTC Acoustic( 2856): ioctl ACOUSTIC_UPDATE_ADIE failed -1
E/HTC Acoustic( 2856): ioctl ACOUSTIC_UPDATE_ADIE failed -1
E/HTC Acoustic( 2856): ioctl ACOUSTIC_UPDATE_ADIE failed -1
E/HTC Acoustic( 2856): Cannot open audience_2051 device (-1)
E/AudioHardwareMSM7X30( 2856): set_tpa2051_parameters fail
E/AudioHardwareMSM7X30( 2856): set_aic3254_parameters failed
E/AudioPolicyManagerBase( 2856): mSupportBacMic = 0
If anyone is further than I am, I'd be interested to hear what you've done.
rmk40 said:
Well, here's where I'm at now. After pushing the entire Sensation ROM to system, I've replaced the following libs with those from the GB leak:
libandroid_runtime.so
libaudio.so
libaudioalsa.so
libaudioeffect_jni.so
libaudioflinger.so
libaudiopolicy.so
libhtc_acoustic.so
libhtc_ril.so
libreference-ril.so
libril.so
libsurfaceflinger.so
libsurfaceflinger_client.so
Replaced bins:
app_process
bluetoothd
rild
rmt_storage
sound7x30
surfaceflinger
Entire /system/etc/firmware directory replaced with GB leak.
All /system/etc/*.csv replaced with GB leak.
And here are the errors I'm seeing on startup: http://pastebin.com/YR5UVNbB.
E/JNIHelp ( 2854): RegisterNatives failed for 'android/server/BluetoothService'
E/AndroidRuntime( 2854): Unable to register all android natives
E/HTC Acoustic( 2856): ioctl ACOUSTIC_UPDATE_ADIE failed -1
E/HTC Acoustic( 2856): ioctl ACOUSTIC_UPDATE_ADIE failed -1
E/HTC Acoustic( 2856): ioctl ACOUSTIC_UPDATE_ADIE failed -1
E/HTC Acoustic( 2856): Cannot open audience_2051 device (-1)
E/AudioHardwareMSM7X30( 2856): set_tpa2051_parameters fail
E/AudioHardwareMSM7X30( 2856): set_aic3254_parameters failed
E/AudioPolicyManagerBase( 2856): mSupportBacMic = 0
If anyone is further than I am, I'd be interested to hear what you've done.
Click to expand...
Click to collapse
Not sure if it helps, but in time i was ported ROM i changed next libs:
Code:
ibwbxml_jni.so
libwebcore.so
libxml2wbxml.so
libandroid_runtime.so
libaudio.so
libaudioflinger.so
libaudiopolicy.so
libAudioTrimmer.so
libc.so
libcamera.so
libcameraservice.so
libdrm1.so
libdrm1_jni.so
libdvm.so
libEGL.so lib
flsaplayerlib.so
libgps.so
libhardware_legacy.so
libhtc_acoustic.so
libhtc_ril.so
libhtcbitmapfactory.so
libicudata.so
libmedia.so
libmedia_jni.so
libmediaplayerservice.so
libnativehelper.so
liboemcamera.so
libOlaBase.so
libOmxCore.so
libOmxH264Dec.so
libOmxMpeg4Dec.so
libopencore_author.so
libopencore_player.so
libopencore_rtsp.so
libpdfreader.so
libreference-ril.so
libril.so
libskia.so
libskiagl.so
libsoundpool.so
libsurfaceflinger.so
libui.so
libutils.so
libwbxml.so
libwbxml_jni.so
libwebcore.so
libxml2wbxml.so
It is obvious not all of libs required, but it seems u missed some libs which are important.
rmk, can u please pm me link ?
your lucky you got logcat working, mine dosent even work.
btw rmk40 did you replace the sound csv files in the etc folder?
edit : nvm you did
siulmagic said:
your lucky you got logcat working, mine dosent even work.
Click to expand...
Click to collapse
Have you tried using my ramdisk/kernel from the 2.30 leak rom?
http://pastebin.com/GDVTuSwi thats how far my brother rafyvitto has gotten it, on his mytouch 4g, still not booting =/
rmk40 said:
Have you tried using my ramdisk/kernel from the 2.30 leak rom?
Click to expand...
Click to collapse
yea , it still does not work, it might be my update script? can you upload yours?
siulmagic said:
yea , it still does not work, it might be my update script? can you upload yours?
Click to expand...
Click to collapse
I've actually been doing all my work without flashing anything. Just manually pushing files onto /system and /data. Pushed the entire thing to /system with the exception of app, which is sitting in /data/system.app. There's a symlink from /system/app -> /data/system.app, just to make it all fit. I think the key is to make sure the permissions are correct in /system/bin.
Have you tried the same process I used to get to the state I'm at?
rmk40 said:
I've actually been doing all my work without flashing anything. Just manually pushing files onto /system and /data. Pushed the entire thing to /system with the exception of app, which is sitting in /data/system.app. There's a symlink from /system/app -> /data/system.app, just to make it all fit. I think the key is to make sure the permissions are correct in /system/bin.
Have you tried the same process I used to get to the state I'm at?
Click to expand...
Click to collapse
it dosent really matter if you push the libs or flash them, i just cant get logcat too work it complains the sh binary is not present when it actually is. and i stripped the rom off a couple of things like livewallpapers, the weather video previews etc etc, iv fitted the whole system folder on the g2 nand just fine.
siulmagic said:
it dosent really matter if you push the libs or flash them, i just cant get logcat too work it complains the sh binary is not present when it actually is. and i stripped the rom off a couple of things like livewallpapers, the weather video previews etc etc, iv fitted the whole system folder on the g2 nand just fine.
Click to expand...
Click to collapse
No, of course, I understand that it doesn't matter whether you push or flash. Does adb shell work? Wondering if you're failing to mount /system entirely.
This is a port of the HTC Salsa Europe Gingerbread Sense release with the libs taken from SebastianFM port to the magic.
This version should fix the gfx crashes in map applications, games, etc. Thanks to Sebastian for the fixed libs
Known issues:
Hardare issues:
- no notifications lights
- no usb mount
- BT (did my best to get BT working but this ROM really hates the Heros BT )
- hotspot
- Camcorder at "High (640x480) quality" is not supported by the Hero. It does work at "Low (320x240)".
Generally I feel this ROM is not 100% stable. It might be stable enough for some to use as a daily ROM, not for me.
Downloads:
HeroSalsa-1.0.zip (Android RTK)
HeroSalsa-1.0.zip (Multiupload)
Imporant: Full wipe is necessary!
Changelog:
version 1.0
Original build from the SFM 1.1 release, with following additions:
* More complete set of apps taken from the original HTC release
* FlyKernel 12a (camera is not 100% stable on LV)
* Some hardware fixes: Wifi, Sensors, sdcard
* USB fix for 2.6.29 kernels (added in version 1.0)
* Full app2SD
* Superuser and busybox (fixed in version 1.0)
* RTL fixes for hebrew (sorry the new version which supports Arabic is not ready yet for GB)
* Teeter (how else can you know the G-sensor works )
* reboot menu
Credits:
Well SebastianFM obviously, he did most of the work on this port
Fix for superuser is from here, credits to rmk
Reserved (for what?!)
Wow really cool ^^
might try this out tonight
did you put in flykernel already?
and... FIRST POST
more details about this ROM please,
Flash it and find out yourself....
thanx, downloading now
Is it just me or is there no Facebook for HTC Sense?
Hi Eras
Thanks for all your hard work on porting Sense roms for us.
I just flashed this ROM, and I see that its only Asian/English/ language.
I cant USB-mount either as you wrote. Maps is not working - same behaviour as in WildHero1.1.
I will keep testing - first impression is that it looks close to WildHero1.1
Best regards,
Henrik
Another rom for our hero, amazing. will try this one later.
Eran, when I was doing this port, dmesg did report problems with USB mounting. I got a report from someone who knows more than me about this and they think it's to do with the fact that the Salsa ROM is compiled on a kernel > .29. There was a greater in-depth explanation but I don't remember it too well . Thing is I tried a .35 kernel and got no issues with USB mounting although the ROM seemed to hang when booting, ie. when preloading assets it slowed right down after loading sim-verification and then stopped. I'm not sure if it would have continued had I left it longer becuase i only left 7 or 8 minutes, but to me thats too long to load basic assets.
JieeHD said:
(...)Thing is I tried a .35 kernel and got no issues with USB mounting although the ROM seemed to hang when booting, ie. when preloading assets it slowed right down after loading sim-verification(...)
Click to expand...
Click to collapse
I'm currently investigating this one aye. On "normal" roms it restarts all apps though, maybe it is the lack of memory on this one?
riemervdzee said:
I'm currently investigating this one aye. On "normal" roms it restarts all apps though, maybe it is the lack of memory on this one?
Click to expand...
Click to collapse
Not sure, although /system in this ROM is massive, well over 170mb space that the Hero has, so unless I've caused problems moving some things to /data/app. dmesg didn't report anything strange when this was happening though, the only indication I got that something was wrong was from logcat.
JieeHD said:
Not sure, although /system in this ROM is massive, well over 170mb space that the Hero has, so unless I've caused problems moving some things to /data/app. dmesg didn't report anything strange when this was happening though, the only indication I got that something was wrong was from logcat.
Click to expand...
Click to collapse
list of things you can remove..
- Mirror (uses front facecamera which we don't have)
- Plurk.. (don't even know what it is, and if someone uses it)
- Teeter (as it can be installed from HTC Hub)
that should clear some MB's =)
JieeHD said:
Not sure, although /system in this ROM is massive, well over 170mb space that the Hero has, so unless I've caused problems moving some things to /data/app. dmesg didn't report anything strange when this was happening though, the only indication I got that something was wrong was from logcat.
Click to expand...
Click to collapse
Wrong. I do not release ROMs which do not fit the hero's system partition:
Code:
/dev/block/mtdblock3 170.0M 167.8M 2.2M 99% /system
Being 99% full is just fine (I have seen perfectly working ROMs with more than 167.8M). In any case, since its read only, any space left free on the system partition is a waste of your internal memory. What Riemer was talking about was free RAM....
I tried to leave as much of the weird new apps on this ROM intact so we can check what they are. You are right about the mirror app, it crashes since we don't have a front camera. Apparently Plurk is some kind of social network, never heard of it before either, but apparently its common enough for HTC to write special app for it.
The Salsa have 320x480 resolution and 800 Mhz processor. Its going to be the future.
You think, it'll will work later well?
All development on this ROM is now here:
http://forum.xda-developers.com/showthread.php?p=14017604#post14017604
Basically, I just don't see the point in supporting both this and the WildHero ROM. Even if I wanted to, I don't think I have the time. For now I think I will concentrate on the WildHero WWE release and/or WildLatte. Anyone who thinks they have something to contribute to any of these ROMs, please feel free to use my work as a base and post your contribution independently. As always proper credits will be nice.
nice ROM... good work..
Posted updated version, based on SFM 1.1 libs and the apps from the official European release. This should hopefully fix gfx crashes in games and map apps.
For some reason both notification lights (also LED) and the USB mount are now broken. Like stated before, I do not have the time to properly maintain this ROM, I am aiming this release mainly at developers JieeHD so that they can take what they think is appropriate for their ROMs. I will concentrate on the WildHero ROM and my other projects.
Thanks eran
Sent from my HTC Hero using XDA App
----------
Code:
25/1/13
N3
Bluetooth Updated
Grab the new kernel for sdcard fix
-------------------------------------
23/1/13
N2 (NIGHTLY2)
WIFI fixed
Audio Fixed
-------------------------------------
23/1/13
2nd build
sd fixed up
-------------------------------------
23/1/13
1st build everything is fuked
Any Off topic will be met with me raging at you and getting your post deleted
Ok this section is the F&Q so if anyone ask's me a question that's been listed here, you'll be ignored.
Q:I cant find all my stuff on the sdcard, where is it?
A: It's in the 0 folder, it's advisable to move all of your stuff to the 0 folder before flashing.
Q:Where's developer options gone?
A: Go to about phone and bash Build Number until it says "you are now a developer"
Q:I flashed your rom and all of my sdcard stuff is gone..I HATE YOU!
A: Did you move it to 0 before hand?.
Q:DO i need to full wipe?
A: YES!
Q. OMG this rom sucks
A. Not my problem
Q. X Rom has X feature, can you put it in?
A. No
sdcard is working, i'll put it in the next build, i'll throw builds out everyday as "nightlies" also guys
LOGCATS OR THE BUG DOES NOT EXIST
Sdcard working build uploaded
Just popping in here to say that it is good to have you although you don't have the device and I am up for any testing if you want any.
Also I will test this soon!
Good Luck with this....,
Shubham.
Re: [ROM] WIP EverVolv 4.2 PrimoU
Lloir said:
sdcard is working, i'll put it in the next build, i'll throw builds out everyday as "nightlies" also guys
LOGCATS OR THE BUG DOES NOT EXIST
Click to expand...
Click to collapse
I never get tired of hearing that
Sent from my One V using xda premium
First of all, there are some issues that stops this rom to be a daily driver. I only tested for a small amount of time due to the fact that i was in a rush to go to work. What I've tested, I guess I covered almost all important parts. There is one issue I couldn't make a logcat for it because I was running out of time but that should be easy to do - the sound.
Second of all, although this is 4.2, who said that 4.2 will not run well on our small device - he is wrong. This boy is capable of running 4.2 with stock speeds - 245 mhz min, 1024 mhz max - at a respectable smoothness. I was amazed how well it moves considering that this is the very first build. There are things that work and others that don't. The largest issue of all is the sound. Why? Because, leaving apart the fact that you can't hear UI sounds, media sounds, the biggest of all is that - you can't hear anything when you call someone and the other person doesn't hear you back as well. GSM is working, celullar data is working well - tested with the stock browser.
Here are a few things that doesn't work so far:
Menu - Manage apps - Slide to SD Card apps AND Settings - Apps are crashing both at the same location - SD Card apps.
Here is a logcat for Menu - manage apps - Slide to SDcard:
View attachment logcat.txt
Here is a logcat for Settings - Apps
View attachment settingsappscrash.txt
As we managed to do 4.1 in the past and even 4.0, we encountered issues with WIFI and bluetooth - Not turning ON. This issue occurs again in this build - It SHOULD be an easy fix to do, i guess.
Here is the logcat for WIFI:
View attachment wifinotworking.txt
Code:
E/WifiHW ( 1885): Supplicant not running, cannot connect
E/WifiHW ( 1885): Supplicant not running, cannot connect
E/WifiStateMachine( 1885): Failed to setup control channel, restart supplicant
D/SoftapController( 1482): Softap fwReload - Ok
D/CommandListener( 1482): Setting iface cfg
D/CommandListener( 1482): Trying to bring down wlan0
E/WifiHW ( 1885): Unable to open connection to supplicant on "wlan0": No such file or directory
I/wpa_supplicant( 3950): Successfully initialized wpa_supplicant
E/wpa_supplicant( 3950): wlan0: Unsupported driver 'nl80211'
Here is the logcat for Bluetooth:
View attachment bluetoothnotworking.txt
As I've said, the sound doesn't work at all. I will make a logcat today, when sdk is downloading at my work place (currently downloading at 40 kb/s) if someone doesn't do it before me.
Another small and minor issue is the following behavior - Mount your SDCARD - everthing works as normal - when the sdcard is mounted, you can notice that the text for the radio button to mount the sdcard says "Mount your sdcard". This is a very minor issue and it can be fixed easily if it is only a textbox to be changed in "unmount your sdcard". (ONE TIME ISSUE)
Will continue to investigate the build today - doing some video playback and other things that i didn't tried but so far and I mean it, it works flawlessly.
LATER EDIT:
Found out a little more issues while I was going through the logcat for Wifi:
CAMERA - Doesn't work - Module couldn't be loaded:
Code:
V/CameraHolder( 3075): open camera 0
E/CameraService( 3567): Camera HAL module not loaded
E/CameraHolder( 3075): fail to connect Camera
E/CameraHolder( 3075): java.lang.RuntimeException: Fail to connect to camera service
E/CameraHolder( 3075): at android.hardware.Camera.native_setup(Native Method)
E/CameraHolder( 3075): at android.hardware.Camera.<init>(Camera.java:340)
E/CameraHolder( 3075): at android.hardware.Camera.open(Camera.java:302)
E/CameraHolder( 3075): at com.android.camera.CameraManager.cameraOpen(CameraManager.java:283)
E/CameraHolder( 3075): at com.android.camera.CameraHolder.open(CameraHolder.java:210)
E/CameraHolder( 3075): at com.android.camera.Util.openCamera(Util.java:358)
E/CameraHolder( 3075): at com.android.camera.PhotoModule$CameraStartUpThread.run(PhotoModule.java:327)
V/StateManager( 3075): startState class com.android.gallery3d.app.PhotoPage
Screenshot couldn't be saved - Something with SDcard issue - Maybe a path or a super user issue? (logcat coming soon)
Gallery could not load photos - External storage not mount error (logcat coming soon)
Trying to go to Camera from the lockscreen by sliding right - "Unfortunately, Gallery has stopped"(logcat should be the one above).
Other issues:
Lockscreen freezes while phone is connected with a usb cable to your PC (not in mount option)
SDCARD is not visible within gallery, file managers etc.
Toolbox - Interface - Tablet & DPI - Custom display density - Not sticking after a reboot
Thank you for a well done job, Lloir.
Your friend,
1ce.
Re: [ROM] WIP EverVolv 4.2 PrimoU
Really good mate...keep up the good work
Sent from my One V using xda premium
Re: [ROM] WIP EverVolv 4.2 PrimoU
Omg ice that's a very nice bug report.. I'll try to come up to your standards
Sent from my One V using xda app-developers app
Nightly\Experimental link updated grab that build and let me know what works\doesn't work
-Lloir
Kernel?
Very good job with the slim bean, lloir. Now, the JB 4.2 . It's the foot.
I'm ready to try it. But I can' t find the kernel. When I try to download, I arrive on a page with a very very long text but not on a boot.img. have I made a mistake?
Thank's a lot for all your hard work
patgou.007 said:
Very good job with the slim bean, lloir. Now, the JB 4.2 . It's the foot.
I'm ready to try it. But I can' t find the kernel. When I try to download, I arrive on a page with a very very long text but not on a boot.img. have I made a mistake?
Thank's a lot for all your hard work
Click to expand...
Click to collapse
the kernel is in the OP....kind of hard to miss it.........
Guys KEEP off topic posts out of this thread, this is DEVELOPMENT
patgou.007 said:
Very good job with the slim bean, lloir. Now, the JB 4.2 . It's the foot.
I'm ready to try it. But I can' t find the kernel. When I try to download, I arrive on a page with a very very long text but not on a boot.img. have I made a mistake?
Thank's a lot for all your hard work
Click to expand...
Click to collapse
The same happened for me a couple of times. Try right clicking on the link to kernel and save linked file as...
Re: [ROM] WIP EverVolv 4.2 PrimoU
want to make a logcat about the phone dialer lagging, how to specific the logcat?
Sent from my One V using xda app-developers app
ryanlow134 said:
want to make a logcat about the phone dialer lagging, how to specific the logcat?
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
Code:
http://forum.xda-developers.com/showthread.php?t=1987232
Re: [ROM] WIP EverVolv 4.2 PrimoU
@ryanlow134:while the logcat is running,open the dialer and fiddle around.once done,save it.
Sent from my One V using xda app-developers app
N2 is up...let me know if display is refixed and if audio works
Lloir said:
N2 is up...let me know if display is refixed and if audio works
Click to expand...
Click to collapse
N2, you mean nightlies?
sorry for extreme noob question
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?