Related
MOTIVATION
Welcome in the official thread of the project. This post is made to let discover you why this project is born. We are two universitary students that want more about a new branch of th IT Area, the Embedded OS Porting. We have a particular device, the HUAWEI IDEOS U8150, so our port is in this direction.
So don't ask to us why we are porting this version of Android with this device, because this project starts for educate ourself to the porting of Android OS, in particular we are oriented to port CyanogenMod ver 9. We made research to define a good porting for this device, so all the support ,moral, technical and economic(we need more RAM and CPU frequency) is really appreciated. We are also thinking to port, after this ROM Porting, the MIUI v4.
We work to create a stable ROM that could enjoy all great people that have this device. We think that newest releases of Android could run on this kind of mid-low level devices, so we make all the possible to complete this work.
The xDEOS team
raidenfox
sebaker
INFO ON THE STATUS OF PROJECT
Official Website: Here
G+ Page (daily updates) : Here
ABOUT THE ROM
This is the status of our working ROM:
ALPHA 3 (4.0.4)
CODENAME
xDEOS_u8150-alpha3-CM9-signed.0.0-UNOFFICIAL.zip
Changelog
resized system image
removed calendar and example audio and video files
added all GAPPS
more smooth
resized system (only 96MB)
Wi-Fi finally fixed
Internal Headset works (i hope in all devices and not only U8150D)
Removed Gallery (while we fix graphics we don't insert it in)
DOWNLOAD
Here or on the official website
----------------------------------------------------------------------------------------------------
ALPHA 2 (4.0.4)
CODENAME
xDEOS-9.0.0-RC0-u8150-UNOFFICIAL-alpha2-signed
Download
Official Site
Changelog
Update to 4.0.4 Distribution
Removed annoying Red Border
Modified codename
----------------------------------------------------------------------------------------------------
ALPHA 1 (4.0.3)
CODENAME
cm_u8150-9.0.0-KANG-alpha1-signed.raidenfox
WORK
USB
MMC
Browser
Gallery (without HW Acceleration)
Overclock
Thetering
Audio
GPS
Contacts
Wi-Fi
RIL (partially solved)
SENSORS (G - Sensor)
NOT WORK
Graphics Hardware Acceleration
Camera
Bluetooth
other bugs not known..
All the details about the ROM (status of bugs in bugtracker section) is available on this site.
http://www.xdeos.eu
Sorry for my bad english
SCREENSHOT
CWM INSTALLATION
Boot in recovery mode
Flash CWM
Reboot you Phone in recovery again
HOW TO FLASH THE ROM
Select Install from zip
Select cm_8150 zip file downloaded on official site
Flash it
After flash do a wipe/cache
Clean cache
Reboot phone
You have installed xDEOS!
i already tried this cm9 it good but some time of use it started to lag
Have you tried alpha2 ? ANd have you set a little bit of overclock ?
[/COLOR]
tonystark88 said:
Have you tried alpha2 ? ANd have you set a little bit of overclock ?
Click to expand...
Click to collapse
no i tried alpha 1 from other thread i'm not tried alpha 2 now i'm downloading but can't try now because my mom use u8150 and no i't started to lag of 10 hours use
When u have time try it
Sent from my GT-S5660 using xda premium
Ported android kernel 2.6.35 from U8160. New alpha soon
Android Kernel 2.6.35
Sent from my GT-S5660 using xda premium
Hey, tried it out, works great on my T-Mobile Comet. No SIM card, so don't know how it does on the network, but yeah, it's usable, thanks for this!
Is there a way to get haptic feedback on the soft buttons?
May want to put on the first page how to install ICS gapps.
For some reason, Gapps won't work.
Hitorijanae said:
For some reason, Gapps won't work.
Click to expand...
Click to collapse
GApps fare note included yet
Sent from my GT-S5660 using xda premium
Fitchman said:
Hey, tried it out, works great on my T-Mobile Comet. No SIM card, so don't know how it does on the network, but yeah, it's usable, thanks for this!
Is there a way to get haptic feedback on the soft buttons?
May want to put on the first page how to install ICS gapps.
Click to expand...
Click to collapse
Your SIM id not recognized?
Sent from my GT-S5660 using xda premium
New site and new informations on the status of project here.
tonystark88 said:
Your SIM id not recognized?
Sent from my GT-S5660 using xda premium
Click to expand...
Click to collapse
No, I just literally had no SIM in it, so I couldn't try data.
i tried alpha 2 and it's not lag as alpha 1 good job
can you work for lg optimus me p350 cm9 i'm working on aosp ics but cm9 is good then aosp ics i tried many times to boot cm9 but always getting not bootable rom,
new alpha 3 is coming out...in upload...
Alpha 3 comes out. Changelog, download link and other news/details on the official page
cips gokhle said:
can you work for lg optimus me p350 cm9 i'm working on aosp ics but cm9 is good then aosp ics i tried many times to boot cm9 but always getting not bootable rom,
Click to expand...
Click to collapse
I don't have the device and this (xDEOS) is my first port, but we can try to do it, maybe you can cooperate with me and test releases on your device if u want.
New alpha 3 version in the head of post and on the official website. News for testers in the website.
New photo with this changelog:
resized system image
removed calendar and example audio and video files
added all GAPPS
more smooth
resized system (only 96MB)
Wi-Fi finally fixed
Internal Headset works (i hope in all devices and not only U8150D)
Removed Gallery (while we fix graphics we don't insert it in)
Gallery is not installed but you can install quickpic, a beautiful gallery
Well done boys!! Great job! But the RIL works??
These kernels are for CyanogenMod 10 - Alpha 4.
The goal of these builds is to fix the issues with phone signal, which is not properly working with the stock kernel. Nothing was changes, no extra features, no nothing.
There won't be any more "development" now that the bug is fixed.
The experimental sync bug fix, as the name says, it's a new sync bug fix I was testing. It's here because it partially fixed the missing signal issue at first, but it's not the real fix.
Downloads:
kernel-cm-10-A4-signal_fix.zip: dhiru's kernel + signal fix [0001, 0002] - (previously known as V1)
kernel-cm-10-A4-signal_fix-exp.zip: experimental sync bug fix [0003, 0004] + signal fix [0001, 0002] - (previously known as V2)
kernel-cm-10-A4-restore.zip: stock alpha 4 kernel.
Note: I forgot to change the "name" of the kernel, so you'll get [email protected]_CM9. Don't worry, it's for CM10
Even though I marked V2 as experimental build and I added it as alternative choice, it's the most downloaded version.
As I reported several time ago, mobile data is maybe less stable with it and I think it's because the PDA state is controlled with early suspend instead of the regulr suspend, as it was in the old Samsung releases. In case of problems, flash V1.
If you noticed anything, please report
Source code:
android_kernel_samsung_latona at 0e84cc4896 + patches attached, applied as indicated above.
I verified that when a stock ROM is used, GPIO 126 is normally set to 0.
UPDATE
Click to expand...
Click to collapse
If you are stuck at Samsung splash screen and you are unable to reboot in recovery (I don't know why some users are facing this issue), so you are not able to flash another kernel or restore a backup, you can try to flash one of the kernels with ODIN.
Downloads:
kernel-cm-10-A4-signal_fix-ODIN.tar: dhiru's kernel + signal fix [0001, 0002] - (previously known as V1)
kernel-cm-10-A4-signal_fix-ODIN-exp.tar: experimental sync bug fix [0003, 0004] + signal fix [0001, 0002] - (previously known as V2)
kernel-cm-10-A4-restore-ODIN.tar: stock alpha 4 kernel.
Reboot in Download mode and flash as PDA.
Kernel modules are not included in the PDA. They are not necessary if you were using dhiru's CM with no custom kernels. If you are not sure, do as follows:
Flash kernel as PDA with ODIN (assuming you are stuck at Samsung splash screen and can't reboot in recovery)
Reboot in recovery (pull the battery if nothing works and use the three-keys combo)
Flash CyanogenMod 10 zip (your data will be preserved)
Flash once again kernel as PDA with ODIN
_____
Older posts:
Update: Now I know what stock ROMs use (GPIO 126 = 0). I'll soon update the kernel.
I already wrote that this won't be a custom kernel, no extra features, overclock etc. I opened this thread simply to test a fix, that's why I opened it in the general section, even though the dev section would have been more appropriate.
I'm lazy, so read this post.
kernel V1: includes only the sec_get_param_value fix
kernel V2: includes both the first change (the reworked sync bug) and the sec_get_param_value fix
Very old post:
Click to expand...
Click to collapse
As I posted in dhiru's thread, with my kernel I catch the mobile signal faster than with the stock kernel. I don't have to wait, all I have to do is to turn off and then on the screen once.
I've recently done some changes to my kernel regarding the sync bug. So, suspecting those changes are what makes the difference, I applied the same changes to dhiru's kernel and built it.
I tried to reboot few times and there's really a difference, at least for me.
I suspect that with the stock kernel there are only issues in reporting the current intensity, because 3G and calls seem to work.
Download: (Flash from recovery)
kernel-cm-10-Alpha4-TEST.zip
kernel-cm-10-Alpha4-RESTORE.zip
Source code:
android_kernel_samsung_latona at 0e84cc4896 + patch attached + unset CONFIG_SVNET_WHITELIST
I don't know if battery life is affected, if the sync bug is really gone (no issues till now) or if there are issues with this kernel (I'm not using it. I only tested it for a few minutes). Flash at your own risk.
Don't report any bug in CM10 thread if you are using this kernel. Use the restore zip first, try to reproduce the bug and then report.
Question
Hi loSconosciuto, i have one question regard alpha 4. I have problem with signal too (as i posted in alpha 4 general thread) but i think it is beacuse my modem (LUBKPD) has been overwrite to DDLE1. Is there any posibility to create a flashable zip only to overwrite my (our, for those who live in south america and has the same problem). Sorry to ask you but i do not know what to do, cause my media storage don't get recognize and i can`t back to stock rom and no one reply my question in general, my phone is practically a stone, except for that moment when get signal (sms and calls only). Thank you!
jsp1984 said:
Hi loSconosciuto, i have one question regard alpha 4. I have problem with signal too (as i posted in alpha 4 general thread) but i think it is beacuse my modem (LUBKPD) has been overwrite to DDLE1. Is there any posibility to create a flashable zip only to overwrite my (our, for those who live in south america and has the same problem). Sorry to ask you but i do not know what to do, cause my media storage don't get recognize and i can`t back to stock rom and no one reply my question in general, my phone is practically a stone, except for that moment when get signal (sms and calls only). Thank you!
Click to expand...
Click to collapse
I could, but I don't have LUBKPD modem.
All you have to do is to take modem.bin from the PDA of your ROM (as you may know, you can open it as a normal tar), copy it in /radio overwriting the existing one and reboot. Permissions will be automatically set on reboot.
If you want, here two (different) flashable zips I made for myself. You have to replace modem.bin inside of the zip with yours and then flash.
radio-cm-XXLE4-galaxysl-signed.zip (will erase /radio and then copy the modem)
radio-cm-KPU-galaxysl-noerase-signed.zip (will simply copy the modem)
Works perfectly. Thank you dear Sir :thumbup:
Sent from my GT-N8013 using xda app-developers app
Ok, I think I almost fixed the problem. sec_get_param_value is an exported symbol defined in param.ko (yeah, brilliant...), but we don't use that module anymore in alpha4. The consequence is that the function that turns on the modem is never executed completely.
It still needs some improvements. switch_sel is never set or initialized, but at least the connection is immediately enstablished now. The problem is that I'm not sure which is the best option, so I'll wait for more opinions about it.
In the meanwhile I built two new kernels:
kernel V1: includes only the sec_get_param_value fix
kernel V2: includes both the first change (the reworked sync bug) and the sec_get_param_value fix
V2 is a little bit more "experimental".
OP updated with the new patch.
__
Maybe this is not the right place for this thread, but I opened it here because there won't be any development.
I flashed the V2 and I got the signal instantly after flashing
Sent from my GT-I9003 using xda app-developers app
Thanks man it works great for me...flashed v2 and boom it turned on
Sent from my GT-I9003 using CM10 alpha4 Tapatalk 2
It works so good thank you so much I hope you will continue your very good job
Envoyé depuis mon GT-I9003 avec Tapatalk
Its working fine till now, Thanks alot!. I just wanted to say would you please add move governers in the subsequent release
This thread should be moved to development section.
So that people are aware of the fix.
And it works perfectly, thanks to losconsiuoto
Sent from my GT-I9003 using xda premium
hi
loSconosciuto said:
I'm lazy, so read this post.
kernel V1: includes only the sec_get_param_value fix
kernel V2: includes both the first change (the reworked sync bug) and the sec_get_param_value fix
As I posted in dhiru's thread, with my kernel I catch the mobile signal faster than with the stock kernel. I don't have to wait, all I have to do is to turn off and then on the screen once.
I've recently done some changes to my kernel regarding the sync bug. So, suspecting those changes are what makes the difference, I applied the same changes to dhiru's kernel and built it.
I tried to reboot few times and there's really a difference, at least for me.
I suspect that with the stock kernel there are only issues in reporting the current intensity, because 3G and calls seem to work.
Download: (Flash from recovery)
kernel-cm-10-Alpha4-TEST.zip
kernel-cm-10-Alpha4-RESTORE.zip
Source code:
android_kernel_samsung_latona at 0e84cc4896 + patch attached + unset CONFIG_SVNET_WHITELIST
I don't know if battery life is affected, if the sync bug is really gone (no issues till now) or if there are issues with this kernel (I'm not using it. I only tested it for a few minutes). Flash at your own risk.
Don't report any bug in CM10 thread if you are using this kernel. Use the restore zip first, try to reproduce the bug and then report.
Click to expand...
Click to collapse
After i flashed with the CM10 alpha 4 the first problem i found the signla problem but thanks to your great hard work it was solved so easily and that too without any errors.
Request to Moderators Please move this thread to Developement or merge this post under the CM10 alpha 4 update
Well, flashed V2 and device is stuck at the initial Samsung screen. It won't even boot into recovery. Anybody face the same? My cousin is furious right now!
spacebar2011 said:
Well, flashed V2 and device is stuck at the initial Samsung screen. It won't even boot into recovery. Anybody face the same? My cousin is furious right now!
Click to expand...
Click to collapse
first tell me which rom were u on, and did you update to cm10 alpha 4 and followed all the instructions properly as mentioned
rahul_rocks3 said:
first tell me which rom were u on, and did you update to cm10 alpha 4 and followed all the instructions properly as mentioned
Click to expand...
Click to collapse
I wrote some of the original instructions on the i9003 forums, so procedure/method is not a problem here.
I think the issue is I flashed the v2 kernel over the ParanoidAndroid latest 2.54 Alpha4 assuming that as the base is this ROM, the kernel would work. But got a soft brick. Its all fine now, had to go through the whole KPE, LF2 process and now flashing CM10 Aplha4.
If you could just tell me if replacing the modem.bin from LF4 is enough for the signal issues or do I still need to flash the V2 kernel?
Thanks in advance!
EDIT: Flashed V2 but got a 2nd soft brick. Went through the whole process again () My signal and data are working but the indicator is greyed out.
resolved problems
I had problems relating to signal strength and storage.
Thanks and its now working perfectly.
---------- Post added at 08:04 AM ---------- Previous post was at 08:03 AM ----------
rahul_rocks3 said:
After i flashed with the CM10 alpha 4 the first problem i found the signla problem but thanks to your great hard work it was solved so easily and that too without any errors.
Request to Moderators Please move this thread to Developement or merge this post under the CM10 alpha 4 update
Click to expand...
Click to collapse
+1
Flashed V2... It's working great. Thanks.
Sent from my Nexus 7 using xda premium
Thanks works like a charm.
spacebar2011 said:
Well, flashed V2 and device is stuck at the initial Samsung screen. It won't even boot into recovery. Anybody face the same? My cousin is furious right now!
Click to expand...
Click to collapse
Spacebar! How the heck are you?
Sent from my Samsung Galaxy SL on CyanogenMod 9 !
arindammanidas said:
Spacebar! How the heck are you?
Sent from my Samsung Galaxy SL on CyanogenMod 9 !
Click to expand...
Click to collapse
I'm very well mate, you? :highfive:
Just been off the radar due to a choked studio schedule. I've been somewhat active on the One X forums though.
Cousin asked me to update his SL (passed on from me) and this happened last night. I'm not sure whether to flash the v2 kernel again as signal etc is working but the icon is all grey and it takes about 15 mins after a reboot to get signal. Don't have the time to go through the entire clean flash process all over again.
spacebar2011 said:
I'm very well mate, you? :highfive:
Just been off the radar due to a choked studio schedule. I've been somewhat active on the One X forums though.
Cousin asked me to update his SL (passed on from me) and this happened last night. I'm not sure whether to flash the v2 kernel again as signal etc is working but the icon is all grey and it takes about 15 mins after a reboot to get signal. Don't have the time to go through the entire clean flash process all over again.
Click to expand...
Click to collapse
I'm doin' good!
I'm still on CM9.... but v2 seems to work for some people including loSconosciuto himself....
Sent from my Samsung Galaxy SL on CyanogenMod 9 !
[ROM][4.0.4][29.01.13] BananaSandwich v0.2 - first smooth & fast ICS ROM (CM9 based)
Download:
http://www.mediafire.com/?e870iwf5ejptd
installation:
#1: Download and put files to sdcard
#2: Flash Recovery_Patch-ICS_banana4444.zip (phone will automatically reboot into recovery; superwipe included)
#3: Flash ROM: BananaSandwich_v0.1.zip
(#4: Flash FontPack-ICS_banana4444.zip) optional - see what this contain, if you won't use these fonts, don't flash this file
#5: Flash kernel: ezgb-2636-v1.5.3-ics_S.zip
#6: Flash boot-v1.5.9-Alpha3-CustomMTD_S.zip
#7: Reboot and wait few minutes
If there will be sth wrong with sound after first boot, reboot phone into recovery and type in cmd: adb shell fix_permissions (it won't help to ringtones)
cmtd - 120 / 3
FontPack contains:
DroidNaskh-Regular.ttf
DroidSansArmenian.ttf
DroidSansEthiopic-Regular.ttf
DroidSansFallback.ttf
DroidSansGeorgian.ttf
DroidSansHebrew-Bold.ttf
DroidSansHebrew-Regular.ttf"
DroidSansMono.ttf
DroidSansThai.ttf
Requirements:
* Radio 28.25/27.08
* SPL 0013d
* Ra-dream recovery (or cwm but you need to use cmtd)
http://www.mediafire.com/?a3ay0gxvfj9y8
Credits:
jordfaz - for great base
CyanogenMod - for base of base
PowerPlop - for helping me to solve many problems
tvall - for invaluable advice and his files
ezterry - for kernel
dsixda - for best android kitchen
Works:
Wi-Fi (fixed)
Audio (fixed)
Touchscreen
Screen rotation
Hardware acceleration
Data
Call
Apps
Backlight
Keyboard
Root
Vibration
Mobile network
SD card - fixed
Auto rotation - fixed
Physical keyboard (except shift and alt keys)
All buttons (like 'Home')
Doesn't work:
Camcorder
Bluetooth
Camera
ADB
ext
Not tested:
GPS (should work)
Compass
v0.2
SD Ext - fixed
Impressive!
Wow, 3rd ICS for G1!!! Looks amazingly fast (for ICS), how did you do it? I'm assuming it's the hw acceleration. Where's the Dalvik cache stored, that was a big problem in terms of speed for previous ICS ROMs.
I now have a G2 (Desire Z) so will be able to test this in the near future + give feedback
Youtube working?
Build-in screenshot function is working?
What ROM did you use as a base?
firstly i used your rom as a base (on video) with tvall's and jcarrz's files help, but now im working on cm9 - much faster and stabler
screenshot works, i'll check youtube later
Great to seem some more ics love! Ill have to try this out come the weekend! Thanks much!
Sent from my HTC Vision using Tapatalk 2
cm9 based rom in 2nd post, tell me guys, what you think about it
if you have ideas how to fix issues, send me pm with solution, i'll be very thankful
banana4444 said:
cm9 based rom in 2nd post, tell me guys, what you think about it
if you have ideas how to fix issues, send me pm with solution, i'll be very thankful
Click to expand...
Click to collapse
Which ROM did you use for the CM9 base? Rotation works right (no black screen).
Let me know if you have tested youtube.
cm9 base: http://forum.xda-developers.com/showthread.php?t=1620617
i can't test youtube now, because wifi, sdcard & adb doesn't work yet, but i'm working on it
most important thing is fixing adb, rest will be much easier then
If you have any questions, you may always PM me!
Sent from my Sapphire using xda app-developers app
hey OP thanks for puttin in work on this ancient device
I go to work @ 4 PST, do u think the links will be up by then? thx
banana4444 said:
Doesn't work:
Camcorder
Bluetooth
Wi-Fi
Camera
ADB
SD card
Auto rotation
Click to expand...
Click to collapse
Some of these sound like a kernel issue. What kernel are you using?
ezgb-1.5.3 ics
I don't think these are kernel issues, because it works fine on powerplop's base. Few of them should be fixed tonight.
My mind is blown!! Im trying this as soon as i get home and flash it to my G1. I wonder if, when HTC made the G1, they had the slightest idea that almost four years latter it would still be getting use and that more importantly it would have such advanced software forced into it and still run nicely.
banana4444 said:
ezgb-1.5.3 ics
I don't think these are kernel issues, because it works fine on powerplop's base. Few of them should be fixed tonight.
Click to expand...
Click to collapse
Yeah, that kernel should be fine. I'm guessing libs?
Well, cool! Best of luck to you!
Are you going to github your project?
so....how about that rom?
I'm awaiting patiently this release (so patiently that I keep refreshing this thread).
This would be a great boost for my cellphone, because everyone else is all happy with their 4.0, 4.1 and 4.2s in their all new cellphones.
1.5.3-ics? Is it safe to assume that's the one I built? If so, did you try the linaro one? It should perform a little better.
I should get back to work on my ics and jb roms and kernel. I've been really neglecting my android projects recently...
tvall said:
I should get back to work on my ics and jb roms and kernel. I've been really neglecting my android projects recently...
Click to expand...
Click to collapse
Not like you have done a lot of great stuff for our community already. Just saying...
tvall said:
1.5.3-ics? Is it safe to assume that's the one I built? If so, did you try the linaro one? It should perform a little better.
Click to expand...
Click to collapse
Yes, I tried, but it doesn't even boot. Any ics rom doesn't boot for me with this kernel.
I originally released this rom on 2fastforums.com (http://2fastroms.com/showthread.php?5435-WIP-18-Dec-2012-CM7-Kernel-CM-msm7x30) and now feel it is ready for release on XDA. (Site is currently down for unknown reasons)
CM7 for HTC Merge/Lexikon
Click to expand...
Click to collapse
Code:
Features:
-100% stock CM7 from source
What works:
Almost everything
Click to expand...
Click to collapse
What doesn't work:
MMS on USC?
Jittery Compass
Click to expand...
Click to collapse
Instructions
1) Flash recovery through bootloader or fastboot
2) Boot into recovery and factory reset, also go into mounts and format system
3) Flash Rom
4) Flash GApps
Click to expand...
Click to collapse
Downloads
Recovery: http://d-h.st/users/e334/?fld_id=6766 (Either one will work, I personally prefer v5.0.2.8 Capacitive Touch)
ROM: http://d-h.st/users/e334/?fld_id=6727
GApps: https://www.box.com/s/79bpq0ywdxcf4093t926 (thanks liamf1!)
Click to expand...
Click to collapse
Source
Kernel: https://github.com/jianC/htc-kernel-msm7x30
Lexikon Device Tree: https://github.com/jianC/android_device_htc_lexikon
Lexikon Proprietary Vendor Tree: https://github.com/jianC/android_vendor_htc
Click to expand...
Click to collapse
All my changes are documented on github.
Credits: Cyberblade (CDMA fix), liamf1 (beta tester/helpful feedback) 2fast4u88, Cyanogenmod & Team, Kali-, Neopeek & Team, UnitedDev & Team, and everyone else who contributed.
Please leave any feedback about bugs/problems/glitches/etc and I will try to fix them.
Thank you ;D
Sent from my HTC Merge using Tapatalk 2
faille13 said:
Thank you ;D
Sent from my HTC Merge using Tapatalk 2
Click to expand...
Click to collapse
Nice to see you on here too
Lol yeah, I'm everywhere.
Sent from my HTC Merge using Tapatalk 2
---------- Post added at 01:34 PM ---------- Previous post was at 01:12 PM ----------
I don't get around here too often. I haven't seen a dedicated forum for my merge yet.
Sent from my HTC Merge using Tapatalk 2
GPS problem
How to fix the GPS ?
It won't turn on , I mean GPS icon is not shown in the notifications bar and it searches for the satellites forever .
I use 20130121 version of this mod and gsm mode .
Gytixas said:
How to fix the GPS ?
It won't turn on , I mean GPS icon is not shown in the notifications bar and it searches for the satellites forever .
I use 20130121 version of this mod and gsm mode .
Click to expand...
Click to collapse
Hmm.. i'll look into it.
I am so happy that new version established but i GSM doesn't work. Please fix the bug
Thanks
Mistake
sorry sorry, GSM works perfect, Just needed to reboot. Thanks a lot. but Bluetooth and GPS doesn't work either. Plz fix these bugs ! Thanks
nikoloz995 said:
I am so happy that new version established but i GSM doesn't work. Please fix the bug
Thanks
Click to expand...
Click to collapse
+1
development of the firmware is?
Thank you so much, this is the best rom for this phone (the only working cyanogen). I am happy to report that after a few weeks use it has across the board improved my phones responsiveness, battery life, and usability. However... I have one problem. I live in Alaska and have GCI as a carrier... when I alter my cdma apn info, everything works up to the point I want to change my MCC and MNC... it's defaulting to 310 and 012 respectively. When I leave those values alone it saves the apn... when I alter them, the apn entry disappears! How can I fix this? I I need it to be 311 and 370 but can't get it to save my apn.
If this never works, I don't care, I wil continue using this rom without mobile internet or mms downloads... it's just that good.
lexikonlover said:
Thank you so much, this is the best rom for this phone (the only working cyanogen). I am happy to report that after a few weeks use it has across the board improved my phones responsiveness, battery life, and usability. However... I have one problem. I live in Alaska and have GCI as a carrier... when I alter my cdma apn info, everything works up to the point I want to change my MCC and MNC... it's defaulting to 310 and 012 respectively. When I leave those values alone it saves the apn... when I alter them, the apn entry disappears! How can I fix this? I I need it to be 311 and 370 but can't get it to save my apn.
If this never works, I don't care, I wil continue using this rom without mobile internet or mms downloads... it's just that good.
Click to expand...
Click to collapse
APN backup and restore app worked for me on US Cellular (backup apn from stock install, then restore to CM7), though I had to switch to GoSMS as a messaging app for MMS to send properly (stock app would receive but not send MMS - SMS worked normally in both). I had no success manually entering the apn info - didn't seem to have any effect when I tried.
@JianC
I found an issue with the 20130121 version from Jan 21 you posted on 2fastroms: If the phone is left on the charger it will charge all the way up, then discharge all the way back to zero while still plugged in. It still displays that it is at 100%, but then abruptly drops to whatever the actual charge level is after a few minutes of use. I've tried wiping battery stats to no effect and it works properly in stock rom. This is the only bug I can't seem to work around... Any fix or suggestions for things to try would be most appreciated! Thanks again for your work on this ROM!
Fixed GPS (and other issues), please see OP!
EDIT: I'll look into the apns issue... I don't use my Merge on CDMA so it's a stab in the dark.
The final version of CM7 has been uploaded (charging bug *should* be fixed).. I will not be supporting CM7 anymore but will be working on Evervolv/CM10.1.
Thanks for your feedback and support!
jianC said:
The final version of CM7 has been uploaded (charging bug *should* be fixed).. I will not be supporting CM7 anymore but will be working on Evervolv/CM10.1.
Thanks for your feedback and support!
Click to expand...
Click to collapse
CM10.1 availible to test?
DJ_MiX said:
CM10.1 availible to test?
Click to expand...
Click to collapse
Nope, he working on kernel .
http://review.evervolv.com
Sent from my HTC Merge using xda premium
If any help with the kernel is needed I will try my best to free up some time and pitch in some help. I have made several kernels for several other devices and the most popular being for the Acer Iconia tablets here on XDA see my signature. Great to see a CM rom for the merge on here though!! GB works fine for me, not that much cool factor from cm 10 or cm 10.1 as I have compiled quiet a few nightlies for the A100.. Other than the Project Butter and the overall UI I could care less about JB/ICS.
linuxsociety said:
If any help with the kernel is needed I will try my best to free up some time and pitch in some help. I have made several kernels for several other devices and the most popular being for the Acer Iconia tablets here on XDA see my signature. Great to see a CM rom for the merge on here though!! GB works fine for me, not that much cool factor from cm 10 or cm 10.1 as I have compiled quiet a few nightlies for the A100.. Other than the Project Butter and the overall UI I could care less about JB/ICS.
Click to expand...
Click to collapse
@linuxsociety That would be awesome if you could. Elginsk8r and I have already ported the board files but I can't figure out what's keeping it from booting..
@ everyone: CM9 for the htc merge is here!: http://forum.xda-developers.com/showthread.php?p=44487058#post44487058
jianC said:
@linuxsociety That would be awesome if you could. Elginsk8r and I have already ported the board files but I can't figure out what's keeping it from booting..
Click to expand...
Click to collapse
Does it just boot loop or does it go black? does the CM logo appear? Guess there is no logcat output via adb either or you'd probably have nailed it by now. Maybe we will have to get jtag debugging output so we can see exactly what is causing the kernel panic and work from there.
I have just now had time to get on xda and check up on the new status. I will try to clone the git repository and check the kernel .config for the cm10 build. Just a thought but on most devices that have a working kernel with cm9 the exact same kernel + modules work fine with CM10. Have you all tried the kernel from CM9 that was just recently posted on any CM10 builds for the device? Not much has changed between ICS and JB that are dependent on in kernel features or that require bleeding edge mainline kernel and/or proprietary kernel patches. However there is a good possibility that the issue is more to do with the bootloader that is required to chainload the android OS for JB causing CM10 not to boot properly. So updating the bootloader may be necessary for JB/CM10 to boot properly. Nevertheless we need some debugging output in order to pinpoint what exactly is the problem going on. I am going to flash cm9 to my merge now and see how everything goes. I may experiment with the cm9 kernel and a cm10 build if I can find one for the merge. My hardware I have right now would take quiet some time to build JB as I haven't even used this old c2d laptop to build any android roms yet lol. Sorry for such a long posting but hopefully it is of some help in finding the resolution to the problems we have.
Thanks guys!
linuxsociety said:
Does it just boot loop or does it go black? does the CM logo appear? Guess there is no logcat output via adb either or you'd probably have nailed it by now. Maybe we will have to get jtag debugging output so we can see exactly what is causing the kernel panic and work from there.
I have just now had time to get on xda and check up on the new status. I will try to clone the git repository and check the kernel .config for the cm10 build. Just a thought but on most devices that have a working kernel with cm9 the exact same kernel + modules work fine with CM10. Have you all tried the kernel from CM9 that was just recently posted on any CM10 builds for the device? Not much has changed between ICS and JB that are dependent on in kernel features or that require bleeding edge mainline kernel and/or proprietary kernel patches. However there is a good possibility that the issue is more to do with the bootloader that is required to chainload the android OS for JB causing CM10 not to boot properly. So updating the bootloader may be necessary for JB/CM10 to boot properly. Nevertheless we need some debugging output in order to pinpoint what exactly is the problem going on. I am going to flash cm9 to my merge now and see how everything goes. I may experiment with the cm9 kernel and a cm10 build if I can find one for the merge. My hardware I have right now would take quiet some time to build JB as I haven't even used this old c2d laptop to build any android roms yet lol. Sorry for such a long posting but hopefully it is of some help in finding the resolution to the problems we have.
Thanks guys!
Click to expand...
Click to collapse
The .35 kernel works fine for CM10.0 but I'm having some issues booting cm10.1 with the .35 kernel because of some graphics memory allocation issues. The main issue is that there are a few issues that can't be fully fixed without the 3.0 kernel such as the camera/camcorder, ION support, etc (which is WIP here: http://review.evervolv.com/#/c/6609/ ). I have already tried probing for the UART TX/RX pins on the lexikon motherboard with a bus pirate but I have not found anything to date. I ordered a micro usb breakout board yesterday for USB UART debugging and am going to pick up some resistors from radioshack so we can hopefully get some progress on the 3.0 kernel because it won't boot far enough to adb or dmesg for our purposes. The problem isn't CM10 right now, but the kernel, which would require jtag or uart debugging, as you have mentioned. I hope that we can get the 3.0 kernel booting soon so we can have cm9/10 fully working.
jianC said:
The .35 kernel works fine for CM10.0 but I'm having some issues booting cm10.1 with the .35 kernel because of some graphics memory allocation issues. The main issue is that there are a few issues that can't be fully fixed without the 3.0 kernel such as the camera/camcorder, ION support, etc (which is WIP here: http://review.evervolv.com/#/c/6609/ ). I have already tried probing for the UART TX/RX pins on the lexikon motherboard with a bus pirate but I have not found anything to date. I ordered a micro usb breakout board yesterday for USB UART debugging and am going to pick up some resistors from radioshack so we can hopefully get some progress on the 3.0 kernel because it won't boot far enough to adb or dmesg for our purposes. The problem isn't CM10 right now, but the kernel, which would require jtag or uart debugging, as you have mentioned. I hope that we can get the 3.0 kernel booting soon so we can have cm9/10 fully working.
Click to expand...
Click to collapse
This sounds about like the exact same issues that was experienced when I was helping hashcode work on the original kindle fire device and getting it to work with ICS. I 'think' with the HTC it shouldn't be near as hard to resolve the issue to get full hw acceleration, memory mappings camera/gps and all the extra bells and whistles if we make an attempt at backporting the necessary support into the .35 kernel instead of trying to upgrade * to 3.x which will be adding to the work and break more things than it fixes. Since HTC apparently isn't going to be releasing any updates for the device it looks like it is going to be left all up to us to make one of two decisions:
1) backporting kernel - only the few things remaining needed for our current working GB kernel to have full support for ICS/JB roms
OR
2) updating to 3.x.x and merging HTC fixes and 3rd party patches -through several mainline kernel patches and keeping the proprietary htc addins compatible.
My opinion/suggestion:
I'd think of the two options that backporting would be the most logical answer to the equation since we are only missing support for few things and you already have everything working except the camera, ION, BINDER(?), and other >=3.0.0 android patches. Plus the device is pretty well coming to a good place to say cease development work and either enjoy the device or upgrade to something newer. So if we could get JB support or even just ICS working fully I think 99.99% of all owners/users would be more than 99.99% happy!! I know I would be very happy myself!
Alpha Omnirom 5.0 (Trying to get calls to work properly on CM first before doing more omni builds))
baseband is still unknown. So no phone calls or data.
Alpha Cyanogenmod 5.02 with working baseband
https://drive.google.com/file/d/0B4k5OpXTXcS9NF8zN1dreFAtOUk/view?usp=sharing
Build 5.0.1:
https://drive.google.com/file/d/0B4k5OpXTXcS9NVp0Sm9YMFdEUUE/view?usp=sharing
Calls should now work without lockups. Data seems flakey? Let me know your finding
(This is now working due to rolling back to old RIL blobs (pre 4.3). This means that the connection process takes longer on initial start-up and switching to air-plane mode as well. )
Leave wifi on to avoid reboots.
Also this doesnt have the camera bug fix yet that Derteufel made.
Nice.. Never been a fan of omni.. I'm more a cm or aosp person
Sent from my GT-I9305 using XDA Free mobile app
REVIEW
Thank you very much for this build for the i9305
I have been waiting for the first lollipop build
I installed this rom and this is a written review after one hour of usage
1 the phone boots without any problem
2 lollipop gapps are working
3 Sometimes wifi works and sometimes no
4 Bluetooth works
5 some random reboots and sometimes it stuck so I need to remove the battery to get it working again
6 no FCs at all
7 seems fast
8 when I open an app installe from play store the phone stucks and I remove the battery
Thanks again and I wish u improve this rom in the coming days
Good job mate but I think it'll be better to edit your thread to make something more attractive, Flash Guide for noobs , links to gapps, alternative dl links , what works, what doesn't , credits , shiet like this would be better for everyone.
The main problem of your rom seems to be the kernel (random reboots , wifi issues , random freezes)
Anyways , good luck and thank you for the rom
aaz03 said:
Good job mate but I think it'll be better to edit your thread to make something more attractive, Flash Guide for noobs , links to gapps, alternative dl links , what works, what doesn't , credits , shiet like this would be better for everyone.
The main problem of your rom seems to be the kernel (random reboots , wifi issues , random freezes)
Anyways , good luck and thank you for the rom
Click to expand...
Click to collapse
Thanks for the feedback.
This isnt meant for n00bs to flash yet. This is an alpha.
In Alphas you expect to get problems! This is only meant for testing and for trying out 5.0 on your device...
can we flash this normally?
CM 5.0.1 build added to OP. Please read notes about what isnt working before flashing!
So the latest build is the most stable one (CM12)? Can I help you in any way, testing, logs or something?
limnaln said:
So the latest build is the most stable one (CM12)? Can I help you in any way, testing, logs or something?
Click to expand...
Click to collapse
Well at this point in time no. I've just got to try to figure out whats going wrong still and then people can test to see if it works for them and if there is any long term problems with it. Until then its just make a change, compile and flash and I'll let people know if I get anywhere.
for me it is stuck on bootloop... first flashed wih wipe full/dalvik/cache then flashed gapps - bootloop. second dirty flashed again, booted, android is upgrading, optimizing apps, then rebooted and again bootloop... how to get past this ?
Tested. Boots okay. Data baseband ok. Incoming calls ok. Outgoing calls impossible. Tested with 2g
laurent.siku said:
for me it is stuck on bootloop... first flashed wih wipe full/dalvik/cache then flashed gapps - bootloop. second dirty flashed again, booted, android is upgrading, optimizing apps, then rebooted and again bootloop... how to get past this ?
Click to expand...
Click to collapse
As I said this doesnt have the camera firmware patch added so some people might get bootloops... I'll add this in the next day or two from Derteufel
infrag said:
As I said this doesnt have the camera firmware patch added so some people might get bootloops... I'll add this in the next day or two from Derteufel
Click to expand...
Click to collapse
So, we are at the final step - outgoing calls, huh?
There also appeared some new commits on nameless gerit, just informing
Outgoing calls can be made now. But it seems to lockup when hanging up. New link in OP for 'new' build.
Calls should now work!
This is using old ril blobs so initial connection from boot will take longer. Also I think data is stuffed a bit. Seems to take a long time to get connected. Seems to work for me after that though. Post your finding please!
Hopefully Derteufel can figure out the problem with the newer blobs but till then this is working if anyone is interested.
Edit: only got one question. Can wifi be turned off. Will disabling it cause bootloops?
infrag said:
Calls should now work!
This is using old ril blobs so initial connection from boot will take longer. Also I think data is stuffed a bit. Seems to take a long time to get connected. Seems to work for me after that though. Post your finding please!
Hopefully Derteufel can figure out the problem with the newer blobs but till then this is working if anyone is interested.
Click to expand...
Click to collapse
Yes, it does work indees! In and out! Really great, the whole system is smooth.
Great work. Will be swapping back to the i9305 from the note 2.. All we need now is for someone to work on the stock cm kernel to make it smoother.
Sent from my GT-N7105 using XDA Free mobile app
Great work on calls! Please let us know when you include the camera firmware fix so I can download again and flash, this is the only thing causing me bootloops and preventing me for further testing. Thanks
Sent from my GT-I9305 using XDA Free mobile app
winxuser said:
Great work. Will be swapping back to the i9305 from the note 2.. All we need now is for someone to work on the stock cm kernel to make it smoother.
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
Stock kernel? We are only using that to get data working... I'm sure Derteufel will switch to his own kernel as soon as he irons out the problems with phone calls locking up etc. (Or he switches to old RIL blobs for now)
Then there will be the challenge of getting R4P0 drivers to work properly.
After that who knows? Fix opensource compass?
Then Nameless may have other upgrades to implement for HWC.