Running Folio 3x 0.4a
The ROM doesn't utilize all RAM as memory for android system
cat /proc/cmdline
mem=448M[AT}0M nvmem=128M[AT}384M vmalloc=256M XXXXXX
Is there any easy way to resolve it?
Hello folks! how are you doing?
Since we've seen Alpha kernel is still an alpha and we need to provide developers with every detail of our device we can.
I've decided to search through threads and get some commands from there to gather the information required:
You can gather these data by downloading Terminal Emulator from the market or by properly installing Google SDK and doing an adb shell then running the commands.
If commands do not seem to work at first glance, please reboot the phone then try again running the commands below.
Edit 1:
For all the people having problems not mentioned on the bug list, please report the problems in this spreadsheet
https://docs.google.com/spreadsheet/ccc?key=0AkQTVc3TvAUxdFNBOWFFRzNneWRHcW56MEtLVGJqdVE#gid=0
There are several sheets to fill with the mentioned problems
Edit 2:
For all users who might have problem gathering Tegra Revision, Speedo ID, CPU Process, Core Process; please install leaked rom / AtrICS, reboot and try searching again.
Else; please send me the dmesg command output via PM and I'll upload the results.
Please note that I'll discard dmesg from kernels that are not the leaked and/or 3.1
---
Identify Memory type:
Grab a terminal then run after a reboot
Code:
su -
dmesg | grep LPDDR2
Types of Memory
LPDDR2 MR5: 0x0003 (0x0303) = Elpida (Manufactuer)
LPDDR2 MR6: 0x0000 (0x0000) \
LPDDR2 MR7: 0x0000 (0x0000) / = 50nm
LPDDR2 MR8: 0x0054 (0x5454) = 1GB
LPDDR2 MR5: 0x0003 (0x0303) = Elpida (Manufactuer)
LPDDR2 MR6: 0x0001 (0x0101)\
LPDDR2 MR7: 0x0000 (0x0000)/ = 40nm
LPDDR2 MR8: 0x0054 (0x5454) = 1GB
LPDDR2 MR5: 0x0006 (0x0606) = Hynix (Manufacuter)
LPDDR2 MR6: 0x0000 (0x0000)\
LPDDR2 MR7: 0x0000 (0x0000)/ = 54nm (Note that this is still 54nm for MR7 = 0x0001 (0x0101))
LPDDR2 MR8: 0x0054 (0x5454) = 1GB
---
Identify which Panel Type do we have:
After a fresh reboot
Grab a terminal
Code:
su -
dmesg | grep atag
or
Code:
su -
dmesg | grep panel
Examples:
Code:
dmesg | grep atag
mot_parse_atag_motorola: panel type: 0x80000740
or
Code:
dmesg | grep panel
<6>[ 0.000000] parse_tag_motorola: panel_size: 0x740
---
Identify Tegra Revision:
Code:
su -
dmesg | grep Tegra
then search for something similar to
Code:
"Tegra Revision: AXX prime"
---
Well, let's see if we can help Atrix Kernel Team to improve the kernel with this useful information
Also, if anybody would like to contribute showing how to gather more data; that'd be awesome and I'll edit this post
Thanks guys, have a good day!
You are the man!!!....good work my friend...:good:
Thanks for this.
Thanks
This is super helpful. Now if I can just get my post count up high enough to post to dev forums....
Types of Memory
LPDDR2 MR5: 0x0003 (0x0303) = Elpida (Manufactuer)
LPDDR2 MR6: 0x0000 (0x0000) \
LPDDR2 MR7: 0x0000 (0x0000) / = 50nm
LPDDR2 MR8: 0x0054 (0x5454) = 1GB
Identify which Panel Type do we have:
dmesg | grep panel
<6>[ 0.000000] parse_tag_motorola: panel_size: 0x740
However, using command: "dmesg | grep Tegra" doesnt give me anything close to any revision information.
Seems like you ran dmesg a little too late. You need to run it as soon as possible upon bootup.
ravilov said:
Seems like you ran dmesg a little too late. You need to run it as soon as possible upon bootup.
Click to expand...
Click to collapse
Is it supposed to be a capital T in tegra? I rebooted several times and get the same stuff every time
I tried dmesg | grep revision
and got this:
CPU: ARMv7 Processor [411fc090] revision 0 (ARMv7), cr=10c53c7d.
vintage47 said:
Is it supposed to be a capital T in tegra? I rebooted several times and get the same stuff every time
Click to expand...
Click to collapse
No idea, but you can use grep -i Tegra, that should make capitalization irrelevant.
Solved, I was looking on dmesg from old kernel
--------------------------------------------------------------------------------------------------------------------------
Hello,
how I find the Tegra Revision, Speedo ID, CPU Process, Core Process that request Kristianp in my dmesg? I am stupid or it show diferent?
best regards,
Ferenc.
I cant find the tegra revision either. I can see the first thing in the log, but not the tegra revision.
Do after a fresh reboot in leaked kernel and Rom ( 10.1 epinter is mine)
Reboot when SD Card is present
Dear JhonnyX:
As I cannot write in the Google Docs Spreadsheet, please find the information from my Atrix Below. The Bug is the reboot when entering deep sleep with SD card inserted.
Sorry but I could not find my Atrix Revision on the early dmesg.
Best regards
Javier
ingelectronico said:
Dear JhonnyX:
As I cannot write in the Google Docs Spreadsheet, please find the information from my Atrix Below. The Bug is the reboot when entering deep sleep with SD card inserted.
Sorry but I could not find my Atrix Revision on the early dmesg.
Best regards
Javier
Click to expand...
Click to collapse
PM'ed you regarding the missing info
Also, users who might have spreadsheet access problem, please let me know via PM.
new fields
I want to add my info on the modem drops spreadsheet.
How do I find what values my phone has for these fields?
Speedo ID
CPU Process
Core Process
CPU governor
Connect the phone to usb and activate adb. Reboot. As soon as finished reboot, use adb shell and type dmesg > /mnt/sdcard/dmesg.txt
Now search that file.
This has been answered many tines before.
Next time use search
Enviado desde mi MB860 usando Tapatalk 2
How can i root simmtronics xpad mini
Specification :
Processor 1 GHz Quad Core
PLATFORM:
Operating System--Android 4.2.2 (Jelly Bean)
Sensors--3 Axle Load Sensors, G-Sensor
MEMORY:
RAM 1 GB DDR3
STORAGE
Internal Storage 8 GB
Expandable Storage Capacity 32 GB
DISPLAY
Display Type 7.85 inch HD Capacitive Touchscreen with 1024 x 768 pixels
Other Display Features IPS Display
Please Suggest me a process to root the phone ,Back up firmware ..
Any Questions about requirement of more specification/details of Device are welcome
CWM Port
Hi,
This tablet is already rooted just download SuperSU app from Play store.
I am porting custom recovery to Simmtronics XPad Mini but unfortunately I have not taken backup of stock recovery.
If anyone have the tablet, I just need you to run following command in android terminal and send me the recovery.img & boot.img files. Before running the command give root access to terminal through superSU app
Code:
su
dd if=/dev/block/nandg of=/sdcard/recovery.img
dd if=/dev/block/nandc of=/sdcard/boot.img
m.swastik said:
Hi,
This tablet is already rooted just download SuperSU app from Play store.
I am porting custom recovery to Simmtronics XPad Mini but unfortunately I have not taken backup of stock recovery.
If anyone have the tablet, I just need you to run following command in android terminal and send me the recovery.img & boot.img files. Before running the command give root access to terminal through superSU app
Code:
su
dd if=/dev/block/nandg of=/sdcard/recovery.img
dd if=/dev/block/nandc of=/sdcard/boot.img
Click to expand...
Click to collapse
Hey, maybe i can help i am not sure but still...I also own Simmtronics tablet but i own Simmtronics Xpad Freedom...It has the same specs as Simmtronics Xpad Mini..Only thing that Xpad Mini doesn't have is Sim Slots while with Xpad Freedom you have the ability to insert sim and call..Otherwise everything is same..Same screen res,same ram.....I have the boot.img and recovery.img file but it is extracted from Simmtronics Xpad Freedom not from Xpad Mini...If that be of some help to you i can upload it here..:good:
How can i root my oblio min 8x8i tablet ? The programs like "odin" does not see it ?
most of oblio tablets came pre-rooted, you must be have root permissions when write "su" in any terminal emulator I just researched but I cannot find it's chipset but cpu is cortex A8 so its must be a allwinner a10 so you can even boot arm linux from sd card most of oblio tablets(such as oblio mint plus 7 just google this magical words "sunxi linux")
kingoroot working usually
reinstalling factory image = use livesuit with proper .img file
installing roms @xda we have jelly bean and if you google for a10 devices you gonna see marshmallow even possible (psst some of roms need a little modifications)
final trick: changing boot screen(not bootanimation just logo)
1-)adb devices
2-)adb shell
3-)mkdir /sdcard/nanda
4-)mount -t vfat /dev/block/nanda > /sdcard/nanda
5-) exit
6-) adb push ./linux.bmp /sdcard/nanda/linux/linux.bmp
linux.bmp must be a 32bit depth bmp file original resolution 120x120(in my tablet) but 480x480 is fine
-----
ps = I know this is a very old topic but maybe someone in somewhere finds this info and maybe help
Hello guys, I have a problem with this box: the system partition was tempered with (they tried to remove root) and I want to flash a new rom to fix it.
I opened it to check the hardware but the manufacturer have shielded the wifi chipset so I can't read the numbers on it.
Dmesg says:
Code:
dhd_conf_set_chiprev: chip=0x4334, chiprev=3
And I found these files in etc/wifi/
p2p_supplicant_overlay.conf
wpa_supplicant.conf
Folder 40183
config.txt
fw_bcm40183b2.bin
fw_bcm40183b2_apsta.bin
fw_bcm40183b2_p2p.bin
fw_bcm4334b1_ag.bin
fw_bcm4334b1_ag_apsta.bin
fw_bcm4334b1_apsta.bin
fw_bcm4334b1_p2p.bin
nvram.txt
So it's a broadcom4334, right? Too bad I haven't found any rom that clearly states bcm 4334 or 40183 and s905x, except this
Full specification as read from the amazon page @ https://www.amazon.it/gp/product/B0788MX52X/
OS: Android 7.1.2
Bluetooth: 4.0
CPU: AmlogicS905X Quad Core Cortex A53 a 1.5 GHz 64 bit
GPU: Penta-core Mali-450MP
RAM: 2 GB DDR
ROM: 16 GB EMMC
Wifi: IEEE 802.11 a / b / g / n, Dual-Band 2.4G/5G
LAN: 10 / 100M, standard RJ-45
The Motherboard (Aida says it's p212) doesn't have an hidden button, unlike other boxes, but I can boot into recovery using a terminal emulator
Of course I tried reaching to goobangdoo but they haven't replied.
Edit: typos
Edit: updates
I want at least root the box, I found
deamonsu, su, su.bak in system/xbin
su in sbin
Rootchecker says root is not installed properly.
I have the UPDATE&BACKUP and I used it to install:
UPDATE-unSU-signed.zip > deletes nothing
SuperSU-v2.82-201705271822 > bad recovery error
Magisk-v16.0 > failed to find meta-inf/com/android/metadata in update package
Everything failed and I tried from recovery, same thing.
I can still return the box so I'm trying not to install twrp since I don't have the stock recovery.
I'm stuck.