The official CM 10.2 nightlies for both the Xperia T and Xperia V builds have begun...
Browse to get.cm and choose mint (T) or tsubasa (V).
KelleyCook said:
The official CM 10.2 nightlies for both the Xperia T and Xperia V builds have begun...
Browse to get.cm and choose mint (T) or tsubasa (V).
Click to expand...
Click to collapse
Anyone tried it yet?
jimilegolas said:
Anyone tried it yet?
Click to expand...
Click to collapse
Just loaded it:
Good news: The Echo Bug is gone!
Bad news: WiFi will not grab an IP address.
So its back to tilal's last (9/26) CM build for me. I'll try again in a week or so.
Xperia T is now officially into CM 10.2 nightlies. Today there's a new release.
KelleyCook said:
Just loaded it:
Good news: The Echo Bug is gone!
Bad news: WiFi will not grab an IP address.
So its back to tilal's last (9/26) CM build for me. I'll try again in a week or so.
Click to expand...
Click to collapse
KelleyCook said:
Just loaded it:
Good news: The Echo Bug is gone!
Bad news: WiFi will not grab an IP address.
So its back to tilal's last (9/26) CM build for me. I'll try again in a week or so.
Click to expand...
Click to collapse
What about the speakerphone screech and the blue screen of death?
2Kelley: means that wifi is not working? What build? from 16th of 17th?
looker1 said:
2Kelley: means that wifi is not working? What build? from 16th of 17th?
Click to expand...
Click to collapse
Both nightlies have broken Wifi
Edit: There's been a new one. Has anybody tested it? I guess it should be the same with previous ones.
Edit2: Yeah, same **** with previous nightlies
Still no love for Xperia TX
Sent from my LT29i using XDA Premium 4 mobile app
Nightly 2013-10-20 Wifi still sucks.
Sometimes it connects for a few seconds and drops connection, sometimes you get Authentication failure.
efs12 said:
Nightly 2013-10-20 Wifi still sucks.
Sometimes it connects for a few seconds and drops connection, sometimes you get Authentication failure.
Click to expand...
Click to collapse
Still none of 4.3 builds have wifi working. Needs to be patient :fingers-crossed:
looker1 said:
Still none of 4.3 builds have wifi working. Needs to be patient :fingers-crossed:
Click to expand...
Click to collapse
You mean 4.3.1
Edit: Just flashed 21/10 release and Free Xperia bootloader icon is replaced with Sony logo.
Wifi still the same
Going to flash 240 now what i could read out wifi is working there? Gone report later on. What changes to 10.1 except the bugs could u guys find, Anything better on the actual working stuff?
Sent from my X Phone using xda developers app
Yep 21st build can confirm still no Wifi and speakerphone still whistles... But they managed to change the boot screen so I guess its all good lol. Starting to lose patience with custom rom's now me. I posted an in depth idea back in August about CM10.1 about this speakerphone problem. About the top mic not being used and phone always using the bottom one which is next to the speaker and 99% sure this is what causes our whistles and echo problems. Nobody has given a reply as to why we can't try this as its what stock rom does - hit speakerphone and the bottom mic is disabled and top one only active. Devs seem more interested in fiddling with mic gains or reducing the speaker volume which is a bit of a cop out. What we really need is to not use the mic thats next to the speaker for speakerphone calls! Its never going to work properly without compromising something else like reducing volume or mic gain so the speaker won't feedback with the mic. Compare it to taking a picture towards a light. You can mess with exposure and white balance to get a picture but its never going to be what it would be if the light was behind you and not shining into the lens. Same for speakerphone. You're not going to be able to have volume up high, mic gain at optimum and the speaker and mic next to each other. It's just logical that the further apart they are the less they will interfere with each other...
Speakerphone bug quite winds me up really considering it is phones we are running these custom roms on and a simple issue with a phone function hasn't been resolved since mid August! Its like saying hey long as we have all these features and build from latest android source who cares if a basic phone function doesn't work when I think that should be the priority before adding all other bells and whistles (no pun intended).
mdc1983uk said:
Speakerphone bug quite winds me up really considering it is phones we are running these custom roms on and a simple issue with a phone function hasn't been resolved since mid August! Its like saying hey long as we have all these features and build from latest android source who cares if a basic phone function doesn't work when I think that should be the priority before adding all other bells and whistles (no pun intended).
Click to expand...
Click to collapse
Agree 100%
mdc1983uk said:
Yep 21st build can confirm still no Wifi and speakerphone still whistles... But they managed to change the boot screen so I guess its all good lol. Starting to lose patience with custom rom's now me. I posted an in depth idea back in August about CM10.1 about this speakerphone problem. About the top mic not being used and phone always using the bottom one which is next to the speaker and 99% sure this is what causes our whistles and echo problems. Nobody has given a reply as to why we can't try this as its what stock rom does - hit speakerphone and the bottom mic is disabled and top one only active. Devs seem more interested in fiddling with mic gains or reducing the speaker volume which is a bit of a cop out. What we really need is to not use the mic thats next to the speaker for speakerphone calls! Its never going to work properly without compromising something else like reducing volume or mic gain so the speaker won't feedback with the mic. Compare it to taking a picture towards a light. You can mess with exposure and white balance to get a picture but its never going to be what it would be if the light was behind you and not shining into the lens. Same for speakerphone. You're not going to be able to have volume up high, mic gain at optimum and the speaker and mic next to each other. It's just logical that the further apart they are the less they will interfere with each other...
Speakerphone bug quite winds me up really considering it is phones we are running these custom roms on and a simple issue with a phone function hasn't been resolved since mid August! Its like saying hey long as we have all these features and build from latest android source who cares if a basic phone function doesn't work when I think that should be the priority before adding all other bells and whistles (no pun intended).
Click to expand...
Click to collapse
OK so because people are so annoyed with this bug I'm going to post a fix to CM gerrit - it's up to the CM team whether they accept it.
I've known a fix for this for ages BTW - it's fixed in my Omni build - I just haven't bothered because of CM's attitude/my commitment to omni.
Plus Kali- et all the CM team have been busy with newer devices.
mdc1983uk said:
Yep 21st build can confirm still no Wifi and speakerphone still whistles... But they managed to change the boot screen so I guess its all good lol.
Click to expand...
Click to collapse
that made my evening. laughed loud...hehehe funny you
by the way, not using cm here.... hows the bootscreen loking?
tilal6991 said:
OK so because people are so annoyed with this bug I'm going to post a fix to CM gerrit - it's up to the CM team whether they accept it.
I've known a fix for this for ages BTW - it's fixed in my Omni build - I just haven't bothered because of CM's attitude/my commitment to omni.
Plus Kali- et all the CM team have been busy with newer devices.
Click to expand...
Click to collapse
i'm putting al my fait in omnirom :good:
Tilal you're a saint!!
Nice speach mdc1983uk, i totally agree. Iam again on 235 after trying 241 and cm10.2. Both not much changes or fixes. So in about 2 month nothing happend.
I will try tilals and aokp build tomorrow hope they work on dirt flash.
About cm10.2 wifi was working for 2 min and then it was gone. Havent found much changes in that short test. Also no dirt flash back to 10.1 possible. Had to wipe evrything.
Sent from my X Phone using xda developers app
tilal6991 said:
OK so because people are so annoyed with this bug I'm going to post a fix to CM gerrit - it's up to the CM team whether they accept it.
I've known a fix for this for ages BTW - it's fixed in my Omni build - I just haven't bothered because of CM's attitude/my commitment to omni.
Plus Kali- et all the CM team have been busy with newer devices.
Click to expand...
Click to collapse
Tilal you are a good guy! I've looked at changes and they look very promising just hope they get reviewed and added quickly so we can test a nightly. I knew there was more to snd_soc_msm than the volumes but I couldn't work out which DEC and ADC numbers to change to what... Is there any way to add these changes to a existing install so we don't have to wait for CM? I know you can edit snd_soc with hexeditor and reboot but it looks like your fix is dependant on other fixes as well? Like do CM have to implement your thermal fix and noise supression before the changed snd_soc will work as you intend? Sorry i'm not too familiar with gerrit and how all these patch sets get reviewed and tested I just try and bring peoples attention to bugs if I can think of a new solution to try.
Cheers, Matt
---------- Post added at 01:41 PM ---------- Previous post was at 01:29 PM ----------
casis86 said:
Nice speach mdc1983uk, i totally agree. Iam again on 235 after trying 241 and cm10.2. Both not much changes or fixes. So in about 2 month nothing happend.
I will try tilals and aokp build tomorrow hope they work on dirt flash.
About cm10.2 wifi was working for 2 min and then it was gone. Havent found much changes in that short test. Also no dirt flash back to 10.1 possible. Had to wipe evrything.
Sent from my X Phone using xda developers app
Click to expand...
Click to collapse
Thanks. I apologise that it did go on a bit but people have took it in the way I intended and tilal's fix seems to do a lot more than anyone else's so its a good result for the community. I'm back on FXP240 for now. I tried early build of Omni but it got me stuck in a bootloop for some reason. I had the bubbles boot screen and it just stopped there. When I tried to get back into recovery it wouldn't even do that so I ended up having to fastboot flash a new boot.img then my sdcard0 was corrupt so I had to adb push FXP240 back and it became annoying. Can't wait til the official omni nightly's start and i'll definitely be giving it a good once over. Don't mind the look of PACrom either that has a lot of customisation options if not a little too many. Hopefully Omni will be somewhere between CM and PAC in the end and we'll have a great all rounder to choose from.
Related
CyanogenMod for the Vibrant currently contains intermittent issues with the emergency dialing system. I strongly urge you NOT to use CyanogenMod on the Vibrant until they can be fixed.
Help by testing a test CM9 build for it
awesome! nice to have you as "The bringer of CyanogenMod", if it wasn't for this great community, vibrant would be dead!
I know you aren't in charge of these things Fault but any idea when we'll get a new nightly?
jvpde said:
I know you aren't in charge of these things Fault but any idea when we'll get a new nightly?
Click to expand...
Click to collapse
By the looks of it, we might get one tonight.
http://jenkins.cyanogenmod.com/job/android/
The latest nightly link seems down. Would someone else confirm?
Sent from my SPH-D710 using Tapatalk
Working atm
I don't even know who the specific cm7 vibrantmtd mantainer is (if any), that's why I asked if the project had been declared dead. No sign of activity since late February, while other phones have been getting constantly updated nightly builds. There will be a reason for sure.
°_° The OP guy is the maintainer, and we will have cm7 nightlies either this week or next. Cm servers are being upgraded...
Sent from my T959 using XDA
flapane said:
I don't even know who the specific cm7 vibrantmtd mantainer is (if any), that's why I asked if the project had been declared dead. No sign of activity since late February, while other phones have been getting constantly updated nightly builds. There will be a reason for sure.
Click to expand...
Click to collapse
Glacier hasn't had any since ours.
Captivate has had 1 since ours.
Fascinate hasn't had any since ours.
Galaxy S hasn't had any since Feb 16th.
It doesn't mean that it's dead...
does this mean what i think it means
cm: Tag 7.2.0-RC1
looks like cm7/gingerbread is reaching its ripeness!
akfelipe said:
does this mean what i think it means
cm: Tag 7.2.0-RC1
looks like cm7/gingerbread is reaching its ripeness!
Click to expand...
Click to collapse
It still lacks proper TV out (no hardware decoding). And I'm not sure whether the mute/unmute bug has been solved or even whether the GPS is truly functional... apart from those, yep, the ROM seems quite stable...
O never really use TV out or GPS so I wouldn't know, but the mute/unmute should be fixed by now,
the mainteiner is that one who deals with device specific bugs...ask him what's the status with those two.
Sent from my T959 using XDA
akfelipe said:
O never really use TV out or GPS so I wouldn't know, but the mute/unmute should be fixed by now,
the mainteiner is that one who deals with device specific bugs...ask him what's the status with those two.
Sent from my T959 using XDA
Click to expand...
Click to collapse
I'm not sure if the mute-unmute bug is localized to Vibrant. (The changelog was copied from Captivate, which said the mute-unmute was hopefully fixed, Galaxy S also says it.)
(I'm not saying I won't I'll look into it though)
The mute-unmute bug is not fixed. I don't know about TV out, my cable is faulty. raymonddull tested it for me, he got black and white, which is more than I got, but his cable was faulty too!
GPS is most likely poo. Just flash YAGF2 or what ever works for you.
update-cm-7-20120226-NIGHTLY-vibrantmtd. Never work on my vibrant cause of the systemUI error. Are they going to build another nightly or is this the end of the nightly build?
FaultException said:
I'm not sure if the mute-unmute bug is localized to Vibrant. (The changelog was copied from Captivate, which said the mute-unmute was hopefully fixed, Galaxy S also says it.)
(I'm not saying I won't I'll look into it though)
The mute-unmute bug is not fixed. I don't know about TV out, my cable is faulty. raymonddull tested it for me, he got black and white, which is more than I got, but his cable was faulty too!
GPS is most likely poo. Just flash YAGF2 or what ever works for you.
Click to expand...
Click to collapse
TV out works but only partially. Its quality is worse than Froyo's (Samsung's official) and it shows a black screen when someone tries to play a hardware accelerated video.
The mute/unmute bug most of the times is there.
GPS may work to some, it won't to most and the fixes are hit or miss on equal measure. Personally I have last had my GPS working on Froyo days. I know it's not a big deal for most people here on XDA, but for the rest of the world (outside XDA) GPS is kind of a big deal and it's one of those modules that makes smartphones to be "smart"...
Anyhow the situation for CM7 (on our Vibrant) is about the same as in those GB ports from i9000; i.e. most things work, not all. If one needs the full experience of the phone *has to* go back to Froyo ... sadly.
Stevethegreat said:
TV out works but only partially. Its quality is worse than Froyo's (Samsung's official) and it shows a black screen when someone tries to play a hardware accelerated video.
The mute/unmute bug most of the times is there.
GPS may work to some, it won't to most and the fixes are hit or miss on equal measure. Personally I have last had my GPS working on Froyo days. I know it's not a big deal for most people here on XDA, but for the rest of the world (outside XDA) GPS is kind of a big deal and it's one of those modules that makes smartphones to be "smart"...
Anyhow the situation for CM7 (on our Vibrant) is about the same as in those GB ports from i9000; i.e. most things work, not all. If one needs the full experience of the phone *has to* go back to Froyo ... sadly.
Click to expand...
Click to collapse
Can you play hardware accelerated video on Froyo via TV out?
FaultException said:
Can you play hardware accelerated video on Froyo via TV out?
Click to expand...
Click to collapse
Yes, everything works on Froyo as intended... in fact because TV out is a feauture I often use (useful for presentations and such) I often have to go back to Froyo...
update-cm-7.2.0-RC1-vibrantmtd-signed.zip is up now on get.cm
Btw, anyone else not seeing "CyanogenMod Nightlies" in Premium Rom Manager? I used to, but it was quite some time ago.
ginzberg said:
update-cm-7.2.0-RC1-vibrantmtd-signed.zip is up now on get.cm
Btw, anyone else not seeing "CyanogenMod Nightlies" in Premium Rom Manager? I used to, but it was quite some time ago.
Click to expand...
Click to collapse
10char....
Mostdef said:
update-cm-7-20120226-NIGHTLY-vibrantmtd. Never work on my vibrant cause of the systemUI error. Are they going to build another nightly or is this the end of the nightly build?
Click to expand...
Click to collapse
New nightly cooking now: http://jenkins.cyanogenmod.com/job/android/304/
I'll start a build each night for one, until automatic nightlies are sorted out.
EDIT: Hmm, looks like there is a problem right now. I'll try again tomorrow.
I decided to build somewhat of nightlies as Evervolv with Android 4.2 is in a very usable state. Since these are nightlies there may be severe bugs at any time. I will not be taking bug reports unless you can provide adequate logs. I am mainly just building nightlies and trying to fix device specific issues where I can.
Do not use 4.1 gapps. Please use the ones listed here for now as they are for 4.2 and stripped down.
Items that need attention: (Not working or buggy)
BT audio seems messed up too, not sure if it works in phone calls yet, it does connect to a headset
Camera preview is glitchy - use a different camera app if you don't want a glitchy camera - IE try Camera ICS
Downloads:
Evervolv nightlies
Gapps:
Latest Gapps
The rest is straight from preludedrew's post for Evo 4g:
Right now the current source we are working on is Jellybean (Android 4.2.x).
For those that don't know what evervolv is, Evervolv is an AOSP (Android Open Source Project) rom. We're fully open sourced and encourage it with no restrictions. The work put into this rom is community driven and and Evervolv Project is made up of numerous members and contributors.
Below is the "Not working" or items that are buggy list. I'm going to keep it short and simple for the time being and let ya'all figure bugs out, and I will update this.
Quote:
Here's a couple links to keep in mind:
Evervolv Github: https://github.com/Evervolv
Evervolv Gerrit: http://review.evervolv.com/
Evervolv website: http://www.evervolv.com/
(The website has not been updated since our gingerbread builds... I know I know.)
IRC: #evervolv
Quote:
[GPL Compliance]
Kernel Source: https://github.com/Evervolv/android_kernel_htc_qsd8k
No way, I figured this was way out of reach for us this soon. Although I need to wait n see how it works for a bit, but I'm dying to get this. Please tel me the video and camcorder issue can be fixed with this
Sent from my ADR6300 using xda app-developers app
tiny4579 said:
I decided to build somewhat of nightlies as Evervolv with Android 4.2 is in a very usable state. Since these are nightlies there may be severe bugs at any time. I will not be taking bug reports unless you can provide adequate logs. I am mainly just building nightlies and trying to fix device specific issues where I can.
Downloads:
Latest Evervolv build:
Evervolv-Dives-3.2.0-Nightly-2012.12.13-inc.zip - 129.28 MB
Gapps:
gapps-jb-20121212-signed-inc.zip - 26.66 MB
The rest is straight from preludedrew's post for Evo 4g:
Right now the current source we are working on is Jellybean (Android 4.2.x).
For those that don't know what evervolv is, Evervolv is an AOSP (Android Open Source Project) rom. We're fully open sourced and encourage it with no restrictions. The work put into this rom is community driven and and Evervolv Project is made up of numerous members and contributors.
Below is the "Not working" or items that are buggy list. I'm going to keep it short and simple for the time being and let ya'all figure bugs out, and I will update this.
Quote:
Items that need attention: (Not working or buggy)
** Resetting for 3.2 release **
GPS?
BT audio seems messed up too, not sure if it works in phone calls yet
Quote:
Here's a couple links to keep in mind:
Evervolv Github: https://github.com/Evervolv
Evervolv Gerrit: http://review.evervolv.com/
Evervolv website: http://www.evervolv.com/
(The website has not been updated since our gingerbread builds... I know I know.)
IRC: #evervolv
Quote:
[GPL Compliance]
Kernel Source: https://github.com/Evervolv/android_kernel_htc_qsd8k
Click to expand...
Click to collapse
EV Gerrit has been down all day today
Working on fixing storage force closing. I'm kind of disappointed as with something this big I'd expected more comments by now. Though this is fun to have to struggle over and attempt to fix issues.
tiny4579 said:
I'm kind of disappointed as with something this big I'd expected more comments by now.
Click to expand...
Click to collapse
Probably because there are very few of us left... I'm waiting til there is something that is perfect to replace this.. I have had it since day 1 (pre-order) 1 year contract.. so I have been out of contract for a year and a half and am buying the next phone full price to retain the unlimited data. So if I'm spending 700 or so it better be damn near perfect.
As this has been... and mine is still in perfect shape.
Finally I found the thread! Hey guys
Sent from my Nexus 7 using xda premium
---------- Post added at 11:54 PM ---------- Previous post was at 11:32 PM ----------
Flash Incredikernel on this rom?
Sent from my Nexus 7 using xda premium
I was at work today, so just seeing this now. I also didn't figure we'd see 4.2 at all or anytime real soon. Just blows me away at the length of time we have managed to keep the OG Dinc ahead of the pack.
I will download in a few days, in the process of moving right now. I originally had my heart set on the Inc4g, but the crap VZ was pulling with their new plans and the locked bootloaders, made me hold out. Those guys got it unlocked, but then I saw the DNA come out. That thing has some serious specs, and is smooth as hell but damn, I just can't wrap myself around the size of it yet. Well, I guess for now, when guys keep coming up with Roms to put on our Dincs, hell, theres no hurry to go anywhere.
Can I flash this over your cm10 or should I Wipe first?
Sent from my ADR6300 using xda app-developers app
Looks promising, might have to flash it up later today!
Sent from my ADR6300 using xda app-developers app
Nice job. WiFi works here haven't tried Bluetooth. Noticed lock screen settings are not included. Has new camera with pinch to zoom preview is unstable but pics are OK. If i have time I'll see if 4.12 gallery works. Haven't added gapps yet
ohredwood said:
I was at work today, so just seeing this now. I also didn't figure we'd see 4.2 at all or anytime real soon. Just blows me away at the length of time we have managed to keep the OG Dinc ahead of the pack.
I will download in a few days, in the process of moving right now. I originally had my heart set on the Inc4g, but the crap VZ was pulling with their new plans and the locked bootloaders, made me hold out. Those guys got it unlocked, but then I saw the DNA come out. That thing has some serious specs, and is smooth as hell but damn, I just can't wrap myself around the size of it yet. Well, I guess for now, when guys keep coming up with Roms to put on our Dincs, hell, theres no hurry to go anywhere.
Click to expand...
Click to collapse
Yeah I 2 am thinking of the inc 4g lte, are you saying it can't be rooted and do what we do with this Inc? I was unaware.
So does anyone have the list of things that so far don't work at all or don't work well? I'm antsy but this time of year I need the phone to work and bluetooth to work too since I do snow removal for work.
tiny4579 said:
Working on fixing storage force closing. I'm kind of disappointed as with something this big I'd expected more comments by now. Though this is fun to have to struggle over and attempt to fix issues.
Click to expand...
Click to collapse
I got as far as figuring out that gapps from 4.1 don't work. Then I called it quits and went to bed. It did boot though without gapps installed, it definitely ran slower than 4.1, but I didn't hit any showstoppers in the five minutes I played with it last night. Got it running now with a stripped-down gapps from goo. So far, so good.
And for those who are dying to know, the camera takes good pictures, has glitchy preview, and trying to record video causes it to FC.
musical_chairs said:
I got as far as figuring out that gapps from 4.1 don't work. Then I called it quits and went to bed. It did boot though without gapps installed, it definitely ran slower than 4.1, but I didn't hit any showstoppers in the five minutes I played with it last night. Got it running now with a stripped-down gapps from goo. So far, so good.
And for those who are dying to know, the camera takes good pictures, has glitchy preview, and trying to record video causes it to FC.
Click to expand...
Click to collapse
Yes there are new gapps in the op because they are linked to /data because /system is to small
Sent from my Droid Incredible using Tapatalk 2
lukkypuggy said:
Flash Incredikernel on this rom?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I would and it works fine
zombolt said:
Can I flash this over your cm10 or should I Wipe first?
Sent from my ADR6300 using xda app-developers app
Click to expand...
Click to collapse
Please wipe coming from CM to AOSP.
zachf714 said:
Yes there are new gapps in the op because they are linked to /data because /system is to small
Sent from my Droid Incredible using Tapatalk 2
Click to expand...
Click to collapse
Actually I fixed that all up if you looked in my gapps and ROM package you would know. The ROM is in /system entirely and the gapps get flashed to system.
kramer56 said:
Yeah I 2 am thinking of the inc 4g lte, are you saying it can't be rooted and do what we do with this Inc? I was unaware.
So does anyone have the list of things that so far don't work at all or don't work well? I'm antsy but this time of year I need the phone to work and bluetooth to work too since I do snow removal for work.
Click to expand...
Click to collapse
The list depends on the community to test. I can't test phone calls and haven't been able to test bluetooth in calls for the same reason but bluetooth seems to work and my headset did connect.
tiny4579 said:
Actually I fixed that all up if you looked in my gapps and ROM package you would know. The ROM is in /system entirely and the gapps get flashed to system.
Click to expand...
Click to collapse
OK I'm confused. gapps get flashed to /system or /data?
saltcreep1 said:
OK I'm confused. gapps get flashed to /system or /data?
Click to expand...
Click to collapse
System. They always do. I just had a test gapps that didn't get posted anywhere. Then I made a smaller gapps package. Didn't you read my post?
Sent from my Galaxy Nexus using Tapatalk 2
running great the camera is glitchy bt wen zooming the flickering stops
Sent from my rooted GameBoy Color
Gave this a try last night and got to play around with some of the new features. Exciting! I'm glad to see that so much progress has been done on 4.2. Over the past month I'd heard multiple times that 4.1 might be the end of the road for the DINC.
Thanks, tiny!
:good:
Okay, I got a couple PM's asking me to open an own thread, as the old CM 10.1 Bug Thread isn't updated anymore and the OP hasn't been online since February 2nd.
So here you go.
For logcats, development-related questions (e.g. implementation discussions) continue to use the thread in the dev discussioin section.
In this thread there won't be any posting restrictions.
Update: I've released a CM10.1 ROM which should fix most of the apparent issues.
More details in the thread: http://forum.xda-developers.com/showthread.php?t=2265329
Edit: this post isn't needed anymore.
You'll find the known bugs and fixes in the second post of the thread linked above.
I would like to test it. But I'm on old bootloader
Sent from my LG-P990 using xda premium
Okay guys, I think I fixed the call rejecting issue, at least it now works for me now.
Download: http://tonyp.hopto.org/cm-10.1-20130416-UNOFFICIAL-p990.zip
I need to make sure that I didn't break it for other Basebands, so please test if you can reject calls and report with your baseband.
If it doesn't work for you on this build please try the yesterdays one to see if there's any difference.
Desticus said:
I would like to test it. But I'm on old bootloader
Click to expand...
Click to collapse
Yes, I'm sorry but I can't build everything for both bootloaders right now.
All that stuff takes lots of time, and I need to focus on my own test builds, I hope you understand.
I am positive that I'll release a stable build, soon.
-----------------------------------
Hello TonyP:
I tried the testbuild, day 16.
And apparently the red frame, to completely gone or so I think.
Can you confirm that?.
As for gapps:
use the usual:
http://goo.im/gapps/gapps-jb-20121212-signed.zip
or showing us the goomanager:
gapps-jb-20130301-signed.zip
Thank you for your progress in the ROM.
Greetings.
tonyp said:
Okay guys, I think I fixed the call rejecting issue, at least it now works for me now.
Download: http://tonyp.hopto.org/cm-10.1-20130416-UNOFFICIAL-p990.zip
I need to make sure that I didn't break it for other Basebands, so please test if you can reject calls and report with your baseband.
If it doesn't work for you on this build please try the yesterdays one to see if there's any difference.
Yes, I'm sorry but I can't build everything for both bootloaders right now.
All that stuff takes lots of time, and I need to focus on my own test builds, I hope you understand.
I am positive that I'll release a stable build, soon.
-----------------------------------
Click to expand...
Click to collapse
Hey Tony Thanks for the great work, I have used your previous build, call rejecting is working fine with the first build. Downloading the current 2nd build.
Just a note: When on call if the speaker is activated, the opposite person voice seems to echo for them, this was an issue on cm10 with pengus rom also, not sure if others have reported.
Baseband- v30a
Ril- Default.
kekks said:
Hey Tony Thanks for the great work, I have used your previous build, call rejecting is working fine with the first build. Downloading the current 2nd build.
Just a note: When on call if the speaker is activated, the opposite person voice seems to echo for them, this was an issue on cm10 with pengus rom also, not sure if others have reported.
Baseband- v30a
Ril- Default.
Click to expand...
Click to collapse
Just wanted 2 say Tony that i'am testing your latest build of cm10.1 and it works helluva smooth
Everything works as it should,smoothest rom so far :good:
Tony,
Do you think HDMI output can also be corrected?
Just flashed it. No problems so far.
tonyp which kowalski kernel do you use? i don't see the kowalski manager. can I flash the latest exp?
Guys, I especially asked you to test call rejecting and post the result with your baseband - and there's not a single reply regarding that.
I do not care if it's smooth or the best or whatever, I wanna make progress with fixing the bugs as long as I got some spare time.
If no one helps in fixing bugs I'll pull the public testbuilds and we do it in a closed testing circle (which will take longer) - that's up to you.
chp2 said:
Tony,
Do you think HDMI output can also be corrected?
Click to expand...
Click to collapse
It can, yes. But it's a mess, unless we get the decompiler by a friends of pengus I doubt we will look further into it.
More details in the dev discussion section.
optimusG said:
Just flashed it. No problems so far.
tonyp which kowalski kernel do you use? i don't see the kowalski manager. can I flash the latest exp?
Click to expand...
Click to collapse
Oh yes, this is important:
Flash the latest pengus kernel on top of this ROM if you want to use it as a daily driver!
There's just a testkernel included.
Just to be sure - it'll need the ICS-bootloader/partition table, correct ? I'm gonna hijack my son's p990 in 6-7 hours so I can test on it all night. If I remember correctly its on v10a BB.
These typos came from my Nexus 7
Reptilez_DK said:
Just to be sure - it'll need the ICS-bootloader/partition table, correct ? I'm gonna hijack my son's p990 in 6-7 hours so I can test on it all night. If I remember correctly its on v10a BB.
These typos came from my Nexus 7
Click to expand...
Click to collapse
Downloading the testbuild too, will flash it soon running V30A BB.. But call rejecting... Am I right if this is what you mean by it:
- Make someone call
- Reject the call
If so, I can have it tested and brought you the results within the next hour...
PS: Good thing this isn't in the development section = noobs allowed here yaaay
Before to annoy Tony, anyone experience very slow UMS mode file transferts in both ways (read & write to flash) on CM10.1?.
I can't write at more than 6MB/s and read at 10MB on my class10 SD (no matter of I/O scheduler). The same SD does 15MB write on ICS and 10MB on CM10.
Okaaaay, flashed it over full wipe, as mentioned with V30A BB. Called up my phone from another phone, rejected it and it went well. If that was a proper test: Success
PS: For heavens sake, with the final CM10.1 release, please do make an option to disable that CRT animation. Every time I see that animation I am seconds away from throwing the phone out the window. Makes me crazy every time
Edit: This is impossible to become a daily driver. Why? Go outside. Stand in the sun. Pick up your phone. Turn it on. Good luck guessing where the icons are on your screen. Brightness goes so low, that I can barely see anything while indoors, imagine outside then.
PA CM10 will always shine on my phone and thats what I'm going to let it do for a long time, a very long time. Bye-bye CM10.1
I can confirm it works with V30A as well.
Natalya, give it is some time, wait till the final product has arrived. That brightness thing was a fail by Google, nothing to do about it.
I have dual boot on my phone, PA11 as the main and CM10.1 testbuilds as secondary. Honestly, I am having difficulties seeing a CM10.1 ROM becoming my daily driver too, but penguins can make a lot of things change, we all know that
I just checked it on V30A as well with the build from post #4, and I can say that call reject works flawlessly.
I know that this isn't the purpose of this testing build, but I just wanted to say that automatic NITZ fix doesn't work for me and even though it detects that my timezone is GMT +3 the time itself is GMT. (I don't even know if that fix is already implemented here so if it isn't, my bad )
And anyways great work Tony!
Call reject on V30a working flawlessly here too
guys a question.
red frame is displayed? In the version of day 16.
by that I do not appear.
with 15 if. that was experimental as tonyp said
greetings and thanks.
clashman90 said:
guys a question.
red frame is displayed? In the version of day 16.
by that I do not appear.
with 15 if. that was experimental as tonyp said
greetings and thanks.
Click to expand...
Click to collapse
Disabled on version of the 16th
Is it just me or by setting the phone to automatic brightness, the low brightness bug disappers.
Sent from my LG-P990 using xda premium
Hello everybody,
so now this is my first posting.
I took an advantage on ebay to get me a near new I9000 for a low price. I was interested to see how Android smartphones
work, what is inside and how to customize.
In between time and after reading much about ROM's and Kernels and so on i decided to go for the CyanogenMod ROM by pawitp.
When i finally got my I9000 to my surprise it was already rooted and had a CM11 flavor onboard.
So i took the chance and made a backup and did a full wipe etc.. and got the latest Nightly (2014_04_22) and the gaaps up
and running quite nicely.
No problems so far.
Everything is fine except the in-call volume on the handset.
Speaker volume and headset volume seem quite o.k. and are manageable through DSP Manager .
However, the earpiece volume is maxed-out but still much lower than on my stock S3 mini, which was given to me by my employer.
Stock and beyond any rooting or so...understandable?
So i read a lot and tried various apps (one after the other) (Voodoo sound, Volume+ to name two) as recommended here.
No avail. Volume of the earpiece seems to be quite a different beast.
What i did not try, and hopefully will not have to, are Meltus Volume hacks or manipulating values by the service codes.
So, does anybody have an idea if the CM11 will get around this problem one day or the other?
I do not want to use another ROM nor do i feel i want another Kernel to mix with.
Perhaps this thread is obsolete, so please put me into the right direction if so.
Or, maybe someone who is allowed to do so can transport this Q into the ROM thread of pawitp.
Thank you all for you attention and have a nice day.
fa-schmidt said:
Hello everybody,
so now this is my first posting.
I took an advantage on ebay to get me a near new I9000 for a low price. I was interested to see how Android smartphones
work, what is inside and how to customize.
In between time and after reading much about ROM's and Kernels and so on i decided to go for the CyanogenMod ROM by pawitp.
When i finally got my I9000 to my surprise it was already rooted and had a CM11 flavor onboard.
So i took the chance and made a backup and did a full wipe etc.. and got the latest Nightly (2014_04_22) and the gaaps up
and running quite nicely.
No problems so far.
Everything is fine except the in-call volume on the handset.
Speaker volume and headset volume seem quite o.k. and are manageable through DSP Manager .
However, the earpiece volume is maxed-out but still much lower than on my stock S3 mini, which was given to me by my employer.
Stock and beyond any rooting or so...understandable?
So i read a lot and tried various apps (one after the other) (Voodoo sound, Volume+ to name two) as recommended here.
No avail. Volume of the earpiece seems to be quite a different beast.
What i did not try, and hopefully will not have to, are Meltus Volume hacks or manipulating values by the service codes.
So, does anybody have an idea if the CM11 will get around this problem one day or the other?
I do not want to use another ROM nor do i feel i want another Kernel to mix with.
Perhaps this thread is obsolete, so please put me into the right direction if so.
Or, maybe someone who is allowed to do so can transport this Q into the ROM thread of pawitp.
Thank you all for you attention and have a nice day.
Click to expand...
Click to collapse
It might be the highest limit to the i9000 (It's an old phone, at least appreciate it for even running). However, I suggest you do change your ROM once, just to check if it is a problem with your ROM. If you do change, I suggest trying Paranoid Android or OmniROM. At times, the Kernel might also make a change. If again you do want to change your Kernel, I suggest Semaphore 3.4.3 or Mackay Kernel
Hit Thanks if I helped!
Gokulbalram said:
It might be the highest limit to the i9000 (It's an old phone, at least appreciate it for even running). However, I suggest you do change your ROM once, just to check if it is a problem with your ROM. If you do change, I suggest trying Paranoid Android or OmniROM. At times, the Kernel might also make a change. If again you do want to change your Kernel, I suggest Semaphore 3.4.3 or Mackay Kernel
Hit Thanks if I helped!
Click to expand...
Click to collapse
Thank you for the answer.
Sure: You are right it is an "old" phone.
And i appreciate the work of the volunteers to keep it up and running.
Hopefully i will find the time during the next days to follow your advice.
Maybe i will even try to go back to stock and check how the phone behaves in it's original environment.
At the moment i am puzzled by another problem. I miss FM radio so much.
Seems as if this feature is missing in a whole lot of ROMs because of massive changes of the "ekosystem" to put it in my words.
But this is not the thread for that. I have to read and learn a lot.
Again, thank you.
Regards,
Frank
fa-schmidt said:
Thank you for the answer.
Sure: You are right it is an "old" phone.
And i appreciate the work of the volunteers to keep it up and running.
Hopefully i will find the time during the next days to follow your advice.
Maybe i will even try to go back to stock and check how the phone behaves in it's original environment.
At the moment i am puzzled by another problem. I miss FM radio so much.
Seems as if this feature is missing in a whole lot of ROMs because of massive changes of the "ekosystem" to put it in my words.
But this is not the thread for that. I have to read and learn a lot.
Again, thank you.
Regards,
Frank
Click to expand...
Click to collapse
About the Radio thing, I think you can download another Radio app like this one. If that doesn't work, I'm guessing then Radio might be disabled in your ROM. Semaphore has the option of enabling or disabling FM Radio.
Gokulbalram said:
About the Radio thing, I think you can download another Radio app like this one. If that doesn't work, I'm guessing then Radio might be disabled in your ROM. Semaphore has the option of enabling or disabling FM Radio.
Click to expand...
Click to collapse
Ah, yes. I see. Thank you. Looks like Spirit2 from the play store.
I'll have a look into the reviews.
Regards,
Frank
fa-schmidt said:
Ah, yes. I see. Thank you. Looks like Spirit2 from the play store.
I'll have a look into the reviews.
Regards,
Frank
Click to expand...
Click to collapse
You. Must. Try. OmniROM. You. Will. Love. It.
fa-schmidt said:
Ah, yes. I see. Thank you. Looks like Spirit2 from the play store.
I'll have a look into the reviews.
Regards,
Frank
Click to expand...
Click to collapse
Any news yet?
Gokulbalram said:
Any news yet?
Click to expand...
Click to collapse
Yes.
I went back to the stable release CM10.2 .
Somewhere on the internet i found a free beta from Spirit2 and installed it just for a test.
It did not run smooth but i could grab FM and listen by speaker and headphones.
What made me nervous is the "speaker damage" disclaimer...
As for the in-call volume: With 10.2 it seems to be louder.
Headphones and speaker are fine but earpiece (or handset?) still is a bit quiet for to use in noisy environments.
But anyway. Before taking further action i test a while.
I want to use this phone as a private phone when i am on commissioning jobs. I often work at industrial sites and since i am not allowed
to make any private calls off my companies' S3 mini i thought it was a good idea to carry a relatively cheap and reliable smartphone
with me.
Besides the academical aspect to know what makes a smartphone work i want a useful and stable operating system without any bloatware.
I will keep in touch with the CM11 thread and from time to time check if they finally achieve a stable release.
Maybe a shoot a second SGS off ebay just to look after OMNI ROM as you suggested. :laugh:
By now i will stay with the CM10.2 and see if it is stable.
And yes, i am going to root my wifes's Xperia Pro
Thanks again for your attention!
Regards,
Frank
fa-schmidt said:
Yes.
I went back to the stable release CM10.2 .
Somewhere on the internet i found a free beta from Spirit2 and installed it just for a test.
It did not run smooth but i could grab FM and listen by speaker and headphones.
What made me nervous is the "speaker damage" disclaimer...
As for the in-call volume: With 10.2 it seems to be louder.
Headphones and speaker are fine but earpiece (or handset?) still is a bit quiet for to use in noisy environments.
But anyway. Before taking further action i test a while.
I want to use this phone as a private phone when i am on commissioning jobs. I often work at industrial sites and since i am not allowed
to make any private calls off my companies' S3 mini i thought it was a good idea to carry a relatively cheap and reliable smartphone
with me.
Besides the academical aspect to know what makes a smartphone work i want a useful and stable operating system without any bloatware.
I will keep in touch with the CM11 thread and from time to time check if they finally achieve a stable release.
Maybe a shoot a second SGS off ebay just to look after OMNI ROM as you suggested. :laugh:
By now i will stay with the CM10.2 and see if it is stable.
And yes, i am going to root my wifes's Xperia Pro
Thanks again for your attention!
Regards,
Frank
Click to expand...
Click to collapse
Xperias are a tough nut to crack. But, you will have fun rooting it. It took me 3 days (Spent 4 hours each) to get root and Install CM on an Xperia Arc S!
Just a small update
Gokulbalram said:
Xperias are a tough nut to crack. But, you will have fun rooting it. It took me 3 days (Spent 4 hours each) to get root and Install CM on an Xperia Arc S!
Click to expand...
Click to collapse
I got me another i9000 for cheap.
Running OMNI KitKat for now with nightly build.
That is a really nice ROM with a smooth feel and just as customizable as a an average user with passion for android can manage.
So thank you, Gokulbalram for the hint.
fa-schmidt said:
I got me another i9000 for cheap.
Running OMNI KitKat for now with nightly build.
That is a really nice ROM with a smooth feel and just as customizable as a an average user with passion for android can manage.
So thank you, Gokulbalram for the hint.
Click to expand...
Click to collapse
Try Neo Kernel along with it! (Why'd you get two? *Starts laughing*)
Gokulbalram said:
Try Neo Kernel along with it! (Why'd you get two? *Starts laughing*)
Click to expand...
Click to collapse
I need one cellphone for "productive use". Means that is has to work.
So to try something, and run the risk of having software or hardware problems for a few days, i need another device.
Plus it is nice to see how official CM11 and official OMNI CM11 compete.
At the moment i would say that OMNI is a little bit upfront. I am going to ask my son to put his SIM card to
it and try out and see if it is stable.
fa-schmidt said:
I need one cellphone for "productive use". Means that is has to work.
So to try something, and run the risk of having software or hardware problems for a few days, i need another device.
Plus it is nice to see how official CM11 and official OMNI CM11 compete.
At the moment i would say that OMNI is a little bit upfront. I am going to ask my son to put his SIM card to
it and try out and see if it is stable.
Click to expand...
Click to collapse
At the moment, my i9000 runs Omni's latest nightlies. Also, I've flashed Neo Kernel. It's very smooth without much noticeable lag.
Head over to the main G4 development page if you are interested in this for the H811/H815.
http://forum.xda-developers.com/g4/development/h811-h815-blisspop-cyanogenmod-12-1-t3185593
There's still a long way to go. Most things are still broken and new builds will generally break things on a regular basis. Just be aware before heading over. The post doesn't need more Posts saying goodbye this/that isn't working, it's still very much a WIP.
Sent from my LG-H815 using Tapatalk
IIIIkoolaidIIII said:
There's still a long way to go. Most things are still broken and new builds will generally break things on a regular basis. Just be aware before heading over. The post doesn't need more Posts saying goodbye this/that isn't working, it's still very much a WIP.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
True, and the OP doesn't have the most recent build where most stuff is actually working. I'm running the 10/15 build (page 76-78...somewhere in there, posted by codeworkx) and most of my audio is working. Haven't tried bluetooth, but I rarely use it, apparently voice calls have an echo, but I never call anyone, either. The only thing I really use that has an issue is the camera that delays on opening, but I'm sure that'll be worked out shortly. As soon as codeworkx got to work on it, it's honestly been pretty stable for a WIP, but I think I have a higher tolerance for broken builds and features, having been a crackflasher for 7 years now. I'm just happy to be back on AOSP/CM at this point with this phone.
schreckles said:
True, and the OP doesn't have the most recent build where most stuff is actually working. I'm running the 10/15 build (page 76-78...somewhere in there, posted by codeworkx) and most of my audio is working. Haven't tried bluetooth, but I rarely use it, apparently voice calls have an echo, but I never call anyone, either. The only thing I really use that has an issue is the camera that delays on opening, but I'm sure that'll be worked out shortly. As soon as codeworkx got to work on it, it's honestly been pretty stable for a WIP, but I think I have a higher tolerance for broken builds and features, having been a crackflasher for 7 years now. I'm just happy to be back on AOSP/CM at this point with this phone.
Click to expand...
Click to collapse
I hope nobody thought I was saying it is ready for prime time! Just a heads up. I have not installed it yet as I will wait for a more highly functioning build, but I also know there is a thirst for development here, so I wanted to share the good news!!
Honestly, if you were to try the 10/15 build, you'd be surprised at how "ready from prime time" it actually is. I've been using it as my DD for the last 2 days and it's actually been pretty nice. Couple small things here and there, but the only thing that's affected me at all so far was the camera delay. Now that there's at least a dev or two that seems like they know what they're doing, I'm hoping development for AOSP/CM stuff starts picking up. The little time that codeworkx has put in so far has been looking extremely promising. (Not to take away from the OP on that, but code made it so that I can actually use it as a DD with sound.)
schreckles said:
Honestly, if you were to try the 10/15 build, you'd be surprised at how "ready from prime time" it actually is. I've been using it as my DD for the last 2 days and it's actually been pretty nice. Couple small things here and there, but the only thing that's affected me at all so far was the camera delay. Now that there's at least a dev or two that seems like they know what they're doing, I'm hoping development for AOSP/CM stuff starts picking up. The little time that codeworkx has put in so far has been looking extremely promising. (Not to take away from the OP on that, but code made it so that I can actually use it as a DD with sound.)
Click to expand...
Click to collapse
Hmmm, I didn't realize it was that far along. Between the 815 talk there, it has become tough to follow. I may give it a go. I assumed you did a complete wipe before installing? Thanks, @schreckles
EDIT: You don't use bluetooth I see, and I do quite a bit. From what I understand, that doesn't work, so that's a non-starter for me. Guess I'll wait.
ShermCraig said:
Hmmm, I didn't realize it was that far along. Between the 815 talk there, it has become tough to follow. I may give it a go. I assumed you did a complete wipe before installing? Thanks, @schreckles
Click to expand...
Click to collapse
Yup, sure did. Full wipe (especially when switching back and forth between CM/AOSP and stock roms) and then flashed the 10/15 H811 build that codeworkx posted the other day, along with the nano gapps he'd suggested.
Small issues: Your LED will stay lit up blue until you plug the phone in and unplug again. No biggie. No "OK Google" or anything that requires the phone mic for me thus far (ie Google Sound Search.) Camera takes approximately 4 years to open, but it does open, and the shots it produces aren't bad. They aren't as good as stock, but that's typically been the trade-off even since back in my OG Droid days when going from stock to non-stock base. Call audio, bluetooth, and NFC apparently have some issues still, but I rarely use any of those, so meh. Oh, and I get a popup stating "Settings has closed" every so often, but it doesn't affect anything. I'm sure I could find the cause if I was motivated, but I'm sure it'll get worked out soon enough.
...Mostly just stuff I can live without for now that's broken. I've even been using Xposed and some of my favorite modules without any ill effects.
So is it more or less a theme now or what? I know what CM is, but as far as functionality, is it quite a bit faster than stock or what?
Thanks!
I am assuming that this is the only public aosp build for the G4?
maximus20895 said:
So is it more or less a theme now or what? I know what CM is, but as far as functionality, is it quite a bit faster than stock or what?
Thanks!
Click to expand...
Click to collapse
It's a completely different build of Android using different frameworks and whatnot. It's built upon AOSP and tweaked framework to make it CyanogenMod. I'm not sure if the one I am using currently is the one in this thread but so far it's been pretty smooth. There are definitely some issues but it's a lot further along than I though it would be. Kudos to those guys!
EDIT: That is the same build I am using (in case anyone is wondering).