yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] rozyid:
Good job... wait to fixed...
[Galaxy Ace II Android Development] shine911:
ok
[Galaxy Ace II Android Development] ziou1908:
oh sorry i mean mm-dd-yy form. so so sorry :P
[Galaxy Ace II Android Development] ichiyamato:
what ace 2 is for slim-3.1.0-20130806-UNOFFICIAL-codina.zip ? is it GT-I8160P or GT-I8160??
[Galaxy Ace II Android Development] shine911:
It for gt-i8160
[Galaxy Ace II Android Development] str3tch72:
Amazing rom, best! :D
[Galaxy Ace II Android Development] audi0fly:
Battery time is awesome :thumbup:
[Galaxy Ace II Android Development] unicornx:
NIce to see a new Rom. Iching to test it. Using stockMG2 (624Ram)..Is it possible for me to try it out?
[Galaxy Ace II Android Development] arpit85:
Yes, just follow the instructions properly.
[Galaxy Ace II Android Development] str3tch72:
I have internet issue. How I can disable it?
[Galaxy Ace II Android Development] shine911:
what problem do you have?

I uploading new version with changelog:

+ Fix Yahoo Lockscreen

+ Fix Layout

+ Update Holo Launcher

+ Disable Device Option

+ Removed Galaxy S2 Setting

+ Disable Automatic Backlight

+ Update TimeZone to 2013d

This is Alpha 1 I thinks it stable to wait a new CM 10
[Galaxy Ace II Android Development] str3tch72:
Mine network is on, but I don't have signal.
[Galaxy Ace II Android Development] shine911:
try turn off internet and reboot re-enable continue turn on you can not have signal but internet work fine :) i have this problem in cm 10
[Galaxy Ace II Android Development] unicornx:
I installed. Performance Improvement Big time

Bugs

Can't surf internet as can't add any APN profile (Tried many times but once the APN profile is saved, nothing appear to choose)

Prefer a better navigation screen because at times navigation screen blows away(I know its a tough ask)

Suggestions

Fix the Camcoder

Use a different file manager (can't Mark multiple files)
[Galaxy Ace II Android Development] shine911:
About camcoder i wait update from cm 10 and file manager i think you should download and install from playstore , and about APN i will check again and Navigation bar i also try enable again and try make it work thx for good idea

edit: i checked APN is add and show check box i checked this box and it work, can you share screenshot for me about APN profile :)
[Galaxy Ace II Android Development] carlospintod:
To make APN work, just turn on airplane mode and then turn it off.

---------- Post added at 01:54 PM ---------- Previous post was at 01:25 PM ----------

Does this ROM have all the features of a Slim Bean ROM? Pie control, gapps theme, etc?
[Galaxy Ace II Android Development] shine911:
Pie Control in 4.2.2 feature, my rom have all feature but not have some config as navigation bar. :)
[Galaxy Ace II Android Development] carlospintod:
Ok, so slim gapps work right?
[Galaxy Ace II Android Development] shine911:
Now slim gapp only support for 4.2.2 you can find in google but i don't known it work right, i recommend you using gapp from cyanogenmod

edit: @up release alpha 2 tester version
[Galaxy Ace II Android Development] carlospintod:
Ok, thanks.

One more question, when I get a notification, the capacitive buttons (back and menu) lit up and don't turn off until I open the notification.

How can I change that?
[Galaxy Ace II Android Development] tofueatsbread:
If im not wrong its BLN. But if your worried about battery life, a user said it doesn't even take 1% of your battery so no worries. The light up is part of cm.
[Galaxy Ace II Android Development] arpit85:
For alpha 2 tester version -

1. Settings f/c on -> developer options -> device information

2. Low volume fix (with stock camcorder giving f/c but saving video) isn't applied in this ROM
[Galaxy Ace II Android Development] shine911:
ok ok now i'm try build Carbon ROM should i not fixing bugs in my rom but it's mini bugs don't worry
[Galaxy Ace II Android Development] arpit85:
Yeah, I also don't care about these bugs, thanks for your hard work & nice ROM
[Galaxy Ace II Android Development] carlospintod:
Ok, but is there a way to turn that off?
[Galaxy Ace II Android Development] tofueatsbread:
Not sure... Someone posted a fix somewhere in slim bean 8.1 thread. Not sure if it works and if it does, not sure if it works on 4.1.2. (Somewhere in development forum not sure)
[Upgrading, Modifying and Unlocking] TCBVai:
I backuped the ROM to my image and who can tell me how to transfer it to nb.nbf file,please??
[Upgrading, Modifying and Unlocking] tumtum:
use ntrw.exe

you can search in this forum about that.

or see this link

http://xdaforums.com/viewtopic.php?t=17410&start=369
[Nexus 4 Q&A, Help & Troubleshooting] toge64:
Hi everyone

I flashed semaphore but would like to return to stock 4.3 kernel for further evaluation. Where can I download the stock 4.3 kernel which I can flash in twrp?

Thanks
[Nexus 4 Q&A, Help & Troubleshooting] faddyie:
For zip use google may be u càn find. Or if u can flash boot.img from factory image package after wiping cache and dalvik cache.

Always do a nandroid backup before flashing..
[Nexus 4 Q&A, Help & Troubleshooting] Sgace:
There are zips in the forums, try searching for them cause i don't know where exactly.
[Nexus 4 Q&A, Help & Troubleshooting] Mercado_Negro:
I looked around and I couldn't find a flashable version for you (maybe I didn't use the correct words in my search). Your best bet is the factory images where you can get it as a .img file and flash it via fastboot.
[Nexus 4 Q&A, Help & Troubleshooting] ELB27:
There you go: http://xdaforums.com/showthread.php?t=2381128

[KERNEL][4.3][JWR66V and JSS15J] Stock flashable 4.3 Kernel
[One (M7) Q&A, Help & Troubleshooting] XxCE0xX:
Why is there such a huge difference between the Rom ability. I know it's a different network code but isn't the One able to run both anyways? Why are some roms GSM only. When I had my Photon nothing like that mattered.
[One (M7) Q&A, Help & Troubleshooting] XxCE0xX:
Bump because seriously curious
[One (M7) Q&A, Help & Troubleshooting] CoryTallman:
As far as I know, almost all ones are the same, except for the sprint model. I believe the partitions are different on the sprint model, and flashing a ROM designed for anything else will not work.

AT&T HTC One

GPe 4.3
[Asus Transformer TF700] Nebrethar:
I am very new to the ROM scene. I have just recently done my second flash on a Transformer TF700t and I am completely stuck.

I flashed and it ran perfectly smoothly the first time around, except for the fact that i flashed in the wrong order and was left without gapps. I recovered to the stock ROM and tried again, this time in the correct order. I got a message that surprised and stumped me.

"Unable to locate zip file '/storage/emulated/0/goomanager/pa_tf700t-3.15-16APR2013-002620.zip'"

Anyone have any fixes or suggestions on how to remedy this? I will be actively working to solve.

Thanks,

Neb
[Asus Transformer TF700] Nebrethar:
UPDATE:

I wanted to see if it was a program/rom causing the problem.

I tried ROMManager with Cyanogen and it did the exact same thing with a separate directory.

Anyone have any suggestions?
[Asus Transformer TF700] _that:
You forgot to tell us which recovery you are using.
[Asus Transformer TF700] Nebrethar:
My apologies. I have been using twrp the entire time, and recovering off of that as well.
[Asus Transformer TF700] _that:
You forgot to tell us the version number of your recovery.

Try selecting your zip file manually with the recovery's "Install" command instead of using ROM Manager.
[Asus Transformer TF700] jt1998:
Are u saving it to an external SD card? If so Make sure its not formatted NTFS.
[Asus Transformer TF700] Nebrethar:
Thanks guys, been up for a couple hours now with a fresh mind and got it working.

I ended up just reinstalling a fresh stock JB and it seemed to download the OS fine.

Now I am running smooth and perfect on PA
[Android Q&A, Help & Troubleshooting] switchgott:
Hi,

I need your help.

Which kernel modules i have to compile to use a usb Ethernet adapter?

My one is a dm9601.

Source is inside android kernel.

I guess i have to activate inside

.config usb_net and dm9601.

Do i need other modules to get it work?

My problem is that the device wont get a ipv4 dhcp address.

The adapter is recognize vom android but i cant use it.

Any ideas?

This is an error i get:

unregistered net_device error 22

Please help,

Need it.

Big thanks

Gesendet von meinem GT-I9100 mit Tapatalk 2
[Nexus 7 Q&A, Help & Troubleshooting] TheOfficialBrownKid:
So first of all, sorry for being a total noob about this so please help me out.

I flashed Cyanogenmod 10.1.2 onto my Nexus 7 4.2.2 and everything was going fine. After all of that was done I installed Titanium Backup Pro and restored all my Apps including the data. When that finished, I was told to do a reboot for it to take effect, and so I did. But the problem is that it stays on the Cyanogen (splash screen/boot logo?). I have tried wiping the data (data, cache and dalvik cache), but it doesn't seem to work. Everything works well until I restore and reboot. :crying:

Help, Have I done anything wrong, or have I missed a step?
[Nexus 7 Q&A, Help & Troubleshooting] tebytorozo:
i have the exact problem, for some reason when i restore "missing apps + all system data" i cannot rebot my device, the only backup working forme right now is just restore all app, no data .
[Nexus 7 Q&A, Help & Troubleshooting] SlowCobra96:
You can't restore all information backed up across Roms. Only restore app data, use play store to reinstall all apps. This should resolve the problem.

Sent from my Nexus 7(2012) that has zero issues.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Martin1739:
Hi,

Thanks a lot for the great rom. I really appreciate it.

After flahing my second version (August 1)including full wipe I somehow managed to destroy cwm. I can still boot the OS as well as download mode but instead of CWM there is just a black screen. I also tried to flash a New CWM with rommanager and twrp with goomanager. It didn'change anything.

What can I do to get a working recovery if possible without full wipe again (too much work)? This way I'm unable to flash anything.

Martin
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] ThaiDai:
No need to open a thread for a already known problem that is discussed in the 10.2 thread in General.

If you install a very early experimental build you could at least read in the related thread. Or consider installing a Stock Rom.

And as other members you have to install a new Rom with PC Odin to eliminate the problem. I made this already two times - and now use an older 10.2-kernel as workaround.

But please use the thread in General for further postings related to CM10.2, ok?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Martin1739:
I'm sorry I was coming from CM 10, CM 10.1 and for a year or so I was no longer forced to care about such problems for quite a while. So I couldn't find the thread you linked. Xplowild closed his thread and I was a bit lost with so many threads.

Thanks for your help!

regards Martin
[Galaxy S III Q&A, Help & Troubleshooting] Bei60:
this issue is driving me crazy... no matter what i do i can't get good battery life with cm based roms.... no mater what i try: official, temasek, carbon, paranoid, all have **** battery life that barrely last a day.

i always end up going back to sammy based roms like wanamlite. byt i dont like it!

i greenify apps, disable gps, dormancy, startup apps, what else???

if it matters, i never change kernels..
[Galaxy S III Q&A, Help & Troubleshooting] boomboomer:
You aren't experiencing anything new, only Samsung based roms will get good battery life on the S3.
[Galaxy S III Q&A, Help & Troubleshooting] danarama:
Probably due to a lack of sources
[Galaxy S III Q&A, Help & Troubleshooting] Bei60:
what do you mean?
[Galaxy S III Q&A, Help & Troubleshooting] danarama:
Samsung don't release their exynos source code properly, so AOSP developers don't have all the information required to get similar performance out of all the hardware components
[Galaxy S III Q&A, Help & Troubleshooting] Bei60:
is there any aosp or aokp based rom that will provide good battery life?
[Galaxy S III Q&A, Help & Troubleshooting] danarama:
They're all about the same
[Galaxy S III Q&A, Help & Troubleshooting] Notor1ouS-:
they last the same for me with custom kernels.

i wont go back to sammy
[Galaxy S III Q&A, Help & Troubleshooting] voodoofox:
To me, any CM/AOSP and any kernel included or custom last about the same, and that is about 40% less then stock samsung rom.

Of course depending on situation...

However I won't be coming back to stock samsung rom any time soon :)
[Galaxy S III Q&A, Help & Troubleshooting] danarama:
Agreed, custom kernels help a lot but still not quite as much as stock. Similarly, im sticking with aosp
[Galaxy S III Q&A, Help & Troubleshooting] AthlonGFX:
Probably irrelevant but i tried the Illusion Rom and it gave me 1d 53h of normal usage whereas sammy barely gets me through the day

Just thought id mention it:p
[Galaxy S III Q&A, Help & Troubleshooting] danarama:
1 day + 4 days?
[Galaxy S III Q&A, Help & Troubleshooting] xclub_101:
You are confusing things here...

You are confusing things here - the lack of sources is somehow relevant to the kernel part, and generally the best kernels in regard to power consumption are the custom ones (like Perseus, Siyah and so on) - which are precisely started from the sources coming from Samsung.

The ROM part only talks to the kernel part, and once you have the same kernel (like Siyah) talking to both a CM ROM and a Sammy ROM and you get better power consumption in Sammy I don't really see how that can be related to "lack of sources".
[Galaxy S III Q&A, Help & Troubleshooting] AthlonGFX:
hahahaha sorry my bad:silly:

1d 13h
[Galaxy S III Q&A, Help & Troubleshooting] voodoofox:
Yeah sure, I even got on couple of occasion over 2 day and maybe 3-4hrs...

But however on stock with the the approximately same usage I would still have 30-40% more usage time.
[Galaxy S III Q&A, Help & Troubleshooting] danarama:
No im not confusing things - but you're over simplifying things. The kernel sources are complete. Siyah uses the samsung kernel sources as a base and it interacts with touchwiz roms perfectly. The same kernel does not interact with aosp roms in the same way.

Set up a touchwiz rom with basic settings and siyah kernel and compare it to aosp with the same basic settings and kernel and touchwiz will win hands down.

Samsungs kernel source may be complete but the exynos and hardware sources are incomplete. That's why an aosp rom camera is much lower quality than samsungs using the same hardware.

Also its worth noting that these dual purpose kernels are built from a mixture of samsung sources and Google sources. Otherwise they wouldn't be able to support 4.2.2 aosp roms...because 4.1 kernels are different to 4.2 kernels...hence no existing kernels can work on 4.2 sammy roms. We need their kernel sources for that, but they will come unlike complete exynos sources.

If you look at the snapdragon variants of the s3, the chipset is well documented so the developer community have much more scope to get comparable battery performance but this isn't an option for us. This is why the developer community here are so frustrated with samsung and the i9300 to the point where team hacksung decided they no longer wish to support cyanogen on exynos devices. We are unable to exploit the hardware to its full potential as we don't have what's required. Developers need to use a lot of guess work to get things working. Our s3 device tree for aosp roms is incomplete and this is samsungs fault for not being forthcoming with their non kernel sources
[Galaxy S III Q&A, Help & Troubleshooting] xclub_101:
You are still confused :(

That is completely irrelevant to what it was discussed - and is also false since for instance your own post is somehow trying to suggest that the AOSP camera works perfectly for non-Exynos S3 and works bad for Exynos S3 - once you get your time to check reality instead of propagating stuff you will see that is just another myth and that:

a) the AOSP camera is about as bad for BOTH CPUs

b) the information that is missing has nothing to do with the CPU from Samsung but instead with the camera itself.

And getting back to what this thread was about - POWER CONSUMPTION - the facts show that most CM ROMs have worse power consumption than most Sammy ROMs when both scenarios are run with the SAME KERNEL compiled from sources. A very remote point might be (maybe) made for device-drivers that are blobs (and where custom ioctls maybe are not documented) - but CPU / power management is not one of those! Debunking even further your childish talking point - with the same Sammy ROM the POWER CONSUMPTION is clearly better when running with one of those custom kernels then when running standard Samsung kernel - so any point that somehow any information relevant to power consumption is missing - when actually the custom open-source kernels are demonstrably better in this regard - now stands forever debunked :p
[Galaxy S III Q&A, Help & Troubleshooting] slaphead20:
Without the exynos source the cm kernels can't take full advantage of exynos power saving features..... Simple.

On another note, I suggest you tone down your attitude, and apologise for calling rootSU childish, and don't treat this place like somewhere you can come to wind people up or I will personally introduce you to the moderators :cool:
[Galaxy S III Q&A, Help & Troubleshooting] davtse:
I would just put him on ignore. It won't be the first time he's acting like an obnoxious know-it-all and it certainly won't be his last. For all his talk, I haven't seen him contribute anything remotely useful to any sort of development, just pointless ranting, raving and demanding.
[Galaxy S III Q&A, Help & Troubleshooting] danarama:
Well I've made the point I wanted to make. I wont be dragged in to a conflict about it. For everyone who is interested in my point of view, it's up there to read :)
[Galaxy S III Q&A, Help & Troubleshooting] xclub_101:
I think you are now getting a little delusional - I was already clearly pointing out that with the same kernel - exactly the same kernel - the cm ROMs get inferior results - a fact that was pointed out also by the starter of this thread and which clarifies that the problem is not necessarily in cm kernels.
[Galaxy S III Q&A, Help & Troubleshooting] slaphead20:
I think, along with many other people, I will just quietly add you to my ignore list.

In the dual boot kernel, depending on whether it's being used on cm or Sammy will alter how it is is interacting with the chipset. As rootSU said, those kernels use 2 sets of source.

Reading through your post history it becomes very apparent that you enjoy baiting people and are somewhat lacking in social skills, maybe these things should be addressed before you bury yourself any deeper.

And yes, I've heard the standard retort to that numerous times from numerous trolls......the thing is, you are bothered by what people think, your just to scared to admit it, to defensive to be nice.

One simple question.

Why do you enjoy winding people up and baiting them.

When you answer that you might make some progress
[Galaxy S III Q&A, Help & Troubleshooting] xclub_101:
Hmm ...

Except that your example has absolutely nothing to do with the topic discussed - which was power management!

No, that IS the childish point building on a longstanding myth promoted around here - regarding power management it does not seem to be anything that is "exclusive" - since of course a dual kernel like Siyah has all the info inside - it is there and at most cm just neglects it (as for instance they have been neglecting for 12 months that cm was writing in a sector on a file-system they were not recognizing - something that after almost 12 months only recently was fixed).

That being said - have you ever checked the kernel source code? Last time when I checked there were like 2 kernel modules that were different between the two paths and both are compiled from full source - one is the video driver and CM is choosing to use the newer version (but that is 100% a choice - the older one is also there), and another one might be the wireless driver - and again the CM path seems to have the newer one. Source code seems to be available for all 4 versions of the 2 modules (and actually a few other versions) - the path is drivers/media/video/samsung/ and drivers/net/wireless/.

Of course something is different - but regarding power management it is already all source code and no blob - so your point that "sources are missing" is false in regard to power consumption - it might be true in regard to other points (which I still doubt given the source in Siyah kernel) - but anyway that is a clear fallacy in regard to power management!

Again, this point proves that the power consumption problem is NOT from the lack of some "magic source".

Your point might (or might not) be correct in some general case - however in this very specific case where we were talking about power efficiency your point was demonstrably/experimentally wrong.

---------- Post added at 06:03 PM ---------- Previous post was at 05:57 PM ----------

That is simply not true - with dual-boot kernels there is a single kernel tree and anybody can check the source code and last time when I checked there were like 2 kernel modules that were different (and source code was available for all there - so absolutely certain that there was not some "magic source" missing from one path; see for more details my previous post).
[Galaxy S III Q&A, Help & Troubleshooting] danarama:
Please give us a play-by-play on this source code to prove your point.
[Galaxy S III Q&A, Help & Troubleshooting] xclub_101:
Hmm ...

1. In the future it might help to quote me if you want me to notice some reply.

2. Baby-steps teaching is not going to happen - but to get people started this should help:

https://github.com/gokhanmoral/ramfs-sgs3/blob/master/sbin/init

https://github.com/googyanas/Googy-Max-Kernel/blob/master/build_kernel.sh
[Galaxy S III Q&A, Help & Troubleshooting] danarama:
True, you can only "teach" baby steps if you yourself can walk.

I was expecting you to show evidence using source code that proved your ridiculous point that "only 2 modules" difference between the AOSP and Sammy aspect of a dual purpose kernel.

This is the commit used to turn Perseus into an AOSP compatible kernel. As you can see, there is a f**k load of code so even if there were only 2 modules, it is no minor difference

https://github.com/DerTeufel/androi...mmit/3c57b32a2930115423450564b293e7712c50b25e

246 changed files, 30,894 insertions.

The links you posted do nothing to show the actual differences between AOSP and Samsung from a source perspective.

Goodbye amigo! I've no more time for you