Related
Here is a 4.3 ROM built from AOSP source designed to emulate what a Verizon 4.3 ROM would be like. The changes from AOSP include the addition of GAPPS, addition of Verizon apps, appropriate binaries so everything works, addition of busybox, correct eri.xml, home screen layout to mimic a stock ROM, and the removal of the tethering restriction. The ROM is not pre-rooted, so flash Chainfire's SuperSU if you want root.
As usual, flash at your own risk and post any successes or problems.
Download Link(s) for v4.0: MD5: be4377ab16432112f09d18ae37c91041
DOWNLOAD via Goo.im
Cubby.com MIRROR
SuperSU v1.51 - you may want to check for a more recent version if this link becomes outdated. Flash after you flash the ROM.
Bugs - text-to-speech may not work correctly. Please flash fix attached to this post after flashing the ROM. Thanks AndroJak!
MODS:
Extended Power Menu - CM style
- Ability to reboot, hot reboot, reboot recovery, & reboot bootloader.
- Replaces /system/framework/android.policy.jar
- Thanks to Cyanogenmod and xIC-MACIx
- DOWLOAD
- MIRROR
Thanks to mmuzzy for help building from aosp (fixing t-cdma64 in eri.xml and cell broadcasts menu, plus other stuff I'm probably forgetting), adrynalyne, and djp952 for help building from AOSP.
mwalt2 said:
Here is a stock, rooted, busybox, etc. ROM built from the 4.1.1 AOSP source for Verizon. It has GAPPS included from the GSM developer preview and the Verizon apps as well (MyVerizon and the backup one). My attempt was to make a stock rooted ROM for Verizon based off of the 4.1.1 source on AOSP. Some things are still added to this rom from 4.0.4 IMM76K Verizon ROM, but I did include the new binaries for toro. I haven't fully tested everything, but camera, google now, gps, and wifi all work as expected. I'll try to get some add-on's / mods before too long and have them posted as flashable .zips.
As usual, flash at your own risk and post any successes or problems.
Download Link(s):
about 5 min or so....
Click to expand...
Click to collapse
first cant wait!!! ^.^
Here we go!!!!!
Is Google Now working? I know mmuzzy was having issues on his AOSP ROM. Either way, I'll give 'er a test once the download links are available.
Download for 1 server is ready now. I'll get a mirror up as well.
BrandT90 said:
Is Google Now working? I know mmuzzy was having issues on his AOSP ROM. Either way, I'll give 'er a test once the download links are available.
Click to expand...
Click to collapse
Yes, it's working. I asked it how long a bridge was and it read the answer back to me. I haven't done much more than that though yet.
Downloading. Looking forward to this. Thanks Mwalt for sharing!!!
Quick DL as well. 2 minutes has got to be a new record for a JB rom
BrandT90 said:
Is Google Now working? I know mmuzzy was having issues on his AOSP ROM. Either way, I'll give 'er a test once the download links are available.
Click to expand...
Click to collapse
OP says Google Now is working. I'm downloading now.
excellent. you're a regular johnny on the spot!
downloading now, hope its all good! i'm looking for a "stock jb" style rom of the newest update. ill post my outcome shortly. going to test the basics that are supposed to work.
Is a flash to the JB bootloader recommended? Finally, a build that seems to have all/most components working! No issues with the 4G's or the LTE's?? Lol.
Galaxy Nexus - Slim ICS 4.2
Downloading now. Any thoughts on current JB kernel compatibility?
i wiped data, cache and dalvik cache 2x each, installed and installed trinity kernel on top and hit reboot. (i like trinity for the colors and such, and good battery life ).
first boot took a minute.
updating some apps and gonna test some things.
still getting t-cdma 64 as a carrier
mwalt2 said:
Here is a stock, rooted, busybox, etc. ROM built from the 4.1.1 AOSP source for Verizon. It has GAPPS included from the GSM developer preview and the Verizon apps as well (MyVerizon and the backup one). My attempt was to make a stock rooted ROM for Verizon based off of the 4.1.1 source on AOSP. Some things are still added to this rom from 4.0.4 IMM76K Verizon ROM, but I did include the new binaries for toro. I haven't fully tested everything, but camera, google now, gps, and wifi all work as expected. I'll try to get some add-on's / mods before too long and have them posted as flashable .zips.
As usual, flash at your own risk and post any successes or problems.
Download Link(s):
DOWNLOAD from Dev-Host
MD5: 8383b87cc2f9e5b510807c3034052ffe
Click to expand...
Click to collapse
Any issues in this build? Also, what are the install instructions?
when going to sounds to set ringtones i have a lot of doubles of default ringtones, wonder where i can remove them?
^System/media/ringtones maybe?
Galaxy Nexus - Slim ICS 4.2
works well so far. thanks!
xweaponx said:
Downloading now. Any thoughts on current JB kernel compatibility?
Click to expand...
Click to collapse
I've always used stock, so I can't really comment. Now that source is out, I'd expect the JB kernels to work better.
imablackhat said:
still getting t-cdma 64 as a carrier
Click to expand...
Click to collapse
No sure what causes this, but I've never seen it with this build or the previous developer preview build. Did it happen on first boot before you installed anything else?
tycoon177 said:
Any issues in this build? Also, what are the install instructions?
Click to expand...
Click to collapse
I'd recommend a full factory reset, but people can try what they feel comfortable with. Personally, I did a factory reset, wiped both caches, and then flashed the ROM (with TWRP).
imablackhat said:
when going to sounds to set ringtones i have a lot of doubles of default ringtones, wonder where i can remove them?
Click to expand...
Click to collapse
Do you have any on your sdcard partition in the Ringtones folder? If not, I'd check \system\media\audio path (subfolders for ringtones, alarms, etc). Delete any duplicates you find in there. I don't have any duplicates and there aren't any in the rom.zip I uploaded.
just overwrote mms.apk in system/apps to get the custom pink mms, and got a quick reboot to my boot screen, this never happened on 4.1 roms that weren't source, don't know if this is normal because i replaced the app and it was a one time thing (i hope). as far as going to system/media/ringtones, i see them but there arent any doubles, however theres doubles when i go to select a ringtone from the menu, for everything system related, ringtones and notifications.
What issues have people had? Any boot issues?
I replaced the "stock" keypress ogg files from ics/jelly bean that sound better with this 4.1.1 release, the new key click sounds are horrible. works fine. i used to have t-cdma 64 with any build from 4.1.1 there is a fix that works that ill just apply. its a xml file or something.
I'm looking for a stable Android 4.0 or above ROM which can be flashed using Odin. Any threads or links?
zacszy said:
I'm looking for a stable Android 4.0 or above ROM which can be flashed using Odin. Any threads or links?
Click to expand...
Click to collapse
Well I am not aware of any 4.0 or above ROMs that can be flashed via ODIN. I am sure if any developer wants, they may be able to do it but I really think that flashing via recovery is always a better choice compared to ODIN. I see no advantage for ODIN flash...
Do you mind telling me why do you need odin flash???
Well..
thearif said:
Well I am not aware of any 4.0 or above ROMs that can be flashed via ODIN. I am sure if any developer wants, they may be able to do it but I really think that flashing via recovery is always a better choice compared to ODIN. I see no advantage for ODIN flash...
Do you mind telling me why do you need odin flash???
Click to expand...
Click to collapse
Well, I'm more familiar with Odin flashing compared to recovery mode, and it's a whole lot easier compared to other flashing methods. I don't find that the recovery mode is easy to understand, so you mind to provide me the steps (better if they are easier to understand and follow) and also a link to a stable Android 4.0 Rom?
zacszy said:
Well, I'm more familiar with Odin flashing compared to recovery mode, and it's a whole lot easier compared to other flashing methods. I don't find that the recovery mode is easy to understand, so you mind to provide me the steps (better if they are easier to understand and follow) and also a link to a stable Android 4.0 Rom?
Click to expand...
Click to collapse
Do you have root access on your phone? Every step is actually quite easy to follow. There are really good guides on both general and development sections. But beforewe delve into howto's you should clarify what constitutes STABLE for you...
We have ICS (4.04) as well as JB ( 4.1.2 and 4.2.2) in the development section. All are pretty good but here and there they may have some bugs. Just go to their threads check them out. On the very first page of a ROM thread what works and what doesn't are listed. Decide whether you can live with one of them then we can talk about howto's.
I recommend CM9, CM10 and CM10.1 all from the developer arco68...
OHHH with a custom recovery, you don't even need a computer to flash a new ROM. That surely is a bonus...
Sent from my GT-I8150 using xda app-developers app
Okay..
thearif said:
Do you have root access on your phone? Every step is actually quite easy to follow. There are really good guides on both general and development sections. But beforewe delve into howto's you should clarify what constitutes STABLE for you...
We have ICS (4.04) as well as JB ( 4.1.2 and 4.2.2) in the development section. All are pretty good but here and there they may have some bugs. Just go to their threads check them out. On the very first page of a ROM thread what works and what doesn't are listed. Decide whether you can live with one of them then we can talk about howto's.
I recommend CM9, CM10 and CM10.1 all from the developer arco68...
OHHH with a custom recovery, you don't even need a computer to flash a new ROM. That surely is a bonus...
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
I have root access on my phone. Well, I don't see the ROM thread that you mentioned. Stable means that the ROM is not easy to crash or eats up my RAM even when I'm not using it, while common bugs are still acceptable if they can be fixed (I can't find threads from arco68, so I don't know what you mean by his CM9 and all those so...)
Hope you can enlighten me more about this recovery method and the difference between the CMs (if possible, also include any differences between ICS and JB b'coz I don't know which one to choose)
Recovery is super easy:
Download the zip and put it on your SD (internal or external, makes no difference)
Then turn of your phone
Press and hold Volume up + Power button + home button
Once the screen turns on, release the power button, but keep holding onto the other two
Then the recovery menu shows up
choose install zip from SD
select the zip and hit install
finished
Here are the links, with more detailed instruction on how to do it
CM10.1
http://forum.xda-developers.com/showthread.php?t=2214042
CM10
http://forum.xda-developers.com/showthread.php?t=1990795
CM9
http://forum.xda-developers.com/showthread.php?t=1576874
Ups and downs?
Are there any down sides regarding the CM9 mod? And can I change the shortcuts on the lockscreen if I install CM9?
And also, what is CWM actually? I don't understand from the FAQs in the forums or other sites, so can you tell me what CWM is (CWM5 or CWM6) and how to access or install that?
Sorry, I'm really considered a total newbie in this sort of stuff 8(>o<)8
zacszy said:
Are there any down sides regarding the CM9 mod? And can I change the shortcuts on the lockscreen if I install CM9?
And also, what is CWM actually? I don't understand from the FAQs in the forums or other sites, so can you tell me what CWM is (CWM5 or CWM6) and how to access or install that?
Sorry, I'm really considered a total newbie in this sort of stuff 8(>o<)8
Click to expand...
Click to collapse
Its a kind of recovery, called ClockworkMOD. Now its the 6.0.3.0 version if I'm not wrong...
Linky: here
Okay, the process of installation of a custom recovery is tedious. Link: here DO NOT USE THE FILES IN THIS PAGE. JUST THE INSTRUCTIONS.
Now, flash the ROM (any of the three is fine. I personally recommend CM9 or 10 cus its in its RC stages, which means Resource... something)
The instructions is on the ROM page itself. And you're done. I or arco are not held responsible if your phone is screwed up in the process (very little chance) or
if your heart fails because its loading for a longer period than it should be.
HAVE FUN!
Sent from my 4.1 running Galaxy W.
iDelta said:
Now its the 6.0.3.0 version if I'm not mistaken.
Click to expand...
Click to collapse
In CM9, I see that the ClockworkMod needed is 5.5.xxxx, so wouldn't CM9 crash if i use the 6.0.3.0 version instead of 5.5.xxxx?
And also, does the CM9 have any bugs? Because I saw some in the posts by people about CM10 but not CM9 (refer to links of above comments)
Anyway, it is a pleasure to receive help from you and the person above.
zacszy said:
In CM9, I see that the ClockworkMod needed is 5.5.xxxx, so wouldn't CM9 crash if i use the 6.0.3.0 version instead of 5.5.xxxx?
And also, does the CM9 have any bugs? Because I saw some in the posts by people about CM10 but not CM9 (refer to links of above comments)
Anyway, it is a pleasure to receive help from you and the person above.
Click to expand...
Click to collapse
Well obviously, since its a custom ROM, its bound to have bugs. There's no such thing as a "perfect" ROM. And I have 6.0.1.something CWM and I have flashed every single ROM, from 9-10.1. So it shouldn't be a problem.
Sent from my 4.1 running Galaxy W.
zacszy said:
In CM9, I see that the ClockworkMod needed is 5.5.xxxx, so wouldn't CM9 crash if i use the 6.0.3.0 version instead of 5.5.xxxx?
And also, does the CM9 have any bugs? Because I saw some in the posts by people about CM10 but not CM9 (refer to links of above comments)
Anyway, it is a pleasure to receive help from you and the person above.
Click to expand...
Click to collapse
Man, if you want a stable rom, buy another phone.
iDelta said:
Well obviously, since its a custom ROM, its bound to have bugs. There's no such thing as a "perfect" ROM.
Click to expand...
Click to collapse
I believe I have caused some misinterpretation here. What I mean is that I want to know if there is anything that's not working in CM9. The stuff below is found from the CM9 thread.
What's working:
Audio
Receiving and making calls
GPS
Compass
Proximity sensor
Wifi
Bluetooth
USB mass storage
HW accelerated gui
HW accelerated video
Camera
Torch
Wifi and USB tethering
There isn't anything that's not shown as "not working", so I'm asking you about it just for confirmation.
If there isn't anything, I will flash CM9 soon. :laugh:
zacszy said:
I believe I have caused some misinterpretation here. What I mean is that I want to know if there is anything that's not working in CM9. The stuff below is found from the CM9 thread.
What's working:
Audio
Receiving and making calls
GPS
Compass
Proximity sensor
Wifi
Bluetooth
USB mass storage
HW accelerated gui
HW accelerated video
Camera
Torch
Wifi and USB tethering
There isn't anything that's not shown as "not working", so I'm asking you about it just for confirmation.
If there isn't anything, I will flash CM9 soon. :laugh:
Click to expand...
Click to collapse
Everything works fine.
For CM9 for sure.
Madzix said:
Everything works fine.
For CM9 for sure.
Click to expand...
Click to collapse
Yeah, CM9 is like the most stable out of the three... hardly any bugs
Sent from my 4.1 running Galaxy W.
iDelta said:
Its a kind of recovery, called ClockworkMOD. Now its the 6.0.3.0 version if I'm not wrong...
Linky: here
Okay, the process of installation of a custom recovery is tedious. Link: here DO NOT USE THE FILES IN THIS PAGE. JUST THE INSTRUCTIONS.
Now, flash the ROM (any of the three is fine. I personally recommend CM9 or 10 cus its in its RC stages, which means Resource... something)
The instructions is on the ROM page itself. And you're done. I or arco are not held responsible if your phone is screwed up in the process (very little chance) or
if your heart fails because its loading for a longer period than it should be.
HAVE FUN!
Sent from my 4.1 running Galaxy W.
Click to expand...
Click to collapse
I just noticed something in your post. Just to clarify, RC mean "Release Candidate" not resource something... Just so you know. First alpha's come, then beta's, and right before a FINAL version is released in which most of the bugs are squashed, a release candidate comes to make sure everything is working. If for example, no bugs remain in a release candidate, it is renamed to FINAL as far as I know
However, there are different understanding of these names on the internet. For example, for some, once a product is in a BETA phase, no more new features added from there on. However, that may not be true for CM releases here, I am not sure.
and @zacszy, both CM9 and CM10 are pretty stable. I have not encountered any show stopping bugs but that maybe because of the way I use my phone, as I dont play games. I use it mostly for productivity, internet surfing, couple of youtube videos, music...
Try them all. I am sure you will pick one that suits your needs..
thearif said:
both CM9 and CM10 are pretty stable. I have not encountered any show stopping bugs but that maybe because of the way I use my phone, as I dont play games. I use it mostly for productivity, internet surfing, couple of youtube videos, music...
Click to expand...
Click to collapse
Really appreciate your help @thearif and I would definitely try them out before really settling in with the CM I want
thearif said:
I just noticed something in your post. Just to clarify, RC mean "Release Candidate" not resource something... Just so you know. First alpha's come, then beta's, and right before a FINAL version is released in which most of the bugs are squashed, a release candidate comes to make sure everything is working. If for example, no bugs remain in a release candidate, it is renamed to FINAL as far as I know
However, there are different understanding of these names on the internet. For example, for some, once a product is in a BETA phase, no more new features added from there on. However, that may not be true for CM releases here, I am not sure.
and @zacszy, both CM9 and CM10 are pretty stable. I have not encountered any show stopping bugs but that maybe because of the way I use my phone, as I dont play games. I use it mostly for productivity, internet surfing, couple of youtube videos, music...
Try them all. I am sure you will pick one that suits your needs..
Click to expand...
Click to collapse
Thanks for the definition. Just saying, you can't call it fully stable cuz .... well that's impossible. It is only nearly stable.... you may have not said it but I'm just saying. Haha
Can your single core run 4.1? My Galaxy W can! That's how I sent this!
---------- Post added at 11:30 PM ---------- Previous post was at 11:29 PM ----------
zacszy said:
Really appreciate your help @thearif and I would definitely try them out before really settling in with the CM I want
Click to expand...
Click to collapse
Good luck :thumbup:
Can your single core run 4.1? My Galaxy W can! That's how I sent this!
I read about an omnirom available for our captivate glides running 4.4.2
Anyone tried running this yet? How stable is it?
I found the link here: http://true-android.blogspot.ca/2014/03/update-samsung-captivate-glide-sgh-i927.html
I also dont know, for any rom that has separate gapps, when would you flash those? After or before the new rom? at the same time? Like, if after a ROM flash it automatically reboots, it will boot up with no gapps and likely not run - correct?
Was just curious about how buggy it is. Even if down the road when things are smoother, im excited to see if i can get this one running!
Pawprints1986 said:
I read about an omnirom available for our captivate glides running 4.4.2
Anyone tried running this yet? How stable is it?
I found the link here: http://true-android.blogspot.ca/2014/03/update-samsung-captivate-glide-sgh-i927.html
I also dont know, for any rom that has separate gapps, when would you flash those? After or before the new rom? at the same time? Like, if after a ROM flash it automatically reboots, it will boot up with no gapps and likely not run - correct?
Was just curious about how buggy it is. Even if down the road when things are smoother, im excited to see if i can get this one running!
Click to expand...
Click to collapse
you can find more information here: http://forum.xda-developers.com/showthread.php?t=2541182
Gapps is included. You must install rom zip first, because it formats system partition.
Official gapps doesnt compatible with our phone, I think its better not installing.
hmm..
Pawprints1986 said:
I read about an omnirom available for our captivate glides running 4.4.2
Anyone tried running this yet?
Was just curious about how buggy it is. Even if down the road when things are smoother, im excited to see if i can get this one running!
Click to expand...
Click to collapse
I am using omni ROM . . somehow I find it less buggy than cm 11
Nevertheless I would wanna give my thanks and even though I am pointing out bugs . . I really do appreciate his work .. A lot
Omnirom is very very stable has all if not most of the theming features except for trebuchet launcher
//It is a bit more battery consuming but I like it cause I am able to run my processor at 1.4ghz which is sweeeet!!!
//It has issues with OK Google functionality the audio is lagged and irritating
//The Google experience launcher is not built for it
//It has issues with Google maps 7 but there is a fix to have 6th version to back you up when needed
//it has issues with Skype and the fix is work in progress I guess..
//GPs is a bit slow but works
//WiFi direct crashes for me
Once in a blue moon the phone might rebot itself cause of a crash..
Though considering WiFi tethering , 3g switching, link2sd ,memory swapping
Ksm everything is working really try it . . its an amazing experience from an amazing phone
Can someone tell me the difference between wifi direct, wifi sharing, and wifi sharing manager??
Wifi itself is working in 4.4.2 right?
Also, were your keyboard backlights working automatically or did you ened qwerty led?
is qwerty led something that needs to be running all the time. or "ongoing" in the top drawer?
Wi-fi direct is a type of communication between two devices, similar to Bluetooth, so you can send files. I never used this, even when transfering big files from one phone to another, it's better to use an USB OTG cable - the connection speed is lightning fast!
Don't know what you mean about wi-fi sharing. Maybe wi-fi tethering (hotspot) - it's when you share your phone 2G/3G internet connection via wi-fi. This thing is working fine. Wi-fi itself is working, of course.
As for keyboard light: when tested OmniROM, I used liblight solution, but the qwertyled using is simple too: just launch it and you're done. While the service is running, keyboard light will work.
Now I'm on CM 11, and I have 11 days of uptime already, I recommend this ROM (but that's just my taste). In CM 11 keyboard backlights are working from the box, no need for qwertyled.
Also, I looked at the link you posted, to the true-android blog. Please, don't use the guide one can found there, it's awful. You can't install 4.4.2 ROM with recommended 2.6.3.0 TWRP, the correct one is 2.6.3.1 from bubor here, and you don't need any gapps beside included in the ROM.
Better use this guide from stormdude124: [UPDATED][2014][How-to]Everything you need to know and do to your Captivate Glide, it's updated, it's verified and there's no ads!
Makshow said:
Now I'm on CM 11, and I have 11 days of uptime already, I recommend this ROM (but that's just my taste). In CM 11 keyboard backlights are working from the box, no need for qwertyled.
Also, I looked at the link you posted, to the true-android blog. Please, don't use the guide one can found there, it's awful. You can't install 4.4.2 ROM with recommended 2.6.3.0 TWRP, the correct one is 2.6.3.1 from bubor here, and you don't need any gapps beside included in the ROM.
Better use this guide from stormdude124: [UPDATED][2014][How-to]Everything you need to know and do to your Captivate Glide, it's updated, it's verified and there's no ads!
Click to expand...
Click to collapse
Can you use a cyanogen mod rom with clockworkmod recovery installed? i remember trying cyanogenmod with my phone and couldnt get it to work.
Just flash TWRP 2.6.3.1 from link above, it's superior to clockworkmod recovery (CWM) in all ways: touch interface, working backups with compression, charging support and it allows to install KitKat roms. With CWM you can install ROMs up to android 4.3, so, you still can install CM 10.1.3 or CM 10.2 with CWM, but not CM 11.
about wifi direct and sharing...
Pawprints1986 said:
Can someone tell me the difference between wifi direct, wifi sharing, and wifi sharing manager??
Wifi itself is working in 4.4.2 right?
Also, were your keyboard backlights working automatically or did you ened qwerty led?
is qwerty led something that needs to be running all the time. or "ongoing" in the top drawer?
Click to expand...
Click to collapse
Hey yeah the difference btw wifi direct and sharing is that in wifi direct you connect two devices directly to transfer files...
in wifi sharing you need to host a web adress to share your files
as a result in wifi sharing you host a list of your stuff on a web adress(local) which gets downloaded by other devices on your wifi connection
and a wifi sharing manager can either do this (host ur files using an ip) or my personal favorite is astro which can acess my pc's sharing folder over wifi which is preety awesome>..unlimited storage
also note that in a wifi sharing manager you cannot recieve files easily . . maybe airdroid but it can only run on a pc
wifi sharing apps are airdroid and other file managers like root browser
wifi direct requires specific drivers and libs... i guess.. hence not all devices can do it ..
anyway you should go for cm 11 or omni both are incredibly stable with an occasional hiccup.. which is occasional heh
also would suggest that if you do proceed to install please follow from the developer sources on xda rather than some blog etc
Hello everybody,
I,ve read all around the forum but I couldn´t find information about my problem so i try it here.
From stock V500 20d I rooted and Installed TWRP 2.7.1.0 thanks to the good information in the Forum. After that, I've installed the ROM CM11 (M10) and, from the first reboot, the screen bright is very low. I hardly could do the first configuration and when it finished I selected the full bright.
After some time working it seems that it recovers some bright and I can down a little bit the bright from top.
Every time I restart the device I have the same bright issue.
Can anyone help me?.
Thanks a lot
reypescador said:
Hello everybody,
I,ve read all around the forum but I couldn´t find information about my problem so i try it here.
From stock V500 20d I rooted and Installed TWRP 2.7.1.0 thanks to the good information in the Forum. After that, I've installed the ROM CM11 (M10) and, from the first reboot, the screen bright is very low. I hardly could do the first configuration and when it finished I selected the full bright.
After some time working it seems that it recovers some bright and I can down a little bit the bright from top.
Every time I restart the device I have the same bright issue.
Can anyone help me?.
Thanks a lot
Click to expand...
Click to collapse
Extremely common problem when you were on the 4.4.2 base and are now an AOSP based rom. You either need to change kernels to RedKernel or flash the tablet back to the 4.2.2 base and then reflash your CM rom.
RedKernel info is here: http://forum.xda-developers.com/lg-g-pad-83/development/kernel-redkernel-t2856297
4.2.2 base info is here: http://forum.xda-developers.com/showthread.php?t=2719411
muiriddin said:
Extremely common problem when you were on the 4.4.2 base and are now an AOSP based rom. You either need to change kernels to RedKernel or flash the tablet back to the 4.2.2 base and then reflash your CM rom.
RedKernel info is here: http://forum.xda-developers.com/lg-g-pad-83/development/kernel-redkernel-t2856297
4.2.2 base info is here: http://forum.xda-developers.com/showthread.php?t=2719411
Click to expand...
Click to collapse
Thank you very much
I try to read the info and decide what to do.
Thanks again
Ok it´s done
First I´ve installer V500-4.2.2-Base from recovery, I have reinstalled CM 11 and everything OK.
I have tried a step beyond and I have installed [KERNEL][v500][4.4.4][AOSP] RedKernel [16/09] (everybody seems to be very happy with it) but, after install synapse I run it and appears "No UCI support detected". Seems that kernel doesn´t support it.
Thank you again for your help
reypescador said:
but, after install synapse I run it and appears "No UCI support detected". Seems that kernel doesn´t support it.
Thank you again for your help
Click to expand...
Click to collapse
Seems to be problems with Super SU but I can´t solve them at the moment
You must install the UKM scripts from recovery. Read the op from the red kernel thread...
edisso10018 said:
You must install the UKM scripts from recovery. Read the op from the red kernel thread...
Click to expand...
Click to collapse
What he said!
This confused me at first too. In the very early days of redkernel he included his own forked version of the UKM scripts those have been removed because the UKM script maintainer agreed to merge his changes and therefore he doesn't have to maintain his own copy (better for all involved so he can focus on kernel development). Search the thread you will find a link to where you can download the official UKM scripts and your problem will go away.
I currently run redkernel on the 4.4.2 base myself. I have not reverted to the 4.2.2. base since my last factory restore. I am very happy with this configuration...
muiriddin said:
I currently run redkernel on the 4.4.2 base myself. I have not reverted to the 4.2.2. base since my last factory restore. I am very happy with this configuration...
Click to expand...
Click to collapse
Originally I had issues with the sd card mounting with the 4.4.2 base. Has this been fixed with Red Kernel?
Sent from my LG-V500 using xda premium
ncguy68 said:
Originally I had issues with the sd card mounting with the 4.4.2 base. Has this been fixed with Red Kernel?
Sent from my LG-V500 using xda premium
Click to expand...
Click to collapse
I had the same problems. Mine was two fold, my sd card was dying (I have since got a new one) and the 4.4.2 base was still sometimes having an issue that sd card monitor would show as a bad removal. This was even with the new sd card. Once I switched to Infected's build of slimkat with the redkernel I have not had a bad removal (after running this way now for over a month) and the sd card monitor used to track at least one bad removal a week with stock 4.4.2. I have no idea if this will help others but it is working so far for my device. I am always running sd card monitor since I had problems and it is still reporting a clean record.
muiriddin said:
I had the same problems. Mine was two fold, my sd card was dying (I have since got a new one) and the 4.4.2 base was still sometimes having an issue that sd card monitor would show as a bad removal. This was even with the new sd card. Once I switched to Infected's build of slimkat with the redkernel I have not had a bad removal (after running this way now for over a month) and the sd card monitor used to track at least one bad removal a week with stock 4.4.2. I have no idea if this will help others but it is working so far for my device. I am always running sd card monitor since I had problems and it is still reporting a clean record.
Click to expand...
Click to collapse
Thanks. I am already using Infected's Slimkat, but I am still on 4.2.2 base. I may flash 4.4.2 base and give redkernel or mani kernel a try.
Sent from my LG-V500 using xda premium
ncguy68 said:
Thanks. I am already using Infected's Slimkat, but I am still on 4.2.2 base. I may flash 4.4.2 base and give redkernel or mani kernel a try.
Sent from my LG-V500 using xda premium
Click to expand...
Click to collapse
You didn't ask, but my approach would be:
Use LG tool to revert to 4.4.2 stock
Root with towel root
Install recovery and loki (I need to get you a link for this, but it involves editing a batch file to tell it to still install with revision d instead of b)
reboot recovery using adb, and immediately unplug cable
flash a recovery designed for 4.4.2 (2.7.0.1) from this link http://forum.xda-developers.com/showthread.php?t=2551499
Then install infected slimkat, redkernel and the ukm zip files
I never use the 4.4.2 base files to flash the device to 4.4.2 I always use the LG Tool and go from there.
muiriddin said:
You didn't ask, but my approach would be:
Use LG tool to revert to 4.4.2 stock
Root with towel root
Install recovery and loki (I need to get you a link for this, but it involves editing a batch file to tell it to still install with revision d instead of b)
reboot recovery using adb, and immediately unplug cable
flash a recovery designed for 4.4.2 (2.7.0.1) from this link http://forum.xda-developers.com/showthread.php?t=2551499
Then install infected slimkat, redkernel and the ukm zip files
I never use the 4.4.2 base files to flash the device to 4.4.2 I always use the LG Tool and go from there.
Click to expand...
Click to collapse
Just curious … is there something wrong with flashing the base files to switch between 4.2.2 and 4.4.2?
Now that I have two Gpad's I plan to install 4.4.2 base on one and compare it with 4.2.2 base on the other. Just wonder if I can tell any difference.
Thanks for the info.
Sent from my LG-V500 using xda premium
ncguy68 said:
Just curious … is there something wrong with flashing the base files to switch between 4.2.2 and 4.4.2?
Now that I have two Gpad's I plan to install 4.4.2 base on one and compare it with 4.2.2 base on the other. Just wonder if I can tell any difference.
Thanks for the info.
Sent from my LG-V500 using xda premium
Click to expand...
Click to collapse
I am unaware of a problem with the 4.4.2 base files provided. I have just never used them, I already had the LG Support Tool downloaded and it was easiest to use the path I knew and was comfortable with.
The key thing (and why I run the 4.4.2 base instead of the 4.2.2. base) that is different is the brightness at its lowest setting. The 4.2.2 base on many of the V500's suffers from alternating light and dark spots on one side of the tablet when viewing the tablet in low light with the brightness at its lowest setting and viewing gmail (any app with a white background basically). I use my tablet mostly in dark conditions like this (man I make it sound like I live in a basement somewhere *laughs*). The 4.4.2 base firmware changes the tablet so it functions well at the lowest brightness.
The first picture in this thread shows the screen problem I refer to (although not on a white screen):
http://forum.xda-developers.com/showthread.php?t=2553055
UNOFFICIAL CyanogenMod 11.0 BETA V0.3
by MisjugdedTwat a.k.a. BangL
WHAT IS THIS?
This is an UNOFFICIAL build of CM-11.0 ( CyanogenMod 11.0 ) for Huawei Mate (hwmt1_u06)
I am basically just continuing the work of others by merging and compiling, so credit goes to surdupetru, joestone, asyan4ik, mrAlmid and all coders who contributed to CyanogenMod.
DISCLAIMER
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
REMEMBER
If you choose to use my unofficial build, pls don't post your issues and/or request in the official CyanogenMod forums. My builds contain unofficial code and MAY affect the official debugging process.
I do this in my free time, for free. Never forget that
Take care and do backups before flashing!
FIRST INSTALLATION (of THIS rom)
!!! BACKUP EVERYTHING !!!
Make sure your bootloader is unlocked, and install TWRP 2.8.1.0
Download the ROM, and put it on your SD-card
Download Gapps, and put it on your SD-card (optional)
Boot into TWRP
Do a FULL WIPE (system, data, cache, dalvik) ! - you can try to keep data, but it will most likely fail booting.
Install the ROM, using TWRP
Install the Gapps, using TWRP (optional)
Reboot to system
UPDATE INSTALL (when you already have another version of this rom installed)
Download the ROM, and put it on your SD-card
Download Gapps, and put it on your SD-card (optional)
Boot to recovery
Wipe system
Install the ROM, using TWRP
Wipe cache & dalvik
Install the Gapps, using TWRP (optional)
Reboot to system
LATEST CHANGES
V0.3
V0.2
CM SOURCES MERGED UP TO:
Change 110843 - manifest: Remove vendor/cyngn repo
http://review.cyanogenmod.org/#/c/110843/
INCLUDED KERNEL
whirlwind.kernel
KNOWN BUGS
a2dp is not running perfect, but it runs. - sometimes.
Nfc is probably not working at all, not sure.
GPS acts a little weird sometimes.
Video compression results in pure trash.
Clock might get desynced
DOWNLOADS
Please note this build is for bug-hunting purposes only, yet! (Plain CM is boring anyways)
I am just starting to build for this device and with this build am currently trying to get a stable basis for other roms.
My goal is having a fully working code-base for any AOKP-based 4.4 ROM.
So PLEASE join the testing phase, try every ****ing functionality on your phone and report the results here, so i know whats done and what needs to be done. Thanks!
Rom
https://www.dropbox.com/sh/gd42e500zsrl7e0/AACjh4We8ZjULayjWFL7Y1lla?dl=0
Gapps
Use any "ARM - 4.4" package from open gapps (i recommend the nano variant)
Bootloader/Recovery
If you are still on a locked bootloader, having an unrooted stock rom, or an old twrp installed, use this updated unlock/recovery suite for windows and linux:
TWRP 2.8.1.0
SOURCE CODE
https://github.com/hwmt1-u06/android
NOTICE:
I removed the asound codecs, which increases the sound volume dramatically. I wanna enjoy my music loud, when i'm sitting in the bus!
This kinda ****s up the speaker, since its too loud now, which causes clipping.
I use the Equalizier in CM's DSP Manager to reduce the speaker volume (by turning all levels around -6db)
Having loud volume, and the ability to decrase it, is better than having silence and no ability to increase it, right? Thats like going to the hair stylist and wanting longer hair.
Cool, thanks for your effort!
Will give it a try when I feel I have enough time
UPDATE V0.2
CHANGES
Fixed rebooting to recovery
Changed some default system props related to adb and root
Thats it, any bugs?
Otherwise i will now focus on porting more aokp roms, building twrp and a maybe a kernel.
Hi,
is NFC functional in this ROM?
(In B331 is not.)
Stutter bluetooth audio sometimes?
(In B331 there is)
sijben said:
Hi,
is NFC functional in this ROM?
(In B331 is not.)
Stutter bluetooth audio sometimes?
(In B331 there is)
Click to expand...
Click to collapse
Its probably both messed up as well in this ROM, i don't have the hardware to test those functions. Maybe you can tell me
Misjudged, in your instructions I see a clear distinction between a "first time install" and an "update install".
What is the difference between the two?
I mean, I get an idea what it is about but do not feel confident to base a decision on.
SvenHee said:
Misjudged, in your instructions I see a clear distinction between a "first time install" and an "update install".
What is the difference between the two?
I mean, I get an idea what it is about but do not feel confident to base a decision on.
Click to expand...
Click to collapse
its meant like this:
- first install the first installation of THIS rom
- update install is when you already have this rom installed (e.g. v0.1) and you wanna update to another version of this rom (e.g. v0.2), and keep your apps, data and settings.
and remember to backup first!
EDIT: Updated instructions in first post
Very good, thanks!
Okay been giving this CM11 ROM a test drive this week on my Mate. My Mate is the 1 gig version and I have a bad case of call ? screen delay on this ROM. Is there a patch that can help with this? I will admit though that I probably expect too much from my poor little Mate because I have tons of apps on it
I must say though your ROM is the smoothest running ? CM11 ROM I've tried. Good job.
If I could only get rid of or just reduce the call screen delay I could run ? this as my daily driver. But this week I just missed too many calls due to the call ? screen delay.
Keep up the good work. You can depend on me to test any ROMs you put out. :thumbup:
sent from my MT1-U06 using Tapatalk 2
Flashed it on my P6, replaced the kernel with the AK cm kernel for P6 and switched to ART. Very smooth rom, havent seen any issues or bugs yet except the wifi dropping, which does not mean much as it instantly reconnects. Good job.
Edit: Don't know about the ascend Mate but on the P6 OTG is fully functional and stable.
after 24 hours of being my phone:
Bluetooth audio gave me a full cd instead of less than one song, gps works.
I only miss pie control, but that in not CM if I read correctly.
Keep up the good work!
Would love to try your version of carbon rom, if you get round to that
Thanks for tests your reports, guys!
let's see..
SvenHee said:
after 24 hours of being my phone:
Bluetooth audio gave me a full cd instead of less than one song, gps works.
I only miss pie control, but that in not CM if I read correctly.
Keep up the good work!
Would love to try your version of carbon rom, if you get round to that
Click to expand...
Click to collapse
Wait.. what? Are you telling me a2dp is working perfectly fine? I did not expect that at all!
Yeah, i will port more ROMs, but first i had to have my own kernel (see below) :fingers-crossed:
blankulus said:
Okay been giving this CM11 ROM a test drive this week on my Mate. My Mate is the 1 gig version and I have a bad case of call ? screen delay on this ROM. Is there a patch that can help with this? I will admit though that I probably expect too much from my poor little Mate because I have tons of apps on it
I must say though your ROM is the smoothest running ? CM11 ROM I've tried. Good job.
If I could only get rid of or just reduce the call screen delay I could run ? this as my daily driver. But this week I just missed too many calls due to the call ? screen delay.
Keep up the good work. You can depend on me to test any ROMs you put out. :thumbup:
sent from my MT1-U06 using Tapatalk 2
Click to expand...
Click to collapse
ive already patched in a tweak to help that problem atleast a little, i am not sure if theres more i can do.
as far as i know it's a well known jb/kk-problem on devices with very low ram... i had an LG O2x, which hab like 500MB ram or something... it was pretty much ununsable when someone called. i remember something like they started to remove the incallUI from the permanently-open list - if you know what i mean. and that's why it's causing this problem.
i don't really have this problem at all, to be honest. so maybe you can help it by removing some service-apps.. or maybe theres some app to force another app to stay loaded? i don't know, just an idea.
tauio111 said:
Flashed it on my P6, replaced the kernel with the AK cm kernel for P6 and switched to ART. Very smooth rom, havent seen any issues or bugs yet except the wifi dropping, which does not mean much as it instantly reconnects. Good job.
Edit: Don't know about the ascend Mate but on the P6 OTG is fully functional and stable.
Click to expand...
Click to collapse
arg... P6? different kernel?
so your report doesnt really help me, since i dont even know what the exact differences between the MT1 and the P6 are, and most off the hardware related stuff is kernel related!
Good to see it's running well for you, though.
But thank you very much, srsly.
btw: you are having the wifi dropping too? thats weird, i was sure thats a kernel & /system/lib/modules thing.
...which is why i focused on kernel building for now. It seems like some people are smashing any modules they can find at their kernel until it works somehow. - this is a huge mistake. kernel modules in /system/lib/modules MUST be built against the exakt same kernel, they will be used on.
To be sure to have that clean, i felt like i need to get into that stuff as well. - and i actually just succeded like 30 minutes ago.
I will try out some things on this build, and when everything seems stable to me, i will even release my own kernel, which will always be shipped with the correct modules
But that will be HIGHLY experimental, and for the MT1 only!
Only had minor hiccups when browsing the internet at the same time.
Now testing the second session of music
Edit: A few more hiccups in one session, pretty good play a bit later. Very usable.
Installed and so far its very smooth
Maps thinks I am at a different road every now and then, causing strange new rout options. But this corrects quickly.
Can not get navigation started by clicking address in calendar appointment, then maps keeps restarting. Had the same thing with Mr. Amids carbon rom.
It does start from clicking icon and copy/paste the address.
SvenHee said:
Maps thinks I am at a different road every now and then, causing strange new rout options. But this corrects quickly.
Can not get navigation started by clicking address in calendar appointment, then maps keeps restarting. Had the same thing with Mr. Amids carbon rom.
It does start from clicking icon and copy/paste the address.
Click to expand...
Click to collapse
interesting.. is there any cm based rom, where you dont have that problem?
Carbon was the only 4.4.4 rom by Mr. Amid I got working, I know now (with your explanation) that I should have wiped data too when flashing a new rom.
I can not recall having the Maps problem with 4.2 roms.
UPDATE V0.3
CHANGES
Fixed /data/share paths in frameworks-base and system-core
System-props and init.rc script optimization
Using wpa_supplicant_8_ti instead of wpa_supplicant_8
Prebuilt B331 kernel and kernel-modules removed
Built whirlwind.kernel #2 from sources
Built wifi modules against whirlwind.kernel #2
Is a2dp, gps and wifi better with this build, or maybe even worse?
Will I be able to upload videos to instagram ?