It appears there is a new CM on the way... And it appeared it wasn't available for the Note 2... And that made me disappointed, so I set out to put that right.
4.3 is a small update from 4.2. Unfortunately, Google also decided to change almost everything about filesystem mounting. And Samsung exynos devices are a hotchpotch of everything...
Today, xplodwild and I carried out a war of attrition against the nasty Samsung devices. Firstly, there remains a battle-scar in the form of graphics, where we had to disable the ability of the device to screenshot itself. You'll see this in the lack of thumbnails for your long-press-home task switcher. #Blame-Samsung
Storage was a nightmare, but I have finally beaten it into submission. It should now work. Nicely. And properly. At least for now.
Because open source is wonderful, a VERY messy device tree (commits need squashed etc) - https://github.com/pulser/android_device_samsung_n7100/
I suggest a wipe before flashing, but I have tested from 4.2.2 and should be OK actually, maybe some apps will cry, but that's not my problem
Link: http://goo.im/devs/pulser/N7100/CM/cm-10.2-20130810-UNOFFICIAL-n7100.zip
Pretty much everything is working and tested - you shouldn't have any issues getting it to boot. The other version posted appears it may have issues booting, but I was not aware of its existence until just now. Actually, seems there's no link in the other thread, give this a shot, and see if it helps you. There's a lot of issues on Exynos devices when doing any kind of update... Sneeze and it might explode!
XDA:DevDB Information
Unofficial CM 10.2 for Galaxy Note II (N7100), a ROM for the Samsung Galaxy Note II
Contributors
pulser_g2, CM Team
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.0.x
Based On: CM 10.2
Version Information
Status: Alpha
Current Stable Version: N/A
Current Beta Version: 10 August
Beta Release Date: 2013-08-10
Created 2013-07-30
Last Updated 2013-08-10
Thanks,
Trying now and will report.
BTW (off-topic but... I believe necessary when it comes to AOSP and Exynos) When I click on your githup link the Audio recording fix is on top of the list for 6 months ago, which reminds me; we have never got the chance to see CM 10.1 recording audio properly on videos or sound record apps (not saying it is mono but the sound is terrible actually).. For now it seems the only thing that prevents me (and some others I guess) from using any AOSP ROM as a daily and "fully functional" driver is this problem. Any chance that we can see 10.2 have proper audio recording? Since our voice is recorded just fine on calls we can say the mic is working as it should on both at earspeaker and the loudspeaker. So, there is a software which can use the mics properly and I -with all my heart and never-ending hope- believe this software could be also used for good sounded video recording or help us not to shout too much for Google Now
Thanks for reading. And the ROM
---------- Post added at 01:06 AM ---------- Previous post was at 12:43 AM ----------
It boots just fine. So is everything so far.
works without a hitch. no bootloop nothing. simply booted up and worked. Huge thanks for that PulserG2 and xplodwild =)
Will try this new one tomorrow... Thanks!
BTW. Is anyone using GoBackup Pro or Titanium Backup? I had an issue on my Nexus 4 running 4.3 .
They didn't restored my Apps. Since the Note 2 uses a SD Card Slot, would it be the same issue?
Gesendet von meinem GT-N7100 mit Tapatalk HD
lolmensch said:
works without a hitch. no bootloop nothing. simply booted up and worked. Huge thanks for that PulserG2 and xplodwild =)
Click to expand...
Click to collapse
Awesome. Was pretty sure I had fixed it properly, but always good to check
Downloading and trying it right now I'll be giving a feedback
Sent from my GT-N7100
Eric-Mod said:
Will try this new one tomorrow... Thanks!
BTW. Is anyone using GoBackup Pro or Titanium Backup? I had an issue on my Nexus 4 running 4.3 .
They didn't restored my Apps. Since the Note 2 uses a SD Card Slot, would it be the same issue?
Gesendet von meinem GT-N7100 mit Tapatalk HD
Click to expand...
Click to collapse
No issues, my testing process includes restoring from titanium backup, with data, from external SD
_delice_doluca_ said:
Thanks,
Trying now and will report.
BTW (off-topic but... I believe necessary when it comes to AOSP and Exynos) When I click on your githup link the Audio recording fix is on top of the list for 6 months ago, which reminds me; we have never got the chance to see CM 10.1 recording audio properly on videos or sound record apps (not saying it is mono but the sound is terrible actually).. For now it seems the only thing that prevents me (and some others I guess) from using any AOSP ROM as a daily and "fully functional" driver is this problem. Any chance that we can see 10.2 have proper audio recording? Since our voice is recorded just fine on calls we can say the mic is working as it should on both at earspeaker and the loudspeaker. So, there is a software which can use the mics properly and I -with all my heart and never-ending hope- believe this software could be also used for good sounded video recording or help us not to shout too much for Google Now
Thanks for reading. And the ROM
---------- Post added at 01:06 AM ---------- Previous post was at 12:43 AM ----------
It boots just fine. So is everything so far.
Click to expand...
Click to collapse
This sounds like something more for the guys that did the work on the audio HAL. I've not looked into the solution, but audio on these devices is a dirty hack with tinyhal
there are some occasional rendering glitches with the stock browser while loading a page and scrolling through. nothing majorly bad but still visible at times.
(independent of the webpages i visited)
despite that I didn't come across any other bugs. once again great job :good:
finally glad to see the update in our devices thank you guys
Sent from my GT-N7100 using xda premium
Re 4.3 in general
I have been testing 4.3 on an "old" device , my Nexus S, the last couple of days. Interestingly, the device was much smoother than 4.2 based ROMs, at least on that limited processor device.
Once this all gets ironed out is there reason to believe that 4.3 will be better for our Note 2's?
Thanks for your work !
jcrompton said:
I have been testing 4.3 on an "old" device , my Nexus S, the last couple of days. Interestingly, the device was much smoother than 4.2 based ROMs, at least on that limited processor device.
Once this all gets ironed out is there reason to believe that 4.3 will be better for our Note 2's?
Thanks for your work !
Click to expand...
Click to collapse
It really depends on your use cases...
I can make the fastest and most cutting edge android phone lag like crazy without installing anything silly...
I just need to type at my full speed on SwiftKey for about a minute and it will be lagging pretty horrendously. That's a bad app - SwiftKey is very poor lately for performance.
Why do I mention this? Well, your definition of better or smoother will really depend on what you are doing. Android is a horrendously complex operating system. It is ridiculously inefficient in many ways such as how data is presented to the user.
As such there are many badly written apps which will slow down your device. I reckon unless Google considers using native code for drawing the screens, we will never reach the true smoothness the hardware is capable of.
At the end of the day, a particular apple phone is available with lesser processor, graphics and RAM. Yet it offers smoother in-use performance because of its use of native code where possible, rather than a virtual machine based language like java.
I don't think it seems significantly faster than 4.2, but I probably am hard to please. I simply despair as I look at the code in android... All the nasty object orientation and strange ways to to things... Each and every time it happens, the java virtual machine must run instructions.
I reckon if you reduced the number of lines of code used to achieve simple tasks like show the settings menu (which is horrendous with resources in countless files and java classes), performance would be vastly superior.
Probably not much of an answer, but if anyone else is irritated by the horrendously inefficient code in android, I've finally found someone else who sees it!
That actually helps a lot. I think the processor and the device makes a difference too with the Nexus S being a "Google" device and the Note 2 being Samsung.
I just notice that when browsing Tapatalk that seems to be my main gauge - the scrolling seemed pretty smooth even on the Nexus S.
I read in the Nexus thread that the 4.3 code was written to run with less sytem resources but I wasn't sure of the source of that comment.
---------- Post added at 09:11 PM ---------- Previous post was at 08:45 PM ----------
IF YOU LOSE ROOT WHEN INSTALLING 4.3
I lose root when I install this ROM but if you will flash the newest update from Chainfire you will re gain
http://download.chainfire.eu/344/SuperSU/UPDATE-SuperSU-v1.50.zip
That's amazing!!! great help and flashing now!
update: AOSP keyboard having FC
everything else within expectations. no problem with using the ROM so far!
amazing amazing effort and feels like 95% finished product!
Gapps?
Thanks for bringing 4.3 for Note 2. Are the official CM10.2 gapps compatibile with this ROM?
vishnu8058 said:
Thanks for bringing 4.3 for Note 2. Are the official CM10.2 gapps compatibile with this ROM?
Click to expand...
Click to collapse
http://goo.im/devs/kashamalaga/gapps4.3/gapps-jb-4.3-20130726.zip
Inviato dal mio GT-N7100 con Tapatalk 2
I want 2 try this but i read someone lose the root of his phone... Some other people also that problem?
Sent from my Galaxy Note II using xda app-developers app
gamesz2 said:
I want 2 try this but i read someone lose the root of his phone... Some other people also that problem?
Sent from my Galaxy Note II using xda app-developers app
Click to expand...
Click to collapse
You loss the root, HOWEVER, If you read that guy's post, he Said flash that file and you'll get root..
Im other words,
1. Flash CM10.2
2. Flash Gapps
3. Flash the file from the previous post
Sent from my GT-N7100
Mohammed779 said:
You loss the root, HOWEVER, If you read that guy's post, he Said flash that file and you'll get root..
Im other words,
1. Flash CM10.2
2. Flash Gapps
3. Flash the file from the previous post
Sent from my GT-N7100
Click to expand...
Click to collapse
thanks! i flashed the 10.2 with the older official gapps... nothing seems to be wrong with it and everything is working
do you know what is new with the latest GApps as attached a few posts above?
Flashed it, and it's working good. For the 1st Build it's working quite fine. But the camera (app?) isn't working properly. I took one pic, the camera froze, and when I launched the camera again, it said "No connection to camera".
It's the first build so yeah.. this can happen of course
Related
I can not post on the developer area so After_silence many thanks for your great work!
How many mediapad users using CM? After_silence has told that there are too few users out there using media pad, so he is no longer interested in developing for media pad. how many are we? I myself would love to continue using his excellent CM 10.1 and was eagerly waiting for BT to work on mediapad .
Sent from my Huawei MediaPad using Tapatalk 2
I want to install it but I'm using 301w model device and I'm not sure if it's going to work on it. I'm afraid to install it
I can't post to developer forums because I don't have enough post count so I'm middle of nowhere now.
just follow the steps and walla~ Jelly bean on mediapad!!
justynz said:
just follow the steps and walla~ Jelly bean on mediapad!!
Click to expand...
Click to collapse
I have been using it for a while. I just wish somehow the Wi-Fi htspot problem could be fixed
I use CM10(4.1.2) because of working hotspot and BT
gokcen said:
I want to install it but I'm using 301w model device and I'm not sure if it's going to work on it. I'm afraid to install it
I can't post to developer forums because I don't have enough post count so I'm middle of nowhere now.
Click to expand...
Click to collapse
Hey I'm using S7303u and cm10.1 works fine, I'm currently working on porting AC!D MOD for all enhanced audio, beats, xloud and clear+, bravia2 to run on media pad, its almost ready just running into storage issues in the system partition, not enough room to fully flash my zip, libs and framework not flashing, causing boot loop, broke zip into two desperate zips, you can install one or the other, works fine, but I need all mods together with settings to manipulate sound. I hope his break isn't two long was really looking forward to new builds, guess I'll try and get Bluetooth working for now
here... also using CM10... tried the CM10.1 for testing... and it is okay... but i am using BT and HOTSPOT so i return back to CM10... also can't reply to the CM10 thread...
so maybe after_silence thought there were only few of us using his FIRMWARE... but if the 10 post LIMIT is not there... he would receive a lot of response... and user feedback...
thanks again... for the nice firmware... still looking forward for the 4.2.2 (CM10.1)...
joebuttons1 said:
Hey I'm using S7303u and cm10.1 works fine
Click to expand...
Click to collapse
So if 303u is working on 301u device, is that mean I can use 301u rom's on 301w too? Is that what you mean?
441Excelsior said:
I use CM10(4.1.2) because of working hotspot and BT
Click to expand...
Click to collapse
same
gokcen said:
So if 303u is working on 301u device, is that mean I can use 301u rom's on 301w too? Is that what you mean?
Click to expand...
Click to collapse
device: S7303u
rom:301u
its all the same thing my device is tmo springboard, so of course by using mediapad fw I lose 4g capabilites, but other than that, cm10.1 runs smooth
Happy user
I am running 10.1 happy with it.
Thank you very much.
thank you: it is a great ROM
thanks to After_Silence
I am using this ROM and my friend too
andro41 said:
I am running 10.1 happy with it.
Thank you very much.
Click to expand...
Click to collapse
Lovin the ROM as well CM10.1 on my Springboard.
Sent from my GT-N7105 using xda premium
I use too. And cannot post on developers forum too
But I caught bug: once I could not unlock screen. I pressed power button, screen turned on for a half a second and became off after this...
Then i pressed power button for a long time and pressed it again. Device turned off. After booting all works fine.
agreed, many thanks to the wonderful developers
i'm currently using aokp 30.1 final jb4.1.2, looking forward to bluetooth & most importantly more stable hdmi mirroring on the 4.2.2 nightlies though (so can output & play stuff like playstation emulator there or use with wireless keyboard/mouse as nice media pc on tv)
my device is mediapad s-301u
AW: How many using CM10.1 by After_Silence
I kept an eye on it for months, but it never became perfect enough to flash it, and hey, doesnt it have the seal of approval/quality "unofficial".
Now, game over, man.
it seems that he has just release a new cm10.1 rom 20130330
thankyou after_silence for continuing this project silently
AW: How many using CM10.1 by After_Silence
Hi
I'm using this ROM too.
Great work, After_Silence! Now installing todays release!
Torstiko
Sent from my Nexus 4 using xda app-developers app
danisukses said:
it seems that he has just release a new cm10.1 rom 20130330
thankyou after_silence for continuing this project silently
Click to expand...
Click to collapse
awesome. word has it he has got hdmi audio out now but no bluetooth right? well I suppose BT is not a deal breaker. could anyone comment on stability of HDMI out on new release as well as whether it supports external/internal SD swap as AOKP 30.1 Final did? (or perhaps if there is some other work around for it? got a lot of data hungry games)
lecorbusier said:
I kept an eye on it for months, but it never became perfect enough to flash it, and hey, doesnt it have the seal of approval/quality "unofficial".
Now, game over, man.
Click to expand...
Click to collapse
for us it's just a simple waiting game. for the devs it's plenty of hard work.. i'll keep my hopes up :laugh:
Where to get the ROM's
Hey guys,
I'm currently running the Stock Springboard + ROOT and loving it. Theres only one problem though: if i fill up my 32GB SD card with music, the machine slow to a halt. I believe this is an OS issue. Does anyone know if the new ROM's take care of this issue? Bluetooth is important to me. I'd prefer everything working: HDMI, 4G, BT & hotspot. Can someone give me some advice and where to get the ROM's and which ones to get?
Cheers,
Zubin
There are so many varied and out of date opinions on this and then so many people that are just guessing, so I have to ask.
Are either 4.1.2 or 4.2.1 completely stable? I'm getting that NONE of the 4.2s are stable at all and that they're experimental at best. Is this true? If so, is 4.1.2 the only stable ROM right now? I don't get a kick out of the phone FCing on me when I try to edit a photo or something.
Thanks for any clarification.
tinpanalley said:
I'm getting that NONE of the 4.2s are stable at all and that they're experimental at best. Is this true? If so, is 4.1.2 the only stable ROM right now?
Click to expand...
Click to collapse
are you talking about Samsung ROMs? then yes
I'm talking about Samsungs OR AOSP. Either one.
Sent from my GT-I9300 using xda app-developers app
tinpanalley said:
I'm talking about Samsungs OR AOSP. Either one.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Samsung - stable
AOSP - not 100% because lack of sources, but OK for a daily driver.
Sent from my washing machine using xda premium
AOSP ROMs will never be as stable as Sammy-based ones
Ok, I think my question got a bit misconstrued. I get that a Samsung ROM is always more stable since it's the base of this phone's OS.
But therefore...
- 4.1.2 and 4.2.1 BOTH stable on Samsung.
- neither stable on AOSP because of lack of sources
Is that correct, then?
And by stable, I mean that I just want a camera that works with all features, can save to the SD card, no weird crashes from using basic phone menus and functions (volume, notifications menu, etc)
tinpanalley said:
Ok, I think my question got a bit misconstrued. I get that a Samsung ROM is always more stable since it's the base of this phone's OS.
But therefore...
- 4.1.2 and 4.2.1 BOTH stable on Samsung.
- neither stable on AOSP because of lack of sources
Is that correct, then?
And by stable, I mean that I just want a camera that works with all features, can save to the SD card, no weird crashes from using basic phone menus and functions (volume, notifications menu, etc)
Click to expand...
Click to collapse
Camera is working but the picture quality is a bit worse than on the stock camera. Pictures can be saved on SD card
Sent from my washing machine using xda premium
tinpanalley said:
Ok, I think my question got a bit misconstrued. I get that a Samsung ROM is always more stable since it's the base of this phone's OS.
But therefore...
- 4.1.2 and 4.2.1 BOTH stable on Samsung.
- neither stable on AOSP because of lack of sources
Is that correct, then?
Click to expand...
Click to collapse
no, samsung 4.2 is not stable, like I said.
by your definition of stable, AOSP 4.2 is stable
Ok, I see. In which ways do AOSP 4.2 ROMs fall short then? I know they obviously don't have Samsung apps like S-beam, smart TV functionality, NFC, etc. But is there something that's always 'broken' on AOSP ROMs?
Sent from my GT-I9300 using xda app-developers app
Some don't like MMS. Some dont like camera.
I use camera fine though, Not bothered about SMS
Ok cool, like I said I just don't want something stupid like you can't play a game and then send an email because the whole phone crashes. :silly: Or a ROM with TERRIBLE battery drain.
tinpanalley said:
Ok cool, like I said I just don't want something stupid like you can't play a game and then send an email because the whole phone crashes. :silly: Or a ROM with TERRIBLE battery drain.
Click to expand...
Click to collapse
then AOSP have been stable for a loong time
rootSU said:
Some don't like MMS. Some dont like camera.
Click to expand...
Click to collapse
Well, then that's not my idea of stable. I guess I'll stick to Samsung ROMs.
Jelly Bean stable?
I recently bought a galaxy s3 and had flashed the 4.2.2 jellybean update. it worked great, no crashes and ran smooth. On monday it notified me that there were two stable updates. I updated both one at a time with TWRP and flashed. It seemed ok all night. In the morning when i plugged in my USB flash drive with my OTG cable the screen just went black. Now it doesnt do anything. It wont even go in to download mode. So i guess i the 4.2.2 was ok but the updates werent.
tinpanalley said:
Well, then that's not my idea of stable.
Click to expand...
Click to collapse
That's because you don't know what stable means.
Stable means... Does not reboot constantly. Does not freeze constantly. It runs stable.
You are talking about broken features. Camera is easily fixable. MMS, well if you want MMS, go back to Smasung ROMs.
---------- Post added at 10:26 AM ---------- Previous post was at 10:25 AM ----------
janicans said:
I recently bought a galaxy s3 and had flashed the 4.2.2 jellybean update. it worked great, no crashes and ran smooth. On monday it notified me that there were two stable updates. .
Click to expand...
Click to collapse
There is no official 4.2.2 for the S3.
rootSU said:
That's because you don't know what stable means.
Stable means... Does not reboot constantly. Does not freeze constantly. It runs stable.
You are talking about broken features. Camera is easily fixable. MMS, well if you want MMS, go back to Smasung ROMs.
Click to expand...
Click to collapse
Ok, well that's true, that's why I'm asking these questions.
So do 4.2.1, 4.2.2 AOSP have the same level of stability?
Is 4.1.2 considered something that's MUCH more stable at this point?
tinpanalley said:
Ok, well that's true, that's why I'm asking these questions.
So do 4.2.1, 4.2.2 AOSP have the same level of stability?
Is 4.1.2 considered something that's MUCH more stable at this point?
Click to expand...
Click to collapse
Its hard for me to Quantify.
I only used Smasung 4.0.4, 4.1.1, 4.1.2, 4.2.1 Then AOSP 4.2.2
I dont use MMS so the fact it doesn't work properly is no big deal for me. It force closes when I try to attach a picture. I am not sure about receiving MMS (As I say I dont use it).
For me, AOSP - everything works great. More stable to me than Samsung ROMs (less bugs) except MMS which i do not use. Actually I find AOSP faster too.
I do not use the stock AOSP camera. I never had problems with it but some users did. But i replace mine with the camera that has more functions...
http://forum.xda-developers.com/showthread.php?t=1746611
What I would say is, If you think you can live without MMS, give it a try. Dont mess with overclock / undervolt and see for yourself how fast and stable it is.
If you really need MMS, Maybe it is not worth the test. I am not sure how apps like Go SMS handle it.
In conclusion, I find AOSP faster and more stable than sammy. But I dont use MMS.
I hope this helps somewhat
Yeah, it does help. I can find another solution for MMS (GoSMS Pro, etc) but I don't want basic things being broken. Like I just found out there's no mute on this ROM for audio. Somebody mentioned something about not being able to silence their ringer. That's something I can't be flexible about. I guess I'll look for an AOSP other than temasek.
I like paranoid android myself. Definitely silences
Sent from my GT-I9300 using Tapatalk 2
Any thoughts from anyone on MIUI?
Here is a thread for the official CM10.1.
Here is where to get it
http://get.cm/?device=tf201
demercie said:
Here is a thread for the official CM10.1.
Here is where to get it
http://get.cm/?device=tf201
Click to expand...
Click to collapse
come on guys animate this thread,news about autorotation?
---------- Post added at 10:50 PM ---------- Previous post was at 10:46 PM ----------
pit84 said:
come on guys animate this thread,news about autorotation?
Click to expand...
Click to collapse
demercie this thread is a good idea because alle the guys post on the unofficial builds threads when i have a news about the mayor fix of the nightly i post here thanks
I've been running the last of the UNofficial 10.1 nightlies, dated May 22. Other than no autorotation, it seems to run just fine. Once the Official nightlies started a few weeks ago, I jumped in and flashed a few, up to the 0629 nightly. In addition to the autorotation issue, suddenly my dock battery is not recognized, and I have (apparently already known) issues where both external SD cards are not recognized, on the device or in Windows. Checking the changelogs, I note that there have been HUGE changes/additions in the last few nights, so I figured I'd try the July 4 nightly. BIG effing mistake, UI crashes immediately, multiple error mesages, and I could barely get back to TWRP to restore my faithful 0522 Unofficial.
Thoughts on why the unofficial build works fine, but the "official" ones don"t? What could I be doing wrong?
Thx...
jp071848 said:
I've been running the last of the UNofficial 10.1 nightlies, dated May 22. Other than no autorotation, it seems to run just fine. Once the Official nightlies started a few weeks ago, I jumped in and flashed a few, up to the 0629 nightly. In addition to the autorotation issue, suddenly my dock battery is not recognized, and I have (apparently already known) issues where both external SD cards are not recognized, on the device or in Windows. Checking the changelogs, I note that there have been HUGE changes/additions in the last few nights, so I figured I'd try the July 4 nightly. BIG effing mistake, UI crashes immediately, multiple error mesages, and I could barely get back to TWRP to restore my faithful 0522 Unofficial.
Thoughts on why the unofficial build works fine, but the "official" ones don"t? What could I be doing wrong?
Thx...
Click to expand...
Click to collapse
Did you wipe before installing? I know its CM to CM but like you said there have been lots of changes. If it still crashes then it's probably effed for the moment.
jp071848 said:
I've been running the last of the UNofficial 10.1 nightlies, dated May 22. Other than no autorotation, it seems to run just fine. Once the Official nightlies started a few weeks ago, I jumped in and flashed a few, up to the 0629 nightly. In addition to the autorotation issue, suddenly my dock battery is not recognized, and I have (apparently already known) issues where both external SD cards are not recognized, on the device or in Windows. Checking the changelogs, I note that there have been HUGE changes/additions in the last few nights, so I figured I'd try the July 4 nightly. BIG effing mistake, UI crashes immediately, multiple error mesages, and I could barely get back to TWRP to restore my faithful 0522 Unofficial.
Thoughts on why the unofficial build works fine, but the "official" ones don"t? What could I be doing wrong?
Thx...
Click to expand...
Click to collapse
yes,well i have this bug in my official nightly but is really soon for a stable build and the developers release one build for day let them operate.i think 1 or 2 moins and the big issues are solved
shuwoo said:
Did you wipe before installing? I know its CM to CM but like you said there have been lots of changes. If it still crashes then it's probably effed for the moment.
Click to expand...
Click to collapse
Sort of. I did do a number of cache wipes, but I admit I never did do a full wipe/ factory reset. I also note on other forums that the early July Nightlies are causing others some of the same crashes I saw, so I guess I'm not alone. We'll have to be patient
Aren't the Unofficial builds a port of the TF300 or TF700 builds? It would definitely account for the fact we're starting all over with features on the nightly builds as this would be a completely new tree starting from the ground up on inclusion of feature sets as the build comes together.
Been running the nightly for a few days now and it's been just fine for me. Of course, I did start off the entire 10.1 journey with a total wipe first.
BUILD cm-10.1-20130701-NIGHTLY-tf201
A couple obvious missing features to point out for those who may be just getting to this:
Auto-rotate not working
Dock/Keyboard battery not recognized
Function buttons on the keyboard not recognized (obviously)
Loading up the 0706 Nightly right now so I'll run through the motions later and give a more detailed outline of things I notice.
---------- Post added at 10:22 AM ---------- Previous post was at 09:43 AM ----------
OK, cm-10.1-20130706-NIGHTLY-tf201 should be avoided.
When it comes up it immediately starts throwing System UI failures. Had to force power off and go into recovery mode in order to gain control.
Last known good for me was cm-10.1-20130701-NIGHTLY-tf201 so I rolled back to that from TWRP. Considering it's reported that this issue appears on the 0704 as well, I figured it was safest to go back that route for now.
I think I'll give it a few days before trying another build and just keep an eye on the builds to see if anything significant changes to resolve this.
For now, 20130701 is the most stable that I'm aware of. Perhaps someone else can chime in if they are running anything newer successfully.
tsvortex said:
Aren't the Unofficial builds a port of the TF300 or TF700 builds? It would definitely account for the fact we're starting all over with features on the nightly builds as this would be a completely new tree starting from the ground up on inclusion of feature sets as the build comes together.
Been running the nightly for a few days now and it's been just fine for me. Of course, I did start off the entire 10.1 journey with a total wipe first.
BUILD cm-10.1-20130701-NIGHTLY-tf201
A couple obvious missing features to point out for those who may be just getting to this:
Auto-rotate not working
Dock/Keyboard battery not recognized
Function buttons on the keyboard not recognized (obviously)
Loading up the 0706 Nightly right now so I'll run through the motions later and give a more detailed outline of things I notice.
---------- Post added at 10:22 AM ---------- Previous post was at 09:43 AM ----------
OK, cm-10.1-20130706-NIGHTLY-tf201 should be avoided.
When it comes up it immediately starts throwing System UI failures. Had to force power off and go into recovery mode in order to gain control.
Last known good for me was cm-10.1-20130701-NIGHTLY-tf201 so I rolled back to that from TWRP. Considering it's reported that this issue appears on the 0704 as well, I figured it was safest to go back that route for now.
I think I'll give it a few days before trying another build and just keep an eye on the builds to see if anything significant changes to resolve this.
For now, 20130701 is the most stable that I'm aware of. Perhaps someone else can chime in if they are running anything newer successfully.
Click to expand...
Click to collapse
Thanks for the confirmations. And yes, as you indicate, the Unofficials are built on the TF700. I did a complete wipe/reset etc and then tried the 0701 that seems to work fine, but I ran into the same problems. In addition to the three issues noted above, I continue to have no access to either of the external SD cards, which for me is a show-stopper. I'll have to stick with the 0522 Unofficial for a while, at least it's fully functional for me..
jp071848 said:
Thanks for the confirmations. And yes, as you indicate, the Unofficials are built on the TF700. I did a complete wipe/reset etc and then tried the 0701 that seems to work fine, but I ran into the same problems. In addition to the three issues noted above, I continue to have no access to either of the external SD cards, which for me is a show-stopper. I'll have to stick with the 0522 Unofficial for a while, at least it's fully functional for me..
Click to expand...
Click to collapse
I've got nothing better to do than blow up my tab every few days so I'll keep posting up results when I do, lol.
The latest nightly has a force close on System UI. I even wiped EVERYTHING and did a clean install... Same thing. Going back one night, and things should be just fine!
Micro SD card isn't working yet, but this is just a nightly... I'm not worried about it.
HDMI out is working, so that's awesome!
Thanks for testing the unofficial editions. I think it will be better soon!
I m using the app "rotate" to make the table force rotate. It will be useful in the unofficial roms.
Sent from my Galaxy Nexus using xda premium
07032013 build OK. July 4th and after give the FC's.
Sent from my EPAD using Tapatalk HD
mm284781423 said:
Thanks for testing the unofficial editions. I think it will be better soon!
I m using the app "rotate" to make the table force rotate. It will be useful in the unofficial roms.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
post a link for this app?Thanks
2013/07/08 build still has UI crashes.
Is there anyone from the CM team watching this thread? If there is I will gladly post a logcat when I get the chance.
nexwave-mat said:
Is there anyone from the CM team watching this thread? If there is I will gladly post a logcat when I get the chance.
Click to expand...
Click to collapse
Post, and I'll see what I can do...
Auto-rotate and the dock stuff is already in the review process.
who have tested the 08\07 nighly? FC?
Me. With Clean install
Sent from my Galaxy Nexus using xda app-developers app
atoyu said:
Me. With Clean install
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
And ? Any UI crash issues ? sd-card ? rotate ?
demercie said:
And ? Any UI crash issues ? sd-card ? rotate ?
Click to expand...
Click to collapse
@atoyu
so what?
The SystemUI was on my nexus 4 too... and I experienced it on this so here is the commits they shared in the nexus4 thread to fix it... if it helps or if anyone reads these...
BTW I have no idea if these really are the culprit but thats what they gave us in the n4 thread
http://review.cyanogenmod.org/#/c/45076/
and possibly
http://review.cyanogenmod.org/#/c/45102/
although not sure about that one...
Sent from my EPAD using xda app-developers app
HEY GUYS!!
So im super new to XDA forums, but i came here to get some help. So ive never flashed a custom ROM before but ive read on it extensively and have an idea of the terms and what-not. i recently flashed my s2 i9100 to the latest cyanogenmod rom using their app and desktop aid. i really loved the new look and feel on my s2 and i was positive Sammy wouldn't be rolling out any future updates on this hardware.
After the honeymoon period was over i came to notice the grating little issues that made me switch back to official jellybean TW. The cyanogenmod firmware they flash with the app is 10.2, so its jelly bean 4.3. It was a "stable" firmware, so they say. Heres a list of the problems.
1. YouTube became very very pixelated and i did some searches and couldnt find a fix.
2. Games like Temple Run 2 performed much worse than with the stock OS, lots of frame skipping could be seen, which makes a game like TR2 unplayable.
3. There were alot of crashes on the stock cyanogenmod launcher, especially after installing apps.
I really appreciate the work cyanogen does but i posted these issues on their forums and i feel like im an isolated incident being that noone has posted on it.
SO IF THERE IS ANYONE OUT THERE WITH THE SAME ISSUES AS ME OR WITH ADVICE, PLEASE HELP ME OUT, IT WOULD BE REALLY APPRECIATED.
CM for i9100 are only nightlies.
Nightly means that the firmware is every (not anymore) day/night getting updated, why? Because of bugs. Nightlys are oftne minor bug improvments compared to the one before.
There are no stable CM roms, except CM 9 so i've heard, just Nightlies.
Hope this clears it up.
PS. Maybe you can try other roms that have CM base..
I am using cyanogenmod 10.2 nightlies right now in my I9100G, and i don't have any problems, wouldn't go back to stock. Games work much better for me because this ROM is lightweight and uses ram better, i never used the desktop aid so i can't comment on that but maybe you should flash from recovery, there might be bugs with that aid, and which cyanogenmod are you using? If you are trying to use kitkat, there will be lots of bugs its only natural because it's been 2 weeks since kitkat went out, try 4.3.
TheGovernment said:
CM for i9100 are only nightlies.
Nightly means that the firmware is every (not anymore) day/night getting updated, why? Because of bugs. Nightlys are oftne minor bug improvments compared to the one before.
There are no stable CM roms, except CM 9 so i've heard, just Nightlies.
Hope this clears it up.
PS. Maybe you can try other roms that have CM base..
Click to expand...
Click to collapse
Oh thanks for the repl. I didnt know that the firmwares were nightlies when using the official app. i thought the app description was that it flashes the latest stable cyanogen build. Just a question, being that ive flashed it twice to try and mitigate the issues to no avail, (ive wiped dalvik and cache and formatted) whats my next step? i really liked it but those issues are pretty disappointing/
Dakura said:
I am using cyanogenmod 10.2 nightlies right now in my I9100G, and i don't have any problems, wouldn't go back to stock. Games work much better for me because this ROM is lightweight and uses ram better, i never used the desktop aid so i can't comment on that but maybe you should flash from recovery, there might be bugs with that aid, and which cyanogenmod are you using? If you are trying to use kitkat, there will be lots of bugs its only natural because it's been 2 weeks since kitkat went out, try 4.3.
Click to expand...
Click to collapse
I would try it the "old" way but im a little afraid. do you think that the fact that you are using the G variant would make a difference?
the only way to make youtube better was to loas previous version. and the games didnt necessarily have a constant lag, it seems more like a frame sync or clipping issue than a frame chugging/ lagging issue. The cyanogen build i was using was 10.2. so it was 4.3.1. thanks for your reply.
cquallo89 said:
I would try it the "old" way but im a little afraid. do you think that the fact that you are using the G variant would make a difference?
the only way to make youtube better was to loas previous version. and the games didnt necessarily have a constant lag, it seems more like a frame sync or clipping issue than a frame chugging/ lagging issue. The cyanogen build i was using was 10.2. so it was 4.3.1. thanks for your reply.
Click to expand...
Click to collapse
Sorry, can't help you further, since i'm still on a stock sammy based rom
cquallo89 said:
I would try it the "old" way but im a little afraid. do you think that the fact that you are using the G variant would make a difference?
the only way to make youtube better was to loas previous version. and the games didnt necessarily have a constant lag, it seems more like a frame sync or clipping issue than a frame chugging/ lagging issue. The cyanogen build i was using was 10.2. so it was 4.3.1. thanks for your reply.
Click to expand...
Click to collapse
Might be a unique problem for you. You can try this: http://forum.xda-developers.com/showthread.php?t=2532929
If it doesn't work, don't use cm and try other roms, as i said there might be a unique problem with your device.
I'm not going to make any recommendations because that's against XDA rules, but it stands to reason that the 10.2 builds won't be as 'polished' as the 10.1 builds purely because they haven't been under development for as long. If you don't like the bugs in 10.2, try something 'older'..........
sent from either my Alliance powered S2 or my ArcoCM powered W via XDA Developers App
keithross39 said:
I'm not going to make any recommendations because that's against XDA rules, but it stands to reason that the 10.2 builds won't be as 'polished' as the 10.1 builds purely because they haven't been under development for as long. If you don't like the bugs in 10.2, try something 'older'..........
sent from either my Alliance powered S2 or my ArcoCM powered W via XDA Developers App
Click to expand...
Click to collapse
Thanks for your replies guys,
im wondering if i should just wait for an official kitkat build.
but either way ill try your suggestions. looking forward to positive results.
just a heads up though i found another poster on a cyanogen forum that describes the same youtube problem. so maybe its not just me after all
There will be issues with the 10.2 builds for some time to come.....no disrespect to the developers, they've done /are doing a fantastic job to help keep the S2 alive. All custom ROMs go through this process and as they progress, the bugs become less and less.........
And as far as official KitKat.......not going to happen.....Samsung ended official support for the S2 with Jellybean....
sent from either my Alliance powered S2 or my ArcoCM powered W via XDA Developers App
keithross39 said:
There will be issues with the 10.2 builds for some time to come.....no disrespect to the developers, they've done /are doing a fantastic job to help keep the S2 alive. All custom ROMs go through this process and as they progress, the bugs become less and less.........
And as far as official KitKat.......not going to happen.....Samsung ended official support for the S2 with Jellybean....
sent from either my Alliance powered S2 or my ArcoCM powered W via XDA Developers App
Click to expand...
Click to collapse
Well overall the ROM is fantastic. I love the look and feel and added functionality. What I meant about waiting for official kitkat is an offcial rom from cyanogen based on kitkat. Im sure that support for s2 will continue so long as the hardware is capable.
Hi, I would ask if there is a very vanilla ROM (not CM), similar to stock, but without Google Apps
OpenAndroidUser said:
Hi, I would ask if there is a very vanilla ROM (not CM), similar to stock, but without Google Apps
Click to expand...
Click to collapse
I'm pretty sure you could flash AOSP itself. It's stock, but theres no Google apps.
Sent from my Nexus 6P using Tapatalk
http://forum.xda-developers.com/moto-e-2015/orig-development/caf-6-0-surnia-t3250165 this was the first pure AOSP Marshmallow ROM available, been using it for almost a year now & its 100% stable.
cmason37 said:
http://forum.xda-developers.com/moto-e-2015/orig-development/caf-6-0-surnia-t3250165 this was the first pure AOSP Marshmallow ROM available, been using it for almost a year now & its 100% stable.
Click to expand...
Click to collapse
Hey @cmason37, thanks for posting this as I'm always searching for those elusive MM 'Stable' Roms I would like to try that rom, however, the above link has been disabled. If you could repost the link that would be excellent.
In the meantime I'll scrub the world wide web for this file, thanks
Bm6
Sent from my XT1527 using XDA-Developers mobile app
BillyMumphry said:
Hey @cmason37, thanks for posting this as I'm always searching for those elusive MM 'Stable' Roms I would like to try that rom, however, the above link has been disabled. If you could repost the link that would be excellent.
In the meantime I'll scrub the world wide web for this file, thanks
Bm6
Click to expand...
Click to collapse
It works just fine for me. Are you visiting the link on your phone, or PC?
I'm on my phone right now. Thanks I'll go sit at the PC and try.
Sent from my XT1527 using XDA-Developers mobile app
BillyMumphry said:
I'm on my phone right now. Thanks I'll go sit at the PC and try.
Sent from my XT1527 using XDA-Developers mobile app
Click to expand...
Click to collapse
btw I wouldn't recommend it, I was trying it and it's preatty buggy and outdated. It doesn't have fm radio and it's using only bottom microphone for video recording (stock 6.0 uses both mics so there is stereo effect). It also doesn't support any new custom kernels because it wasn't updated for ages. The worst thing is that it slows down a lot after few days and you need to reboot. On stock 6.0 with squid kernel the performance drop wasn't that big, I was using it for 30 days without reboot and it was still pretty good.
iks8 said:
btw I wouldn't recommend it, I was trying it and it's preatty buggy and outdated. It doesn't have fm radio and it's using only bottom microphone for video recording (stock 6.0 uses both mics so there is stereo effect). It also doesn't support any new custom kernels because it wasn't updated for ages. The worst thing is that it slows down a lot after few days and you need to reboot. On stock 6.0 with squid kernel the performance drop wasn't that big, I was using it for 30 days without reboot and it was still pretty good.
Click to expand...
Click to collapse
I don't have any of those problems, except for msybe fm radio but I don't give a crap about that. But, I can flash squid kernel & I don't get performance drops often. So it's literally bug free for me. Maybe you should try flashing it again. After all, bad flashes happen.
cmason37 said:
I don't have any of those problems, except for msybe fm radio but I don't give a crap about that. But, I can flash squid kernel & I don't get performance drops often. So it's literally bug free for me. Maybe you should try flashing it again. After all, bad flashes happen.
Click to expand...
Click to collapse
I tried it for three times always with the same resoult ;/ btw I don't own this phone anymore.
iks8 said:
I tried it for three times always with the same resoult ;/ btw I don't own this phone anymore.
Click to expand...
Click to collapse
My apologies you guys for not getting back earlier. I've been fumigating for bugs.
Those issues you were describing are the exact issues I'm dealing with today on my current ROM a popular CM based true to form option-heavy, stability-light ROM. This is a shame as its been fairly reliable platform for me. The occasional issue that was easily remedied with a reboot, a restore or a reflash. The past few months have been bug after bug for me. Mostly a pesky incompatibility issue with my ROM and OpenGapps.
Its seems all I've been doing lately is testing alternative gapp pkg sources, kernels and mods.
What makes this issue the real tops though is that the ROM I use was just listed as "Official" and "Stable" last month. There may be a weekly update waiting in the basket for me but the basket build server is down.
So....?
Not sure where to go from here. I'll tell you this much though. When I decided to try and root this device 8 months ago I had no idea it involved so much. I can almost write my own svripts, I'm understanding the bugreports I generate and read and i haven't spent this much time in a ToyBox since I was 9.
Lol. I'm not complaining though... I love to learn.
Oh and I still haven't tried the ROM you recommended as of yet. PC seems buggy now too.
iks8 said:
I tried it for three times always with the same resoult ;/ btw I don't own this phone anymore.
Click to expand...
Click to collapse
Sent from my XT1527 using XDA-Developers mobile app